From my Google Play console I linked a project. Then I created a service account. Still, when refreshing the console, it still says "There are no service accounts associated with your project."
Waited over 24 hours already. The purpose of all that is receipts validation.
Picture 1: a linked project:
Picture 2: service-account created:
I had the same problem, I fixed it this way:
When you create a service account in step 2, you need to select a role to grant this service account some permissions, although it shows the step is optional, but for some cases, it's not. If you skip this step, the newly created service account will not show up at the Google Play Console API access page, and you will get this error message, The current user has insufficient permissions to perform the requested operation when you run your code.
You much enable "Google Play Android Developer API" (one of Google Api & services) for your application via a credential!
Google supplies many API for developers can call them from their app. A credential same as a permit (3 types of credentials : API key (such as youtube), OAuth, Service Account)
If you never enable one API, it never shown on API Access page!
In my case:
Even if you have created a service account,
When you have already deleted the service account with the same name,
It appears to have been deleted from the IAM tab of Google Cloud Platform.
So it is assumed that it is not visible in the play console.
TODO:
Create a service account with a different name (I gave the owner permission in step2 when creating, Like Q Locker's answer.).
After creation, it was immediately exposed in the play console.
I faced the same issue because I selected a wrong project instead of the project for which the service account to be created. Please double check the project name in the drop-down at top of the page (after going to the link of Google Cloud Platform). By default the right project to be selected automatically. But if no project is selected beforehand and you are asked to select a project, then select the right project carefully. Otherwise the service account won't show up after completing the whole process.
Another thing to mention, although the project is supposed to be selected automatically, initially it didn't happen and I was given the available projects to select from. The project may appear in the recent projects, otherwise click the SELECT PROJECT link and find yourself.
Moreover when I additionally logged out and removed all the other Google accounts from the browser except the account which is used in Google Play Console. That time I was redirected to service account creation page with the correct project selected beforehand.
Make sure the project name on screen 1 and screen 2 are the same. In my case project name were different.
Screen 1: Main API Access page on Google Console
Screen 2: Google Cloud Platform page
Related
I am new in using google map, I have tried for a day. but when I try to create google map API key for my android project through web site https://cloud.google.com/maps-platform/?apis=maps
then I always failed to create API key like the image below:
am I do something wrong or it is just temporary problem from google ? or is there any alternative to crate API Key for Android Google Map ?
this error only appear on my specific google account, when switch to other gmail, this error never appear
Did you try these steps?
Login to Google with the sys admin email address of the 'G Suite'
account
Go here https://console.cloud.google.com/iam-admin/iam/organization
click on the identity tab on the left menu. (it created an identity)
click on the 'IAM' option on the left menu
Add billing account roles to the sys admin email by clicking on the
pencil icon to the right of that user name. (I assume you could
probably add another user here from the organisation and assign the
billing roles to them instead)
Go to the Gsuite admin: https://admin.google.com/ and click on 'Apps'
Then click on 'Additional Google services' and enable 'Google
developers console'
Then go to https://console.cloud.google.com/billing select your
organization from the 'Select an organization:' dropdown box
click on the 'add billing account' button in the middle of the screen
from
Enable Google Maps Platform error
This issue has been recognized in Google Maps Issue tracker and has been addressed. If you are still having issues with this concern, kindly star the issue and add a comment of the issue that you are experiencing with replication step as well.
It could have been something temporary. Do you get the same error now, when trying to follow the Get Started URL? https://cloud.google.com/maps-platform/?apis=maps
If so, a couple things to check:
Are you really logged in with a valid Google account when accessing this page? (since you mention a "specific google account", I assume this is not your issue here)
Are you maybe using a G Suite domain account, on which Google Developers Console access has been disabled?
1) If you are not logged in with a valid Google account, you will get this error. You can create a new non-gmail.com Google account on the following page:
https://accounts.google.com/signup/v2/webcreateaccount?hl=en-GB&flowName=GlifWebSignIn&flowEntry=SignUp&nogm=true
2) If you are logged in with a valid Google account, is that a G Suite account? If so, maybe the error happens because your domain admin disabled Google Developers Console access on your account. If so, here is how an admin can re-enable this service: https://stackoverflow.com/a/45621397/11316072.
Note: when the Get Started button doesn't work, you can go to the Google Developers Console directly to create a new project (https://console.cloud.google.com/project), create an API key ((https://console.cloud.google.com/apis/credentials?project=), enable the APIs you need (https://console.cloud.google.com/apis/library?project=), and enable billing on your project (https://console.cloud.google.com/billing/linkedaccount?project=).
I have two Google Analytics accounts A and B, each with their own properties which I am attempting to generate configuration files for (more specifically, google-services.json files) in order to use Google Analytics with my Android app. I'm using the Enable Google Services for your app wizard.
When you reach the Choose and configure services step, it should allow you to choose both a Google Analytics account and an Analytics Property from their associated selection boxes every time you run this wizard. The problem is that the selection box for choosing a Google Analytics Account only appears on the first run of this wizard, and afterwards becomes a pre-filled field that cannot be modified.
This means that if I generate a configuration file for a Property using Account A, I cannot generate another configuration file for a Property using Account B since the wizard pre-fills a non-modifiable text box with Account A, and only Account A's Properties appear in the next selection box.
How can I generate a google-services.json configuration file for a Property under a Google Analytics Account I cannot switch to?
I have admin access to both of these accounts, so this is not an issue.
The configuration file is necessary for Google Analytics to work once the app is released to the public (as described here).
Similar unsolved questions have been asked here for Android and here for iOS (both platforms use the same wizard to enable the Google Analytics service).
Managed to figure out a very simple workaround to solve my own question: remove yourself from the account you're stuck on, so the wizard is then forced to let you choose another account.
To achieve this:
Log into Google Analytics and choose the Admin tab.
In the ACCOUNT column, from the drop-down box, choose the account you were bound to (in the Enable Google Services wizard).
In the same column, choose User management.
Click the Remove myself from this account button.
Then go back to the Enable Google Services wizard again and you should now be able to select another account.
I hope this helps others at least until Google fixes the site, as this was a rather annoying problem to solve!
I figure out the solution for this issue is that we can move the account to trash. After we create an config file, restore the account.
Hope this may help
On this page Google staff gave an answer to this bug:
This is currently working as intended even though it may not seem so. There may be an update to fix this but in the meantime you can just copy an existing Configuration file and edit it. The only thing you need to change is the Analytics tracking ID value.
For example, in the configuration JOSN file you'll see an entry like:
"services": {
"analytics_service": {
"status": 2,
"analytics_property": {
"tracking_id": "UA-XXXXX-YY"
}
},
Replace the UA-XXXXX-YY value with the property ID (for the GA
Account) you want to use. You can use the Account Explorer to find the
correct property ID:
https://ga-dev-tools.appspot.com/account-explorer/
Note that Tracking ID and Property ID mean the same thing.
I am developing an Android app and I'd like to start testing out push notifications. From a code perspective, I'm all set. My current challenge is that I simply do not know how to get a Google Cloud Messaging API key from Google.
There are loads and loads of tutorials and videos online showing how this can be done in about 10 seconds but Google has recently updated it's developer center and none of the tutorials seem to apply any more. The current process seems very cumbersome and not at all similar to what I've seen online.
I realize that this barely passes as a programming question (if at all) but there is no way that I'm going to even begin to be able to develop anything without an API key from Google.
Is someone able to point me in the right direction?
CommonsWare was right about three years ago (2013). This is a revision to his answer.
Note: Even if you have already enabled any services and have API keys this will still work.
Log in to Google Services with your google account. (This is not the same as the Google Console)
Click on Pick a Platform
Click on Enable services for Android
Fill out the app name and package name
Select Cloud Messaging. (Or any other service you want. You can come back to this later and add more)
Click on Generate Configuration Files
Boom. Right there on top in the Cloud Messaging card under Server API key
Also, you will want to download the google-services.json file and copy it to the app/ or mobile/ module directory in your Android project
but Google has recently updated it's developer center and none of the tutorials seem to apply any more
:: sigh ::
That's yet more work for my next book update...
The current process seems very cumbersome and not at all similar to what I've seen online.
Bearing in mind that I am already set up with keys, and therefore may be seeing somewhat different stuff than would somebody with no keys:
Step #1: Log into https://cloud.google.com/console with your Google account
Step #2: In the navigation on the left, go into "APIs & auth > APIs"
Step #3: Find "Google Cloud Messaging for Android" and click the "OFF" button next to it (note: this might involve then agreeing to additional terms of service)
Step #4: In the navigation on the left, go into "APIs & auth > Registered apps"
Step #5: Wait a really long time, apparently.
Step #6: Click the red REGISTER APP button.
Step #7: Give the app a name and choose Web Application, then click Register
Step #8: Click the "Server Key" section for your server key
Google has updated their api console recently to Google Cloud Console.
In short terms , you need to create an Android application and pick Accessing APIs via a web server. this service has a detailed guide for that
The easiest way to configure GCM API key and Sender ID, is to Google login with your account and continue the Wizard : https://developers.google.com/mobile/add :)
To get FCM (Firebase cloud messaging) key for a web app
login into Firebase
Create a new app by clicking the big 'Add Project' button
Wait a few seconds and watch the circle chase its tail
Click "Add Firebase to your web app "
Copy the api key
My apologies for asking this question on Stackoverflow, but Google says that this is my only choice. I have a support package from Google in theory, but all attempts to get a PIN yield "Invalid Operation" (a different problem).
I am just trying to use the Google web page instructions to create an Android client Id for secure access to AppEngine Endpoints.
In the following Google instructions, steps 6 and 7 point me to non-existent user choices on the Google Cloud console.
Straight from the web page:
[https://developers.google.com/appengine/docs/java/endpoints/auth#Java_Creating_OAuth_20_client_IDs]
...
Creating an Android client ID
...
Open the Google Cloud Console. [https://cloud.google.com/console]
When your project appears in the projects pulldown menu, select it to make it the active project. [Selected the project from the table of projects]
Click APIs and Auth and select Registered Apps [No such selections exist; tried all links - nothing even close to on topic.]
If your app is not yet registered, select the Register App button. [No such link exists.]
…
I hope Google is listening and can help. My apologies to everyone else. I have no other way to contact Google.
I don't understand what's the issue, as the instruction provided is correct and that's how we generated the client ID for our projects:
Now I managed to sign the apk (using Eclipse Android Tools) and adb install .. to the device for testing.
But this removed the debug function, e.g. "step over" which make problem tracing much more difficult.
Is it possible to debug the inapp billing using Eclipse?
Unfortunately I don't think there is any way to step debug, I have just been using print outputs. This is due to the fact that you have to sign your app with a release key in order for it to communicate properly with the billing service. Very annoying.
When you go through the in app billing documentation, you kinda realize that it can take substantial amount of time to understand this complex piece of technology. Most developers feel the need for a working HelloWorld, and then later play around with the builds.
I have uploaded 2 projects
The android sample project. You can download this project, and immediately run the sample. This will help you quickly debug/trace thru and figure out how the in app billing works.
A cleaned up project to help you integrate your app quickly. This can help like a library. Just integrate make your “purchase requests” on your “checkout” button action.
Mind you : I have not incorporated the security recommendations. Read android in app billing documentation. Until then you are on your own risk.
For 1
Download “http://www.4shared.com/file/f5wH3qke/InAppBilling1.html”
Create a new gmail account for all correspondence (Why, I will explain below)
Pay that 25$ and purchase a “Market Place” account.
Import the project to your eclipse environment
Create a signed application apk, File-Export-Select Your Project-Create OR Use keystore, it should be valid for 25 years from today.
Upload the signed apk to the market place as a “Draft Application”, DO NOT PUBLISH it.
For the uploaded apk, you need to add “In App Products”. You will find this link on the home page for your uploaded apk.
In Security.java dont forget to add your “public key” from your market place account “edit profile” page.
On the “In App Product List”, you need to add the following products one by one
The text below should used as “In app Product id”
sword_001 as Managed
potions_001 as Unmanaged
Title and Description dont matter (for testing purpose). Add what you need here.
Cost add 1$ (minimum)
Click auto fill
Save
Publish the in app project (dont get confused here, you only need to publish the in app product, NOT the APP)
In the test account, add your personal gmail id here. Now, this gmail account needs to be configured as your first gmail account on your phone.
Yes, this WONT work on your emulator
Now the sample app should work.
For 2
Download “http://www.4shared.com/file/h8YnJyf_/InAppBillingIntegration.html”
To integrate, in your calling activity initialize the checkout code
Handler handler = new Handler() ;
CheckoutPurchaseObserver checkout = new CheckoutPurchaseObserver(this, handler);
To send the checkout request for your product
checkout.sendCheckoutRequest(purchaseUri.toString(),null);
Important Note :
This purchaseUri is the “In-app Product ID” of your resource on the “market.android.com/publish-->Create New In-App Product” options. This string should be set as the “in app product” id.
That’s why the “id” is most important. The “In-App Product ID” is how you refer to that particular product.
Also, in Security.java dont forget to add your “public key” from your market place account “edit profile” page.**
Debugging Notes
LogCat will show all errors as InAppBilling tag
This project creates a shared_preferences named “inappbilling” And debug is set to true
The androidmanifest.xml may not be needed since this project does not
have a home screen.
Why do we need to create a new gmail account ?
Simple. The account you purchase your market place account for, cant be used for “testing” your in app billing. Since you cannot purchase products for yourself. And your primary account on your device should be set as a “test account” on the market place account. Chicken-Egg issue here. Hope its clear.
An interesting blog I came by “http://crazyviraj.blogspot.com/2011/06/some-notes-on-implementing-in-app.html“ (not mine).
In my app, I used the test product id, android.test.purchased, which will simulate the actual buying process (ie, will show the in app dialog and you'll be able to purchase and get a response that can be handled by your application). Using that product id, you can run the in app code on the device (unsigned) via eclipse over usb connection. You still might need to work around some things for testing (ie, account for the fact that you are using a testing product id and not your real id), but I found using that product ID did help me quite a bit.
See the testing section of the in app billing guide