Why does Day.js return ‘Invalid Date’ for API date strings with timezone offsets in iOS 15 (mPaaS)?
I’m working on a project using the Mini Program mPaaS framework by Alibaba Cloud, and I’m encountering an issue with date parsing in JavaScript. Specifically, on iOS 15, my date strings (e.g., “2025-01-10 00:00:00.000+0700”) return “Invalid Date”. I suspect this is due to stricter parsing rules in the WebKit engine used by the mini-program environment. Here’s my code…
Why does Day.js return ‘Invalid Date’ for API date strings with timezone offsets in iOS 15 (mPaaS)?
I’m working on a project using the Mini Program mPaaS framework by Alibaba Cloud, and I’m encountering an issue with date parsing in JavaScript. Specifically, on iOS 15, my date strings (e.g., “2025-01-10 00:00:00.000+0700”) return “Invalid Date”. I suspect this is due to stricter parsing rules in the WebKit engine used by the mini-program environment. Here’s my code…
Why does Day.js return ‘Invalid Date’ for API date strings with timezone offsets in iOS 15 (mPaaS)?
I’m working on a project using the Mini Program mPaaS framework by Alibaba Cloud, and I’m encountering an issue with date parsing in JavaScript. Specifically, on iOS 15, my date strings (e.g., “2025-01-10 00:00:00.000+0700”) return “Invalid Date”. I suspect this is due to stricter parsing rules in the WebKit engine used by the mini-program environment. Here’s my code…
Why does Day.js return ‘Invalid Date’ for API date strings with timezone offsets in iOS 15 (mPaaS)?
I’m working on a project using the Mini Program mPaaS framework by Alibaba Cloud, and I’m encountering an issue with date parsing in JavaScript. Specifically, on iOS 15, my date strings (e.g., “2025-01-10 00:00:00.000+0700”) return “Invalid Date”. I suspect this is due to stricter parsing rules in the WebKit engine used by the mini-program environment. Here’s my code…