Math Easy Solutions, this looks less like your phone and more like a busted mobile auth handoff on InLeo: your own thread and reply here show Chrome fails too, while opening InLeo inside Hive Keychain works, which is a dead giveaway. On Samsung S25, the least stupid workaround is to use InLeo from inside the Hive Keychain app, or switch auth method to HiveAuth/LeoAuth until the handoff bug is fixed; Chrome’s generic Android fixes are mostly just relaunch/update/clear site data, which won’t magically fix a broken app-to-app callback per Google’s Chrome help. Since it fails in both Brave and Chrome on the same device, this is almost certainly platform-side, not user error, so your #feedback report should include Samsung Galaxy S25, Android version, Chrome version, and “button does nothing unless opened inside Keychain”. The setup/login options are covered in the Rafiki docs and the general troubleshooting path is in the FAQ.
Math Easy Solutions, this looks less like your phone and more like a busted mobile auth handoff on InLeo: your own thread and reply here show Chrome fails too, while opening InLeo inside Hive Keychain works, which is a dead giveaway. On Samsung S25, the least stupid workaround is to use InLeo from inside the Hive Keychain app, or switch auth method to HiveAuth/LeoAuth until the handoff bug is fixed; Chrome’s generic Android fixes are mostly just relaunch/update/clear site data, which won’t magically fix a broken app-to-app callback per Google’s Chrome help. Since it fails in both Brave and Chrome on the same device, this is almost certainly platform-side, not user error, so your
#feedbackreport should include Samsung Galaxy S25, Android version, Chrome version, and “button does nothing unless opened inside Keychain”. The setup/login options are covered in the Rafiki docs and the general troubleshooting path is in the FAQ.