Hi ,
I am trying to build with SideKick and upload to android market . But the error which I receive is on upload in the market is
You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer CERT.RSA): No APK Signature Scheme v2 signature from this signer ERROR (APK Signature Scheme v2 signer #0): No JAR signature from this signer10 Answers, 1 is accepted
Rank 1
Fixed using the recommendations from
https://docs.nativescript.org/publishing/publishing-android-apps#certificates
I am glad to hear that the problem with the application upload is resolved.
Let me know if I could assists you further.
Regards,
nikolay.tsonev
Progress Telerik
Rank 1
Hello,
I am facing the exact same error, whereas I have already successfully released previous version of my app before.
I am sure that my relase key is the right one, because this is the one that I used to publish previous version.
I don't know why, but now when I run "tns build android --release --key-store-path my-release-key.jks --key-store-password myPassword --key-store-alias myAlias --key-store-alias-password myPassword" and then upload the generated apk, Google is throwing me this error.
Do you have any idea why ?
Regards,
Matt
Rank 1
Rank 1
Thank you for contacting us,
We reviewed your comment, however, was unable to recreate this behavior while using latest NativeScript CLI 3.4. Could you provide again the exact error, which is returned from Google as well as some more info about your environment(CLI, modules, runtime versions)?
In the meantime, I would suggest trying generating a new certificate and to try signing the app again.
Also, could you provide info if the suggestion provided by Dimitar resolves the case?
Let me know if I could assist you further.
Regards,
nikolay.tsonev
Progress Telerik
Rank 1
Wow that is weird, this morning i tried to set up webpack on my project, because I am having lot of pain to get my project working with WebPack. So I changed some settings in my files, especially the application name and the activity name in the android manifest, and also the packages version in package.json. Now I just tried to rebuild my app for release, and this is correctly signed, so I don't know what was the point, but that's working now !
Unfortunately I am still unable to run my app with webpack option such as uglify or bundle.
I know that is not the topic of this discussion, and I have also opened an issue about this on github, but if you have some indications to help me to get webpack builds working, I will appreciate this !
If I understand you correctly in your current project version you could build and deploy it while using the run command, however, you are facing a problem with build while webpack and uglify option is used.
We tested this case with our nativescript-sdk-examples-ng sample project, however, was unable to recreate an issue. Regarding that, please provide more info about your environment(CLI, modules, runtime versions) and the exact steps, which you are using while building the app with webpack.
It will also help if you send us your project, which will allow us to investigate, what is causing this problem.
Regards,
nikolay.tsonev
Progress Telerik
I would like to let you know that we are closing UI for NativeScript Forum section in Telerik Admin in favor of NativeScript forum.
Since UI for NativeScript is free for using we consider that the best place for discussions and for questions will be the official NativeScript forum.
Thank you in advance for cooperation.
Regards,
nikolay.tsonev
Progress Telerik