App killed when android phone too aggressive in memory preservation, authorizeAndExchangeCode not completed

[albertocappellina-intesys]

Hi,

on some Android phones that employ overly aggressive memory management, we are encountering an issue. While the in-app browser is displayed (presenting the Keycloak interface to complete the login flow), the operating system may decide to terminate (kill) the app in the background to conserve memory.

Consequently, by the time the login process completes, the app is relaunched from a cold start, and the login state (e.g., session data) is lost.

What is a possible workaround for this situation?

Thanks

[abdusalamApps]

@albertocappellina-intesys We're having the same issue in our app, and no solution found yet.