Does seem to be a Google Chrome problem, app logs in fine using the Firefox web browser.
Cheers
Rob
I have the exact same problem on my Chromebook. I need to use the cloud version since the charts app gives me the ālogin cancelledā error. The Firefox workaround doesnāt work for me. The cloud version is fine, but there should be no reason that the app doesnāt work in the Chrome browser in the Chrome environment.
This problem still exists with the latest Charts Mobile App release.
On Chromebook, I have both the built-in Chrome and FireFox browsers. I am correctly entering my credentials, but after the Identity Page closes (and accepts my login) I am returned to the App home page with the āLogin Cancelledā notice in Red present. There is no āTrouble Signing Inā or other alternative button other than āSign In.ā
Just out of curiosity, was this tested with a Chromebook?
Weāre investigating.
Which browser is the default one out of the installed ones?
Regards,
Stephen
Chrome. But I can select either one at time of clicking a valid redirect to a URL link if desired.
I see. And choosing Firefox instead has no effect?
Stephen
Correct. The behavior is consistent in both browser cases - Identity page closes (with no errors) and Iām returned to the App Home Page with the āLogin Cancelledā error in red atop the Sign In button.
I have a 9.1 MB screen recording to show the behavior if that might help. I can send it to you via e-mail.
Weāre working on a potential fix for this. Please standby and weāll get back to you.
Regards,
Stephen
Thank you, much appreciated!
Hi Guys,
We have released a new version today that should make Sign In stable on Android devices in general. For Chromebook specifically you need to install an Android browser, for example Chrome using Google Play. The Android app can only communicate with other Android applications and will not be able to perform authentication using the ChromeOS Google. Please keep us updated if you still encounter problems.
Kind regards,
Markus
1 Like
Will test it out - thanks!
I am running GoogleChromeOS 110.0.5481.112 (Official Build) (64-bit) on a Google Pixelbook.
I updated Charts today - 27-FEB-2023, in the notes it does state āFixed some issues that prevented the sign-in button from working when certain 3rd-party browsers were selected as default.ā Version 8.21.0
I am using Chrome browser on the Pixelbook to connect the Sign-In and launch the Identity Page on Navigraph. Itās still not working unfortunately.
Do you know how I can reset the Sign-In link on the Charts app so it lets me select a different browser? I want to try with Firefox which is the only other browser on my system.
The Chrome Browser is integrated into ChromeOS. Are you recommending a different one?
Iād have to find one that is reliable. Thereās many knock-offs passing themselves as Chrome browsers. Iāll see if there is another one. I do have Firefox installed which launches in a phone size window so Iām assuming that is an Android app and will work.
Do you know how I can disassociate the Sign-In link and let me choose a different browser? At the moment, it auto-launches the built-in Chrome browser which is part of the problem Iām guessing. If I can get it to let me pick Firefox I can retest this version.
The Chrome browser integrated in ChromeOS is made for ChromeOS and cannot communicate properly with Android applications, just with other apps built for ChromeOS. Firefox built for ChromeOS will not help in this regard either, it should be the Android Firefox installed via Google Play for it to work properly.
I donāt have a Chromebook myself but this seems to be the way to set the default browser How To Change Default Browser On Chromebook - YouTube.
Kind regards,
Markus
Well, I managed to clear the preferences/association and confirmed I can pick between Chrome (which is invalid, because itās ChromeOS integrated) and Firefox, which I can confirm is the Android version - it even forces me to choose between Phone and Tablet window sizes.
The Identity attempt fails. I confirm Iām entering the right credentials. It returns me back to the Charts Sign In with Login Cancelled in red status above the button.
However, I saw something different I hadnāt seen before - there was an open tab in the Firefox browser with an Identity Page error message. Perhaps itās helpful? Please see below.
After trying a few more times last night I contemplated a bit.
I know the team is working on a lot of things, I donāt want this to end up pulling hours away from development and support of other items core to the business.
Worst comes to worst, I just use Charts Cloud on the browser, which works well enough for my purposes. My recommendation would be to put another line in the system requirements/specifications list stating āNot working/recommended under ChromeOS.ā That way, the expectations are totally baselined.
Thanks for looking into it!
Hi @Casualclick,
The Android app works fine for several users, so we just need to understand why it does not work for you. The error message you got can be indicative that cookies are turned off in the browser. Can you please check that this is not the case?
Kind regards,
Markus
Good news: Itās working!
Moderate news - Iām not sure why.
I double-checked Firefox and noted Enhanced Protection Tracking was ON - this is default at least in Version 110. I turned it OFF per screenshot below and the initial results were the same - no login.
I inspected the Charts settings one more time in Manage Apps and nothing was changed. I did note that if you go through the typical App troubleshooting step of clearing both Cache and Local Storage, the Permissions of Location and Local Storage are turned OFF. I made sure those were ON before leaving that screen, and re-entered it once to make sure those switches were persistent state.
I then tried it once more, with Charts Cache and Storage cleared and Firefox ETP Off. Failure again.
Not wanting to operate Firefox without ETP on, I turned it back ON. Just for giggles, I tried it one more time, and it worked. I donāt know what might have been the step that fixed it. Perhaps clearing storage on the Charts App might be the key, but itās working now. Itās a little troubling that I canāt nail down root cause, but thatās technology lifeā¦
Thanks for your patience and guidance in this support request!