A bit later than I’d wanted, but here it is, the January '25 release.
The main changes are
• Winter Field Day (including scoring, and section name lookups!)
• Support for multiple station calls in a single operation (i.e. two friends activating the same park passing the mic back and forth, this will generate multiple ADIF files, spot both calls, etc)
And of course, lots of minor bug fixes and small improvements here and there.
Look for it as an update in the Apple AppStore, Google Play Store, or Apple’s TestFlight.
So, “Build 25.1.0” is the “human readable name” of the base build of the app, while “2501002” is the build number. The difference is that the build number must be different, and higher, for each build we produce. While the “build name” can be the same between two or more builds.
Then “25.1.0-rc2” is the version for the incremental updates we can push for the app without having to produce a full new build. These are downloaded automatically and don’t require app store approval.
In general then, the version numbers follow the monthly releases, so “25.1” is January '25, and “25.2” will be February.
2501001 was the first full build for January, and it corresponded to Release Candidate 1. Then came a few incremental upgrades to fix some bugs and lead to 2501002 and 2501003, which is the build approved by the app stores today. The number is bases on the year (2 digits), month (2 digits) and sequence (3 digits).
When it’s time to start the “prereleases” for february I’ll create a 24.1.99 version, with base build 2501901 (and 902, etc if needed), which then becomes 25.1.0 and build 2502001 for the “release candidates”, and usually one or two more builds to ensure the version downloaded from the stores does not require incremental updates right away.
And right now, the latest should be 25.1.0 - Build 25.1.0 (2501002) but I think I made a small mistake and did not remove the “rc2” label from the build.
Thank you for the update, Sebastian. I like Ham2K Polo very much since several SOTA activations. Since I tried it first I forgot fast about other logging apps. Really really great. Even today I used it, while it has been updated by Android.
I saw, in the export ADIF the field FREQ is added now. This leads to upload problems at the SOTA database, in my case: there is a misunderstanding in kHz and/or MHz. So my shortwave activation became a GHz + unknown frequency activation.
When I deleted all FREQ fields in the ADIFs by hand, everything is normal like before.
I dont know if that is a bug or maybe POTA needs the data like this. But I think for SOTA it is not usable from today. I also used to upload my logs to GMA (cqgma.org). GMA is not accepting the exported logs at all, from today.
Thanks a lot, I hope there will be some solution, without manual editing every adif.
The problem occours, when not logging the excact frequency but only the band, like I usually do. The new versions adds the general band-beginning frequency to the exported SOTA adif like “7000” for the 40m band. The SOTA database reads this as 7000 MHz instead of kHz. Actually when there is no frequency given in an adif, the importing systems are already adding these, like the sota database is doing it, too.
