Chrome v88 (88.0.4324.93) for Android does not recognize date
See original GitHub issueDevice: Android phone (with Android v10) Browser: Chrome v88 (88.0.4324.93).
dayJs(‘2021-01-26T00:00:00Z’).tz(tz) returns “Invalid Date”. Started happening with Chrome upgrade v88.
dayJs(dateWithFormat).tz(tz) --> Works everywhere except Chrome88 on Android 10
dayJs.tz(dateWithFormat, tz) --> Works on Chrome 88 for Android 10.
Shouldn’t these methods return the same values irrespective of the browser or the underlying OS?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:20 (1 by maintainers)
Top Results From Across the Web
Chrome for Android Update - Chrome Releases
We've just released Chrome 88 (88.0.4324.93) for Android: it'll become available on Google Play over the next few weeks.
Read more >We are facing issue on Android mWeb Chrome/88.0.4324. js new ...
We are facing issue happen on Android mobile browser chrome/88.0.4324.93 or chrome/88.0.4324.141. Our customers are getting wrong date while run our ...
Read more >Chrome 88 brings better password protection and Incognito ...
Android Police · Chrome 88 brings better password protection and Incognito screenshots while sunsetting Flash (APK Download).
Read more >Google Chrome: Fast & Secure 88.0.4324.93 - APKMirror
Google Chrome: Fast & Secure 88.0.4324.93 APK Download by Google LLC ... Consult our handy FAQ to see which download is right for...
Read more >How to Update Chrome to the Latest Version - Google Chrome
If you haven't closed your browser in a while, you might see a pending update. If an update is pending, the icon will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I wrote this polyfill to fix this issue. It is really ugly, but it should work.
Notice: This code is only usable if you do not use “toLocaleString” anywhere, except dayjs. It just fix dayjs, but can break other code (if it use toLocaleString method).
Looks like chrome started to ignore locale in arguments ECMA-402