I created a GCP App Engine (AE) project using Java 11. Once the AE project was created, I then linked it to Firebase (as opposed to creating natively through Firebase to begin with). Everything worked fine.
Today I deleted the Firebase account thinking it would keep original AE project, since I thought it was simply an add-on to my core AE project. I was wrong. Both the AE project and the Firebase account were deleted. I restored both through the GCP admin screen and the site came back up (both the AE project and Firebase functionality).
The problem now is that I can't deploy new versions of my code with gcloud app deploy. The build logs (on GCP's end) list the following error:
Step #3 - "analyzer": Already have image (with digest): us.gcr.io/gae-runtimes/buildpacks/java11/builder:java11_20200816_11_0_RC00
Step #3 - "analyzer": ERROR: failed to initialize cache: failed to create image cache: accessing cache image "us.gcr.io/my-project-dev-287623/app-engine-tmp/build-cache/ttl-7d/default/buildpack-cache:latest": connect to repo store 'us.gcr.io/my-project-dev-287623/app-engine-tmp/build-cache/ttl-7d/default/buildpack-cache:latest': GET https://us.gcr.io/v2/my-project-dev-287623/app-engine-tmp/build-cache/ttl-7d/default/buildpack-cache/manifests/latest: DENIED: Permission denied for "latest" from request "/v2/my-project-dev-287623/app-engine-tmp/build-cache/ttl-7d/default/buildpack-cache/manifests/latest".
Now I'm locked out from deploying any new code. Any ideas?
This issue was resolved when I enabled billing for my account. Please check if you have billing enabled/linked billing account for your project.
I want to point out a misunderstanding in your question, I forgot to mention it in my first message. There is NO link GCP project to the Firebase project. Firebase project IS a Google Cloud project. That is why when you delete the Firebase project, the GCP project gone. it is intended behavior. The way you mean link, it is actually to add Firebase services to the current GCP project
It is certain that the permission error. You need to grant permission to the docker. Also it may caused by the ' Cloud Build API', checked if ' Cloud Build API' has been enabled and try to disable it and then enable it. It may help. Let me know if the issue continues
If your billing and Build API are enabled please check this. After the end of the trial period, Google asks to Upgrade account to enable its services. Google shows a notification bar to do it on top of the Cloud Console.
Due to payment failure in my case. There was a pending payment of $0.01 for previous month & payment failed as the minimum payment is $10. I have paid $10 in advance & working fine.
Related
Your app is uploading users' Installed Application information to https://cloudconfig.googleapis.com without disclosing it in the privacy policy in Play Console.
I have searched in my project but there is no trace of the collecting the data using the link, indeed I use firebase SDK. Expecting a reason for rejection, when we use the same google products in our projects.
I have implemented the Android's in-app update API into my android application by following the steps given by Official documentation: Google Official Document and Google Official Document and now I want to test the in-app update flow with my QA build variant.
I am getting an error while trying to upload the android QA build variant into the internal app sharing upload page (internal app sharing) i.e. internal testing track of Google play console.
I am not sure but I think this happens because of different application id (i.e. package name) as I append .qa suffix to original application id. (applicationIdSuffix '.qa')
Is there any way to upload the QA build into the testing track of Google play console by keeping suffix to application id.
Also, the official document says that "To set the priority for an update, use inAppUpdatePriority field under Edits.tracks.releases in the Google Play Developer API. Priority can only be set when rolling out a new release, and cannot be changed later." Does that mean I won't be able to test the update priority with QA build environment and thus the immediate update?
Is there any way where I can test all the above things? Please help...!
I've made a chat app that uses Firebase's feature Real-time database.
I face a problem with google authentication. The problem started when I downloaded the app from the Play Store, the authentication was working perfectly when I was running the app in debug mode. When users try to sign in they get a toast message code:10 message:10.
I would like to note here that: I've added the SHA1 fingerprint. How can I solve this?
*Not sure if this is helpful but I've followed step by step this tutorial
You need three keys in order to make it work:
The debug key. Informations here.
The release key. Informations here.
Google Play App signing key. Informations here.
All these keys are needed in order to make the sign-in process work.
Other informations here.
After generating SHA1 for release key, I forgot downloading the new google-service.json file that caused the same error.
Make sure you follow the instruction https://developers.google.com/android/guides/client-auth to generate and add debug/release SHA1 to firebase console and download google-service.json after updated.
If you use Use app signing by Google Play option, you need an additional step:
After uploading app into google play console, go to Release management > App signing, copy SHA1 and paste to firebase console
Update
In the new google play console, the App signing key can be found as following:
Setup > App signing
Make sure you have added signed SHA1. If you are using debug one then it will not gonna work for live apk.
You need to put "debug.keystore" in this path C:\Users\USER_FOLDER_NAME.android
then in Android studio follow the below steps
1. Run your project
2. Click on Gradle menu
3. Expand Gradle Tasks tree
4. Double click on android -> signingReport
You can see SHA in Run Tab
for more information see link
For me the problem was that i registered app and enabled google signin on Firebase console but I was testing with the debug version of app which has slightly different package name (same name but ended with .debug) so it was not working because the debug app is not yet registered. so additionally to my release app i also added the debug app to the firebase project for the app and it generated it's own google-services.json which i download and set to src/debug/google-services.json.
I believe this might be useful to some one else.
After doing login in bluemix I tried to upload a java artifact to bluemix with the Cloud Foundry java buildpack and I always get this message;
FAILED Authentication has expired. Please log back in to
re-authenticate.
I have tried to logout and login many times (using "manual account login" and "api key login"). Login is always OK but the error persists. This is the bluemix login result
API endpoint: https://api.eu-de.bluemix.net (API version: 2.92.0)
Region: eu-de
User: irivera#tripbru.com
Account: Account name (account id) <-> other
Resource group: default
Org: selected org
Space: selected space
Also I checked the time sync and is synchronised with ntp (no problem).
I´m in spain and trying to upload to Bluemix Germany
Tried to uninstall bluemix client deleting all files before and no result
This problem began yesterday, but just one hours before I uploaded a lot of artifacts in distinct apps without any problem (including the "now in error app")
Solved with a "trick". Seems to exist any "intermitent" problem with apps already deployed to bluemix.
First, delete the app from control panel (or remove with CLI). You have to ensure that not only the app was deleted, also that the route must not exists (I think that this is the real problem).
After clearing all "records" of the already deployed app, the new version can be deployed again without problems.
Now this problem happens once or twice a week. it´s not a solution, but at least I can continue deploying app versions
In Debug mode, Google Play Games shows it's loading screen and I can even log in. However, afterwards I am receiving this error in a clean message box:
The application is incorrectly configured. Check that the package name and signing certificate match the client ID created in Developer Console. Also, if the application is not yet published, check that the account you are trying to sign in with is listed as a tester account. See logs for more information.
In Release mode, the game crashes and I am receiving this error in Android Studio:
Access Not Configured. The API (Google Play Game Services API) is not enabled for your project. Please use the Google Developers Console to update your configuration.
In Google Play Developer Console, all the marks are ticked. I don't understand why it is not working. Should I do something with the SHA key or client ID?
I did not publish my settings yet, but it says The Google Play game services settings are ready to test. I use my developer account as test account on the same device as I am testing on.
I was using the wrong SHA1 keys. I had to create a new GPGS Game and perform step 3C on this page: https://developers.google.com/games/services/console/enabling