An error occurs on write when the item already exists, when it should just be replaced

[mattbodley]

We are facing an issue of:

PlatformException(Unexpected security result code, Code: -25299, Message: The specified item already exists in the keychain., -25299, null)

Which is strange because it should just be updated as normal. It works fine in tests and manual tests but I just found this in crashlytics for iOS.

This occurs via:

 await _storage.write(
          key: LocalSecureStorageBase.itemKey, value: itemValue);

Settings are:

    IOSOptions getIOSOptions() =>
        const IOSOptions(accessibility: KeychainAccessibility.first_unlock_this_device);
    _storage = FlutterSecureStorage(
        aOptions: getAndroidOptions(), iOptions: getIOSOptions());

It is strange as it is just on iOS (for the moment) and there doesn't seem to be any other reports of this happening.

We are using flutter_secure_storage version 9.2.2

[jerrypaulsam]

Same here

[rokk4]

We are also observing this in our sentry.

[acacioveit]

same here, any workaround for now?

[acike]

same here

[acike]

I found a workaround:

For example, if you store data using different options:

1. static const _storage2 = FlutterSecureStorage();
2. static const _storage = FlutterSecureStorage(iOptions: IOSOptions(accessibility: KeychainAccessibility.unlocked_this_device));

If you initially store data with _storage2, you need to call deleteAll on _storage2 before you can write to another storage instance like _storage.

need someone to help me clarify this when writing data with different options I'm still confused because it seems that both storages use the same location (so you cannot write the existing key even if _storage is initialized first) . However, when I try to read from both in the next execution, I find that _storage2 has no data left after calling deleteAll, while _storage still retains its data as expected. This makes me think that the storages are not actually in the same location. So the question is I need to know when store data using different options will be stored at the same location or not?

[azack]

It looks like there was a lot of important related discussion in issue #711, and #751 was merged to fix this issue. Can we get a new release that includes that fix, @juliansteenbakker ?

[anisalibegic]

Is there any update on this topic @juliansteenbakker?