S sajadkharestani New Member May 6, 2020 #1 Hi A few days ago I asked Google Play to reset the b4a sign key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore If I compile the project with the created key In b4a 9.80 Displays message The key algorithm is not supported please help me thanks Attachments Screenshot (656).png 16.2 KB · Views: 346
Hi A few days ago I asked Google Play to reset the b4a sign key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore If I compile the project with the created key In b4a 9.80 Displays message The key algorithm is not supported please help me thanks
DonManfred Expert Licensed User Longtime User May 6, 2020 #2 sajadkharestani said: In b4a 9.80 Click to expand... No, you are using B4A 8.3. Upvote 0
S sajadkharestani New Member May 6, 2020 #3 DonManfred said: No, you are using B4A 8.3. Click to expand... yes Upvote 0
S sajadkharestani New Member May 6, 2020 #4 sajadkharestani said: Hi A few days ago I asked Google Play to reset the b4a sign key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore If I compile the project with the created key In b4a 9.80 Displays message The key algorithm is not supported please help me thanks Click to expand... when i compile the application with the debug key (b4a) and sign the application output with Google Guide (apksigner) SHA1 debug key does not change and SHA1 the new key does not replace the debug key please help me thanks Upvote 0
sajadkharestani said: Hi A few days ago I asked Google Play to reset the b4a sign key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore If I compile the project with the created key In b4a 9.80 Displays message The key algorithm is not supported please help me thanks Click to expand... when i compile the application with the debug key (b4a) and sign the application output with Google Guide (apksigner) SHA1 debug key does not change and SHA1 the new key does not replace the debug key please help me thanks
Erel B4X founder Staff member Licensed User Longtime User May 7, 2020 #5 First upgrade to v9.80. Secondly don't use the debug key. Upvote 0
S sajadkharestani New Member May 7, 2020 #6 Erel said: First upgrade to v9.80. Secondly don't use the debug key. Click to expand... I use b4a 9.80 If I compile the project with the created key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore (I asked Google Play to reset the b4a sign key) Displays message The key algorithm is not supported Upvote 0
Erel said: First upgrade to v9.80. Secondly don't use the debug key. Click to expand... I use b4a 9.80 If I compile the project with the created key I made the sign key with this guide: keytool -genkeypair -alias b4a-keyalg RSA -keysize 2048 -validity 9125 -keystore b4a.keystore keytool -export -rfc -alias b4a-file upload_certificate.pem -keystore b4a.keystore (I asked Google Play to reset the b4a sign key) Displays message The key algorithm is not supported
Erel B4X founder Staff member Licensed User Longtime User May 7, 2020 #7 Start from the beginning. Have you already uploaded the app to Google Play? Upvote 0