-
Notifications
You must be signed in to change notification settings - Fork 496
Error when communicating with Google API(10): Unable to validate key file signature. #737
Comments
Hi. Could you provide us with more Information of the Context, App Version and when this occured? |
I have the same problem. |
Hi. Thanks for pointing out your issue, however we would really need more detailed information on the context of your devices, your setup and your installation. Otherwise it is extremely hard for us to correctly identify the issue. Thanks so much for your understanding. Important Info:
|
@jakobmoellersap have the same problem after restart the phone. Do you need detailed informations? |
got the same bug, app has been installed for a couple of days and already displayed "Niedriges Risiko" before. When i close the error report it shows the green display "niedriges risiko" again this occures reproducable after each startup (including after a restart of the phone)
|
In the morning, the descripted Problem was persisting. But now, I have a new problem:URSACHE: 3 Fehler bei Kommunikation mit
|
@gitbrueck please refer to the other issues referencing error 3 like #499 and #508 |
Just as a headsup: This means that key files are actually sent to the API, so most likely the concern is (as discussed in #642) a security API problem within certain devices from certain manufacturers together with the applied security providers. On the bright side: You do get the keys of the server onto your device, however the security handling is broken apparently. |
Same here Honor 7 Premium 32 GB (Android 6). The problem popped up yesterday morning but after a few hours it disappeared. |
I cleared data and cache of Google Play Store. Maybe like @Martin-Wegner just wait and see. |
Same problem with a Huawei P8. |
Same on Huawei ALE-L21 |
Same error occurred on my phone today 25 June 2020 in the morning. App seems running fine now - don't know if everything indeed works as it should in the background (?).
Update: |
It would be extremely helpful if anyone that experiences this error can submit a proper bug report to us via adb as seen here: |
I took a bug report, but I'm hesitant to share it publicly. Is there any way for me to share it privately? |
I took a bug report via my smartphone as well. |
Can you guys take a look at #642 and see whether you have matching reports or similar problems in your report? The errors seem to correlate |
Here is my filtered log:
|
Same problem here on Android 6.0.
Afterwards, there's a new error:
After getting rid of the error messages by clicking "okay" the app seems to be working fine. "Risiko-Ermittlung aktiv, niedriges Risiko". However after leaving the app via back-button and entering it again via clicking the link on the home screen, the 2nd error message is back (Google API(39508)).
As far as I remember, I've never seen that error ("9002, file is not a database: , while compiling: select count(*) from sqlite_master;") before. |
39508 is rate-limiting since the API Call is done twice but the Submission in the API is failing and detected by the transaction, which in turn rolls back and then thinks the call never came through. This is also the reason why the rate-limiting appeared in the first place. |
@Tj20 can you give us a device model so that we can check whether this correlates? |
It's a Vernee Thor (2016), model number: "thor", Android 6.0, latest OS update: Oct 2016 (thor_20161008), Kernel 3.18.19 |
Okay, could you give us some more details of your devices via ADB? Concretely, we would like to know the GMS Version. this can be retrieved via the following command: |
Update for #737 (comment): Same error happened today on Device
Update
LogHere my heavily filtered log - hope I didn't remove relevant lines: Click to expanddumpstate: 2020-06-26 09:49:14
Build: MMB29M.G900FXXU1CRH1
Build fingerprint: 'samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys'
Bootloader: G900FXXU1CRH1
Kernel: Linux version 3.4.0-14131106 (dpi@21HHAF15) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Aug 6 19:17:53 KST 2018
Command line: console=null androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x37 ehci-hcd.park=3 androidboot.sec_atd.tty=/dev/ttyHSL0 sec_log=0x100000@0x10000008 sec_dbg=0x80000@0x10100008 sec_debug.reset_reason=0x7 mdss_mdp.panel=1:dsi:0:mdss_dsi_samsung_1080p_cmd_fa2 lcd_id=0x602813 Panelres=1 pmic_info=3 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=9aa7269813c11255783e75057c7fbe00 connie=SM-G900F_OPEN_EUR_7913b415b9abe36d19ad1ca2d6f21f49 loglevel=4 samsung.hardware=SM-G900F androidboot.revision=14 androidboot.emmc_checksum=3 androidboot.warranty_bit=0 fg_reset=0 androidboot.bootloader=G900FXXU1CRH1 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 uart_dbg=0 sec_debug.pmc8974_rev=2 vmalloc=450m level=0x574f4c44 androidboot.emmc=true androidboot.serialno=4f1d4c8e androidboot.baseband=msm
------ SYSTEM LOG (logcat -v threadtime -d *:v) ------
--------- beginning of main
06-26 09:48:22.290 818 818 I ActivityManager: Start proc 23475:de.rki.coronawarnapp/u0a259 for service de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService
06-26 09:48:22.340 23475 23475 W ResourcesManager: getTopLevelResources: /data/app/de.rki.coronawarnapp-1/base.apk / 1.0 running in de.rki.coronawarnapp rsrc of package null
06-26 09:48:22.680 818 1656 D PackageManager: setEnabledSetting : userId = 0 packageName = de.rki.coronawarnapp cmp = androidx.work.impl.background.systemjob.SystemJobService newState = 1 callingPackage = 10259
06-26 09:48:24.150 23475 23567 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/journal.tmp
06-26 09:48:25.720 23475 23574 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/9fe44808aba26677253c42a986222fcd.0
06-26 09:48:25.720 23475 23574 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/9fe44808aba26677253c42a986222fcd.1
06-26 09:48:26.000 23475 23574 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/b280261e5c73c5c112da3956deefb48e.0
06-26 09:48:26.000 23475 23574 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/b280261e5c73c5c112da3956deefb48e.1
06-26 09:48:27.310 23475 23568 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/58eddfcca85aa33b90375bd75b332fee.0
06-26 09:48:27.310 23475 23568 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/58eddfcca85aa33b90375bd75b332fee.1
06-26 09:48:27.890 13871 14868 I ExposureNotification: ThreadSafeLevelDbWrapper: do open LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:27.890 13871 14868 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@d2ff9e created [CONTEXT service_id=236 ]
06-26 09:48:27.900 13871 14868 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@d2ff9e closed [CONTEXT service_id=236 ]
06-26 09:48:27.900 13871 14868 I ExposureNotification: ThreadSafeLevelDbWrapper: do close LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:27.960 13871 4874 W System.err: stat failed: ENOENT (No such file or directory) : /data/user/0/com.google.android.gms/app_en_diagnosis_keys/1593157707970/export0.bin
06-26 09:48:27.980 13871 4874 E AsyncOperation: serviceID=236, operation=ProvideDiagnosisKeysOperation
06-26 09:48:27.980 13871 4874 E AsyncOperation: OperationException[Status{statusCode=Unable to validate key file signature: Pipe is closed, resolution=null}]
06-26 09:48:27.980 13871 4874 E AsyncOperation: at bnt.a(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:187)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at azi.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:11)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at ddp.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:2)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at avl.b(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:12)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at avl.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:7)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at stk.run(:com.google.android.gms@202117018@20.21.17 (040308-316502805):0)
06-26 09:48:27.980 13871 4874 E AsyncOperation: at java.lang.Thread.run(Thread.java:818)
06-26 09:48:28.010 13871 13871 I ExposureNotification: ThreadSafeLevelDbWrapper: do open LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:28.010 13871 13871 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@a006f38 created [CONTEXT service_id=236 ]
06-26 09:48:28.030 13871 13871 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@a006f38 closed [CONTEXT service_id=236 ]
06-26 09:48:28.030 13871 13871 I ExposureNotification: ThreadSafeLevelDbWrapper: do close LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:28.040 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Starting matching job. [CONTEXT service_id=236 ]
06-26 09:48:28.050 23475 23513 I WM-WorkerWrapper: Worker result RETRY for Work [ id=4c91f2e3-9a01-4a5b-8710-e92d52366787, tags={ DIAGNOSIS_KEY_ONE_TIME_WORKER, de.rki.coronawarnapp.worker.DiagnosisKeyRetrievalOneTimeWorker } ]
06-26 09:48:28.060 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Java pre-filter started. [CONTEXT service_id=236 ]
06-26 09:48:28.090 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do open LevelDb contact-tracing-contact-record-db [CONTEXT service_id=236 ]
06-26 09:48:28.090 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:contact-tracing-contact-record-db instance btz@2e946e4 created [CONTEXT service_id=236 ]
06-26 09:48:28.540 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Java pre-filter found 0 keys with sightings [CONTEXT service_id=236 ]
06-26 09:48:28.540 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Java tracing started. [CONTEXT service_id=236 ]
06-26 09:48:28.540 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:contact-tracing-contact-record-db instance btz@e775202 created [CONTEXT service_id=236 ]
06-26 09:48:28.570 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do open LevelDb en-exposure-result-storage-db [CONTEXT service_id=236 ]
06-26 09:48:28.570 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:en-exposure-result-storage-db instance btz@356b713 created [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:en-exposure-result-storage-db instance btz@356b713 closed [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do close LevelDb en-exposure-result-storage-db [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:contact-tracing-contact-record-db instance btz@e775202 closed [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Traced 0 diagnosis keys and found 0 matches. [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:contact-tracing-contact-record-db instance btz@2e946e4 closed [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do close LevelDb contact-tracing-contact-record-db [CONTEXT service_id=236 ]
06-26 09:48:28.650 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Persisting matching request record. [CONTEXT service_id=236 ]
06-26 09:48:28.660 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Matching job complete. Run time=603350362 ns. Matches not found. [CONTEXT service_id=236 ]
06-26 09:48:28.670 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do open LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:28.670 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@60c8c4e created [CONTEXT service_id=236 ]
06-26 09:48:28.670 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper:en-matching-request-db instance btz@60c8c4e closed [CONTEXT service_id=236 ]
06-26 09:48:28.670 13871 9091 I ExposureNotification: ThreadSafeLevelDbWrapper: do close LevelDb en-matching-request-db [CONTEXT service_id=236 ]
06-26 09:48:28.670 13871 9091 I ExposureNotification: [MatchingTracer: requestId=1593157707598, package=...rki.coronawarnapp] Successfully removed request. Matching job complete. [CONTEXT service_id=236 ]
06-26 09:48:43.050 13871 13871 I ExposureNotification: ExposureNotificationChimeraService.onUnbind [CONTEXT service_id=236 ]
06-26 09:48:44.960 21047 21047 I Timeline: Timeline: Activity_launch_request id:de.rki.coronawarnapp time:1183018648
06-26 09:48:44.990 818 1264 D ActivityManager: Launching de.rki.coronawarnapp, updated priority
06-26 09:48:45.020 818 902 V MARsPolicyManager: updatePackagesScore PackageInfo name -- de.rki.coronawarnapp
06-26 09:48:45.100 818 957 D ISSUE_DEBUG: InputChannelName : a782ac4 Starting de.rki.coronawarnapp
06-26 09:48:45.160 23475 23475 W ResourcesManager: getTopLevelResources: /data/app/de.rki.coronawarnapp-1/base.apk / 1.0 running in de.rki.coronawarnapp rsrc of package null
06-26 09:48:45.160 23475 23475 W ResourcesManager: getTopLevelResources: /data/app/de.rki.coronawarnapp-1/base.apk / 1.0 running in de.rki.coronawarnapp rsrc of package null
06-26 09:48:45.170 23475 23475 W ResourcesManager: getTopLevelResources: /data/app/de.rki.coronawarnapp-1/base.apk / 1.0 running in de.rki.coronawarnapp rsrc of package null
06-26 09:48:45.210 818 957 V WindowStateAnimator: Finishing drawing window Window{a782ac4 u0 d0 Starting de.rki.coronawarnapp}: mDrawState=DRAW_PENDING
06-26 09:48:45.220 818 957 V WindowStateAnimator: Finishing drawing window Window{a782ac4 u0 d0 Starting de.rki.coronawarnapp}: mDrawState=COMMIT_DRAW_PENDING
06-26 09:48:45.350 818 1656 I ActivityManager: Start proc 23847:com.wsomacp/u0a29 for content provider com.wsomacp/.db.XCPDBSqlProvider
06-26 09:48:45.830 818 1957 D ISSUE_DEBUG: InputChannelName : 7c7ee92 de.rki.coronawarnapp/de.rki.coronawarnapp.ui.main.MainActivity
06-26 09:48:45.850 13871 13871 W ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000102/dl-Nearby.integ_202304013020300.apk / 1.0 running in com.google.android.gms rsrc of package null
06-26 09:48:46.150 818 835 V WindowStateAnimator: Finishing drawing window Window{7c7ee92 u0 d0 de.rki.coronawarnapp/de.rki.coronawarnapp.ui.main.MainActivity}: mDrawState=DRAW_PENDING
06-26 09:48:46.160 818 957 I ActivityManager: Displayed de.rki.coronawarnapp/.ui.main.MainActivity: +1s166ms
06-26 09:48:46.160 818 957 I Timeline: Timeline: Activity_windows_visible id: ActivityRecord{efd0ed9 u0 de.rki.coronawarnapp/.ui.main.MainActivity t21655} time:1183019844
06-26 09:48:46.210 13871 2245 D BluetoothAdapter: STATE_BLE_ON
06-26 09:48:46.210 13871 2245 I ExposureNotification: Utils#isSupported enabled=true, isDeviceSupported=true, isBluetoothSupported=true, BluetoothAdapter.isMultipleAdvertisementSupported=false [CONTEXT service_id=236 ]
06-26 09:48:46.320 23475 23567 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/79b223ef7f5defd91b9eb3ebf8e0f68a.0
06-26 09:48:46.320 23475 23567 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/79b223ef7f5defd91b9eb3ebf8e0f68a.1
06-26 09:48:51.370 23475 23568 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/06949b74c3b8765ee756681acfa04329.0
06-26 09:48:51.370 23475 23568 W System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/de.rki.coronawarnapp/cache/http_cache/06949b74c3b8765ee756681acfa04329.1
06-26 09:48:51.510 13871 9091 W System.err: stat failed: ENOENT (No such file or directory) : /data/user/0/com.google.android.gms/app_en_diagnosis_keys/1593157731521/export0.bin
06-26 09:48:51.610 13871 9091 E AsyncOperation: serviceID=236, operation=ProvideDiagnosisKeysOperation
06-26 09:48:51.610 13871 9091 E AsyncOperation: OperationException[Status{statusCode=Unable to validate key file signature: Pipe is closed, resolution=null}]
06-26 09:48:51.610 13871 9091 E AsyncOperation: at bnt.a(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:187)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at azi.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:11)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at ddp.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:2)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at avl.b(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:12)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at avl.run(:com.google.android.gms.policy_nearby@202304013@202304013027.315351686.315351686:7)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at stk.run(:com.google.android.gms@202117018@20.21.17 (040308-316502805):0)
06-26 09:48:51.610 13871 9091 E AsyncOperation: at java.lang.Thread.run(Thread.java:818)
06-26 09:48:51.700 23475 23475 W System.err: com.google.android.gms.common.api.ApiException: 10: Unable to validate key file signature: Pipe is closed
06-26 09:48:51.700 23475 23475 W System.err: at android.support.v4.media.MediaDescriptionCompatApi21$Builder.setResultOrApiException(MediaDescriptionCompatApi21.java:3)
06-26 09:48:51.700 23475 23475 W System.err: at com.google.android.gms.internal.nearby.zzae.onResult(com.google.android.gms:play-services-nearby@@18.0.2-eap:2)
06-26 09:48:51.700 23475 23475 W System.err: at com.google.android.gms.common.api.internal.IStatusCallback$Stub.zaa(com.google.android.gms:play-services-base@@17.3.0:2)
06-26 09:48:51.700 23475 23475 W System.err: at com.google.android.gms.internal.base.zaa.onTransact(com.google.android.gms:play-services-base@@17.3.0:3)
06-26 09:48:51.700 23475 23475 W System.err: at android.os.Binder.execTransact(Binder.java:453)
06-26 09:48:51.800 818 1685 D ISSUE_DEBUG: InputChannelName : 2866a45 de.rki.coronawarnapp/de.rki.coronawarnapp.ui.main.MainActivity
06-26 09:48:52.280 23475 23475 W : Unable to open '/system/framework/com.qti.location.sdk.jar': No such file or directory
06-26 09:48:52.330 23475 23475 W : Unable to open '/system/framework/com.qti.location.sdk.jar': No such file or directory
06-26 09:48:52.400 23475 23475 W : Unable to open '/system/framework/com.qti.location.sdk.jar': No such file or directory
-------------------------------------------------------------------------------
DUMP OF SERVICE dbinfo:
Applications Database Info:
** Database info for pid 23475 [de.rki.coronawarnapp] **
Connection pool for /data/user/0/de.rki.coronawarnapp/no_backup/androidx.work.workdb:
Open: true
Max connections: 4
Available primary connection:
Connection #0:
isPrimaryConnection: true
onlyAllowReadOnlyOperations: false
Most recently executed operations:
0: [2020-06-26 09:49:15.092] [Pid:(818)]executeForLong took 0ms - succeeded, sql="PRAGMA temp.page_size;"
1: [2020-06-26 09:49:15.092] [Pid:(818)]executeForLong took 0ms - succeeded, sql="PRAGMA temp.page_count;"
2: [2020-06-26 09:49:15.092] [Pid:(818)]executeForCursorWindow took 0ms - succeeded, sql="PRAGMA database_list;"
3: [2020-06-26 09:49:15.088] [Pid:(818)]executeForLong took 0ms - succeeded, sql="PRAGMA page_size;"
4: [2020-06-26 09:49:15.086] [Pid:(818)]executeForLong took 2ms - succeeded, sql="PRAGMA page_count;"
5: [2020-06-26 09:48:45.779] [Pid:(23475)]execute took 1ms - succeeded, sql="COMMIT;"
6: [2020-06-26 09:48:45.779] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT * FROM room_table_modification_log WHERE invalidated = 1;"
7: [2020-06-26 09:48:45.779] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT * FROM room_table_modification_log WHERE invalidated = 1;"
8: [2020-06-26 09:48:45.779] [Pid:(23475)]execute took 0ms - succeeded, sql="BEGIN EXCLUSIVE;"
9: [2020-06-26 09:48:45.779] [Pid:(23475)]execute took 0ms - succeeded, sql="COMMIT;"
10: [2020-06-26 09:48:45.779] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT id, state, output, run_attempt_count FROM workspec WHERE id IN (SELECT work_spec_id FROM worktag WHERE tag=?)"
11: [2020-06-26 09:48:45.779] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT id, state, output, run_attempt_count FROM workspec WHERE id IN (SELECT work_spec_id FROM worktag WHERE tag=?)"
12: [2020-06-26 09:48:45.779] [Pid:(23475)]execute took 0ms - succeeded, sql="BEGIN EXCLUSIVE;"
13: [2020-06-26 09:48:45.778] [Pid:(23475)]execute took 0ms - succeeded, sql="COMMIT;"
14: [2020-06-26 09:48:45.778] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT * FROM room_table_modification_log WHERE invalidated = 1;"
15: [2020-06-26 09:48:45.778] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT * FROM room_table_modification_log WHERE invalidated = 1;"
16: [2020-06-26 09:48:45.778] [Pid:(23475)]execute took 0ms - succeeded, sql="BEGIN EXCLUSIVE;"
17: [2020-06-26 09:48:45.777] [Pid:(23475)]execute took 0ms - succeeded, sql="COMMIT;"
18: [2020-06-26 09:48:45.776] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT `progress`,`work_spec_id` FROM `WorkProgress` WHERE `work_spec_id` IN (?)"
19: [2020-06-26 09:48:45.776] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT `progress`,`work_spec_id` FROM `WorkProgress` WHERE `work_spec_id` IN (?)"
Available non-primary connections:
Connection #1:
isPrimaryConnection: false
onlyAllowReadOnlyOperations: true
Most recently executed operations:
0: [2020-06-26 09:49:15.093] [Pid:(818)]executeForCursorWindow took 0ms - succeeded, sql="PRAGMA database_list;"
1: [2020-06-26 09:49:15.093] [Pid:(818)]executeForLong took 0ms - succeeded, sql="PRAGMA page_size;"
2: [2020-06-26 09:49:15.092] [Pid:(818)]executeForLong took 1ms - succeeded, sql="PRAGMA page_count;"
3: [2020-06-26 09:48:23.528] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT `required_network_type`, `requires_charging`, `requires_device_idle`, `requires_battery_not_low`, `requires_storage_not_low`, `trigger_content_update_delay`, `trigger_max_content_delay`, `content_uri_triggers`, `WorkSpec`.`id` AS `id`, `WorkSpec`.`state` AS `state`, `WorkSpec`.`worker_class_name` AS `worker_class_name`, `WorkSpec`.`input_merger_class_name` AS `input_merger_class_name`, `WorkSpec`.`input` AS `input`, `WorkSpec`.`output` AS `output`, `WorkSpec`.`initial_delay` AS `initial_delay`, `WorkSpec`.`interval_duration` AS `interval_duration`, `WorkSpec`.`flex_duration` AS `flex_duration`, `WorkSpec`.`run_attempt_count` AS `run_attempt_count`, `WorkSpec`.`backoff_policy` AS `backoff_policy`, `WorkSpec`.`backoff_delay_duration` AS `backoff_delay_duration`, `WorkSpec`.`period_start_time` AS `period_start_time`, `WorkSpec`.`minimum_retention_duration` AS `minimum_retention_duration`, `WorkSpec`.`schedule_requested_at` AS `schedule_requested_at`, `WorkSpec`.`run_in_foreground` AS `run_in_foreground` FROM workspec WHERE id=?"
4: [2020-06-26 09:48:23.527] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT `required_network_type`, `requires_charging`, `requires_device_idle`, `requires_battery_not_low`, `requires_storage_not_low`, `trigger_content_update_delay`, `trigger_max_content_delay`, `content_uri_triggers`, `WorkSpec`.`id` AS `id`, `WorkSpec`.`state` AS `state`, `WorkSpec`.`worker_class_name` AS `worker_class_name`, `WorkSpec`.`input_merger_class_name` AS `input_merger_class_name`, `WorkSpec`.`input` AS `input`, `WorkSpec`.`output` AS `output`, `WorkSpec`.`initial_delay` AS `initial_delay`, `WorkSpec`.`interval_duration` AS `interval_duration`, `WorkSpec`.`flex_duration` AS `flex_duration`, `WorkSpec`.`run_attempt_count` AS `run_attempt_count`, `WorkSpec`.`backoff_policy` AS `backoff_policy`, `WorkSpec`.`backoff_delay_duration` AS `backoff_delay_duration`, `WorkSpec`.`period_start_time` AS `period_start_time`, `WorkSpec`.`minimum_retention_duration` AS `minimum_retention_duration`, `WorkSpec`.`schedule_requested_at` AS `schedule_requested_at`, `WorkSpec`.`run_in_foreground` AS `run_in_foreground` FROM workspec WHERE id=?"
5: [2020-06-26 09:48:23.390] [Pid:(23475)]executeForCursorWindow took 1ms - succeeded, sql="SELECT output FROM workspec WHERE id IN (SELECT prerequisite_id FROM dependency WHERE work_spec_id=?)"
6: [2020-06-26 09:48:23.389] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT output FROM workspec WHERE id IN (SELECT prerequisite_id FROM dependency WHERE work_spec_id=?)"
7: [2020-06-26 09:48:23.380] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT DISTINCT tag FROM worktag WHERE work_spec_id=?"
8: [2020-06-26 09:48:23.379] [Pid:(23475)]prepare took 1ms - succeeded, sql="SELECT DISTINCT tag FROM worktag WHERE work_spec_id=?"
9: [2020-06-26 09:48:22.780] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT long_value FROM Preference where `key`=?"
10: [2020-06-26 09:48:22.779] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT long_value FROM Preference where `key`=?"
11: [2020-06-26 09:48:22.762] [Pid:(23475)]executeForChangedRowCount took 0ms - succeeded, sql="PRAGMA recursive_triggers='ON';"
12: [2020-06-26 09:48:22.762] [Pid:(23475)]executeForChangedRowCount took 0ms - succeeded, sql="PRAGMA temp_store = MEMORY;"
13: [2020-06-26 09:48:22.761] [Pid:(23475)]executeForChangedRowCount took 0ms - succeeded, sql="PRAGMA foreign_keys = ON"
14: [2020-06-26 09:48:22.755] [Pid:(23475)]executeForCursorWindow took 6ms - succeeded, sql="SELECT identity_hash FROM room_master_table WHERE id = 42 LIMIT 1"
15: [2020-06-26 09:48:22.755] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT identity_hash FROM room_master_table WHERE id = 42 LIMIT 1"
16: [2020-06-26 09:48:22.754] [Pid:(23475)]executeForCursorWindow took 0ms - succeeded, sql="SELECT 1 FROM sqlite_master WHERE type = 'table' AND name='room_master_table'"
17: [2020-06-26 09:48:22.754] [Pid:(23475)]prepare took 0ms - succeeded, sql="SELECT 1 FROM sqlite_master WHERE type = 'table' AND name='room_master_table'"
18: [2020-06-26 09:48:22.750] [Pid:(23475)]executeForLong took 0ms - succeeded, sql="PRAGMA user_version;"
19: [2020-06-26 09:48:22.750] [Pid:(23475)]executeForLong took 0ms - succeeded, sql="PRAGMA wal_autocheckpoint=100"
Acquired connections:
<none>
Connection waiters:
<none> |
Now receiving error “timeout“ https://drive.google.com/file/d/1BZ-H3Kr6AllXBGtSYmmj99D5hADFRcMw/view?usp=drivesdk |
Hey everyone, First of all, sorry for us being silent about this but there was quite some investigation going on. The issue is identified and actively being worked on in a joint effort and I will write here once a fix is ready. We are terribly sorry for the issues and trust concerns this causes and caused up until now and we will try to mitigate as fast as we responsibly can. Also special shoutout to @kbobrowski for his amazing work on reverse engineering GMS that gave us the heads-up into the right direction. The Error will also resolve most rate-limiting problems (39508) once fixed, as the pipeline breakdown also caused the limit to be reached on retry. Best Regards on behalf of the Android Team, |
@helga-engels you had a regular HTTP Timeout, please check your internet connection. |
Thank you @jakobmoellersap for your effort and doing this fantastic work and to @kbobrowski who has identified the problem. |
Hi I had a different problem (API(39508) and asked for technical support on the phone. They recommended to uninstall and reinstall which I did. Now I have the problem mentioned above error communicating with API(10). I am using Samsung Galaxy J7. |
I followed this hint. All data was lost and after one day I get error communicating with API(10). |
This is not a good reputation for this app, I think. "Normal" users will refuse installing it when they read about the problems. See https://www.zeit.de/digital/2020-06/corona-warn-app-bugs-hinweise |
Just a quick clarification: All APP data was lost, that means the number of active days and your current risk status. |
There is no software without bugs. But this is not the platform for complaining this, but for contributing to the solution with informations, error logs, ideas etc.☺ |
I just spoke to the technical support. They explained more about this API(10) as well as API(39508). It is not a problem with the app but with the communication system. Google is informed, as I was told, and there shall be a solution from google's side in the next few days. |
Update to #737 (comment): Update: API(10) error also occurred on 3 Jul 2020, but without API(20) |
After deleting complete data (Google Play-Dienste, Corona-Warn) nevertheless permanent communication error API(10). The focus seems to be on bugs in google play services, but they were not updated shortly before first appearance of error API(10). And the error is still remaining after deleting all data. What about bugs in server software? |
Das ist doch echt einfach nur peinlich. Da wird massig Geld vom Staat in die App versenkt, das ganze dauert Monate wird als "DIE APP" schlechthin beworben von Politik und anderen. Hat das eigentlich niemand getestet? Oder hat Google sich entschieden nachdem die App fertig war jetzt mal schnell was an der API zu ändern damit die App nicht mehr sauber funktioniert? Ernnsthaft das ding is kein Candy Crush zum rumdaddeln wo Bugs zwar ärgerlich sind aber nich weiter problematisch. |
@jakobmoellersap is there an approximate ETA from Google when they will fix their implementation? Preferably before the exposure keys start expiring. |
Dear @crazyduck33 , even though we understand your anger, we kindly ask you to focus on the issue and not use the comments for unrelated discussions that do not help in getting this issue fixed. If we get more unrelated comments, we will have to lock the conversation and provide updates only when available. Of course, this app has been tested intensively, and the actual development by SAP and Telekom only started beginning of may. The error occurred only in productive usage and was not present beforehand. Also while we this error occurs on some devices, it does not affect all of them and therefore does not render the app unusable for everybody. To also answer @alois31 's question: no, we unfortunately do not have an ETA for the fix. |
Dear @tkowark, the focus seems to be only on bugs in google play services, but these were not updated shortly before first appearance of error API(10). And the error is still remaining after deleting all data. What about bugs in server software? |
As mentioned in #737 (comment) the issue is identified. |
developers: Please clean-up by deleting all the useless comments like "some problem here" or destructive bullshit like @crazyduck33 's comment to make this issue readable (and of course my comment). After 103 comments this thread is almost unusable if you want to know the technical background. |
As a retired software developer, I know that there is no software without errors. However the majority of users don't. They heard about the price (x millions) and are wondering why they get an app that doesn't work. As this error is well known and because you and Google are working on it, you should release an update that displays an appropriate message in german, eg. "Dieser Fehler ist uns bereits bekannt, wir arbeiten hart daran! Bitte haben Sie Geduld und unternehmen Sie nichts. Insbesondere versuchen Sie nicht, die App erneut zu installieren. " It is very urgent. Users wiĺl refuse to install this app. See here: https://www.bedienungsanleitung24.de/frage/corona-app-fehler-mit-google-api-10 I know about the beaurocratic obstacles to publish a new release or even hotfix but you will lose thousands or millions of users! |
As much as I would love to do that, simply deleting comments will also be taken very negatively (and please, watch your language). I can only state again that the issue is identified: #737 (comment) Hence, we want to thank you all again for your input and will inform you when a fix is available. Until then, this discussion will be locked to avoid further derailing. |
Thank you all again for your input. As we receive plenty confirmation that the error is gone with the latest Exposure Notification Framework version (https://www.coronawarn.app/de/faq/#ENF_version), we will accordingly close this issue. If you still experience the issue despite running on the latest ENF version, please open a new issue in this repository! |
Auf Gerät mit Android 6.0
Scan 24.06.2020.pdf
Internal Tracking ID: EXPOSUREAPP-1714
The text was updated successfully, but these errors were encountered: