On start of PoLo and starting a new operation I always need to enter the settings menu as no automatic connection to SOTA SSO is started as it looks like. Entering the settings this will trigger (directly) the connection to the SOTA SSO.
If I do not enter the settings menu firsthand I can not send a spot.
1.) This SOTA SSO login should happen on start of PoLo or at least on starting a new or opening a SOTA operation.
Upon first connection:
As long as there is perfect network coverage it is no problem. But on a lot of summits the data connection is unsteady and one might loose the connection. Whenever that happens one needs to login again by closing the operation and opening the Settings page. Very uncomfortable.
Desired feature would be that everytime one attempt to send a spot a connecting is established without any manual user interaction.
2.) Upon user sends a spot do just do a new login. Send the spot. Logout. My suggestion is to forget about any SSO token update or similar (it is just now working reliable).
But what I still need to do is to first go to the settings menu to “initiate” the connection to SOTA SSO first. Otherwise it will not work.
I am just looking at the code to understand at what point this should happen…
So testing here on my Android device, and emulator, I was able to spot from both without going to setting screen first. They have been logged in since 29th November and 2nd December as well.
Can I just check your using latest December release candidate?
Also, do you have 2nd factor authentication on your account? I don’t myself, and wondering if that’s a factor somehow.
This bit of code is only called when user presses the login button, which then opens the browser where you put in your username and password. Are you saying you need to do this every time?
Yes. I do need to enter the settings dialog every time. It then logs in automatic to SSO without my interaction.
This should be “triggered” automatic at the start of the app or when starting a new operation. Or maybe it does that but not for me… strange.
Okay. Well that’s using same code to fetch a token, and display your callsign, as the used for the self-spotting. But they do call different API’s which have different responses.
Maybe we could make the code just try to get a new token for any response other than success, in case on occasion sotawatch is returning something like a gateway timeout, or service unavailable error, due to server load or something.
Is the fetch token action done every time one wants to send a spot with the “Self-Spot” button or by entering “SPOT” in the Callsign field?
Or is that something that is happening always in the background ?
It’s only done when trying to spot, via either method, and also when going on settings page. There is no need to do it in the background, as refresh token (used to fetch an access token) should be valid for 30 days.