When opening a session to log into my website, there is, if exists, information stored in IndexDB we are trying to access from a previous session. Ideally, information from living in Safari, but would settle for information in the parent app or instance. My understanding was information 'like cookies' was available, but documentation is seemlingly vague around this topic.
I have struggled to find anything explaining the availability of IndexDB specifically, although it does work in one case (I'm about to experiment with it, so I just know of one now).
Upon first loading of the page, a get call:
const ids: string[];
const results = await this.db.entities.bulkGet(ids);
In the logs, I see there is this error:
_e: Error: Error
name: AbortError
message: The operation was aborted. AbortError: The operation was aborted.
inner: DOMException: The operation was aborted.
Immediately after, because there is supposed to be some result from the database, the site creates a new entity, and stores it with no issue.
This information does not persist however, as opening a second session, the same operation happens due to the same error.
We're using XState, which typically is able to catch this error and continue, sometimes does not catch the error, and the state stands still.
So far, this behavior has only been experience on iOS with ASWebAuthenticationSession (not ephemeral).
Any insight would be appreciated, even if it means abandoning this webview class for something more for this purpose.