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?
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?
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 am working on a project that will work on android devices and will convert them in kiosk. So at this moment I am doing R&D on Kiosk mode, but there is very little help on it. But I came across different things. These are using DPM, Using EMM or Using Android Management API
I just wanted to do following things to ship my app to my clients.These objectives are as follow
If client is installing my app, he should follow simple steps (like android permissions) to make my app as default app.
While following simple steps, my app must make android device as Kiosk and should make my app unable to exit by clients user.
My app must be able to clear kiosk mode from device so that client can use his device as simple device
The most important thing is, we are not shipping devices with our app and we may not have any physical access to the client device and client may not be so much technical. So app must do all things
**So from the perspective of these above 4 points , what is best for me please share your knowledge. What will be best for me to go with? Please help me as this is so much confusing...
**
Fully managed mode
In fully managed mode the entire device is managed and the device needs to be factory reset before setup. To set up a device in fully managed mode you need to use a QR code.
For devices running Android 7.0 or above:
Turn on a new or factory-reset device.
Tap the same spot on the welcome screen six times to enter QR code mode. Connect to a WiFi network.
Scan the QR code.
For devices running Android 6.0:
Turn on a new or factory-reset device.
Follow the setup wizard and enter your Wi-Fi details.
When prompted to sign in, enter afw#setup.
Tap Next, and then accept the installation of Android Device Policy.
Scan the QR code.
Work profile mode
In work profile mode corporate apps and data are kept secure in a self-contained work profile while the user keeps control of the rest of the device. To set up a work profile you can either use a QR code or an enrollment link.
Using the enrollment link:
Make the link accessible on the device (send it via email or put it on a website).
Open the link.
Or using the QR code:
Go to Settings > Google.
Tap "Set up your work profile".
Scan the QR code.
What's next?
By now you should have a managed device configured with a basic policy, but there's much more you can do with the Android Management API
for more info : https://developers.google.com/android/work/release-solution
Hi I have developed an web application using google app engine, for google shared domain contact, Its working fine when I am running it in the localhost but when I deploy that application into google app engine it showing warning screen before user conforming for consent(as shown in the image).
I am using 2 scope http://www.google.com/m8/feeds/contacts/ and https://www.googleapis.com/auth/userinfo.email. when I try to add a user information in the google shared contact I am getting a exception message as www.google.com. How can I resolve the problem? am i need to verify my application in the oauth_app_verification. Can any one solve this?
Thank you.,
You need to go through the verification process before you launch your app. This new process came recently to protect user's data. You can start the verification by submitting this form but before it is recommended to follow steps here
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