Description
On Chinese-manufactured devices (e.g. Xiaomi, Huawei, OPPO, OnePlus, Realme), users going through the account recovery flow get stuck on the final "Finish" page. The page appears to load but never progresses or dismisses, leaving the user unable to complete recovery.
Steps to reproduce
- Open the app on a Chinese-manufactured Android device
- Navigate to the account recovery flow
- Complete all recovery steps
- Arrive at the Finish/confirmation page
- Observe that the page is stuck — no navigation away occurs and no success state is reached
Expected behavior
After completing all recovery steps, the user should be taken past the Finish page and returned to the main app flow (e.g. dashboard or login screen) with a success confirmation.
Supporting Media
No media provided yet. Screenshots or screen recordings from an affected device would be very helpful.
Desktop:
- Device: Mobile — Chinese-manufactured Android (e.g. Xiaomi, Huawei, OPPO, Realme)
- OS: Android
- Browser: N/A (native app)
- Version: Unknown — needs to be confirmed on affected devices
Additional Context
This issue appears to be specific to Chinese OEM devices, which often ship with customised Android ROMs that have aggressive battery optimisation, background process killing, or non-standard WebView implementations. Any of these could be interfering with the post-recovery navigation or async completion logic on the Finish page. Worth investigating whether a WebView quirk or a lifecycle event is being swallowed on these devices.
Description
On Chinese-manufactured devices (e.g. Xiaomi, Huawei, OPPO, OnePlus, Realme), users going through the account recovery flow get stuck on the final "Finish" page. The page appears to load but never progresses or dismisses, leaving the user unable to complete recovery.
Steps to reproduce
Expected behavior
After completing all recovery steps, the user should be taken past the Finish page and returned to the main app flow (e.g. dashboard or login screen) with a success confirmation.
Supporting Media
No media provided yet. Screenshots or screen recordings from an affected device would be very helpful.
Desktop:
Additional Context
This issue appears to be specific to Chinese OEM devices, which often ship with customised Android ROMs that have aggressive battery optimisation, background process killing, or non-standard WebView implementations. Any of these could be interfering with the post-recovery navigation or async completion logic on the Finish page. Worth investigating whether a WebView quirk or a lifecycle event is being swallowed on these devices.