New date issue on Android device

[Paul Lovegrove]

Hey there

Up until 2 days ago my Scheduler component was working fine. I had the timezone property set to Australia/Sydney. 

But as of 2 days ago on Android devices all dates are now 11 hours out. It appears to think dates are in UTC and apply a 11 hour offset for Australia. 

Any ideas? Im on the latest Scheduler version. 

[Nevitha Ravi]

Hi Paul, 

Greetings from Syncfusion Support. 

We have checked the reported timezone problem but we couldn’t replicate the problem at our end. Please find the below sample. 

https://stackblitz.com/edit/timezone-problem?file=index.ts  

If the issue persist still please share the below details. 

• Your system timezone
• Issue replicating scheduler code or sample

Regards, 

Nevitha 

[Paul Lovegrove]

Issue is still occurring on my android device using your code link below. See my attachment. No events are showing.

I am on a Samsung Galaxy Tab A. (android OS 7.1.1)

Chrome version: 88 ( latest)

Attachment: IMG_1019_b6a648d.zip

[Paul Lovegrove]

please refer to this https://stackblitz.com/edit/js-x1afvw?file=index.js ( go to Month view and you can see them on the first week of Feb.)

This shows correctly on Chrome 88 on windows 10, but not on Android (7.1.1) on Chrome v88 - no events show. 

[Balasubramanian Sattanathan]

Hi Paul, 

Thanks for the reply 

We have checked and tried to reproduce the reported problem in the below samples. But unfortunately, we were unable to reproduce it at our end. Since the appointments are rendered in the UI properly. 

Samples 

https://stackblitz.com/edit/js-x1afvw?file=index.js 

https://stackblitz.com/edit/timezone-problem?file=index.ts 

Here is the video demo that works as expected. 

https://www.syncfusion.com/downloads/support/forum/161767/ze/video685260919.zip 

Kindly share your system time-zone and clear replication steps to proceed further.  

Regards, 

Balasubramanian S 

[Paul Lovegrove]

My timezone is Australia/Sydney.

The issue is a bug with Chrome for Android and the use of the toLocaleString that Syncfusion are doing is causing this issue.

This is the ej2.js code, and you can see the toLocaleString call - 

  Timezone.prototype.offset = function (date, timezone) {

        var localOffset = date.getTimezoneOffset();

        try {

            var convertedDate = new Date(date.toLocaleString('en-US', { timeZone: timezone }));

            if (!isNaN(convertedDate.getTime())) {

                return ((date.getTime() - convertedDate.getTime()) / 60000) + localOffset;

            }

            return 0;

        }

        catch (error) {

            return 0;

        }

    };

Here is the Chrome bug logged with Chromium - https://bugs.chromium.org/p/chromium/issues/detail?id=1171671

Are you guys planning to fix?

[Balasubramanian Sattanathan]

Hi Paul, 

Thanks for the details. 

Currently, we are checking the reported problem at our end and will update the validation details on or before February 5, 2021. We would appreciate your valuable patience. 

Regards, 

Balasubramanian S

[Balasubramanian Sattanathan]

Hi Paul, 

Sorry for the late reply. 

We would suggest you to upgrade the Scheduler package to the latest one and check whether your reported problem has resolved or not. If the problem is not resolved, kindly share the issue replication steps with video demo to provide the solution at the earliest. 

Regards, 

Balasubramanian S