JonnyBeeGod / nSuns-5-3-1-iOS-issues

Issue Tracking for nSuns 5/3/1 iOS app
33 stars 1 forks source link

Timer not working for iOS 13 #81

Closed Joe-Goodall closed 5 years ago

Joe-Goodall commented 5 years ago

Since upgrading to iOS 13 the timer seems to be cleared when the app is in the background.

Steps to reproduce:

  1. Start the rest timer.
  2. Navigate away from the app - I opened the clock and started the stopwatch and let it count up to just over 30 seconds.
  3. Navigate back to the app and the rest timer is now gone.

    • Device: iPhone Xs
    • OS: iOS 13.1
    • App Version: 1.11.2
JonnyBeeGod commented 5 years ago

I know, Apple has been taken it’s time reviewing my next update 😒 it will go live hopefully in the next days as soon as it’s approved with some cool stuff in it this time and should also fix the crashing timer issue. Cheers, Thanks for reporting

Von meinem iPad gesendet

Am 25.09.2019 um 20:15 schrieb Joe Goodall notifications@github.com:

 Since upgrading to iOS 13 the timer seems to be cleared when the app is in the background.

Steps to reproduce:

Start the rest timer. Navigate away from the app - I opened the clock and started the stopwatch and let it count up to just over 30 seconds. Navigate back to the app and the rest timer is now gone. Device: iPhone Xs OS: iOS 13.1 App Version: 1.11.2 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

JonnyBeeGod commented 5 years ago

Released the new app version yesterday. It would be great if you could report back if the problem still persists

Joe-Goodall commented 5 years ago

I can confirm the app updated overnight and the timer is now working as expected.

jfclark35 commented 5 years ago

I have still been experiencing this issue, though only on t2 or accessory sets. T1 works ok. The timer will disappear if I navigate away from the app or if my screen locks. Sometimes the timer will also just not appear.

I do 4 day if it matters.

Using IOS13 but I also noticed this happening before I updated from 12.