Getting tons of reports that Overcast is crashing or getting killed in the background after about 30 seconds of playback on iOS 12.4.
Any other iOS devs hitting problems like this? Any ideas? It seems to have resulted from 12.4 itself, not any changes to my code in that time.
Energy logs aren’t helpful: the only entries I have are showing it getting killed for higher CPU usage than I think is possible in my code (e.g. 900% over 16 seconds), and the stack trace is all just _dispatch_workloop_invoke with no other context.
Do you have crashlogs from App Store connect? If Soringboard terminates your app, you typically get a message at the top of the crashlog indicating the issue. We had similar issues with CPU time exceeding limits. Maybe a missing beginBackgroundTask?
happening to me on @doppi_app, although it’s not super consistent. when reproducing with the debugger, it’s usually a crash on some random thread with not a lot of useful info. i thought it was my code ¯\_(ツ)_/¯
The only time I had the happen was a beta you pushed out a week ago. I had been listening to the watch and resumed playback on the phone. The only way to stop it was to quit the watch app from the dock.
I don’t have Overcast, but since updating to 12.4 Spotify has gone screwy and the MPNowPlayingInfoCenter keeps going out of sync and i can’t play music in any other app unless I force quit Spotify (even if it’s not playing anything) ... might not be related but worth mentioning
Running 12.4 on an iPhone 6 (I know...) and getting constant crashes. I first noticed it yesterday, but the problem fixed itself after a power cycle, and has worked fine ever since — until an hour ago. Suddenly it’s unusable.
Just happened to me in iOS 12.3.1 and overcast 2019.7.
The screen was locked (iPhone was in my pockets) and I was listening a podcast on my AirPods.
Overcast was not the last app I used before locking the screen (Twitter was).
The audio simply suddenly stopped.
The lock screen didn’t show any audio activity.
I had to unlock the screen and launch the app again to continue listening to the podcast (I had to hit the play button, too)