I am trying to create a Google Play Developers account but am unable to proceed any further as when I am on the Public Name screen, it states "To continue, fix errors". Anybody has faced this issue before and knows how to work around it? I am unable to send an email to Google as well as it somehow requires me to produce a Developers ID and App Bundle ID
Related
In Feb I upload an app on play store but now I get some violation email and my app was removed from google play store. I thought it's a normal issue and i will fix it. After 1 day I got another mail from google play and my app was suspended. the reason was impersonation policy. They explain that the logo and title is copied but this is wrong I created logo and title myself. So the question is how to deal with it, my app has over 1m download.
Should I registered trademark ?
My appeal was rejected.
They ask me to show letter or some written permission. But from where I get this permission because there is no firm and company registered same as my app's name or logo.
If someone wants to help please suggest what could I do
I just made one test purchase for an item, and it failed because my Wi-fi died, but for some reason Google Play then gave me a message that the order was pending or something and that I should check it on some link (I forgot to write it down).
When I tried to make that same test purchase again, Google Play gave me that "You already own this item" error. Said purchase is NOT in my order history in the Google Play dashboard.
What's going on, and how do I resolve this?
EDIT: Clearing the Google Play Store cache, clearing the Google Services Framework cache, and reinstalling the app does not work.
EDIT 2:
I managed to resolve this issue by Force Stopping the Google Play Store app, clearing its data, then restarting it. Right now, I can only conclude that the purchases made when the Wi-fi is disconnected is in the Play Store app's Data, not Cache.
My question thus becomes: Is it the developer's responsibility to handle this particular case (when the solution is not within the app itself), and how does one handle it?
I had the exact same issue, where I got the error message that I already own this item, but the getPurchases call returned an empty list.
What ended up working for me was getting the purchase history if this list is empty, and taking the purchase token for the last purchase of this specific product id and using that for the consume:
mService.getPurchaseHistory(version, packageName, "inapp", null, new Bundle());
Keep in mind the history contains the information of the last purchase of each of the product types from this user, so make sure to compare the product id's to the relevant one.
I encountered the same problem on some of my devices with a particular application that I already paid for and installed on another device. Clearing cache and force-stopping the Google Play store (and similar) applications on the phone did not help. What did help was to log-in on the Google Play store via Chrome on PC, and install the application from there, to any of my devices registered with Google Play. The Google Play on the phone side then showed the app "installing .. ". The app indeed was installed in minutes.
I'm trying yo update a game on google play to support leaderboards and achievements. (https://play.google.com/store/apps/details?id=com.rightpedalstudios.dragonseason)
However, when I go to link the app I get the message "This client ID is globally unique and is already in use."
I've searched online for people who have had the same problem and the advice they are given is to delete the client ID in the developer console, and if the app has been deleted there then undelete it first. However, there is nothing in the console using the ID, nor is there any deleted apps. As far as I can tell there is no app using the client id.
I did find another person asking a similar question here that was never answered.
Failing to create client ID, due to duplication of signing fingerprint by another Android OAuth2 client
I also get the message "The signing fingerprint you specified is already used by another Android OAuth2 client." When I try to set up a client ID from the developer console. (I know I'm not meant to do that if I'm using google play games, I just wanted to check if it failed from there too.)
I've tried contacting google support, I was directed to the google API support, and then directed here.
Two other developers that have worked on this project could have somehow created a client ID. Although I have contacted them and neither of them recall creating one.
Is there anyway to find out where this client ID is being used?
You have to delete the client id in the Google API console (now confusingly renamed the Google Developers Console !). Then you can link the app to the game straight away. I have just done this, and it worked fine for me. I wanted to link an existing app to a different game, so I deleted both the debug and prod(release) definitions and was able to immediately link the app to the new game.
Note that for many of us, doing work on Google Play Game Services in the Google API console is a last resort - many of us have encountered Google related bugs in the past by doing this !
This image may help:
I am trying to update Merchant Information in my Google play account. I have two queries on this,
Before I could do anything on this page, there is an error window as,
An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}.
How to resolve this?
Google play requires business website under the 'Merchant Information' section. What should
I put there?
Cheers!
Fixed this with the help of Google play support team. Needed to clear the browser cache and cookies. Besides, keeping the system time consistent with the current time(which was wrong initially).
I'm Trying to modify information in the Linked Apps section of Google Play Games Services in the Developer console. Things such as translated titles and whether or not the game uses anti-piracy or not.
It is coming up with the following error every time:
Your changes could not be saved. Please try again. (-32600)
Has anyone come across this?
That's because you're logged in to the above console using account 1, and later tried accessing the console from another Google Account. I faced the same issue and was resolved once I was logged back in to the correct account