Benjamin_Loison/PlayStore
1
0
Code Issues 5 Packages Projects Wiki

Mise à jour impossible Element on Xiaomi Mi A3 #2

New Issue
Open
opened 2024-04-09 18:17:45 +02:00 by Benjamin_Loison · 7 comments
Benjamin_Loison commented 2024-04-09 18:17:45 +02:00
Owner
Copy Link

image

I tried unsuccessfully one more time.

découvrez ces solutions de dépannage courantes: https://support.google.com/googleplay/answer/14122894

Envoyer des commentaires just closes the window.

The app is on internal storage.

I unsuccessfully tried to stop the app before updating it.

Could check adb logs.

Tracked at Benjamin-Loison/element-android/issues/12.

+26

![image](/attachments/5286c46e-3c2d-42c6-a5b1-3e0f61c70a00) I tried unsuccessfully one more time. `découvrez ces solutions de dépannage courantes`: https://support.google.com/googleplay/answer/14122894 `Envoyer des commentaires` just closes the window. The app is on internal storage. I unsuccessfully tried to stop the app before updating it. Could check adb logs. Tracked at [Benjamin-Loison/element-android/issues/12](https://github.com/Benjamin-Loison/element-android/issues/12). +26
image.png
99 KiB
Benjamin_Loison changed title from `Mise à jour impossible` Element to `Mise à jour impossible` Element on Xiaomi Mi A3 2024-04-09 18:18:20 +02:00
Benjamin_Loison commented 2024-04-09 18:39:44 +02:00
Author
Owner
Copy Link
adb logcat
Output: 
04-09 18:24:35.712 21099 21099 I Finsky  : [2] adjd.k(336): im.vector.app is installed but certificate mismatch
04-09 18:25:07.938  1280  1683 W PackageManager: Package im.vector.app signatures do not match previously installed version; ignoring!
04-09 18:25:07.965 21099 21099 E Finsky  : [2] sot.d(22): Submitter: commit error message INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package im.vector.app signatures do not match previously installed version; ignoring!

Current version is 1.6.12 and try to install 1.6.14 according to play.google.com/store/apps/details?id=im.vector.app.

adb shell getprop ro.product.cpu.abi

arm64-v8a

Are there Play Store APK archivers to investigate when the signature changed? element-android/releases should already be a good start.

apksigner verify --print-certs -v vector-gplay-arm64-v8a-release-signed.apk

m vector-gplay-arm64-v8a-release-signed.apk; wget 'https://github.com/element-hq/element-android/releases/download/v1.6.12/vector-gplay-arm64-v8a-release-signed.apk' && apksigner verify --print-certs -v vector-gplay-arm64-v8a-release-signed.apk

Play Store:

Returns for 1.6.10: 
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: O=New Vector Ltd.
Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f
Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919
Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd
Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964
Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823
For 1.6.12: 
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: O=New Vector Ltd.
Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f
Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919
Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd
Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964
Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823
For 1.6.14: 
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: O=New Vector Ltd.
Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f
Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919
Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd
Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964
Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823

Do not seem problematic.

F-Droid:

For 1.6.10: 
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=FDroid, OU=FDroid, O=fdroid.org, L=ORG, ST=ORG, C=UK
Signer #1 certificate SHA-256 digest: b15d9b673b55b9fe656190794d872e59ec5b85b3bfb8a76b9442f17eae2887c9
Signer #1 certificate SHA-1 digest: 372a498114d314ac94d05306e395f3b51acb481a
Signer #1 certificate MD5 digest: b2a98d494b9299de2b7cb72572c6b9ec
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: f4f6248fe5c24fd8e9acb2fec1e689575cca0de8d6cda4c5452adab799b6aa75
Signer #1 public key SHA-1 digest: 3762e7f4e50614eb890a6fe8d1044ffea6b4c0c0
Signer #1 public key MD5 digest: abef85c647613235f52794afb98e1ded
For 1.6.12: 
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=FDroid, OU=FDroid, O=fdroid.org, L=ORG, ST=ORG, C=UK
Signer #1 certificate SHA-256 digest: b15d9b673b55b9fe656190794d872e59ec5b85b3bfb8a76b9442f17eae2887c9
Signer #1 certificate SHA-1 digest: 372a498114d314ac94d05306e395f3b51acb481a
Signer #1 certificate MD5 digest: b2a98d494b9299de2b7cb72572c6b9ec
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: f4f6248fe5c24fd8e9acb2fec1e689575cca0de8d6cda4c5452adab799b6aa75
Signer #1 public key SHA-1 digest: 3762e7f4e50614eb890a6fe8d1044ffea6b4c0c0
Signer #1 public key MD5 digest: abef85c647613235f52794afb98e1ded

I have not noticed an on-going issue or merge request on fdroiddata and the last version is 1.6.12 in this repository, so without any potential F-Droid additional delay.

It seems that anyone manual update is not welcomed on F-Droid.

Related to element-android/issues/8803 and element-android/issues/8708.

Related to Benjamin_Loison/AuroraStore/issues/6.

```bash adb logcat ``` <details> <summary>Output:</summary> ``` 04-09 18:24:35.712 21099 21099 I Finsky : [2] adjd.k(336): im.vector.app is installed but certificate mismatch 04-09 18:25:07.938 1280 1683 W PackageManager: Package im.vector.app signatures do not match previously installed version; ignoring! 04-09 18:25:07.965 21099 21099 E Finsky : [2] sot.d(22): Submitter: commit error message INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package im.vector.app signatures do not match previously installed version; ignoring! ``` </details> Current version is 1.6.12 and try to install 1.6.14 according to [play.google.com/store/apps/details?id=im.vector.app](https://play.google.com/store/apps/details?id=im.vector.app). ```bash adb shell getprop ro.product.cpu.abi ``` ``` arm64-v8a ``` Are there Play Store APK archivers to investigate when the signature changed? [element-android/releases](https://github.com/element-hq/element-android/releases) should already be a good start. ```bash apksigner verify --print-certs -v vector-gplay-arm64-v8a-release-signed.apk ``` ```bash m vector-gplay-arm64-v8a-release-signed.apk; wget 'https://github.com/element-hq/element-android/releases/download/v1.6.12/vector-gplay-arm64-v8a-release-signed.apk' && apksigner verify --print-certs -v vector-gplay-arm64-v8a-release-signed.apk ``` Play Store: <details> <summary>Returns for 1.6.10:</summary> ``` Verifies Verified using v1 scheme (JAR signing): true Verified using v2 scheme (APK Signature Scheme v2): true Verified using v3 scheme (APK Signature Scheme v3): true Verified using v4 scheme (APK Signature Scheme v4): false Verified for SourceStamp: false Number of signers: 1 Signer #1 certificate DN: O=New Vector Ltd. Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919 Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256 Signer #1 key algorithm: RSA Signer #1 key size (bits): 2048 Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964 Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823 ``` </details> <details> <summary>For 1.6.12:</summary> ``` Verifies Verified using v1 scheme (JAR signing): true Verified using v2 scheme (APK Signature Scheme v2): true Verified using v3 scheme (APK Signature Scheme v3): true Verified using v4 scheme (APK Signature Scheme v4): false Verified for SourceStamp: false Number of signers: 1 Signer #1 certificate DN: O=New Vector Ltd. Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919 Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256 Signer #1 key algorithm: RSA Signer #1 key size (bits): 2048 Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964 Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823 ``` </details> <details> <summary>For 1.6.14:</summary> ``` Verifies Verified using v1 scheme (JAR signing): true Verified using v2 scheme (APK Signature Scheme v2): true Verified using v3 scheme (APK Signature Scheme v3): true Verified using v4 scheme (APK Signature Scheme v4): false Verified for SourceStamp: false Number of signers: 1 Signer #1 certificate DN: O=New Vector Ltd. Signer #1 certificate SHA-256 digest: f3ff38d2e5a63884864a4e0d45c53b198e7e39c0505bd963f555d6532deabf5f Signer #1 certificate SHA-1 digest: c93e027b9f69ca7b401185594977bc64b8559919 Signer #1 certificate MD5 digest: 5e8f3f162b135c6144b5f5f226eea256 Signer #1 key algorithm: RSA Signer #1 key size (bits): 2048 Signer #1 public key SHA-256 digest: f3dc3acf7a83003985ff0241e1cc0cdfc7a0134cf174c3560a5091b18c6092cd Signer #1 public key SHA-1 digest: f7006a255b299627bbeb770782eb4fef6f2be964 Signer #1 public key MD5 digest: b64387d3c052050425b05909f3658823 ``` </details> Do not seem problematic. F-Droid: <details> <summary>For 1.6.10:</summary> ``` Verifies Verified using v1 scheme (JAR signing): true Verified using v2 scheme (APK Signature Scheme v2): true Verified using v3 scheme (APK Signature Scheme v3): true Verified using v4 scheme (APK Signature Scheme v4): false Verified for SourceStamp: false Number of signers: 1 Signer #1 certificate DN: CN=FDroid, OU=FDroid, O=fdroid.org, L=ORG, ST=ORG, C=UK Signer #1 certificate SHA-256 digest: b15d9b673b55b9fe656190794d872e59ec5b85b3bfb8a76b9442f17eae2887c9 Signer #1 certificate SHA-1 digest: 372a498114d314ac94d05306e395f3b51acb481a Signer #1 certificate MD5 digest: b2a98d494b9299de2b7cb72572c6b9ec Signer #1 key algorithm: RSA Signer #1 key size (bits): 2048 Signer #1 public key SHA-256 digest: f4f6248fe5c24fd8e9acb2fec1e689575cca0de8d6cda4c5452adab799b6aa75 Signer #1 public key SHA-1 digest: 3762e7f4e50614eb890a6fe8d1044ffea6b4c0c0 Signer #1 public key MD5 digest: abef85c647613235f52794afb98e1ded ``` </details> <details> <summary>For 1.6.12:</summary> ``` Verifies Verified using v1 scheme (JAR signing): true Verified using v2 scheme (APK Signature Scheme v2): true Verified using v3 scheme (APK Signature Scheme v3): true Verified using v4 scheme (APK Signature Scheme v4): false Verified for SourceStamp: false Number of signers: 1 Signer #1 certificate DN: CN=FDroid, OU=FDroid, O=fdroid.org, L=ORG, ST=ORG, C=UK Signer #1 certificate SHA-256 digest: b15d9b673b55b9fe656190794d872e59ec5b85b3bfb8a76b9442f17eae2887c9 Signer #1 certificate SHA-1 digest: 372a498114d314ac94d05306e395f3b51acb481a Signer #1 certificate MD5 digest: b2a98d494b9299de2b7cb72572c6b9ec Signer #1 key algorithm: RSA Signer #1 key size (bits): 2048 Signer #1 public key SHA-256 digest: f4f6248fe5c24fd8e9acb2fec1e689575cca0de8d6cda4c5452adab799b6aa75 Signer #1 public key SHA-1 digest: 3762e7f4e50614eb890a6fe8d1044ffea6b4c0c0 Signer #1 public key MD5 digest: abef85c647613235f52794afb98e1ded ``` </details> I have not noticed an on-going issue or merge request on [fdroiddata](https://gitlab.com/fdroid/fdroiddata) and [the last version is 1.6.12 in this repository](https://gitlab.com/fdroid/fdroiddata/-/blob/4c22b1a4131e8fc4f69a1cdcd2c879366f0247d0/metadata/im.vector.app.yml?page=3#L2502), so without any potential F-Droid additional delay. It seems that [anyone manual update is not welcomed on F-Droid](https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/im.vector.app.yml#L2493-L2497). Related to [element-android/issues/8803](https://github.com/element-hq/element-android/issues/8803) and [element-android/issues/8708](https://github.com/element-hq/element-android/issues/8708). Related to [Benjamin_Loison/AuroraStore/issues/6](https://gitlab.com/Benjamin_Loison/AuroraStore/-/issues/6).
Benjamin_Loison commented 2024-06-23 17:09:45 +02:00
Author
Owner
Copy Link

Related to Benjamin-Loison/android/issues/25.

Related to [Benjamin-Loison/android/issues/25](https://github.com/Benjamin-Loison/android/issues/25).
Benjamin_Loison commented 2024-08-18 01:58:19 +02:00
Author
Owner
Copy Link

Same issue following Benjamin-Loison/android/issues/25.

Same issue following [Benjamin-Loison/android/issues/25](https://github.com/Benjamin-Loison/android/issues/25).
Benjamin_Loison commented 2024-08-18 02:29:41 +02:00
Author
Owner
Copy Link

Aurora Store does not seem to have the issue, see Benjamin_Loison/AuroraStore/issues/14.

Aurora Store does not seem to have the issue, see [Benjamin_Loison/AuroraStore/issues/14](https://gitlab.com/Benjamin_Loison/AuroraStore/-/issues/14).
Benjamin_Loison commented 2024-10-09 22:41:36 +02:00
Author
Owner
Copy Link

Related to Benjamin_Loison/vlc-android/issues/4.

Related to [Benjamin_Loison/vlc-android/issues/4](https://code.videolan.org/Benjamin_Loison/vlc-android/-/issues/4).
Benjamin_Loison commented 2024-11-11 14:38:58 +01:00
Author
Owner
Copy Link

Unlike F-Droid, PlayStore does not check for difference in app APK signature before attempting to download and then failing to install due to signature mismatch.

Source: termux-boot/commit/613dc9893f672313e2c572c0089ece7475e04f5b

> Unlike F-Droid, PlayStore does not check for difference in app APK signature before attempting to download and then failing to install due to signature mismatch. Source: [termux-boot/commit/613dc9893f672313e2c572c0089ece7475e04f5b](https://github.com/termux/termux-boot/commit/613dc9893f672313e2c572c0089ece7475e04f5b)
Benjamin_Loison commented 2024-11-18 10:40:45 +01:00
Author
Owner
Copy Link

Maybe related to Benjamin_Loison/tchap-android/issues/2.

Maybe related to [Benjamin_Loison/tchap-android/issues/2](https://codeberg.org/Benjamin_Loison/tchap-android/issues/2).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Benjamin_Loison/PlayStore#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?