Closed Ein-Tim closed 2 years ago
@Ein-Tim Actually, the "fake" certificates indeed have an invalid signature. So the behaviour to reject them is correct (we want to be able to debug even the cryptographic operations like signature verification on the simulator).
If I understand your wish correctly, you want a variant where the signature verification of these fake certificates is "mocked" so that they are accepted and can be stored, and that you can use them to test the behaviour of the app with certificates present.
Please try "Whiskey's debugging trick" if it fulfils your wish.
Note: meanwhile the fake certificates are outdated. So you can scan and store them, but still they are shown as invalid.
I meanwhile consider this as intentional. Thus closing this issue.
Avoid duplicates
Technical details
release/2.12.x
Describe the bug
Selecting the universal QR code scanner on a simulator and then selecting either "HC1" oder "HC2" in the pop-up "Select a QRCode you want to fake" leads to an invalid signature error.
Steps to reproduce the issue
release/2.12.x
Expected behaviour
It should be possible to import certificates without a valid signature to a Simulator.
Possible Fix
Disable signature check for Simulators, maybe via the "Override App Features" option in the Developer Menu?
Additional information
This can be tracked in an internal ticket with #3632.
Internal Tracking-ID: EXPOSUREAPP-9765