search

corona-warn-app / cwa-app-android

Native Android app using the Apple/Google exposure notification API. 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
2.44k stars 495 forks source link

CAUSE: 3 Something went wrong #1645

Closed haodengfrm2 closed 2 years ago

haodengfrm2 commented 3 years ago

Avoid duplicates

Describe the bug

Expected behaviour

Steps to reproduce the issue

Technical details

Possible Fix

Additional context

Internal Tracking ID: EXPOSUREAPP-2410

haodengfrm2 commented 3 years ago

微信图片_20201118105014 微信图片_20201118105010

dsarkar commented 3 years ago

Dear @haodengfrm2,

Thank you for your post. Please have a look here: https://www.coronawarn.app/en/faq/#API10, https://github.com/corona-warn-app/cwa-app-android/issues/1085, https://github.com/corona-warn-app/cwa-app-android/issues/817. Can you confirm that you are using CWA version 1.6.0 or 1.6.1 already, please?

Thanks. Best wishes, DS

Corona-Warn-App Open Source Team

haodengfrm2 commented 3 years ago

Dear Dsarkar, I'm using 1.6.0. I don't understand the description in the link. Dose it mean, It could be solved if I update the software? Best wishes, Hao

Dear @haodengfrm2,

Thank you for your post. Please have a look here: https://www.coronawarn.app/en/faq/#API10. Can you confirm that you are using CWA version 1.6.0 or 1.6.1 already, please?

Thanks. Best wishes, DS

Corona-Warn-App Open Source Team

微信图片_20201118112335

dsarkar commented 3 years ago

@haodengfrm2, thanks for the reply. Can you also please let us know the ENF version, see here https://www.coronawarn.app/de/faq/#ENF_version. Thanks. DS

Corona-Warn-App Open Source Team

haodengfrm2 commented 3 years ago

Thanks for the reply! I don't understand quite well "In the settings, select 'Google > Notifications about possible encounters with COVID-19 infected'" In the settings of Google play or in the settings of CWA? I could not find the Notifications about possible encounters with COVID-19 infected....

@haodengfrm2, thanks for the reply. Can you also please let us know the ENF version, see here https://www.coronawarn.app/de/faq/#ENF_version. Thanks. DS

Corona-Warn-App Open Source Team

Alex-Esko commented 3 years ago

Geräte-Einstellungen > Google > COVID-19-Benachrichtigungen ganz unten: Version 18204217000 (Beispiel)

vaubaehn commented 3 years ago

@haodengfrm2

Geräte-Einstellungen > Google > COVID-19-Benachrichtigungen ganz unten: Version 18204217000 (Beispiel)

translates to

Your Android device settings > Google > Covid-19-notifications scroll down completely Version 18204217000 (example)

vaubaehn commented 3 years ago

@haodengfrm2 and @dsarkar

Dear Dsarkar, I'm using 1.6.0. I don't understand the description in the link. Dose it mean, It could be solved if I update the software? Best wishes, Hao

Dear @haodengfrm2, Thank you for your post. Please have a look here: https://www.coronawarn.app/en/faq/#API10. Can you confirm that you are using CWA version 1.6.0 or 1.6.1 already, please?

The link to the FAQ is obviously not related to your problem. That FAQ item is related to #737 (pipe is closed) which was actually solved with ENF version 15xxxxxxxxx and was affecting Android 6 devices only.

Your error indeed seems to replicate #1085 and #817 .

MikeMcC399 commented 3 years ago

@haodengfrm2

Just to summarize and make the error message searchable (instead of having it in a screen shot):

com.google.android.gms.common.api.ApiException: 10: Unable to validate key file signature: no public key found for package de.rki.coronawarnapp

Mobile device: Meizu Android version: 7.1.2 CWA version: 1.6.0

The instructions to get the Google Exposure Notification System (ENS) version number for an English user interface are on https://www.coronawarn.app/en/faq/#ENF_version

So go to (Android) Settings > Google > COVID-19 exposure notifications then scroll down to the bottom of the screen. (@vaubaehn almost got the translation right 😄 I just checked on my own device which is set to English, so I didn't do any translating.) When this problem occurred previously it was linked to a specific version of ENS, so it would be very helpful to know what version of ENS is installed on your Meizu device.

haodengfrm2 commented 3 years ago

Dear Mike, Thank you very much for your reply and summary. However, I could not find (Android) Settings > Google in Flyme/Meizu phone... 微信图片_20201118224251

@haodengfrm2

Just to summarize and make the error message searchable (instead of having it in a screen shot):

com.google.android.gms.common.api.ApiException: 10: Unable to validate key file signature: no public key found for package de.rki.coronawarnapp

Mobile device: Meizu Android version: 7.1.2 CWA version: 1.6.0

The instructions to get the Google Exposure Notification System (ENS) version number for an English user interface are on https://www.coronawarn.app/en/faq/#ENF_version

So go to (Android) Settings > Google > COVID-19 exposure notifications then scroll down to the bottom of the screen. (@vaubaehn almost got the translation right 😄 I just checked on my own device which is set to English, so I didn't do any translating.) When this problem occurred previously it was linked to a specific version of ENS, so it would be very helpful to know what version of ENS is installed on your Meizu device.

MikeMcC399 commented 3 years ago

@haodengfrm2

... I could not find (Android) Settings > Google in Flyme/Meizu phone

Thanks for the screen shot. There is certainly no Google element in that menu!

It looks like Flyme/Meizu is non-standard concerning the Google Play services, which is a prerequisite for the Corona-Warn-App, because the Exposure Notifications System is licensed via the Google Play services. Were you able to install the Corona-Warn-App from the Google Play Store or did you do it some other way?

It may be possible to get in to the Google COVID menu by a trick.

  1. Open the Corona-Warn-App and make sure that EXPOSURE LOGGING ACTIVE is showing (not STOPPED). If it is STOPPED, then enable it.
  2. Disable Bluetooth.
  3. If you get a red Google COVID notification "Exposure Notifications inactive" you can open it up. Then scroll down to the bottom and look for the Version. For me it says 18204217000.
  4. Also if you manage to open that menu, then you can select Exposure checks and at the top right, select the three-dot menu, then Export exposure checks. Add a .txt file extension to the filename all-exposure-checks.json and post the file here.
thomasaugsten commented 3 years ago

@haodengfrm2 You would help us a lot if you can provide a bug report for us that we can send to google because we are investigating this error over a long time now https://developer.android.com/studio/debug/bug-report and send this to me

haodengfrm2 commented 3 years ago

Dear Mike, Thank you so much for this trick! Here is the picture. Exposure checks is dark that I could not select it. There is no there dot menu also.... 微信图片_20201119081641

@haodengfrm2

... I could not find (Android) Settings > Google in Flyme/Meizu phone

Thanks for the screen shot. There is certainly no Google element in that menu!

It looks like Flyme/Meizu is non-standard concerning the Google Play services, which is a prerequisite for the Corona-Warn-App, because the Exposure Notifications System is licensed via the Google Play services. Were you able to install the Corona-Warn-App from the Google Play Store or did you do it some other way?

It may be possible to get in to the Google COVID menu by a trick.

  1. Open the Corona-Warn-App and make sure that EXPOSURE LOGGING ACTIVE is showing (not STOPPED). If it is STOPPED, then enable it.
  2. Disable Bluetooth.
  3. If you get a red Google COVID notification "Exposure Notifications inactive" you can open it up. Then scroll down to the bottom and look for the Version. For me it says 18204217000.
  4. Also if you manage to open that menu, then you can select Exposure checks and at the top right, select the three-dot menu, then Export exposure checks. Add a .txt file extension to the filename all-exposure-checks.json and post the file here.
thomasaugsten commented 3 years ago

@haodengfrm2 Thank you for the ENF version but I assume all device has the same ENF version at the moment. Can you please provide the bug report?

haodengfrm2 commented 3 years ago

Dear Thomas, Here attached the screenshot of developer menu. I could not find the bug report setting.... 微信图片_20201119083530

@haodengfrm2 Thank you for the ENF version but I assume all device has the same ENF version at the moment. Can you please provide the bug report?

MikeMcC399 commented 3 years ago

@haodengfrm2

Thank you so much for this trick! Here is the picture. Exposure checks is dark that I could not select it. There is no there dot menu also....

Your screen shot gave two extra pieces of information:

thomasaugsten commented 3 years ago

With the option bug report shortcut in power menu you should see an extra button when you try to turn off the phone. I assume the error is gone? If not please start the app with the error before creating the bug report

haodengfrm2 commented 3 years ago

With the option bug report shortcut in power menu you should see an extra button when you try to turn off the phone. I assume the error is gone? If not please start the app with the error before creating the bug report

Dear Thomas, Sorry but there is no such a button. It seems that Flyme did not implement this function...

MikeMcC399 commented 3 years ago

With the option bug report shortcut in power menu you should see an extra button when you try to turn off the phone. I assume the error is gone? If not please start the app with the error before creating the bug report

Dear Thomas, Sorry but there is no such a button. It seems that Flyme did not implement this function...

It's strange, because in the screen shot you posted, it looks like "Bug report shortcut" is enabled. Perhaps you could get help from your device manufacturer's support / forum?

Bug report shortcut

Here is what it looks like on a Samsung phone with Android 8:

Take a bug report

dsarkar commented 3 years ago

Dear community, dear @haodengfrm2,

We would appreciate feedback if this issue persists with CWA version 1.7.1. Many thanks!

Best wishes, DS

Corona-Warn-App Open Source Team

haodengfrm2 commented 3 years ago

Dear community, dear @haodengfrm2,

We would appreciate feedback if this issue persists with CWA version 1.7.1. Many thanks!

Best wishes, DS

Corona-Warn-App Open Source Team Dear Dsarkar, Thank you very much for your information! I update CWA and now it looks like this: 微信图片_20201201092817 微信图片_20201201092810 微信图片_20201201092803

MikeMcC399 commented 3 years ago

@haodengfrm2 Your screen shot shows "0 checks in the past 14 days". Also you have told us that you have no Google menu to access normally (unless you use the trick of disabling Bluetooth).

It is most likely that there is something wrong with the Google Play services installed on your mobile phone, so you may need to go to your Flyme/Meizu support or forum to get help in installing or re-installing this.

dsarkar commented 3 years ago

@haodengfrm2, are there any news on your issue? Did updating to 1.10.1 change anything? Thanks, DS

haodengfrm2 commented 3 years ago

@haodengfrm2, are there any news on your issue? Did updating to 1.10.1 change anything? Thanks, DS

Dear dsarkar, Thank you for your information. Unfortunately, nothing changed. Maybe it's just the problem of the system of my cell phone. Thanks. Hao

MikeMcC399 commented 3 years ago

@haodengfrm2 Your issue has been open for many months without any further progress. I commented in Dec 2020 (https://github.com/corona-warn-app/cwa-app-android/issues/1645#issuecomment-736648785) that it could be due to Google Play services.

It doesn't seem like anything in the CWA app could be changed to help you. Maybe you could report back your status and then close the issue if there is nothing more to be done?

svengabr commented 2 years ago

I have just checked the linked Jira issue.

Jira Ticket is flagged as: Resolution: Wont Fix Status: Obsolete

Developer comment:

No new information available. Will set it to obsolete.