A WebView session can outlive the main application's session. Persistent web login after native logout can mix account data.
Evaluation approach
Identify cookie, local-storage and cache data stores. Clean relevant data deliberately during account transitions.
Application example
A second portal user must not return to the first user's page through Back navigation or offline caches.
Limits and considerations
Deleting one cookie may not end the entire web session.
Why cookie deletion may be insufficient
Web content may also use local storage, caches or other session mechanisms. Bind the relevant data store to the application account. If old content returns after cleanup, logout is incomplete.
Checks and decisions
- Inventory web stores
- Test Back navigation
- Separate accounts
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.