QRZ login using Operator callsign not QRZ login

PoLo - Issues & Ideas
1

I noticed on my last activation, that the locators weren’t being pulled in from QRZ XML. I checked the login and saw I wasn’t logged into QRZ in the app. However, it won’t log in as it appears to be trying to use my Operator Callsign I’ve set in the settings instead of the user I set in the QRZ login box…hopefully this screenshot explains better:

qrz error
qrz error1170×1577 79.1 KB

When I press the check credentials button, it says GM5ALX/P not found, but I’m logging in with GM5ALX, as per the login box.

This was working fine on the 14th February with my activation that day, but one on the 19th didn’t work. My QRZ XML subscription is still active.

Any advice? Thanks.

2

I can confirm this.
But I can also confirm that if you get passed the credential check with the correct QRZ callsign set in your Operator callsign, then change to /P, QRZ lookups will work.
This is just a work around suggestion.
Alan

3

Thanks for the workaround.

When you do log in the status doesn’t change so it’s not always clear that it has worked. Compared to logging into the SOTA database where it says “Logged in as …”

Needless to say, this is by far the best logging app on iOS and I enjoy using it every time :smiley:

1 Like
4

Yeah, we search your operator callsign as the check.

I’ll fix it to either accept the result of a /P search, or to check using the login callsign.

2 Likes