Storage capabilities¶
Read automobile:devices/{deviceId}/storage/capabilities?appId={packageName} to
learn which storage features a device and app support.
- App-container, user-files, and media-library features are reported as unavailable when the device or app cannot support them (for example, a missing write provider).
- The platform-neutral
secure_statedomain reports Android’s singlestorage.keystorecapability, or iOS’s singlestorage.keychaincapability. Without an app scope, or when the app has not enabled the embedded SDK, no discovery is attempted.
See Keystore test state for the Android secure_state response and
Keystore metadata for inspecting aliases from app tests.
Android secure_state.write and secure_state.namespace_reset remain unsupported.
Use resetKeychain with a declared scope or alias for scoped alias deletion;
it does not write aliases or reset package data.
iOS Keychain¶
storage.keychain never contains a Keychain value.
| Field | Meaning |
|---|---|
inspection |
Always unavailable: AutoMobile does not read Keychain values. |
deletion |
enabled when the app allows deleting at least one exact item; otherwise disabled. unknown when the app’s SDK is too old to report it or could not be reached. |
reason |
Why deletion is not enabled: DISABLED, NO_ALLOWLISTED_SCOPES, SDK_TOO_OLD or BRIDGE_UNAVAILABLE. |
deletionScopes |
The exact items deleteKeychainItem may delete (item class, service, account, access group). Empty unless deletion is enabled. |
Deletion is the only Keychain change AutoMobile makes, so read, write and
namespace_reset stay closed even when deletion is enabled. Each delete still needs
storage mutation authorization (--allow-storage-mutations). If deletion is disabled,
ask the app’s developers to turn on Keychain deletion in the app’s AutoMobile SDK
configuration and allowlist the exact items.
iOS shared stores¶
On iOS, key_value.stores lists the app-group UserDefaults suites the app registered,
and databases.stores lists its registered Core Data stores. Each entry states:
sharing:app_private, orapp_groupwhen other processes such as app extensions can open the store.coordination:single_processfor an app-private store; for a shared one,host_coordinatedwhen the app declared that it coordinates cross-process access, anduncoordinatedotherwise. An uncoordinated read is a point-in-time snapshot that another process may change at any moment.query:supportedfor suites and Core Data stores with read access enabled by the app;unsupportedfor Core Data registrations without read access.
Coordination is whatever the app declared when it registered the store; AutoMobile does
not infer it. Treat an uncoordinated shared store as one that can change between reads.
Querying databases¶
sqlQuery accepts appId and exactly one of these parameter pairs:
databasePathandquery: execute SQL on an app SQLite database. On Android, the path may also be a file name in the app databases directory.storeandentity: fetch attributes from a registered Core Data entity on iOS. OmitdatabasePathandquery. Optionallimitis a positive integer, defaults to the app’s row limit, and is clamped to that limit.limitis only accepted in this mode. Use a store whosequerycapability issupported.
For example: sqlQuery({appId: "com.example.app", store: "Main", entity: "Item", limit: 10}).
Core Data reads return type: "query", columns, rows (strings or nulls),
truncated, and a message. A truncated: true value means more rows exist or the
app shortened the response to meet its row or byte limit. Sensitive attributes
are redacted. These reads never require storage mutation authorization.
Core Data queries require iOS and the app’s Debug storage inspection support.
For unknown_core_data_store, use a store identifier listed in databases.stores in
the storage capabilities resource. For unknown_core_data_entity, use one of that
store’s registered entity names. For core_data_query_unavailable, the app registered
only metadata for that store; ask the app developer to enable read access.
For db_inspection_disabled, enable inspection in the app.
For core_data_fetch_failed, the fetch threw inside the app; check the app logs.
For response_too_large, even the column metadata exceeds the app’s response limit.
AutoMobile rejects invalid or mixed parameter pairs before execution.