Simple API Access status: suddenly INACTIVE - google-drive-api

I was developing android application that has backup to google drive feature.
I have used Simple API Access key and it worked like a charm for few weeks.
However, from yesterday, it does not work at all. (cannot list uploaded files and 403 fobidden error when trying to upload new file) I checked Google APIs Console and found out
Simple API Access
Status: Inactive
and Reports is not available and keeps showing popup message "An unexpected error has occurred. We're looking into it."
I googled about this message but there is no solution. (but found several issues related to google cloud SQL)
I was considering to use google drive on commercial level android app and this is very bad...
I wonder what is the problem and how to reactivate api status.
Thanks :)

Unfortunately, because of the security model of the Drive SDK, we need to be sure that an application is who they say they are, which simple access does not give enough assurance of. For a commercial application, this strength of security is great for users.
For a solution, you need to use Google Play Services as outlined in the documentation. We are currently working on a guide to get started with this very quickly on Android, and should be available within the next week.

Related

GCP project created by an app authorized by me, but I do not have access to it?

I'm developing some automation/integration between a CRM software and my google account. I am attempting to use the Google Apps Script API so I can remotely execute functions in Google Apps Script through the integration I'm building from within the CRM software.
The only problem is, when attempting to run a function which calls a GAS function through the API, I get the following error:
"Apps Script API has not been used in project project number before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/script.googleapis.com/overview?project=103424032563 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."
This would normally be no problem, as I would simply access the GCP portal through the link and enable the GAS API, but when I try to access my project, I don't have access at all, and get the "failed to load data" error.
Further complicating my issue, GCP support will not help because they suspect I am a hacker trying to obtain access to a project that, for all they know, isn't mine.
And because I cannot access this project to authorize the API, I also cannot associate my google script with the same project, as this is a requirement for the Google Apps Script API to function.
I suspect it's the CRM software piece in which I'm developing this integration that is causing this error, (somehow the GCP project is being created by a different user,) but they haven't been all that helpful in determining what's going on.
Have any of you had a similar situation? And, if so, how did you approach solving it?
Further complicating my issue, GCP support will not help because they
suspect I am a hacker trying to obtain access to a project that, for
all they know, isn't mine.
Google Support does not refuse to help. They don't accuse you of being a hacker. Google Support can look at the project and see if you have credentials in the project and if you do they can explain how to authorize yourself. However, Google Support requires a support agreement, which is not free. If you do not have one, then you are not entitled to technical support only billing support. Look up your billing account ID and send a request for billing support. Your billing account will also show you which projects are linked to your billing account.
The issue is that you are trying to access the wrong Project ID. Figure out what is the correct Project ID. If you have the Cloud SDK installed execute this command gcloud projects list and this will tell you which projects your credentials have access to.

CloudRail support for OneDrive For Business

We have used CloudRail to retrive files from OneDrive, Google Drive, Amazon S3 and Dropbox without hassle.
When we have tried to implement OneDrive For Business, we get an error
'The app ID is blocked for access of the O365 Discovery Service'
Does anyone know if this error comes from CloudRail or Azure? If I check the Azure history for the application, it is logging that my sign-n status is successful.
We have had multiple developers go through the setup instructions and get the client ID and secret with the same result.
We have now scaled our application to the example code on the CloudRail website and still the same problem.
Has anyone managed to get OneDrive For Business working with CloudRail?
If so, does anyone have any suggestions?
Thanks in advance
According to Microsoft, this is due to the O365 Discovery Service being depreciated. Existing application will still work but no new ones will.
CloudRail has updated their SDK to use Microsoft Graph instead of O365 and all is working.

Follow official steps to Generate Google Map API for new project, fail to load into Google Cloud Platform

I am trying to add a map into my website marking the location of a place.
So I read that I have to generate API from Official google map API page.
I created a project, setup billing as required.
Then when loading into the Google Cloud Platform, it always throw me an error saying something went wrong:
How am I going to fix this?
There are a number of reasons why this error could have been thrown. Often times further evaluation of the error would be required by reviewing the Stackdriver logs as the rootcause cannot immediately be determined just being viewing the Console error message displayed.
For this type of issues, the recommendation is that you contact the Google Cloud Platform support team or you can create a Public issue on the general Cloud Platform Public Issue Tracker. There is relatively little that can be done on Stack Overflow to help you debug this.

Google Maps Android API v2 - Google Play Store is missing

In the newly published version of my app that is using Google Maps Android API V2, I've implemented all the things suggested by the developer guides to ensure the user has GooglePlayServices installed, and it has been working well on all the devices I own and the several hundred people that have updated to the new version of the app so far.
Today I received a bug report via acra with a strange error. This is happening on the following line of code, after setupMapIfNeeded() has completed:
mMap.setMyLocationEnabled(true);
Logcat reports:
W/GooglePlayServicesUtil(10401): Google Play Store is missing.
Shouldn't the call to GooglePlayServicesUtil.isGooglePlayServicesAvailable() also ensure that the Play Store is installed? That seems like a huge oversight on Google's part if it doesn't.
Any help is appreciated.
In case someone came here by accident or was just wondering why it was not working...
This could happen when user had old Android Market installed, which was replaced by Google Play Store.
Here is relevant issue: http://code.google.com/p/gmaps-api-issues/issues/detail?id=4862 (fixed in february update).

I am facing "The authenticated user has not installed the app with client id" error even after installing the app [duplicate]

I'm working on a Google Drive interface for Emacs. The concept is that Emacs could provide a platform-agnostic way to load, modify and save text documents stored in Google Drive. I've registered my app and can authenticate with OAuth2 and get a file listing with the Docs List API, but when I try to execute an Insert with the Google Drive API, I see an error:
"The authenticated user has not installed the app with client id ..."
Reading further, it seems I need to publish my Emacs application in the Chrome Web Store to get access to the Drive API. That doesn't make sense to me...I noticed that there is a FUSE project in development for Google Drive, which suggests that native development is possible. When I skimmed the code, however, I didn't see a Chrome Web Store component to getting it working.
Am I trying to misuse the API, or is there an route to make this work that makes more sense?
EDIT:
According to Ali Afshar, of the Google Drive team, installation is no longer required to use this API. So what follows may no longer be relevant, but will be left for historical purposes.
So, first off the API does not support application development in the sense that we are both doing it, I wouldn't use the word native though. The good news is I have been doing some research and Google Drive is really just a rebranding of Google Docs. So the Google Docs API could be a good choice as well for the same purposes.
Anyway, here's the steps to solve the error: "The authenticated user has not installed the app with client id ..." Which is a 403 error, for the sake of this answer. These steps assume you have set up an app in the chrome web store as is required, and installed it. I am working on my local machine too, with my project: http://github.com/tom-dignan/gdrive-cli which I have gotten past this error, so I think you should keep plugging away at your emacs version, because I think we can make this work.
a. Open the Google APIs console.
b. Confirm you've already enabled the apis under "API Access" both the API and SDK for Google drive should be enabled. There you get your client secrets/api keys and such. I am almost positive you've done this already, so go ahead to C. (this is here for others who may have missed it)
c. In the left navigation bar, under "Drive SDK" you will need to do the following:
Add a "Support URL" (required)
Add at least a small 16x16 application icon (required)
Add "OAuth Client ID (Required)" under Drive Integration (I was just tinkering and this seems to be the key field.)
Add "Open URL (Required) URL to open for your app from the google drive UI."
Check off "Multiple File Support"
Add some MIME types and file extensions, "text/plain", and txt for example
Add the the auth scopes:
https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/userinfo.profile
Don't bother trying to add the auth scopes for Google Docs here, because it won't work. Google does not want us to use it that way because files that drive apps create should be private to that app. Integration with Google Docs will have to be separate.
Now I know you must be thinking "why do I have to add some of these..." It's because the form makes them required fields. In mine, I put a couple URLs that point to static HTML pages.
Once you've done the above, clean up your state and reinstall your chrome app. Then try your code again, and it should stop giving you a 403.