-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After 1 launch of application buttons ob android native dialogs are unaccessible #10428
Comments
cc @guylouis |
cc @bitgamma |
I don't know exactly what test we make, but I guess we only try to SELECT the applet's AID. We could check the keys by issuing an INITIALIZE UPDATE, but we risk to block the card's ISD if it happens about 5 times (depends on card) so that'd be a bad idea. We could use the ATR + the output of the GET DATA command to see if it is a card with the same configuration as the JCOP4 platform we use. Since this would be a bit hit-and-miss and since it should be easy for the user to realize what they have in their hands, I wouldn't put too much logic to discriminate between a Keycard with deleted applet and a non-Keycard. |
Ok so the message is ok |
It's not only on this error. After error all system-dialogs with OK, Cancel, Continue etc buttons are shown without these buttons. |
I can't reproduce this in dev env |
@churik tried on latest nightly, the issue is not reproducible on redmi note 8 pro, android 9 |
Same issue occurred when attempting to Issue remains until app is closed or reinstalled. Issue disappeared when closing and reopening the app, while notifications kept running. |
@churik is this still an issue? Otherwise feel free to close. Thanks! |
Haven't seen it for a long time. |
Bug Report
Problem
Not sure that this issue is only about keycard errors but tried with the error-report dialog for creating account flow and I couldn't.
Expected behavior
Can tap OK button
Actual behavior
OK button is not accessible; only way to continue use app is to relaunch the app.
Reproduction
Additional Information
The text was updated successfully, but these errors were encountered: