The final RC for July '25 is now available on TestFlight and Google Play Test Program.
It includes:
Please give it a quick test run as soon as possible. I plan to make this generally available later tonight, in order for people to get the public update before Field Day weekend.
I’ve used it for POTA the past couple of days and had no issues to report. I didn’t spot anyone because I didn’t know that was possible to do from the app.
Any luck with the frequency error when uploading ADIF’s containing 40m contacts to SOTAData? Was consistently causing an error when selecting “40m” band in app.
This should have been fixed in 25.7.1 (and newer).
Can you try a new export and let us know if it worked?
I ensured my app has the latest patch and created a test log with fake contacts just now. Unfortunately the problem is still there. For testing sake, tried 80m and I am also seeing the error with that band. SOTAData continues to flag them as invalid entries.
All other HF bands between 80-10 are working fine. It seems to be an issue with it defaulting to “7” and “3” for 40m and 80m respectively.
Note that all the frequencies are what populate when I just select the band of operation in the app, I haven’t entered an actual freq on any of them.
My guess , looking at your entries, that the problem is at the ADIF import of SOTAdata in the Frequency to Band conversion.
Exactly 7.000 MHz SSB - on Lower Side band that is an out of band operation. Pretty sure that is also what the red exclamation mark will tell you.
So maybe try to log your QRG exactly like e.g. 7.036 or so for CW.
Or make a bug report to the SOTA team (VK3ARR Andrew is the main person for SOTAdata)
73 Joe
No, the problem is more subtle than that.
The SOTA site is parsing the value using floating point libraries, and 7.00000 somehow ends up being 6.9999999999999, which then is actually considered out-of-band.
The latest version of PoLo should now export it as just “7”, without decimals, which should allow it to work on the SOTA site.
Thanks Sebastian for the heads up. I have relayed the information to Andrew VK3ARR.
Might be something others logging tools might struggle with too.
