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.
Does it communicate via usb with the camera? If so it is probably because it uses webusb which is not implemented in Firefox https://caniuse.com/?search=webusb
But you can’t make a native app think it is opening Chrome when it’s opening Firefox with just an extension. The extension only changes things inside the browser, but the Canon app probably checks the app ID of the browser it’s opening, which is done at the level of the Android system, and which is not affected by the extension.
[@[email protected]](https://lemm.ee/u/s08nlql9] 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.
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.
Does it communicate via usb with the camera? If so it is probably because it uses webusb which is not implemented in Firefox https://caniuse.com/?search=webusb
I understand, but if the application opens the browser you have to make it believe that it is opening Chrome
But you can’t make a native app think it is opening Chrome when it’s opening Firefox with just an extension. The extension only changes things inside the browser, but the Canon app probably checks the app ID of the browser it’s opening, which is done at the level of the Android system, and which is not affected by the extension.
… which can only be fixed after rooting the phone.
[@[email protected]](https://lemm.ee/u/s08nlql9] 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
Oof.