I send Android build with build hint android.appBundle=true.
And upload the aab file to google play for creating internal testing release with the option "Let Google manage and protect your app signing key (recommended)".
But I get the error "The Android App Bundle was not signed."
I also try "Export and upload a key from Java keystore" option but still failed with the same error.
Thanks.
Did you create an Android Certificate before creating the build?
If you don't create a certificate we print a warning but let you send a debug build. This probably won't work for Google Play though.
Related
i have a react site that am trying to deploy to azure app service (free tiers windows) plan.
i am using VS-Code's Azure App service extention.
when i right click deploy to web app i get the error
11:44:47 AM amn-react-app: Starting deployment...
11:44:47 AM amn-react-app: Creating zip package...
11:53:39 AM amn-react-app: Zip package size: 298 MB
11:53:40 AM: Error: An error has occurred.
where to see the deployment logs to check what happened ?
update
following the update below i was able to see logs but they still not telling details.
I use vscode create a sample react project to test.
And I found, we can check delpoyment logs on portal.
Method 1
Method 2
I also try to use rest api to get deployments info, but failed because I don't find deployment id. If you are interested, you can also try.
Web Apps - Get Deployment
I have used PWA2APK to upload the first version of my React app to Google Play. It worked great. But every time I try to update the app by uploading a new version, I get the following:
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:
SHA1: *******************
and the certificate used to sign the APK you uploaded has fingerprint:
SHA1: **********************
Your APK or Android App Bundle needs to have the package name ****(name_of_previous_version)****.
You need to use a different version code for your APK or Android App Bundle because you already have one with version code 1.
Here's the steps I've been following:
For the first version: paste url to PWA2APK and download APK file. change well-know directory with the SHA from Google Play. Upload first version APK to Google Play. All is good.
Then, when I need to release a newer version of the app: change all of my files, paste url to PWA2APK. Change well-know file again (which this time has a new package_name). Download APK and try to upload to Google Play. That's when the above error shows.
Am I following the right procedure?
Should I just change the package_name to be the same as the previous version?
Does the downloaded APK file need to have its name changed before being uploaded to Google Play?
And by the way, The Google Play console tells me that Google is managing my app signing key.
The package name needs to be exactly the same as the previous versions
Your app needs to be signed as a release app and and have the same signing certificate used to sign it.
Seeing that you are using an online converter, this is probably the problem as it is generating you different package names and certificates.
I built a simple ReactJs app and tried using Google Cloud Build to deploy it as soon as I push a new commit to the master branch on Github.
For that I added an "On push to master" trigger and followed every step from here to configure my Google Cloud and Local Project. In the end I created a cloudbuild.yaml file with the following content:
After a new commit and push the cloud build logs a correct npm install and npm run build, but the firebase stops at the following step.
I didn't understand which file/directory is missing, nor how to fix it. Could anyone help me a little?
Thanks in advance.
So after a whole day of work I found out the problem. Apparently when you generate the firebase image mentioned in the tutorial all its files need to use End of line LF, but in windows it sets all of them to CRLF. I solved the problem using the WSL terminal in windows.
I will signin with google it's working but whenever I'll create release build it not working
GoogleErrorcode : DEVELOPERERROR
Please check if Google Play App Signing is enabled from the Google Play Console -> Release Management -> App Signing.
Please try below steps:
1] You have to copy the SHA1 from the 'App signing certificate' section and need to add it to the Firebase projects general settings section.
2] Afterward need to regenerate the json file and add it to the project.
3] Re-generate the apk and the error will get resolved.
If folks are still having this issue and have stumbled across this as i did. Here's what i figured out for my react native android firebase project
THERE ARE MULTIPLE SHA-1's TO ADD IN FIREBASE
1. SHA-1 For Release Variant
This is found in the Keystore file. You would have to add it to your Firebase Console Project Settings
a. Get release variant SHA-1 by running command below from you RN project root
$ cd android && ./gradlew signingReport
b. Add the release SHA-1 from here to your Firebase Console Project Settings
2.SHA-1 After you upload to google play store for testing / prod rollout
a .SHA-1 is found in the left nav of your google playstore console.
Setup -> App signing -> App signing key certificate
b. Add this to your Firebase Console Project Settings
for google sign in to work in testing / prod
Solved by adding release keystore SHA-1 to firebase console.
Use below command to create release SHA-1 and Add it to firebase console:
keytool -list -v -keystore {keystore_name} -alias {alias_name}
Note : Apk not need to create again.
Yesterday same problem occurred to me.
Google has released a new signing service in playstore publish console in which google will signin your app with his keystore. After signing , it will give you a new SHA which you have to add in your firebase account.
see the image for the better understanding
enter image description here
I have got a solution to this problem.
You have to put both SHA key i.e. SHA for debug Keystore file and SHA for release jks file, into the firebase project setting.
Go to: https://console.firebase.google.com/
Now choose your project
Click the setting button near Project Overview
Choose Project Setting
Enter both SHA1 (debug SHA1 and release SHA1) in SHA certificate fingerprint
Save it
Download the google-services.json file
Run npx react-native run-android --variant=release in terminal
It worked for me very well.
After than many time trying i got the solution.
In GoogleSignin.configure i was place android client it, that why i getting the error
Finally i will place the web client id(Here)
GoogleSignin.configure({
iosClientId: 'client ID',
webClientId: 'My Web client ID'
})
There is a new signing service from Google in the Playstore publish console, in which Google will sign your app with his keystore. After signing, it will give you a new SHA, which you need to connect to your Firebase account.
Go to Google play store ->
Release -> Setup -> App Integrity
Copy: SHA-1 certificate fingerprint from "App signing key certificate"
Add this into Firebase Project
Project Setting -> Select your app -> Add Fingerprints and Paste it here
I can't send a build to Codename One build server anymore. Previously, I was able to "Send Android Build" successful and download the apk. Now, for whatever unknown reasons, the "Send Android Build" just ended without any errors and no apk appears in the Dashboard. (Previously, it asked me something about a certificate. I had to click OK.). I tried multiple times and nothing worked.
Then, I created a new Codename One project (a sample project with native interface). Upon sending the Build (Send Android Build) it worked - it prompted me about the certificate and the build appeared in the Dashboard.
Immediately after that, I tried to send the build again (from my app under development), it was denied with a message that I can send only one build at one time. The error message included my email address, which means it indeed logged in using my account credentials.
After some time (when the sample app was build), I did the "Send Android Build" again, and it was the same: it failed silently and there's no clue.
What could have gone wrong? What settings should I look into?
I'm using IntelliJ IDEA 2017.1.
Thanks!
I digged further and found that there is a log message saying it has exceeded the size and I need to upgrade the account.
Well, Codename One should had put this up in a Dialog box instead of failing silently. :-)