Certificates lost after 'Restore from Backup'

[michael-koeller]

Avoid duplicates

• Bug is not mentioned in the FAQ
• Bug is not already reported in another issue

Technical details

• Device name: iPhone 8
• OS version: 15.0.2
• App version: 1.11.1

Describe the bug

The CovPass App stores its certification data in a way that does not survive a backup/restpre-cylcle.
After 'Restore from Backup' on an iOS device, all certification data ist lost.

Steps to reproduce the issue

1. Restister certificates in the CovPass app via QR-Code scan.
2. Create a baclup of yout iOS device.
3. Reset the iOS device to factory settings.
4. Execute the 'Restore from Backup' option.
5. After successful installation, open the CovPass app.
6. Open the CovPass app.

Expected behaviour

Expected: All registered certificates are still present.

Possible Fix

Take a look at the similar function in the CoronaWarn app, where described procedure does not loose any data.

Additional context

n.a.

[Ein-Tim]

Take a look at the similar function in the CoronaWarn app, where described procedure does not loose any data.

Sure about that? corona-warn-app/cwa-app-ios#3625

[michael-koeller]

Yes, I am.

I did the restore on my iPhone 8 on 2021-10-14. The phone already had iOS 15.0.2 at that time. I had scanned my vaccination certificate QR-Codes in both apps.

After restore on the same device, the certificates were still present in the Corona-Warn-App, but not in the CovPass app.

The surprise hit me hard as I was just standing at the airport check-in terminal and the Corona-Warn-App saved my holiday.

[Ein-Tim]

@michael-koeller

After restore on the same device, the certificates were still present in the Corona-Warn-App, but not in the CovPass app.

Okay, this supports my issue corona-warn-app/cwa-app-ios#3626 where I ask for clarification when something is backupped and when not.

[molk-ibm]

Are we talking about encrypted backups here?

[michael-koeller]

I used a local backup and, yes, it was encrypted.

[jleufgen]

@michael-koeller thanks for your effort! Could you reproduce the bug again? We couldn't.. Maybe the bug no longer exists due to the release updates.

[Ein-Tim]

@jleufgen If there is no feedback from @michael-koeller, I suggest to close this issue, especially because you said you weren't able to reproduce this issue.

[Kurt57]

@Ein-Tim thanks for your feedback. I also see like that and close this issue.