Inspect stored credentials during authentication debugging

Investigate credential and token state in your Flutter app using explicitly allowed secure-storage keys in local development.

SecureStorage tools help you investigate which credentials or tokens are stored when debugging authentication behavior. They can read, replace, or remove explicitly allowed values in the native secure store; keep access limited to the keys and local workflow you need.

Warning: Secure-storage tools can expose or mutate credentials and tokens. Enable them only for explicit local debugging.

const secureStorage = AnsightSecureStorageToolsOptions(
  appleService: 'com.example.app',
  preferencesName: 'secure_debug',
  allowedKeys: <String>['debug_token'],
);

Pass the options through AnsightRemoteToolsOptions and use withAllToolAccess() on the options builder. The suite exposes secure.get_value, secure.set_value, and secure.remove_key; all three use Critical, including reads, so read-only or read-write access will not enable them. The key allow-list still applies. Keep allow-lists narrow and avoid unrestricted access on physical devices containing real user data.