User defaults are getting cleared on relaunching the app after long time

user_14908125 0
Viewed 1381

I have an iOS app where we can login and I'm using user defaults to store data like "firstLogin", "freshInstall", "userName", "sessionTime", etc. I am getting a problem where killing the app(double click on home and swipe up on the app to remove it) and relaunching it after a long time(after about 6hrs) is clearing all the userDefaults I'm setting and the app is opening in fresh install screen. It should actually open in logged in state.

I am using synchronize to properly save the userDefaults.

I don't have any code to explicitly delete the userDefault key-values or clear them. I have a few third party frameworks but I'm not sure how to check if those are causing this issue. How do I know where this problem is coming from? Is there any case where userDefaults gets cleared like that automatically?

The launch screen is determined based on the variable "isLaunchScreenShown" which is being saved in [NSUserDefaults standardUserDefaults]. After 1st install and launch screen is shown, the variable is set as true. When app is uninstalled, the UserDefaults are cleared. But in my case now, the UserDefaults' value for "isLaunchScreenShown" is returning null indicating that it is not set even though it is not the 1st launch after install.

nsuserdefaults objective-c ios
2 Answers
user_169735360

This is related to the new prewarming feature Apple introduced with iOS 15.

https://developer.apple.com/documentation/uikit/app_and_environment/responding_to_the_launch_of_your_app/about_the_app_launch_sequence

It's not supposed to get as far as didFinishLaunching, but one commenter on the dev forums said that it does with their information coming from Apple directly.

Could be a bug. Could be intentional. There are some reports that this has been fixed in 15.4, however it's impossible to confirm because there's no way to know when a prewarm occurs.

Why UserDefaults and Keychain?

Generally prewarming can happen when the device is locked. If it's locked then access to the keychain or user defaults is blocked. So when you check for a boolean value, it will return false... because it can't be found.

Solution?

Don't use UserDefaults. Write to a different file instead.

It would be great if this feature was opt-in, or at the very least opt-out. It's a poorly implemented feature to be sure, and I'm sure has possibly caused thousands of dollars worth of damage at this point.

user_21144820
Related