unlisted gsuite apps link no longer work - google-apps-marketplace

We have a couple of unlisted apps published on the gsuite marketplace, but since today those link give a 400 error:
That’s an error.
The requested URL was not found on this server. That’s all we know.
Last friday they were still working.
The link does work when i use it with my owner account, but all other accounts (private, domain or domainadmin) give a 400 error.
Google, what's wrong?
the link looks like this:
https://gsuite.google.com/marketplace/app/APPNAME/NUMERIC_APP_ID
(actual app info remove, because my unlisted apps are for unlisted for a reason)

Google seems to have fixed the problem.
the old links work again:
https://chrome.google.com/webstore/detail/APPNAME/ALPHANUMERIC_APP_ID
From my marketplace developer account, these are the links used.
thank you Google.

Related

Firebase Analytics console doesn't show up because of X-Frame-Options error

I started to use Firebase Analytics on my developing app, but the analytics console doesn't appear. I can't see even the navigation bar.
Here's a screenshot of my analytics console.
I installed Firebase/Core pods, set -FIRAnalyticsDebugEnabled, and debug console on Xcode says analytics data uploaded successfully.
My first event data sent about 20 hours ago. I'm planning to wait until 24 hours will pass, but is there any possible setting required?
---edit---
I found an error message in my browser's developers console. Here's a screenshot.
It seems some kind of X-Frame-Options problem.
I tried Safari and Chrome, but the results are same.
I found it's a problem of Google account's permission. I used my company's Google account and already got the permission to access Firebase, but permission for Google Analytics seems necessary too!
After getting another permission from the admin in my company, Firebase Analytics console appeared in a right way.

Can't publish a Hangout app (extension)

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.

Unable to add site to Google Push despite being owner in webmaster tools

I am currently getting "You do not have access to the following domain:" error in Google developer console when attempting to use the "Configure webhook notifications" button for Google API push notifications despite the fact that the very same site / domain is listed as mine in Webmaster Tools and I have access to all of the services there. Any ideas?
I guess you also registered "https://yourdomain.com" in google webmaster tools, because the webhooks require https.
The very same thing is happening to me since about one week. I can add all kinds of domains to the push notification list, even "www.chatgrape.com" but not "chatgrape.com".
I described the problem in the Google Product Forums in detail but nobody was able to help me yet: https://productforums.google.com/forum/#!category-topic/apps/general-discussion/Numad1TlCJ8
Yes I actually found that it would only work if I had the https version of the URL registered in Webmaster tools. However, the reason that I can use an https version is that there are some SSL services included with a free CloudFlare account. This does not include using a signed certificate installed on your server. To use Google push, you need to have a certificate installed and it cannot be self signed.

App is not authorized to scopes after installing via chrome web store

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.

Google Apps Marketplace Migration

We have a Google Apps Marketplace App. Or more precisely, we have 2: one in the old marketplace and one in the new. Both point to the same URL, both do exactly the same thing (OAuth2 authenticating the user(even users from the old Marketplace,, because we handle this users like the "normal" users coming from the Chrome Web Store ).
Now Google wants us to move the users from the old Marketplace app to the new one.
How do we do that?
According to Google's document we should call an UpgradeApp API for every domain.
This requires that we find out all the domains (we don't know them because we don't care, if the user is a marketplace user or not).
So we should probably use licenseNotification on the old Marketplace app, to find out all domains and migrate them one by one?
To try this, I tried to issue the API from API Explorer (https://developers.google.com/apps-marketplace/v2/reference/licenseNotification/list) but got a message (403 FORBIDDEN complaining that I should activate the API . How do I do this? (I already have a project where the Marketplace API and Marketplace SDK is enabled).
Will this approach work at all?
Are there simpler ways of doing this?
The API explorer approach works, I just tried.
Make sure you are providing correct applicationId which is the key here.
GET https://www.googleapis.com/appsmarket/v2/licenseNotification/applicationId

Resources