I have published my Extension Sheets Add-on but it's rejected !
Where can I found the details for the reject to correct the problem and re-publish after corrections ?
On the OAuth consent screen the tab "DOMAIN VERIFICATION" was not completed.
When I completed it and re-submit my addon, it was published successfully.
Related
After rollout, My apps has been rejected, and I got email from google PlayStore support. But I still not get a hint.
here is the message:
I see... I must submit relevant documentation through this:
https://support.google.com/googleplay/android-developer/contact/sms_permissions
to obtain a pre-qualification from Google.
We are a new company developing an email client with the google scope https://mail.google.com/
Our app shows the unverified app screen and we submitted a review request with a youtube video.
We got a reply from the "Api Oauth Dev Verification" we can continue the verification only if we submit the app to the app store.
I wonder if this is an automated type email and we should request a verification before we publish the app or not.
Second question they told me they may require a secutity assessment, I wonder if there is a way to prove that our app is local only and do not send any data to a specified server.
Thank you.
I've created a Google Hangout extension app, tested it works privately etc and now I'm trying to publish it. I have followed the instructions here:
https://developers.google.com/+/hangouts/publishing
I've filled in the forms correctly, created the O-Auth client ID, filled out the consent form etc. When I tick the Make this application public tickbox and try to save, a server error message pops up along the lines of:
Server Error
Whoops! Our bad.
Please try again. If the problem persists, please let us know using the "Send feedback" link below. Thanks!
Tracking Number: XXXXXXXXXXXXXXXXXXXXXXXXX
[Send feedback]
I've checked the Chrome console - the request gets a 500 error and in the JSON response I can see:
{"message":"Developer not registered with CWS."}
I have paid the $5 one-off developer fee on the Chrome Web Store and I am the Hangout project owner. I'm not sure what I'm missing here. I need to get this published in the next 24 hours...
Any useful insights? Is there any official support forum for Google+ platform developers?
UPDATE
I was using a Google Apps account before so I've paid the developer fee on a personal account to verify me on CWS, made this account owner of the Hangout project and I still get the same message response.
I believe then that it's basically just broken. Thanks Google.
Google play remove my account from play store. I have 20 app. Admob still generate ads revenue because that app was publish in other unknown market and i have no rights to remove that. And I continuously got mail from admob that violating our police.
I got mail is:
Hello,
This email is to alert you that one of your applications is not currently in compliance with our AdMob program policies and as a result, ad serving has been disabled to your application.
Issue ID#: *******
Ad serving has been disabled to: Video Player (com.***.*******)
Action required: Check all other remaining applications in your account for compliance.
Current account status: Active
Violation explanation
GOOGLE PLAY REMOVAL: AdMob publishers are not permitted to abuse or promote the abuse of any Google product, such as Google Play, YouTube, or Blogger. This includes circumventing, or providing the means to circumvent, the policies or terms of these or other Google products, such as by allowing users to download YouTube videos.
If your app is removed by Google Play policy enforcement, please contact Google Play about an app removal here. If Google Play reinstates your app, please submit an appeal to our team.
Action required: Check account for compliance
While ad serving has been disabled to the above app, your AdMob account remains active. We suggest that you take the time to review the rest of your applications to ensure that they’re in compliance with our policies, and to monitor your apps accordingly to reduce the likelihood of future policy emails from us. Additionally, please note that our team reserves the right to disable accounts at any time if we continue to see violations occurring.
Appeals
If you wish to appeal this disabling then you can do so by using our appeal form.
Thank you for your cooperation.
Sincerely,
The Google AdMob Team
How to can i remove that app ads unit id from Admob?
And How to stop this thing because its admob warning that may disable my admob account?
Any suggestion ??
You can't. You need to remove it from the app and republish the app in the other market.
At the Admob console, select the app with the ads.
check the ad you want to disable, then click < Archive >
this will give you the prompt below.
this will disable your Ads with that Ad unit ID (I hope you didn't use the same ID for all 20 of your apps).
We are in the process of creating our new app for v2 of the apps marketplace. Recently we have run into quite a major issue and we are having a lot of trouble resolving it.
We are testing the workflow where a domain admin installs via the chrome webstore listing. The actual installation of the app works, insofar as the app is installed on the domain and the scopes appear to be granted when looking at the "Manage API client access" section in the domain admin panel (http://i.stack.imgur.com/a63nv.png).
However, when we attempt to use the service account to get calendar or contacts info, we are getting "Requested client not authorized" errors.
{
"error" : "access_denied",
"error_description" : "Requested client not authorized."
}
However, if we manually add our service account + scopes to the domain in question, then accessing the data programmatically works fine (http://i.stack.imgur.com/g6pRg.png).
So, clearly we are missing something here, with how installing a marketplace app via the chrome web store is supposed to work.
Other things to note:
Chrome webstore listing is marked as unlisted.
New marketplace app is not approved (obviously) as the tester received this specific error when attempting to install the marketplace app.
We got it figured out. The issue was in how we declared our contacts API scope in the marketplace sdk setup screen.
In the marketplace setup screen, we declared using the contacts scope without a trailing slash ("https://www.google.com/m8/feeds").
However in our app, we were sending oauth requests for the calendar feed with the slash at the end. ("https://www.google.com/m8/feeds/"). This mismatch caused the whole request to fail with the error message above.
If anyone runs into this and is baffled at why their service account requests are failing, make sure you are consistent with your slashes at the end!
I would suggest to Google that you should update the marketplace sdk screen to also be consistent and reject scopes that do not have a slash at the end. That would have saved us days of frustration.