The specified item could not be found in the keychain

Question

The specified item could not be found in the keychain

Closed this issue 6 months ago · 51 comments

gianlucainnocente commented 7 months ago

Hello,
after yesterday's update (9.1.1) we are encountering this error when trying to read secure storage only on ios:

Unhandled Exception: PlatformException(Unexpected security result code, Code: -25300, Message: The specified item could not be found in the keychain., -25300, null)

How can we solve that?
Thank you

Answer 1 · 2024-05-09T09:02:29.000Z

Same here, data from the keychain can not be read.

Answer 2 · 2024-05-09T09:36:11.000Z

Same here.

Answer 3 · 2024-05-09T12:30:22.000Z

Same here, what's the solution?

Answer 4 · 2024-05-09T13:21:36.000Z

Same here with the last version 9.1.1, and If I back to the previous version the problem is not solved, and now I can't run the app

Answer 5 · 2024-05-09T13:46:09.000Z

and If I back to the previous version the problem is not solved, and now I can't run the app

Huh? Just revert your pubspec.lock to the previous state. That will fix it.

Answer 6 · 2024-05-09T13:46:55.000Z

Same here, what's the solution?

Don't upgrade.

Answer 7 · 2024-05-09T15:52:03.000Z

Same here. Fixed my version to: flutter_secure_storage: 9.0.0.

Answer 8 · 2024-05-09T18:24:52.000Z

Submitted a fix for this in #710.

Looks like the platform function readAll was updated to check for empty keys, but read wasn't. Until my fix is tested and merged, the best bet would be to pin an earlier version.

Answer 9 · 2024-05-09T18:40:34.000Z

For those who get here and need a temporary workaround for version 9.1.1, read is the problem, readAll works fine. You just need to do the key lookup yourself:

final secureStore = const FlutterSecureStorage();

// Not working in 9.1.1
final key = await secureStore.read(key: "some_key"); 

// Workaround -- `key` will be `null` if not present
final key = (await secureStore.readAll())["some_key"];

Answer 10 · 2024-05-09T21:44:52.000Z

For those who get here and need a temporary workaround for version 9.1.1, read is the problem, readAll works fine. You just need to do the key lookup yourself:
final secureStore = const FlutterSecureStorage();

// Not working in 9.1.1
final key = await secureStore.read(key: "some_key"); 

// Workaround -- `key` will be `null` if not present
final key = (await secureStore.readAll())["some_key"];

This works fine for now, Thank you

Answer 11 · 2024-05-10T04:09:07.000Z

Same here, what's the solution?

Don't upgrade.

now i have flutter_secure_storage: ^9.0.0, but still showing same error

Answer 12 · 2024-05-10T04:12:00.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

Answer 13 · 2024-05-10T04:24:50.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

Answer 14 · 2024-05-10T04:42:03.000Z

How i can fix it?

Answer 15 · 2024-05-10T06:15:35.000Z

For those who get here and need a temporary workaround for version 9.1.1, read is the problem, readAll works fine. You just need to do the key lookup yourself:
final secureStore = const FlutterSecureStorage();

// Not working in 9.1.1
final key = await secureStore.read(key: "some_key"); 

// Workaround -- `key` will be `null` if not present
final key = (await secureStore.readAll())["some_key"];

what about secureStore.delete?
i got same problem when i delete.

Answer 16 · 2024-05-10T06:22:08.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

Answer 17 · 2024-05-10T06:38:59.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

is it possible like this ?
final key = (await secureStore.deleteAll())["some_key"];

Answer 18 · 2024-05-10T06:43:16.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

is it possible like this ? final key = (await secureStore.deleteAll())["some_key"];

Only if you are okay with deleting all keys. deleteAll deletes all keys you have stored, and doesn't return anything, so you wouldn't need the ["some_key"] part.

Answer 19 · 2024-05-10T06:51:14.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

is it possible like this ? final key = (await secureStore.deleteAll())["some_key"];

Only if you are okay with deleting all keys. deleteAll deletes all keys you have stored, and doesn't return anything, so you wouldn't need the ["some_key"] part.

But i need to delete the Keys separately.

Answer 20 · 2024-05-10T06:53:10.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

is it possible like this ? final key = (await secureStore.deleteAll())["some_key"];

Only if you are okay with deleting all keys. deleteAll deletes all keys you have stored, and doesn't return anything, so you wouldn't need the ["some_key"] part.

But i need to delete separately.

Then I suggest pinning the version of this package to 9.0.0 or earlier, until it works for you without errors.

Answer 21 · 2024-05-10T06:56:22.000Z

@dilshd specify the version: flutter_secure_storage: 9.0.0

i did, but still same.

You might need to do a flutter clean and rebuild so the downgrade actually happens. As far as the delete method, I am unsure. It's entirely possible that method is bugged as well, in which case the package maintainer can hopefully weigh in with a workaround and/or a fix.

is it possible like this ? final key = (await secureStore.deleteAll())["some_key"];

Only if you are okay with deleting all keys. deleteAll deletes all keys you have stored, and doesn't return anything, so you wouldn't need the ["some_key"] part.

But i need to delete separately.

Then I suggest pinning the version of this package to 9.0.0 or earlier, until it works for you without errors.

i changed to 9.0.0 in pubspec.lock & pubspec.yaml, But the error still showing down.

Answer 22 · 2024-05-10T06:58:13.000Z

@dilshd delete pubspec.lock, run flutter clean, then run flutter pub get and then rebuild the project

Answer 23 · 2024-05-10T07:05:23.000Z

@dilshd delete pubspec.lock, run flutter clean, then run flutter pub get and then rebuild the project

It works, thanks.

Answer 24 · 2024-05-10T10:47:42.000Z

In macOS, I had to pin also the flutter_secure_storage_macos package in pubspec.yaml

dependency_overrides:
  flutter_secure_storage: 9.1.1
  flutter_secure_storage_macos: 3.0.1

Answer 25 · 2024-05-10T13:41:13.000Z

In macOS, I had to pin also the flutter_secure_storage_macos package in pubspec.yaml
dependency_overrides:
  flutter_secure_storage: 9.1.1
  flutter_secure_storage_macos: 3.0.1

More like

dependency_overrides:
  # temporary fix for https://github.com/mogol/flutter_secure_storage/issues/709
  flutter_secure_storage: 9.0.0
  flutter_secure_storage_linux: 1.2.0
  flutter_secure_storage_macos: 3.0.1
  flutter_secure_storage_platform_interface: 1.0.2
  flutter_secure_storage_windows: 3.0.0
  flutter_secure_storage_web:  1.2.0

Answer 26 · 2024-05-11T22:29:40.000Z

write도 마찬가지인데 해결 하려면 어떻게 해야돼??

Answer 27 · 2024-05-12T22:05:59.000Z

The roll back to 9.0.0 worked great after flutter clean. Is there a way to follow the issue on Github so I can update the package once a fix is released?

Answer 28 · 2024-05-13T05:34:32.000Z

Does the OS use cache internally when using Keychain? There is no problem when I access the Key value already in use before the package update, but when I read it again after calling the remove method, a problem occurs.

Answer 29 · 2024-05-13T06:42:02.000Z

Hi all, i am reviewing #710 and will release a fix later today

Answer 30 · 2024-05-13T12:21:57.000Z

Thanks @juliansteenbakker. Looking forward to the fix. Rolling back to 9.0.0 fixed the issue for me

Answer 31 · 2024-05-14T08:46:57.000Z

I'm on 9.0.0 and getting the same error. I did this: delete pubspec.lock, run flutter clean, then run flutter pub get and then rebuild the project - still an issue.

Why would this all of a sudden become an issue, I did not upgrade to 9.1.1?

I had to use readAll() to get the app out.

Answer 32 · 2024-05-14T13:07:30.000Z

Getting the same error, I'm already on version 9.0.0 and I did not upgrade to version 9.1.1

Answer 33 · 2024-05-14T13:22:19.000Z

The roll back to 9.0.0 worked great after flutter clean. Is there a way to follow the issue on Github so I can update the package once a fix is released?

Top Right - Notifications - Subscribe

Answer 34 · 2024-05-14T15:56:48.000Z

This is an odd problem. I'm in 9.0.0 since months and didn't do the upgrade and now I've the error only on the simulator.

I just changed my macbook yesterday so is it really this lib problem ?

ps : workaround seems to be working.

Answer 35 · 2024-05-15T10:57:04.000Z

For those who get here and need a temporary workaround for version 9.1.1, read is the problem, readAll works fine. You just need to do the key lookup yourself:
final secureStore = const FlutterSecureStorage();

// Not working in 9.1.1
final key = await secureStore.read(key: "some_key"); 

// Workaround -- `key` will be `null` if not present
final key = (await secureStore.readAll())["some_key"];
what about secureStore.delete? i got same problem when i delete.

it works for me:

    if (await _secureStorage.containsKey(key: _accessTokenKey)) {
      await _secureStorage.delete(key: _accessTokenKey);
    }

Answer 36 · 2024-05-15T14:52:44.000Z

Seems like the issue is fixed with the latest version (9.2.0)

Answer 37 · 2024-05-15T15:07:12.000Z

Seems like the issue is fixed with the latest version (9.2.0)

I still experience this error after upgrading to

flutter_secure_storage: 9.2.0
flutter_secure_storage_macos: 3.1.0
flutter_secure_storage_platform_interface: 1.1.2

After restarting the secure storage is empty.

await secureStorage.readAll();

returns an empty Map.

If I downgrade back to

flutter_secure_storage: 9.0.0
flutter_secure_storage_macos: 3.0.1
flutter_secure_storage_platform_interface: 1.0.2

await secureStorage.readAll();

returns a Map with all my data.

CC / @juliansteenbakker @ztaylor54

Answer 38 · 2024-05-15T17:47:22.000Z

@techouse I am unable to reproduce this behavior, can you please provide more detail? It would also be a good idea to run a flutter clean and fully rebuild.

@juliansteenbakker I did however notice in my testing that the macOS implementation crashes when the key does not exist, which can be fixed in the same manner as my PR for iOS.

Answer 39 · 2024-05-16T08:03:14.000Z

It seems that the sub-dependencies are not updated (eg: for macOS).
The last version was 7 days ago.

Answer 40 · 2024-05-16T08:10:13.000Z

It seems that the sub-dependencies are not updated (eg: for macOS). The last version was 7 days ago.

The macOS implementation was never updated to match the iOS behaviour. I have updated this just now and am releasing this asap.

Answer 41 · 2024-05-16T08:15:49.000Z

I have released v9.2.1 with these fixes.

Answer 42 · 2024-05-16T09:55:30.000Z

@techouse I am unable to reproduce this behavior, can you please provide more detail? It would also be a good idea to run a flutter clean and fully rebuild.

Hey @ztaylor54 I cleaned it and updated the pods. I'm still having the same problem with v9.2.1.

I did some tests and it looks like using v9.2.1 await secureStorage.readAll() returns an empty Map {}, however, await secureStorage.read(key: 'someKeyName') returns that key's value.

My setup:

OS: iOS v17.4.1
Physical Device: iPhone 13 Pro
Flutter ver: 3.19.6

The keychain was populated with:

flutter_secure_storage: 9.0.0
flutter_secure_storage_macos: 3.0.1
flutter_secure_storage_platform_interface: 1.0.2

I used this simple Dart test code.

final Map<String, String> secureData = await secureStorage.readAll();
print('is secureData empty: ${secureData.isEmpty}');
// call readAll again explicitly
print('stored username via readAll: ${(await secureStorage.readAll())['username']}');
print('stored username via read: ${await secureStorage.read(key: 'username')}');

Using v9.0.0

flutter_secure_storage: 9.0.0
flutter_secure_storage_macos: 3.0.1
flutter_secure_storage_platform_interface: 1.0.2

I get

flutter: is secureData empty: false
flutter: stored username via readAll: foo@bar.baz
flutter: stored username via read: foo@bar.baz

Using v9.2.1

flutter_secure_storage: 9.2.1
flutter_secure_storage_macos: 3.1.1
flutter_secure_storage_platform_interface: 1.1.2

I get

flutter: is secureData empty: true
flutter: stored username via readAll: null
flutter: stored username via read: foo@bar.baz

CC / @juliansteenbakker

Answer 43 · 2024-05-20T13:47:42.000Z

@juliansteenbakker @ztaylor54 I submitted a PR #719 fixing the issue in the comment above

iOS

It seems that somehow the accessibility for readAll was explicitly (possibly deliberately?) set to nil https://github.com/mogol/flutter_secure_storage/blob/eaccd9fb88effab9d3274c51cc91a3bc5886d8fd/flutter_secure_storage/ios/Classes/FlutterSecureStorage.swift#L75 which is not the case for read https://github.com/mogol/flutter_secure_storage/blob/eaccd9fb88effab9d3274c51cc91a3bc5886d8fd/flutter_secure_storage/ios/Classes/FlutterSecureStorage.swift#L105
macOS

The same is true for the macOS package's readAll
https://github.com/mogol/flutter_secure_storage/blob/eaccd9fb88effab9d3274c51cc91a3bc5886d8fd/flutter_secure_storage_macos/macos/Classes/FlutterSecureStorage.swift#L78 vs read https://github.com/mogol/flutter_secure_storage/blob/eaccd9fb88effab9d3274c51cc91a3bc5886d8fd/flutter_secure_storage_macos/macos/Classes/FlutterSecureStorage.swift#L108

If anyone wants to play around with the PR directly you can reference it like this in your pubspec.yaml

dependencies:
  flutter_secure_storage: ^9.2.1

dependency_overrides:
  flutter_secure_storage:
    git:
      url: https://github.com/techouse/flutter_secure_storage.git
      ref: fix/read-all
      path: flutter_secure_storage
  flutter_secure_storage_macos:
    git:
      url: https://github.com/techouse/flutter_secure_storage.git
      ref: fix/read-all
      path: flutter_secure_storage_macos

Answer 44 · 2024-05-28T17:26:18.000Z

I noticed that this also happens when you first do the command:
await SecureStorage.cleanString();
It is not being executed within the function where the new token is captured.
Before my command was directly in OnPressed, when placing it directly in the login() function on the first line this error disappeared.
Future<void> login(Map<String, dynamic> login) async { String url = '/auth/login'; isLoading = true.obs; await SecureStorage.cleanString(); try { dio.Response response = await _customDio.dio.post(url, data: login); (...)

Answer 45 · 2024-05-28T17:34:48.000Z

I noticed that this also happens when you first do the command: await SecureStorage.cleanString();

I must be blind, but I can't find any mention of a cleanString() method anywhere in the codebase.

Answer 46 · 2024-06-11T13:00:15.000Z

FYI, I've experienced this issue writing a string via _storage.write(key: key, value: value); with the latest version 9.2.2.

Answer 47 · 2024-06-19T03:54:34.000Z

this issue still with the latest version 9.2.2 when writing secureStorage.write( key: key, value: value,
aOptions: AndroidOptions( encryptedSharedPreferences: true ),
iOptions: IOSOptions(accessibility: KeychainAccessibility.unlocked_this_device));

Answer 48 · 2024-06-30T13:40:21.000Z

Yes we are hit by this issue too, version 9.2.2.

Answer 49 · 2024-06-30T14:29:14.000Z

in our case issue occurred the first time FlutterSecureStorage.write was called. We now must better debug, coz it could happen again.

[ERROR: flutter/runtime/dart_vm_initializer.ce(41)] Unhandled Exception: PlatformException(Unexpected security result code, Code: -25300, Message: The sp ecified item could not be found in the keychain., -25300, null)
#0
StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:648)
#1
MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:334)
‹asynchronous suspension>
#2 FlutterSecureStorage.write (package:flutter_secure_storage/flutter_secure_storage.dart:114)
‹asynchronous suspension>

Answer 50 · 2024-07-18T13:33:16.000Z

I am also facing this for some of our users not all on 9.2.2. Anyone why it's happening? And also it is happening for some keys not all.

Answer 51 · 2024-07-19T13:46:23.000Z

A workaround solution:

import 'package:flutter_secure_storage/flutter_secure_storage.dart';
import 'package:synchronized/synchronized.dart';

class AuthCache {

  static const _accessTokenKey = "ACCESS_TOKEN_KEY";

  final FlutterSecureStorage _secureStorage;

  final _accessTokenLock = Lock();

  AuthCache._()
      : _secureStorage = const FlutterSecureStorage(
    aOptions: AndroidOptions(
      encryptedSharedPreferences: true,
    ),
  );

  Future<void> setAccessToken(String accessToken) async {
    await _accessTokenLock.synchronized(() async {
      await _secureStorage.write(key: _accessTokenKey, value: accessToken);
    });
  }
}