Hi @jeffz, mobile apps don’t have localStorage. At least for iOS, it neither has anything like “file://” since it’s working in its own sandbox. Apps are only supposed to use restricted system APIs to persist local data or use databases such as SQLite or Realm.
@A_A, thanks for your tip! I’ve successfully used Cordova to bridge solid-auth-client.js and native logic with a customized AsyncStorage. Now I can fetch and persist some information through OIDC and possibly manipulate triples with native logic (if the following problem fixed.)
Now I come across the next problem:
After OIDC authorization, my mobile demo gets the object solid-auth-client without the “session” part. Other than that everything looks fine. Specifically,
- It contains “rpConfig” with almost all sub-fields (provider, defaults, store, registration, etc. ) similar to the web version.
- It also has requestHistory and oidc.session.privateKey.
- It has a field appHashFragment (which does not appear in web version) with empty value.
Do you have any suggestions? The redirect_uri has the scheme of ionic://, would that be the reason?
PS. sample Login/Authorization URIs initiated from ios app: