January '25 - 25.1.3

  • Fixes for a few issues with call info lookups
  • Fixed ADIF export for multi-operator operations

My Android phone update this morning and since the update I am getting username/password incorrect for callsign lookups. I have QRZ enabled and haven’t changed my QRZ username or password on QRZ or in the app

The previous versions were not showing these errors, and the new one does.

Could it be possible that QRZ wasn’t just working in older versions and it was just failing silently?

Ron, Can you make sure your QRZ username is set to your callsign and not your email address? The API requires callsign but logging on to QRZ website can accept email address.
Alan

Anything is possible :grinning:. I reset my QRZ username and password in the app and I’ll use it for a while and report back

Ron Lewen - N7BBQ

https://www.qrz.com/db/n7bbq

Good day!

I re-entered my user name (callsign) and password and lookups are working again, so apparently I fat fingered something. The thing that puzzles me is how I was getting lookups before. I understand that this store message wasn’t in the previous version, but I set up QRZ lookups when I installed the app on my new phone a couple of weeks ago and I thought that it was working.

Oh well… It works now! Sorry for the false alarm!

I am on latest iOS version and the latest Ham2K version and I am also experiencing the Username/Password incorrect issue. I’ve triple-checked my credentials and replaced my email address with my call sign to no avail.

All was well until a couple of weeks ago after an SW update.

Just to be clear on the triple-check issue,. There’s no need to triple check with the actual real time check. i.e. there’s no guess work. Are you tapping the “Check Credentials” button?

In which case you will get a response of your name:

If you haven’t go this version/feature yet, you will soon.
In the meantime just confirm that you are using your callsign as the username and not your email address.
Alan

Thanks for the clarification and snide remark, :stuck_out_tongue_winking_eye:

Unfortunately, that credential check feature is absent in my build. I’ve confirmed the issue with Sebastian.

What snide remark?