Camera Connect requires Chrome? Why?

[guertin]

I recently upgraded Canon Camera Connect on my phone from 3.2 to 3.4. I know that this upgrade requires a Canon ID, which I have, so that's fine. But when I launch the upgraded app for the first time and try to log in with my Canon ID, the login fails with the error message that I must have Chrome installed. In 2025, why is there any possible reason to require a particular browser? The browser wars were over years ago. In my case, I have a de-Googled Android phone without Chrome installed, and no way to install it. It has never been an issue with any other apps, and I have plenty of other browser options. So what's so special about Chrome that Camera Connect needs it? For now I've downgraded back to Camera Connect 3.2, but that may not be a stable long-term solution.

[Waddizzle]

What browser did you use to create the Canon ID?  I have no idea why you get the error message.

But I can make a wild guess. Today’s browsers have the ability to remember web site logins. Did you create the Canon ID on this phone or another device?  If not, then I suggest using the default browser on your phone to log in to Canon.  See if that helps.

[guertin]

Thanks. That sounded like a good idea, but even after logging in with my Canon ID on another browser, I still get the same error when I try to log in with Camera Connect: "You need the Chrome app to sign in." I get the same error if I select either button, i.e. sign in or create a new account. 

[Stephen]

Sorry for the vague error. 

Here's the simple breakdown of why this is happening and what you need to do:

1. The App is Picky: The Canon app is built to handle the secure sign-in step—where you enter your Canon ID and password—using a specific, secure component that is part of the Google Chrome web browser. It doesn't matter what your phone's default browser is (like Firefox or Samsung Internet); the app is hard-coded to look for Chrome.

2. The Fix is Simple: If you see this error, it just means that Chrome isn't installed on your phone, or it might be disabled.

3. Action Plan:

   • Go to your Google Play Store.

   • Find and install the Chrome app by Google.

   • Once it's installed, you don't even need to open it! Just go back to the Canon app and try tapping "Sign in with Canon ID" again.

The app will now be able to use the Chrome component it needs, and you should be able to log in successfully!

[guertin]

Thanks. I figured it was something like that. As I noted in my original post, my phone is de-Googled. That means it has no proprietary Google content on it, using the open-source microG replacement for Google Play Services instead. (The philosophical reasons for doing so are not worth discussing here.) In the years that I've used this setup, I've never had an issue installing any apps (including security-related apps and apps from the Google Play Store) until this. Chrome simply will not install on my phone, which is no great loss except for the way Camera Connect is coded, which appears to be particularly inflexible. I'll see if I can configure microG to allow Chrome to install, otherwise I'll just stick with Camera Connect 3.2

[guertin · Accepted solution]

Follow-up: It's working now. My phone was missing the Google Trichrome library, which is why Chrome wouldn't install. I installed the missing library APK, installed Chrome, and now Camera Connect 3.4 is working. All's well that ends well, but I still maintain it's poor coding that has Camera Connect set up this way.