You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain apps and services using TOTP codes in WebViews have a recurring issue (though it used to be worse): leaving the app to access an authenticator and then returning causes the WebView to close. This can sometimes abort the login process or even the app entirely, forcing a restart. Additionally, the previously copied TOTP code frequently expires by the time the OTP input form reappears, necessitating yet another trip to the authenticator. This process can be extremely frustrating and inefficient.
To work around this, I use Authy with its homescreen widget and leverage automation tools (Touch The Notch -> Tasker -> Popup Widget) to launch the widget in a freeform floating container, such as Popup Widget or Panels. This approach prevents the faulty app or WebView from closing, enabling a seamless and rapid 2FA process. In fact, this workflow has become indispensable for me due to its speed and fluidity.
As far as I know, there are two ways to replicate this workflow:
Widget-Based Approach: Use a homescreen widget to display the authenticator view’s contents. This may require addressing biometric/password locks or even disabling them for the widget to function properly.
Deep Link Intent Approach: Register a deep link intent to launch the authenticator’s base or main activity in a freeform floating window. This requires the ACTION_MANAGE_OVERLAY_PERMISSION permission. It would allow other apps to call the floating version of the app via the Intent system. (Or perhaps even better: just the authenticator view in a floating window that copies the selected code upon click and closes itself immediately.)
The text was updated successfully, but these errors were encountered:
Certain apps and services using TOTP codes in WebViews have a recurring issue (though it used to be worse): leaving the app to access an authenticator and then returning causes the WebView to close. This can sometimes abort the login process or even the app entirely, forcing a restart. Additionally, the previously copied TOTP code frequently expires by the time the OTP input form reappears, necessitating yet another trip to the authenticator. This process can be extremely frustrating and inefficient.
To work around this, I use Authy with its homescreen widget and leverage automation tools (Touch The Notch -> Tasker -> Popup Widget) to launch the widget in a freeform floating container, such as Popup Widget or Panels. This approach prevents the faulty app or WebView from closing, enabling a seamless and rapid 2FA process. In fact, this workflow has become indispensable for me due to its speed and fluidity.
As far as I know, there are two ways to replicate this workflow:
Widget-Based Approach: Use a homescreen widget to display the authenticator view’s contents. This may require addressing biometric/password locks or even disabling them for the widget to function properly.
Deep Link Intent Approach: Register a deep link intent to launch the authenticator’s base or main activity in a freeform floating window. This requires the ACTION_MANAGE_OVERLAY_PERMISSION permission. It would allow other apps to call the floating version of the app via the Intent system. (Or perhaps even better: just the authenticator view in a floating window that copies the selected code upon click and closes itself immediately.)
The text was updated successfully, but these errors were encountered: