Hi all
There are issues from time to time with spotting to SOTAwatch since a log-in to their SSO is needed to do so.
The problem was somewhat mitigated by a new white pop-up window appearing to indicate that I am not logged in to SOTAwatch.
But I didn’t understand exactly when or under what circumstances this warning appears.
In my experience, this window often doesn’t appear until (and quite late) after I press the “Self-spotting” button and a spot is supposed to be sent to the spotting facilities of the programs I’m activating.
This is annoying because it only prevents the SOTA spot, but the other programs spot me immediately. What do I do now? I have to hurry to log in to SOTA via Polo right away and trigger the self-spot again.
The white window is just a warning. So I have to exit the operation, go to the login area, initiate the login, wait for the login confirmation, and then go all the way back to start the self-spot again in the operation. In the meantime, the first chasers from the other programs are already calling . . .
I’m therefore asking here, if possible, for a significant streamlining of the process. Ideally, I’d be able to start the SOTA login directly from this warning – that is, without having to navigate through the various menus.
Here’s a second suggestion to this issue: In my opinion, it’s too late if the warning doesn’t pop up until I’m actually self-spotting. I think it would be better if the warning popped up as soon as I open an operation for which a SOTA reference has been recorded. At that point of the activation, I still have enough time to log into SOTAwatch! It’s also fine if the warning were displayed for older operations – staying logged into SOTAwatch at all times is always better for SOTA enthusiasts.
Thanks for any possible progress.
Vy 73, Markus
NB: This problem gets really nasty when, additionally, the connection to the cellular network is bad and you are stuck in the SOTA SSO login screen. The earlier the login is done – the better! 
Best is: “before Self-Spotting”.