We are currently attempting to publish an App on the Google Marketplace (aka Chrome Web Store).
My boss has paid the $5 developer fee using his Gsuite account, and when I log in to publish the app, it keeps requesting the $5 fee to be paid. We are both part of the same GSuite domain (rulerr.com). I'm guessing this means the payment is tied to his account specifically? Is there any way to get this tied to our Gsuite domain?
As a result of the way this works, if I end up publishing using my account can anyone delegated from my domain modify it? If I was to go on vacation/sick leave/move on to another company then noone in my organization would be able to modify the App details?
Would adding a shared mailbox account specifically for marketplace registration alleviate this issue?
Laurie,
You can create a Google Group and use that as the owner of your app.
https://developer.chrome.com/webstore/publish#set-up-group-publishing
Any member of that group will then be able to publish. (when they have paid the 5$ fee)
Related
Google play console is requesting to verify my identity.
The problem is that the verification form is asking for an organization info and docs while the account is for individual and that is provided in the account details screen.
So what am I missing? Where to go? Or how to contact google support?
I had this after emailing googleplay-developer-support#google.com. Solution: Your payment profile shouldn't be set as organization if your developer profile is set to individual and vice-versa.
Per checking, the payments profile associated with your account is set as an organization. You may choose to verify your account as an organization with the following documents that our system accepts: Certificate of Organization, and a valid ID of the organization's Official Representative.
If you would like to verify as an individual and change the entity type on your payments profile, you would have to create a new account in order to change from organization to individual. You may view your payments profile via pay.google.com
To change the entity type on your Payment Profile, it would need to be deleted and created again. Since a Play Console account can only be associated with one Payment Profile, it will need to be deleted and recreated as well.
To resolve the issue, we can close your Play Console account and refund the registration fee. Then, you can delete your payment profile at pay.google.com before you sign-up for a new Play Developer account. To proceed, please provide confirmation by responding with “I confirm to have my Play Console Developer account closed and have its registration fee refunded.” Also, please remove the existing draft app from the Developer account
I had this issue recently and it turned out it was because I had an old Payment Profile with Account Type of 'Organisation'.
You need to go here: https://pay.google.com/gp/w/u/0/home/settings
Personally, I had two payment profiles; one was for an Individual and one was for an Organisation. Maybe the Organisation one was the default or whatever.
In the end I managed to close that payment profile and create a new developer account after having the first one refunded.
There were a few emails to Google Support going back and forth but that solved it in the end and now I have an app on the Play Store.
I'm developing integration with Google Ads API using their Ruby gem library.
I have an approved oAuth2 account for the Ads scope with an approved developer token that allows any external user to connect with our API.
I have a Google Ads account that manages our own Ads account and two other accounts.
When I authenticate with the API and approve it, I then grab the account with
graph = get_accounts_graph()
Apps::GoogleAds::Account.get_accounts_map(graph)
This surprisingly returns just ONE Ads account, and one that belongs to a client that we manage. Our own two Ads accounts are missing.
So I tried to compare between our client's account and our own.
Under https://ads.google.com/aw/accountaccess I can clearly see we have admin rights to our two ad accounts, just like we do to the client account.
Am I missing some setting somewhere? Has anyone experienced this before?
I ran into this issue at the beginning. The sample in the API client libraries (which I'm going to assume you are using here), calls the customer service
customer_service.list_accessible_customers()
There's actually two different services for retrieving customer account IDs. The customer service only allows access to accounts that are added as direct admins on each account. This is an important distinction as manager accounts don't fall into this category.
What you need to call is the regular GoogleAdsService (not the customer service!) and put your request in the query itself..
query = "SELECT customer_client_link.client_customer FROM customer_client_link"
This will give you a list of account IDs as resource names, not accessible accounts. And you can iterate over them as usual.
Hope that helps.
I'm using Google Sign-in to register and login users to my web app.
We are an edtech product, so I would like to make sure users are registering with a google account that is tied to a school and not using their personal google accounts.
Is this possible?
I don't see a field in user that would indicate this. I also can't find confirmation as to whether or not school google accounts can have an #gmail.com email or if they must use a custom domain.
Note that these account may or may not be using Google Classroom, so I can't rely on that.
Unless you have a List of the "school" accounts and can test against that there is no way for you to know.
Google is not going to tell you if its a school google account. They may know if its a google classroom account but that kind of information is not shared at login time. Probably due to user privacy.
I just register and paid $25 USD to be able to upload an app in the Google Play Store. I used my personal email address, something like sonyaATmydomain.com. The app that I am uploading is for a different domain, e.g. hello.com. I uploaded the app and started to configure all the settings. The problem is that I did not realize that to make the app private (Private Channel) my developers email account must be the same domain as the app, e.g. sonyaAThello.com. So I added a new user with administrator permissions to the app, this new user using the correct domain, e.g. sonyaAThello.com. I logged with this new user account and I cannot see the Private Channel section. Then I logged with my personal email address user and also I couldn't see the option. Then I discovered that to see that section my setup account (the one that paid $25 USD) must be the app domain. But that is not possible. So I tried to transfer the app from my personal account to the new user domain account, BUT at this stage I doubt that is going to work. For what I have read, it seems to enable the private channel, I must have a Goggle Apps account and that is not free. Does anyone know if it is possible to setup the private channel for the play store without having to pay a Google Apps subscription and if yes what's the correct process? Unfortunately I already paid $25 USD but I can't manage to get the private channel :(, thanks a lot
Based off the documentation, it seems there is no getting around having a Google Apps for Work, Education, or Government account.
This work around may not work for you, but what you can do is publish to aplha/beta testers. This will allow you to grant access to whatever users or groups of your choosing. You do not need a production APK for aplha/beta testing, but I'm not sure if you'll be able to get other production information (analytics, ratings, etc).
To be able test any implementation of Android Market licensing (e.g. LVL, In-app Billing), Google advises to create a Google Checkout test account, since the developer cannot buy from himself using his own Google Checkout account.
Sounds great except that the test account must use a real credit card.
Which begs the question: How is this different from a normal account? What is the advantage of a test account over a normal account?
The test account does not have to be associated with the google checkout account. The publisher can have his/her google checkout account set up against the android market account. And as a developer, you can have a test account created.
Test account holders can test the application for LVL and in-app purchasing, etc only if the application is uploaded on the developer console. It does not have to published. But it has to uploaded and activated and saved.
So, it's not true that the test account holder has to have his/her financial details registered with the Google servers. Only the publisher has to do that. And the publisher can add as many test account holders as he/she desires. The publisher will provide a publishing key and that's all the developers need to implement/test their code.
Look for documentation on Google developer site. It explains well.
HTH.
You don't need a separate test account. That's only if you want to include others as testers. Your own publisher account is just fine. If you set the LVL response in your developer account to, say "UNLICENSED" for testing purposes, then only the devices that are set up with that Google account will get this test response.