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.
Related
I have created a Google Chatbot using the Google Hangouts Chat API. The bot has been verified on the store listing of GSuite Marketplace SDK. App visibility is also set to the public mode.
Store Listing Status:
App Visibility Status:
I have also got my OAuth Consent Screen verified and set to external.
Can anyone let me know, what might be the reason that my Chatbot is not available to other G-Suite domain accounts?
OAuth Verification Status:
We do validate the google play in app purchase receipt on our backend server.
For testing we do fake the receipts and test with them our system.
Is there a possibility to do a test purchase from the backend server to google's test server, to generate a receipt?
Or is there a possibility to get an fake receipt directly from google play?
For Android there are static responses for testing, maybe for backend server too.
It will be a better test then to fake the receipt by my own.
All purchases, including test purchases, must be done using an Android application (via a real device or an emulator). It happens because the purchase is executed by the Google Play Store app, and authenticated by the user.
About the server-side API, according to the Google Play Developer API, you can use the Subscriptions and In-App Purchases API to:
[...] manage your app's catalog of in-app products and subscriptions. In
addition, with the Subscriptions and In-App Purchases API you can
quickly retrieve the details of any purchase using a standard GET
request.
So, after your purchase is completed (starting on the device), you can manage it's status, get details from the API and etc.
In Microsoft's Bot Framework, there is Facebook Messenger Channel. And according to the setup page, i followed everything and then have finished configuring things on both Bot Framework and Facebook App ends.
Finished setting up Facebook Webhooks and it's Callback URL (with the required Verify Token). Everything seems to be correct (Please refer to screenshots below)
But when i start trying to chat to my page (from my FB Admin Account), there's no reply, nothing.
What seems to be the problem? And what should i be looking at, please?
Thanks all in advance.
I got it working now.
Inside the Botframework's "Enter your credentials" section, there's Facebook Page Id field to enter, but i didn't know there's a specific Page ID for a Facebook Page (which can be found under "About" tab). In fact, i thought it was the one we used in the URL (For example: https://www.facebook.com/xxxxxxxxxxx, and therefore: xxxxxxxxxxx) but it was wrong.
Then, deauthorized and resubmitted credentials from Botframework.
Thanks everyone for all the helps.
Also, can you verify that your bot works correctly from the test panel and webchat control in the Bot Framework portal.
You may also wish to deauthorize and resubmit credentials.
it's odd that you're not seeing any errors in the bot framework portal for the Facebook channel, that would almost imply to me that the messages aren't making it from the Facebook messenger chat service to the Bot Framework. It looks like you've set the callback URL correctly (from the unmasked part).
You can also hook up Azure App Insights and give us the instrumentation key (via the portal) and we will send any error events to your app insights instance.
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.
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.