Home/ Questions/Q 8407281
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T23:19:04+00:00

What is the best approach to handle syncing when the user can choose to

  • 0

What is the best approach to handle syncing when the user can choose to enable or disable syncing whenever he wants?

Specifically I am currently having the problem that Simperium crashes after its instance have been deallocated. Consider the following scenario:

  1. Create database and insert some objects
  2. Create Simperium instance, sign in and sync all offline created objects
  3. Sign out (meaning releases the Simperium instance)
  4. Create some more objects

App now crashes with:

-[__NSCFString objectsShouldSync]: unrecognized selector sent to instance

where __NSCFString is some former object that already got released

I am using the current master branch.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is a common request, and the “iosupdate” branch has some changes that will help. You can see this GitHub issue for some guidance. To summarize (quoting the author of this question):

    When initializing the simperium instance set the following properties:

    self.simperium.authenticationOptional = YES;

    This make a cancel button appear.

    self.simperium.authenticationEnabled = NO;

    This prevents the authentication dialog from popping up.

    self.simperium.loginViewControllerClass = [LoginViewController class];
    This drops in a custom subclass of SPLoginViewController to overwrite the cancel: message, otherwise you would not get feedback that the user canceled the dialog.

    When the user hits a sign “Sign in” button, I set

    self.simperium.authenticationEnabled = YES;

    which causes the login controller to show up.

    • 0