Open abeljus opened 2 years ago
I was able to get around this by using apksigner
instead of calabash-android
for signing the app.
Instead of resigning the app with calabash-android resign myapp.apk
you can try to do the following:
bundle exec calabash-android build <path_to_apk>
apksigner sign --ks <path_to_debug_keystore> <path_to_apk>
Just make sure that you're signing the app with the same keystore that is being used to sign the test server.
I'm trying to install and run a debug APK with Calabash-android, but it is failing because the scheme of the signature.
My original APK is signed with the debug keystore using scheme v2 (signed when building it via gradle):
However, it cannot be used as it is with calabash-android (getting error No signature files found in META-INF. Cannot proceed.), so I need to resign it with calabash:
Signing process seems to work fine, but when I try to install the just signed APK I'm getting this error:
When trying to verify the signature of the new APK, this is the result:
It seems that the latest Android versions need scheme v2 for the signatures, but calabash resign action is still using v1.
I have already tried creating a new debug.keystore, changing to different versions (ruby, calabash-android, etc.),..., but no success.
Any idea about how to make calabash sign the APK using scheme v2?
Thank you!