I’m going to be cleaning up my various beta test users lists. You’ll probably get an email from me as well just to confirm.
I need to accomplish a couple of things with this house cleaning:
- Regain some slots back from folks who aren’t using them
- And the main thing - make sure that folks who opt-in to beta testing are fully aware of challenges they may face - broken builds, bugs that might prevent you from using HAMRS in the field, etc. With iOS TestFlight, for instance, you can no longer side load a beta version; it replaces what’s on your device. So if HAMRS is now your primary logger and I push out a version on a Friday for myself and others to test for weekend activations, and it buggy, I’d hate for folks to be left in a lurch.
I run automated tests locally as well as general smoke tests on device simulators, so any bugs should be minor, but there is no guarantees as we head into things like cloud sync, hardware integration, etc.
Beta times should be short, 2 weeks at the most, so if you were a previous Beta tester and just want to sit back and wait for stable builds to make their way onto their respective App Stores, you won’t be missing out.
So. If you’d like to opt back in, and understand the ramifications, please fill out this form.
I can’t tell you how much I appreciate the folks in this community. I’ve been bragging to coworkers about how much more useful ham users are compared to gamers 
