Replies: 5 comments 15 replies
-
Yes, can you post the code for when/how you are updating? Are you using the latest version. All saves to installation go synchronously to the Keychain, it seems like you might be saving on different threads, causing an issue somehow. I’m assuming you only have a few places where you are updating the installation. You can try to wrap to wrap those in a DispatchQueue.main.async closure to see if that fixes the issue. |
Beta Was this translation helpful? Give feedback.
-
If the save function is called asynchronously, I'm not sure I understand how dispatching to main will help?
|
Beta Was this translation helpful? Give feedback.
-
I released an update 3 days ago with ParseSwift 4.16.2 and still getting the same crashes. Here is all the code that saves the ParseInstallation (apologies for the messy code, I am self-taught and this app has been a work in progress over 7 years): Updating from objC in the AppDelegate (called from didFinishLaunchingWithOptions):
Registering for notifications:
Updating installation after making purchase with RevenueCat
After user logs in (adapted from SnapCat onboarding):
Updating the users home state and saving to installation:
|
Beta Was this translation helpful? Give feedback.
-
Ok this all makes sense. I'm pretty sure I followed an old Parse tutorial saving the User and Purchase info in the installation, but it makes sense not to do that. I will strip out all the extraneous updates and see if that resolves the crashes. Thanks so much for your help again! |
Beta Was this translation helpful? Give feedback.
-
For those running into this issue, #45 should address the problem. |
Beta Was this translation helpful? Give feedback.
-
I am getting a lot of crashes related to updating ParseInstallation.
crash.txt
crash2.txt
I can post code where I update the ParseInstallation but the crash reports don't seem to pinpoint the origin of the crashes.
Beta Was this translation helpful? Give feedback.
All reactions