search

corona-warn-app / cwa-app-ios

Native iOS app using the exposure notification framework from Apple. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
1.68k stars 285 forks source link

Corona-Warn-App does not open the certificate if the notification "Überprüfen Sie die Gültigkeit Ihrer Zertifikate" is clicked while the app is in foreground #3772

Closed Ein-Tim closed 3 years ago

Ein-Tim commented 3 years ago

Avoid duplicates

Technical details

Describe the bug

If the app is in the foreground and the user clicks on the "Überprüfen Sie die Gültigkeit Ihrer Zertifikate." notification, nothing happens.

EDITED BY Corona-Warn-App Open Source Team

Steps to reproduce the issue

  1. Add a certificate which either will expire soon or which signature will soon get invalid
  2. Get the "Überprüfen Sie die Gültigkeit Ihrer Zertifikate" notification from the CWA
  3. Open the Corona-Warn-App and navigate to the "Zertifikate" tab
  4. Click on the notification from the CWA
  5. See that nothing happens

Expected behaviour

Normally the certificate which the notification was send for is opened.

Additional context

EDITED BY Corona-Warn-App Open Source Team

dsarkar commented 3 years ago

@Ein-Tim Please, in general use a different certificate with a different name. Thanks.

Ein-Tim commented 3 years ago

@dsarkar

Agreed, I'm sorry.

I cannot provide a new video as I did click on all notifications, so I will just leave the video out.

I also deleted my initial OP and will leave your edit as it is (I removed the information that all certificates in my app are invalid).

I hope you understand that this was not with any intention, but only because I had no other option. Sorry again 😅

Have a nice Saturday!

dsarkar commented 3 years ago

@Ein-Tim I understand, no problem. I suggest closing this one and create a new "clean" issue. Thanks! Enjoy your weekend!

jucktnich commented 3 years ago

@dsarkar what should you do in case you don't know if the content is appropriate like in this case? Just creating the issue and waiting for corrections, write the content to an email address, ...? Maybe you could append the Code of Conduct with the intended behaviour?

Ein-Tim commented 2 years ago

Just to follow up: This bug was meanwhile fixed.