You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user later purchases an additional Mac and uses Migration Assistant to transfer data from the other Mac.
The user continues to use Simplenote on both Macs.
This results in two installations with the same value for SPUUIDKey. For me this caused sync issues such as notes sometimes getting "stuck" and no longer updating, and even the appearance of data loss as updating a note without realizing it had not synced changes from the other machine resulted in changes previously made on the other machine being discarded in the current revision.
This situation can be caused by any scenario that results in the Simplenote sandbox container being copied to another system. It's possible this an issue on iOS as well if a user sets up a new device with a backup of an old one and then continues to use the old device as well as the new one.
One potential solution is to store the preference using CFPreferencesSetValue(key, value, kCFPreferencesCurrentApplication, kCFPreferencesCurrentUser, kCFPreferencesCurrentHost). This stores the value in a machine-specific preferences domain such that if the container directory is copied to a different machine the value of UUID_KEY would be nil on the new machine.
The text was updated successfully, but these errors were encountered:
Problem scenario:
This results in two installations with the same value for SPUUIDKey. For me this caused sync issues such as notes sometimes getting "stuck" and no longer updating, and even the appearance of data loss as updating a note without realizing it had not synced changes from the other machine resulted in changes previously made on the other machine being discarded in the current revision.
This situation can be caused by any scenario that results in the Simplenote sandbox container being copied to another system. It's possible this an issue on iOS as well if a user sets up a new device with a backup of an old one and then continues to use the old device as well as the new one.
One potential solution is to store the preference using
CFPreferencesSetValue(key, value, kCFPreferencesCurrentApplication, kCFPreferencesCurrentUser, kCFPreferencesCurrentHost)
. This stores the value in a machine-specific preferences domain such that if the container directory is copied to a different machine the value of UUID_KEY would be nil on the new machine.The text was updated successfully, but these errors were encountered: