Is this issue still being investigated? I’m using version 22.214.171.1243 on macOS and still experience this.
I thought this was fixed with V 7.3.8. Please provide details of the problems experienced, included which browser.
I experience the same problem. Below I have described it in more detail:
I have a yearly subscription (since this month) and I also work with Navigraph Charts 7.3.8. I have an iMac (2017) with OS 11.2.3 and Safari as a default browser.
Charts will unexpectedly turn blue on me every two or three days (after working normally), and tell me to sign in. When I click the “Sign In” box, my browser (Safari) opens and asks me for my credentials, which I duly supply of course. I also check the box “remember me” (I like to be remembered).
After that, the trouble begins. Safari tells me I’m signed in and asks me if I wish to be redirected to my desktop application and I click Yes. Safari then answers that I am signed out and asks me if I wish to open Charts. Again. I say yes, upon which I am switched to the blue screen of Charts, still with the Sign In-Box prominently visible. By the way, if I tell Safari NOT to redirect me it just stays on the same page (You are signed in) and nothing happens to the desktop application, not even when I close and reopen it. I then close Safari altogether and reopen Nav Charts and … the miracle happens. I see the charts, I can fly! …. for two days or so, until this circus starts all over again.
This sign-in protocol does not do its job properly, nor does it make sense to have two independent pieces of software (charts and a browser) cooperate on one simple task: checking whether your subscription is still valid.
Please help me solve this issue, as it might spark some sadness shortly.
By the way, since this morning the same mishap occurs with SimLink. Same sad story.
This describes my experience perfectly. I’m on a late 2019 MacBook Pro using Safari and Charts build 126.96.36.1993.
I have split the thread because the issues that you are experiencing might look like the same issue as the previous thread, but it is indeed not as that issue has been fixed.
We are currently upgrading the whole authentication flow in order to make it more stable, and this task is highly prioritized. While we can’t be entirely sure exactly what is causing the issues you are experiencing, we can be quite sure that what we have in store will mitigate them.
Thank you for your patience!
Until then, please do the following:
- Make sure that you do not have multiple tabs of Navigraph Charts open.
- If you have issues with the app while running macOS Big Sur, please try reinstalling the application in an effort to reset its permissions to those required by the latest version.
@Overtoom31, you mention having issues with Simlink as well. When you perform the sign-in process, particularly the part where you should be redirected to Simlink, does the application get focused or does it stay in the background?
I will check that, however, Simlink is such a simple application, that it does not give me the option to logout. As I am currently logged in again, I am just waiting until the app asks me again to login. Or should I reinstall Simlink as well?
No need to reinstall if it works! But if it stops working again, taking note of what was mentioned would be valuable to us.
Do you remember what you did to get it to work again?
I think I remember: after I shut down Charts and Safari, I got charts to open in logged-in mode. Something comparable happened in Simlink. It MIGHT have to do with shutting down Safari only, but I have been unable to test that assumption.
A post was split to a new topic: Can’t Login in to Charts
Sorry for the delay in replying to this. I am running Charts 188.8.131.523 on macOS Big Sur. I’ve reinstalled the app as well. The problem manifests when I leave the app running for several days without using it. When I go to use it my authentication is expired and it opens identify.api.navigraph.com in Safari. When I login there the browser asks to open Charts. When I allow it to open Charts the cycle continues. I’m redirected once again to identity.api.navigraph.com.
We’re currently at a loss as to how that might happen. However, we have some upcoming changes to the authentication process that could possibly fix this, so stay tuned!
If the problem persists after the update (which is coming in the near future), then we’ll dig deeper and try to find the root cause together.