Im working on a game that uses google drive android api to store save games into app data folder. Now i want to migrate everything to REST api, since gdrive android api is deprecated now, but i noticed very strange statement in deprecation notice here: https://developers.google.com/drive/android/deprecation
"Support for storing and syncing in the app data folder will likely be removed from Drive in the future. Clients requiring app data storage are strongly encouraged to migrate to a non-Drive solution such as Cloud Firestore."
Anybody knows more concrete timeline for app data deprecation apart from "will likely be removed"?
Question is if it's still reasonable to invest time to migrate savegame storage to rest api or to just switch to Cloud Firestore as suggested.
I guess you just need to use the new version of the Google Drive Android API https://developers.google.com/drive/api/v3/appdata
Related
I'm working on an iOS/Android app developed in Unity, that uses Google Sign-in through Firebase Auth, and from what I've read here, that should handle the OAuth 2.0 protocol. I would like to use the Google Drive API to allow the user to load files they have stored in their Drive, but I'm having trouble finding documentation on how to do that in Unity.
The most useful pieces of information are the following GitHub repo and Gist:
Unity Package for Google Drive API
Using Firebase to Authenticate to Google Drive (but not specific to Unity)
Any help on how to do it is greatly appreciated.
For future reference, I ended up using this video to implement Google Sign-in through Firebase in Unity. It was very detailed both on how to set up things from the Firebase side as well as Unity.
As for loading files from Drive, the solution was to use this unity package that allows you to call the native file picker for each platform, being able to load files from all Drive accounts the user logged-in in his/her phone, as well as any other file provider they could have (the phone storage itself, Dropbox...), all in a UI that is familiar to the user. I leave here the issue that led said solution, on another package from the same creator, which, by the way, I have a lot to thank for.
Is Google Play games services, 'Saved Games' feature deprecated?
On their website Saved Games is not listed as deprecated.
https://developers.google.com/games/services/android/savedgames
However when specifying the Drive scope in code, Android studio gives code hints saying the feature is deprecated and on the Google Drive API website, it states this feature is deprecated.
https://developers.google.com/drive/android
The website advices to migrate to the Drive REST API?
and that website advices to migrate to Firebase Cloud Firestore.
Clients requiring app data storage are strongly encouraged to migrate to a non-Drive solution such as Cloud Firestore.
Any clarity would be appreciated.
The Drive API was deprecated. I guess saved games internal implementation uses the Drive REST API now.
Replace Drive.SCOPE_APPFOLDER with new Scope(Scopes.DRIVE_APPFOLDER) to clear the Lint warning. If you'll check the internals you'll see they are the same.
I'm just coming to the end of writing my first game, last thing to do is enable backing up the user's game. I have leaderboards and achievements implemented fine, and all Google's docs say I should be saving games to Drive using .requestScopes(Drive.SCOPE_APPFOLDER) which upon trying leads me to find that it's no longer going to work in 2 months.
Digging further, I found this line from Google: "Support for storing and syncing in the app data folder will likely be removed from Drive in the future."
I'm still learning all this as I go, and I'm using Kotlin (I don't know Java). Can anyone point me in the right direction to where I should be looking to backup users game data if the way Google suggests isn't going to work very soon?
Thanks
Google is deprecating the Google Drive Android API in favor of the Google Drive REST API. Here is the best starting point for implementing that in android that I could find.
I've built an app using Ionic that takes pictures and uploads them to Firebase Storage. What I'd like to do next is to make it so that the directory structure and images are accessible from a Google Team Drive.
What would be a good way to go about this? I don't have any code examples because I'm inexperienced with this and I don't really know where to start.
Would I write code to put in Firebase functions that would upload the images every X hours to a Google Accounts' Team Drive? Since Firebase Storage is just using Google Cloud anyways is there an API I could use? Does Firebase have this capacity already and I just don't know about it?
The Team Drive is under G Suite for my company so I could get a Google account made just for this purpose.
I'm new to Stack Overflow, sorry if this post breaks any rules.
https://github.com/firebase/functions-samples/tree/master/google-sheet-sync
This is the only example on the internet that I could find that addressed this issue.
It is a working (With a few tweaks as of Novemeber 2017) example of OAuth and Google's API for uploading information from the Database to a Google Sheets document via an onWrite() event trigger.
I managed to get this working, and in combination with the Google API docs and a lot of rummaging have sort of managed to get Google Drive connected.
The key points are:
-Follow the Firebase Functions examples
-Examine the google-sheets-sync example
-Firebase Functions takes node.js javascript
Posting this answer because it sounds simple but this was a hell of a lot of digging for me to find this all.
I am a developer and currently working on google drive API on android.
I can query and create file/folder from my app using GoogleApiClient; however, I cannot delete the files from my app.
After I google it and I found out that the newest google drive Android API has not supported it yet.
So, are there other ways to delete files from android app?
The answer is here - SO 22295903, just combine with the old API. Or wait, DELETE has been promised soon.
In SO 22295903, there is a mention of reverting to the RESTful API. I have not done it myself, but I think you would take the resource ID, DriveId.getResourceId() and apply it to the trash or delete method. But it is only an untested idea, so don't shoot me.