You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see here that the allday option is checked before deciding to dynamically compute it. But if I check the analogous iOS code, it does not seem to make the same check. Is there a particular reason for this, or would you like a PR to fix this?
The text was updated successfully, but these errors were encountered:
theblang
changed the title
The allday option works on Android but not iOS
The allday option is not considered on iOS
Sep 27, 2019
@EddyVerbruggen I assume it would just be checking for that allday option being passed in explicitly, and only dynamically calculating if it isn't. That is what the Android Java code looks to be doing.
On a somewhat related side note, is the logic to calculate allday actually correct? I noticed when testing an event that spanned multiple days, but happened to start and end on the same day, that allday would be calculated to true, and thus the time information would get messed up.
I see here that the
allday
option is checked before deciding to dynamically compute it. But if I check the analogous iOS code, it does not seem to make the same check. Is there a particular reason for this, or would you like a PR to fix this?The text was updated successfully, but these errors were encountered: