If this was a web view they wouldn’t even need this screen since it could just done in the “app” itself instead of needing to open an external browser.
If this was a web view they wouldn’t even need this screen since it could just done in the “app” itself instead of needing to open an external browser.
@s08nlql9@lemm.ee try making a dummy app with com.google.chrome(not sure) as package name and login again. Maybe the browser check get bypassed and it opens in the default browser.
I don’t think that app check signature or so. Its probably checking if app exist or not. Except if the app launches chrome by its indent action instead of normal link opening method
This is a native Android app from Canon (not a webpage) requiring to open Chrome instead of my default Firefox app.
Apps are rarely native these days. Everything is a fucking webview.
If this was a web view they wouldn’t even need this screen since it could just done in the “app” itself instead of needing to open an external browser.
If this was a web view they wouldn’t even need this screen since it could just done in the “app” itself instead of needing to open an external browser.
I understand, but if the application opens the browser you have to make it believe that it is opening Chrome
@s08nlql9@lemm.ee try making a dummy app with com.google.chrome(not sure) as package name and login again. Maybe the browser check get bypassed and it opens in the default browser.
For that you need a ROM that supports signature spoofing, but it should be possible, just not for the common user, sadly
I don’t think that app check signature or so. Its probably checking if app exist or not. Except if the app launches chrome by its indent action instead of normal link opening method
Checking the signature seems like it would be good practice. But that doesn’t mean that they do.