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.
Related
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
I recently started playing with Firebase, but I cannot completely understand its relation with Google Play Services. I know that Firebase is a mobile platform, and on Android it is based on Google Play Services, but why there are some modules with the same name of the ones of Google Play Services?
For example, in my build.gradle I can have:
com.google.android.gms:play-services-auth:9.4.0
com.google.android.gms:play-services-ads:9.4.0
but also:
com.google.firebase:firebase-auth:9.4.0
com.google.firebase:firebase-ads:9.4.0
I see that on Firebase documentation there is the list of available components (and note that the last one is actually a Google Play Services module):
com.google.android.gms:play-services-appindexing:9.4.0
The same list for Google Play Services is much longer, so some modules are not available using only Firebase dependencies. Which dependencies should I use and why? Can I use mixed dependencies?
On this new Firebase (from May 18th), Google added a few existing services to it. Google Play Services already had features like: Analytics, AdMob, Test Lab, etc. And you could use them from your Google Developer Console.
But then, they decided to merge some of those features with firebase. This way, you can have all of the features "together" on your Firebase Console. They are now unified to give your users a better experience and to help you (as a developer) easily manage your project.
So, if you want to use firebase, you should use the firebase dependencies. The Google play dependencies are meant for projects created on the Google Developer Console.
I think I am a little confused with using the Google Play Android Developer API.
I have an Android App, built with Parse, that uses Google In-App Subscriptions.
I found the answer here, which is great. But, where do I actually access the API to confirm the subscription from? Do i do it from within my App?? From Parse Cloud Code?
Any ideas?
We need full access of users Google drive, but it's providing limited access. We are unable to find Google APIs Client Library samples. Attached linked provide following information for samples.
From the documentation
The Google Drive Android API currently only supports drive.file and drive.appfolder authorization scopes. If your application requires additional permissions or features not yet available in the Drive Android API, you must use the Google APIs Java Client.
Where can I find Google APIs Java Client documentation and samples?
The GDAA API you're referring to is an API build on top of the REST API and supports only FILE scope.
The REST API supports the DRIVE scope that allows access to all folders/files.
I can offer a very simple DEMO of basic CRUD functionality for the REST API here (and parallel version of the GDAA API here).
Good Luck.
If you need more than the drive.file and drive.appfolder scope offer for your android application then you will need to use the API Client Library for Java instead of the Google Drive Android API available in Google Play Services.
You will also need the Google APIs Client Library for Java which performs common REST API tasks including authentication and token management. Review the "The library runs on Android (#Beta)" section in the README to see how to retrieve a Drive service object on android.
My Problem is, that I want to use any SDK or API to access my google drive from my android phone without using an existing google drive app on my android phone.
I read the instructions on this side: google drive sdk
The code examples does only work for desktop applications and the "integrate with Android" topic on the side does not provide any example how I can access my google drive from my android application.
I already read android-api-for-google-drive here but this leads only to more links and how-to's which are far to complicated and fuzzy.
Has anyone experience with connecting to google-drive from an android application and could help with any example code or "clean-and-short-explained" tutorial?
Luckily, just after you asked this question, Google released their Play Services (see this link), which makes it a heck of a lot easier to access files using the Drive SDK & Drive API. Please see my post on Google Plus that gives a step-by-step walkthrough and code example on how to integrate an Android app with Google Drive documents: https://plus.google.com/u/0/114042449736049687152/posts/CD3L8zcJg5Z
In the tutorial, I reference a particular Google IO 2012 talk (slides at https://docs.google.com/presentation/d/1LrEKp2PqESsES3upS1xsSARz35KS-9QHnYFTKvS2yzM/preview#slide=id.p19), but please read my G+ post because I go through the various flaws, pitfalls, and omitted details from this presentation.
Before you start coding anything, get yourself signed up for the Google APIs (see this link), get into the API Console, and turn on both the Google Drive API and Drive SDK.
Good luck & have fun!