S smileeomar Member Jan 9, 2012 #1 i have a problem that when i want to update my app(with original certificate) in market it shows (Market does not accept apks signed with the debug certificate. Create a new certificate that is valid for at least 50 years.) and if i creat new certificate it show The apk must be signed with the same certificates as the previous version. what can i do please
i have a problem that when i want to update my app(with original certificate) in market it shows (Market does not accept apks signed with the debug certificate. Create a new certificate that is valid for at least 50 years.) and if i creat new certificate it show The apk must be signed with the same certificates as the previous version. what can i do please
Erel B4X founder Staff member Licensed User Longtime User Jan 9, 2012 #2 For some reason you appear as an unlicensed user in the forum. Please contact [email protected] in order to fix it. Upvote 0
For some reason you appear as an unlicensed user in the forum. Please contact [email protected] in order to fix it.
J johnaaronrose Active Member Licensed User Longtime User Sep 7, 2012 #3 Unlicensed user? Erel said: For some reason you appear as an unlicensed user in the forum. Please contact [email protected] in order to fix it. Click to expand... I have the same problem as smileeomar, namely Google Play objecting to the .apk: as in attached screenshot. As you can see from the attached mail message text file, I purchased it on 19 June 2012. View attachment Basic4android_License.txt Upvote 0
Unlicensed user? Erel said: For some reason you appear as an unlicensed user in the forum. Please contact [email protected] in order to fix it. Click to expand... I have the same problem as smileeomar, namely Google Play objecting to the .apk: as in attached screenshot. As you can see from the attached mail message text file, I purchased it on 19 June 2012. View attachment Basic4android_License.txt
Erel B4X founder Staff member Licensed User Longtime User Sep 9, 2012 #4 You are using the debug signing key. See this tutorial: Signing your application before uploading to Android market Upvote 0
You are using the debug signing key. See this tutorial: Signing your application before uploading to Android market
J johnaaronrose Active Member Licensed User Longtime User Sep 9, 2012 #5 Version Name Erel said: You are using the debug signing key. See this tutorial: Signing your application before uploading to Android market Click to expand... I've followed the tutorial & created a new keystore file for my app & then compiled the app again to create a new .apk file. When I now try to upload the .apk file, I get "Google Play requires versionName to be set in AndroidManifest.xml". I've looked at the AndroidManifest.xml file in the project's Objects folder (presumably the same as the one in the .apk file because they have the same time & date stamp) & it shows versionName as "" (versionCode is 1 i.e. the same as I set from B4A's Project - Application Version menu entry). What do I do? Last edited: Sep 9, 2012 Upvote 0
Version Name Erel said: You are using the debug signing key. See this tutorial: Signing your application before uploading to Android market Click to expand... I've followed the tutorial & created a new keystore file for my app & then compiled the app again to create a new .apk file. When I now try to upload the .apk file, I get "Google Play requires versionName to be set in AndroidManifest.xml". I've looked at the AndroidManifest.xml file in the project's Objects folder (presumably the same as the one in the .apk file because they have the same time & date stamp) & it shows versionName as "" (versionCode is 1 i.e. the same as I set from B4A's Project - Application Version menu entry). What do I do?
Erel B4X founder Staff member Licensed User Longtime User Sep 9, 2012 #6 See Project -> Application Version. Upvote 0
J johnaaronrose Active Member Licensed User Longtime User Sep 9, 2012 #7 Problem solved Erel said: See Project -> Application Version. Click to expand... Thanks, Erel. I set Project-ApplicationVersion-VersionString to 1 which resulted in the versionName being 1: I didn't expect that VersionString would become versionName. Uploaded OK to Google Play. PS AndroidManifest.xml now shows: android:versionCode="1" android:versionName="1" Upvote 0
Problem solved Erel said: See Project -> Application Version. Click to expand... Thanks, Erel. I set Project-ApplicationVersion-VersionString to 1 which resulted in the versionName being 1: I didn't expect that VersionString would become versionName. Uploaded OK to Google Play. PS AndroidManifest.xml now shows: android:versionCode="1" android:versionName="1"