Cannot change end time

[RogerTX66]

New events have a default 1 hour time span. When I try to set a different end time I get the date/time chooser wheels, but my changes are not saved and I always end up with events that last 1 hour. If I go into native calendar app then I can change the end date/time. I have a lot of events that only last 30 min so this is a major inconvenience for me to have to not be able to set the correct end time.

[HairyJohn]

Hi Roger!
This is a bit strange, I've just created a new event lasting 30 minutes and it worked fine for me. I then edited it to last 35 minutes and that worked fine for me too.

Could you try the following for me:
Go into myCal, and tap the Info button (top right)
Scroll to the bottom section and set Enable Logging to ON
Close the Info screen
Add an event called Test123 for a 30 minute duration
Edit that event and set it to 1 hour 30 minutes long
Go back into the Info screen
Scroll to the bottom section and tap Email log data to support

I'll take a look at the log as soon as it comes into the support email box.

Thanks!
John

[RogerTX66]

Hi John,

Well, of course, today it's working just fine for me. I tried editing existing events and creating a new event and in all cases I was able to adjust the end time just fine. Let me keep playing around and see if I can reproduce it and I'll send you a log.

Roger

[RogerTX66]

Hi John,

I was able to reproduce and have sent you a log. Earlier I was not able to reproduce, but after scrolling around some in week and month view and then trying to create a new event I could not initially change the end time, but if I changed the start time then I was able to change the end time. I'm pretty sure the other day I could not change the end time even if I changed the start time, but hopefully this current log will give you enough data to chase down the problem.

Roger

[HairyJohn]

Hi Roger!

Thank you for the log file, interesting! I'll try and chase it down now and replicate it.

Regards
John

[HairyJohn]

Just a quick update to this, with Roger's help I was ale to replicate the problem and it was due to differences between UTC and his local timezone. The bug he found is fixed in the latest release, 1.5.1, which is available to download now in the AppStore.

My thanks to Roger for his help on this!

Cheers
John