ERA viewer asks me to login to Connect IQ SDK manager?

beva 11 days ago

When I start Connect IQ SDK manager I'm logged in though.

beva 11 days ago

I restarted VSC and then it first gave me the same message and after that I could login to ERA itself again.

flocsy🤠 11 days ago in reply to beva

Do you also need to log in every time you open ERA Viewer? What OS are you using?

beva 10 days ago in reply to flocsy🤠

No only after the new version was installed and today. Win 11.

flowstate 10 days ago in reply to beva

beva said:
No only after the new version was installed and today. Win 11.

That's a known change which was called out in the SDK changelog.

VS Code > command palette (CTRL/CMD-SHIFT-P) > Monkey C: View Documentation > README

I still don't understand how it's possible for older ERA viewers to work, unless credentials really aren't necessary for the ERA, or if the older ERA viewers use credentials that are already cached elsewhere (but why would the change be necessary in that case).

Maybe it's possible that older ERA viewers will stop working at some point, and this is just some transition phase.

beva 10 days ago in reply to flowstate

flowstate said:
I still don't understand how it's possible for older ERA viewers to work, unless credentials really aren't necessary for the ERA, or if the older ERA viewers use credentials that are already cached elsewhere (but why would the change be necessary in that case).

With regard to the error I got I think it used the login credentials from the Connect IQ SDK manager.

flowstate said:
That's a known change which was called out in the SDK changelog.

I'm aware of that and was already logged in to ERA, I got this error when I already was in the ERA and browsing from one watch face to another.

flocsy🤠 10 days ago in reply to beva

Have you used the same developer key for all your apps?

beva 10 days ago in reply to flocsy🤠

Yes, after I lost it it's in all my apps backup plans :P . This is not something reproducable, it worked fine without the need of logging in for each usage, and after I restarted VSC and logged in again it worked fine again.