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.
Related
We received an email titled "[Action Required] Remove the addApi(Drive.API) code from your apps that initialize the Google Drive Android API" informing us that on February 1, 2023, the Google Drive Android API will be fully turned off and that we would need to respond by removing any reference to addApi(Drive.API). We do not appear to use this API, but we see usages of the Google Drive API in the Google Cloud dashboard for our Android app project. This could very well be REST Drive API calls, but we're not seeing a way to confirm where these API calls are coming from.
Following the documentation's instructions exactly as written, it would appear that the only action needed would be to remove any usages of addApi(Drive.API).
So, We're looking for a confirmation that this is truly the only usage that would cause issues to leave in our Android app once the Android Drive API shuts down. Does anyone know?
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.
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...!
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
I use Google Game Services not in the first time, I have 2 apps using it and doing it ok.
Now I'm working on another app and found that even though it's connected to Google Play Game Services and shows me a user's name it can't use cloud save state feature.
My android app was published and then unpublished, so it is not a draft. Game (in Game Services Tab of Google Play Developer Console) also is published. I have two linked apps with the same package name and different SHA1 footprints: for debug eclipse and release version (as suggested by Google).
I've tried my old app on this emulator (genymotion) and it works and saves state.
I've double checked everything according to
https://developers.google.com/games/services/android/troubleshooting, but it looks that averything is ok.
But when trying to save app state both in release or debug apk I get the same STATUS_DEVELOPER_ERROR and in logcat I see the same message:
[97] a.a: Unexpected response code 403 for
https://www.googleapis.com/appstate/v1/states/3 Error executing
operation: Access Not Configured. The API is not enabled for your
project, or there is a per-IP or per-Referer restriction configured on
your API key and the request does not match these restrictions. Please
use the Google Developers Console to update your configuration.
Of course I've checked Google Developers Console and see that Google+ API, Google Play Game Services, Google Play Game Management and Drive API are on. I've even created a new Game (in Game Services Tab of Google Play Developer Console) and relinked my app to it, the same result: connection ok, yet STATUS_DEVELOPER_ERROR.
I'm trying to compare my new app with the previous, but I use the same IabHelper of Bruno Oliveira. And for my previous game Drive API is turned off, but cloud save works.
What did I forget?