You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing stored values cannot be read (returns error "EntryNotFound").
Our app is storing data offline which is encrypted with a password in the keystore so the user loses this data if we cannot get the key.
Android is reporting the exact same package id and uid. The namespace and keys used in the keychain are are the same.
The only other change is the gradle configuration which had to be updated to work with Qt6
I replicated in a minimal test app running from the IDE (APK is unsigned); additionally the issue is present when updating our release app which is signed with the same cert. I note the underlying Qt6 JNI code has vastly changed which could be the source of the issue.
Any clues for what is happening?
The text was updated successfully, but these errors were encountered:
kage-p
changed the title
Keychain values not readable when upgrading Android app from Qt5 to Qt6
Keychain values not readable when upgrading Android app from Qt5 to Qt6 (qtkeychain 0.14.1)
Jan 12, 2024
Note: if I switch the test app between the Qt5 and Qt6 configuration and run it again, keys appear to be stored separately for each, as if it is a different app
The existing stored values cannot be read (returns error "EntryNotFound").
Our app is storing data offline which is encrypted with a password in the keystore so the user loses this data if we cannot get the key.
Android is reporting the exact same package id and uid. The namespace and keys used in the keychain are are the same.
The only other change is the gradle configuration which had to be updated to work with Qt6
I replicated in a minimal test app running from the IDE (APK is unsigned); additionally the issue is present when updating our release app which is signed with the same cert. I note the underlying Qt6 JNI code has vastly changed which could be the source of the issue.
Any clues for what is happening?
The text was updated successfully, but these errors were encountered: