User Profile

Posts

Posts

Post not yet marked as solved
1 Replies
649 Views

iOS 15 app stuck at LaunchScreen

So I have noticed, and been getting reports from users, that since iOS 15 dropped my app seems to get stuck at the LaunchScreen. This only appears to happen when the app has been in the BG for an unknown amount of time and the user tries to FG the app. When it happens the user will see the LaunchScreen image and be stuck there. If the app is force closed and then reopened it operates normally. I have managed to replicate it once, by fluke, while attached to XCode. The console logs at that point seem to suggest the app is running normally, but can only see the LaunchScreen image. Has anyone else had this issue? I can't seem to find anything after looking around. It may be worth noting that I have never seen the app use the LaunchScreen when going BG to FG prior to iOS 15.
Posted
by sbrioux.
Last updated
.
Post marked as solved
1 Replies
622 Views

CLLocationManager.authorizationStatus() remembered after app deleted

It seems that recently on iOS 13 and XCode 11 I am seeing that the CLLocationManager.authorizationStatus().The reason I say this is because upon using breakpoints and such after deleting the app and reinstalling the app the status is authorizedAlways when I would expect it to be notDetermined like previous. Anyone else noticing this?It's posing some problems with the start up of my iOS application. Currently during our start up process we rely on a change in the authorization status to advance the application past a load up screen. Only way I could find to halt a user at a loading screen until the user has responded to the request for location services.Anyway.. is this an iOS bug or is it supposed to be a feature?
Posted
by sbrioux.
Last updated
.