-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outlook showing wrong time for events on mobile #21
Comments
I guess it has something in common with force-setting time to have UTC timezone in
|
We are also experiencing the same issue. Haven't figured out how to fix this for mobile. Any suggestions or work arounds are welcome! |
Same issue here! |
Seeing this too. The test event shows 12pm -> 12:30pm on mobile instead of 6:30am -> 9:30am This appears to be a bug with Outlook mobile. You can reproduce on desktop by resizing the browser window down and reloading. |
Same issue here! , anyone found a solution? |
This still happening, outlook desktop and web will pick up the right time , but for mobile devices wont |
This seems to be resolved by Microsoft. |
cool, closing the issue then 👍 |
Using this example link: https://outlook.live.com/calendar/0/deeplink/compose?path=/calendar/action/compose&rru=addevent&startdt=2020-12-31T19:30:00Z&enddt=2020-12-31T22:30:00Z&subject=Birthday&body=With%20clowns%20and%20stuff&location=North%20Pole
Will show correctly on desktop but using the same link in iOS (but I'm told this also is a problem on Android) will fail to pick up the correct times. I've tried manipulating the time format in many different ways to get it to pick up without luck.
If I try an event that spams multiple days, using an example like this: https://outlook.live.com/calendar/0/deeplink/compose?startdt=2020-08-12T00:00:00&enddt=2020-08-13T12:00:00&subject=Hello%20World&body=Hello%20World
The end time is correct but the start time is still wrong. From what I can gather it appears to be rounding up to the nearest hour for the start time.
Wondering if anyone else can reproduce this and/or has figured out a workaround for this to work on mobile.
The text was updated successfully, but these errors were encountered: