-
Notifications
You must be signed in to change notification settings - Fork 496
Google APIException (10): Unable to validate key file signature: no public key found #1085
Comments
Hi @rzo1 , I think your issue is indeed similar to #817 (no public key found), but likely different from #737 (pipe is closed?). Could you maybe export and provide the Exposure log: Interesting co-incidence: #817 reported by @eriktews was also on Pixel 3-series on Android 10. For him the error resolved itself the next day, if I remember right. |
More or less yes, so maybe it started to work again after I rebooted the device and of course I had automatic updates enabled in the Play Store, so maybe some component was updated on the phone that solved the issue for me. |
Interesting detail: My wife also uses a Pixel 3a. Her CWA in v1.2.1 is working fine. ENF version 16203302004. Last successful "Risiko-Ermittlung" on my phone was on 25.08.2020 @ 20:42 @vaubaehn here is the exposure log of my phone pretty formatted.
```
[
|
Hello @rzo1 and thank you for reaching out. The initial problem with Best regards, Corona-Warn-App Open Source Team |
The report of #737 (attached PDF) is not exactly the same: #737 is API(10): Unable to validate... : Pipe is closed Your report and #817 is: API(10): Unable to validate... : no public key found I had a look to your exposure log:
|
@vaubaehn Thanks for the details - I must admit, that I did not check the stacktrace in 737 exactly. I have updated my initial bug report and my comment regarding 737. In addition, I have attached the original JSON file of my exposure log: No. On 23.08.2020 everything worked fine (as far as I can remember). I first noticed this behaviour on 26.08.2020. Interesting side-note: I checked another Pixel 3a (same versions as shown above), which has no problems at all. Weird. I can create a bugreport via adb, if needed by SAP (from different Pixel 3a devices). However, I won't post them in public :) |
Hi @mtb77, here is the "Google Play Dienste" version: 20.30.19 (on all Pixel 3a devices similar...) Best, |
Hi @rzo1 thanks for the update! Sascha Corona-Warn-App Open Source Team |
As a follow-up: the issue on my Pixel 3a is gone:
|
Thank you very much for your feedback. I am happy to hear the error is gone with the latest version of our app! Best regards, Corona-Warn-App Open Source Team |
Please, see #1645 (comment). |
Describe the bug
Similar to #817
and #737Technical details
Internal Tracking ID: EXPOSUREAPP-2410
The text was updated successfully, but these errors were encountered: