Markus Meissner

this is already done (nkapp2 uses QT6) - the comment above is about two minor details missing from the update process that are already working on `nitropy` - not about...

As the Password Manager was now [released](https://github.com/Nitrokey/nitrokey-app2/releases/tag/v2.2.1) - we are now working on deployment/distribution - cannot give an ETA yet, but at least it's now on the high priority list

currently there are the following blockers for a full macOS release: * https://github.com/Nitrokey/pynitrokey/issues/145 * secrets touch confirmation seems not to work * auto-detection (add/remove device) not working properly (https://github.com/Nitrokey/nitrokey-app2/issues/252) Any...

yes, this makes sense, guess `nkapp2` is simply too strictly pinnned to its matching `pynitrokey` version - let's see if we can improve for the next release

closing, as this shouldn't happen anymore using nitrokey-sdk (?) please re-open if you see similar issues

yes, this is kind of known behavior currently - some pyside6 threading issue/corner-case we don't handle yet, but usually this shouldn't lead to a core-dump ... we just have observed...

works within the settings tab now....

The underlying error is originating from `pynitrokey` there is an issue for that: https://github.com/Nitrokey/nitrokey-3-firmware/issues/250 Nevertheless I keep this open as such an error should: a) not crash the nitrokey-app b)...

this should be resolved by now - please open a new one if you see similar thing happen

@Eric-Canas would you mind taking a look at how this might be implemented, I'd like to help - but it's not entirely clear to me how to solve that -...