Wheel I create a new operation using the template SOTA (nearest), the SOTA summit is not set anymore automatically but needs to be chosen manually. This was working in older versions, but I do not know when it stopped working!
Thanks for the report. It appears to be a location setting issue.
When you start a new operation, the operation location is not being set even though the device has acquired one. It’s staying unset until after the activities have been assigned.
For me it’s slightly different. If I select a template ,SOTA nearest, it loads a general operation log and then I have to add a SOTA activity. It used to work before the latest update
This problem happens for “Template for POTA (nearest)” as well, and was working prior to the December update. I’ve noticed that there’s a several-second lag in acquiring a grid location as well on my Pixel 7; I kinda remember this delay being shorter before.