I have this issue when using the DuckDuckGo browser. After a few days, launching the remote causes the app to attempt to log in again, which means it launches some URL with the default browser. Upon opening DDG, it forwards to another page telling me that my browser is not supported.
The issues are the following:
- There is no way to authenticate within the app itself.
- It times out after only a couple of days, so it keeps on doing this.
- It only supports a handful of browsers. This is the web and interoperability is the whole reason we use the web.
- Ironically, my browser just uses the WebView component in Android, which runs on the Blink engine - the same engine that Chrome uses. DDG uses WebKit on iOS, which is also Chromium-based.
- The “not supported” page seems to be caused by my browser’s user agent string, not by any actual incompatibility.
- Neither the app nor the website provides a URL I could copy/paste into a supported browser (to use POST data and/or to streamline the UX, one could use Intent | API reference | Android Developers to select Intent | API reference | Android Developers).
- The only workaround I’ve found is to change my default browser long enough to log in.
I haven’t tried messing with the user-agent string but it wouldn’t surprise me at all if that would allow me to proceed; after all, they’re using the same engine and it’s not using any browser-specific features.