You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
I'm filing this for recording keeping purposes, the bug has been identified and fixed however.
When someone tries to install the app on their phone (that hasn't enabled developer options, and requires certificate validation to install) it would prevent the installation giving a certificate invalidation error. The bug was that even after the APK was zip aligned, it wouldn't rename itself.
Two human errors also occurred to result in this problem. The first was failure to identify the process used to align and sign the APKs (jarsigner or apksigner) as a result when I saw the result of the build script bug, I would attempt to resign them which you can't do after using apk signer because that invalidates the certificate (thus creating this problem).
The second error was using a tool to identify the signature details within the APK, which through false positives because it wasn't designed to support Signature Scheme v2 (thus the run around).
The text was updated successfully, but these errors were encountered:
I'm filing this for recording keeping purposes, the bug has been identified and fixed however.
When someone tries to install the app on their phone (that hasn't enabled developer options, and requires certificate validation to install) it would prevent the installation giving a certificate invalidation error. The bug was that even after the APK was zip aligned, it wouldn't rename itself.
Two human errors also occurred to result in this problem. The first was failure to identify the process used to align and sign the APKs (jarsigner or apksigner) as a result when I saw the result of the build script bug, I would attempt to resign them which you can't do after using apk signer because that invalidates the certificate (thus creating this problem).
The second error was using a tool to identify the signature details within the APK, which through false positives because it wasn't designed to support Signature Scheme v2 (thus the run around).
The text was updated successfully, but these errors were encountered: