Repeated Keychain access prompts in v0.49.1 on macOS Tahoe

[TecnoTalarn]

What happened? How can it be reproduced? Provide as much information as possible.

Description:
After updating to version 0.49.1, the application requests the Keychain security key every time it needs to access a password. This behavior occurs even though there is no active password/key set in the system Keychain for this specific action.

Steps to Reproduce:

Install Qlog v0.49.1 on macOS Tahoe.

Attempt any action that requires password access/retrieval.

Observe the system prompt asking for the Keychain key.

Expected Behavior:
The application should access stored credentials seamlessly or according to system settings, as it did in previous versions.

Environment:

Qlog Version: 0.49.1

OS: macOS Tahoe

Hardware: Apple Silicon M2

Additional Context:

The issue is not present in v0.49.0. Reverting to the previous version completely resolves the problem.

I do not have any active security keys configured in my Keychain, yet the app insists on prompting for one.

[aa5sh]

What password is it looking for, is the same one like QRZ or different items?

[TecnoTalarn]

It is asking for my macOS user password. That is the one I enter and the program accepts it.

[aa5sh]

Normally in the title bar I think it says what it is trying to access. I can't get it to pop up to get a screenshot but maybe next time it happens post a screenshot of here and I can show you. That way we can get it narrowed down. Thanks Michael

[aa5sh]

Ok here is an example notice it refers to LoTW on the second line:

[TecnoTalarn]

I have just reinstalled version 0.49.1 using the DMG file I downloaded three days ago, and I am currently unable to reproduce the problem.

Previously, the issue would essentially appear whenever I was downloading or uploading logs to services like LoTW, Club Log, etc. However, I am testing it now and the error has not reappeared.

The only change to my system—though I doubt it is related—was a macOS update that took place last night to version 26.3.1 (a) (25D771280a).

I ask gemini about this and say:

A quick note on that update

Actually, even though you suspect it might not be related, macOS updates often include fixes for network protocols or security permissions (TCC) that can directly affect how apps communicate with external servers like LoTW. It is very possible the OS update resolved a conflict that was causing the crash or glitch!

[foldynl]

The only fix in 0.49.1 that directly affected the code is a minor change in Online Maps. Otherwise, these are changes to the build process for Linux. Nothing that directly affected the MacOS build was here.

[aa5sh]

I have seen this before when I launch test namepsaces, I think it started back when the multiple QRZ API tokens were added. I've never been able to make steps to replicate it, and it seems random. That is why I was wondering if it was that password it was trying to access or something else.

[aa5sh]

Out of curiosity can you check in Keychain just to see if you have anything there unintentionally for QLog possibly it is trying to access?

[TecnoTalarn]

[aa5sh]

Ok so it looks like you have some sort of entries in there from March 21. Not sure why 49.1 is prompting vs 49 not though. So I would think cautiously you have two options:

• Just enter your password and choose 'Always Allow' so it will not keep prompting, shouldn't matter if you didn't enter passwords
• Attempt to delete this entries from KeyChain and then it wont try to access the data/prompt. I haven't tested this so not sure what may happen.