-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay New Entities Initialization #418
Comments
Hi @jleandroperez, Should this issue already be closed, since I'm not able to find the Regards Patrick |
@prvnl not sure what might have caused the nil simperiumKey error (this routine should assign a simperiumKey, if it was not set, at the moment of authentication). However, we've found out that disabling MOC hooks before auth might have side effects for developers who use a custom simperiumKey. We'll revert this merge for the time being, (+ thanks for the heads up!). |
@prvnl (by the way) this is the getter. Name fixed, thanks! |
…ization Implements delaysNewObjectsInitialization property
Note:Usage for the new property is as follows:
Thanks! |
As soon as Simperium is initialized, it begins listening to NSManagedObjectContext change notifications.
All of the inserted objects will get their simperiumKey assigned, even if the user is not logged in.
Let's provide a mechanism to delay the
simperiumKey
assignment: this way, developers will be able to pull objects from X service while Simperium is initialized, and provide agetSimperiumKeyFromLegacyKey
getter, which allows to set a custom simperiumKey.Props to @astralbodies for finding this issue (Thank you Aaron!).
The text was updated successfully, but these errors were encountered: