Forcing UTC for setTime() causes a number of problems for devices with a timezone that's not GMT+0:
Timestamps entered have to be created from a "time at UTC" rather than a real timestamp created from Date(), Calendar, or elsewhere, otherwise the time will be off by X hours
isAmTime() uses the device time zone, so even if we create a timestamp outside the module from "5pm UTC" it may automatically select AM if "5PM UTC" is an AM time in the device timezone.
Both of these issues are resolved by removing the UTC timezone set.
Forcing UTC for setTime() causes a number of problems for devices with a timezone that's not GMT+0:
isAmTime()uses the device time zone, so even if we create a timestamp outside the module from "5pm UTC" it may automatically select AM if "5PM UTC" is an AM time in the device timezone.Both of these issues are resolved by removing the UTC timezone set.