google-drive-android-api

I am abusing this forum to solicit explanation (from the GDAA support team) of intended use of GDAA Notification Feature. The documentation here is quite sufficient to implement it, and the two related SO questions 22980497 and 22778501 touch on the same subject. But I can't get my head around it's intended use. Here is the example. Device A 'touches' the Drive object and gets notification immediately. Device B 'touches' the same Drive object and the device A gets notified ' sometime later ', even if both devices are on wifi. So, what is it good for? The app on one particular device knows that

I'm trying to figure out how to check if a folder exists in Google Drive using the new Google Drive Android API I've tried the following, thinking that it would either crash or return null if the folder is not found, but it doesn't do that (just as long as it is a valid DriveId , even though the folder has been deleted). DriveFolder folder = Drive.DriveApi.getFolder(getGoogleApiClient(), driveId)); If i try to create a file the folder I get from the above code, it does not crash either? I'm clearly having a little hard time understanding how this new API works all to together, especially with

My authorization flow in the new Google Drive Android API is as follows: Menu: SELECT ACCOUNT connect(); onConnectionFailed() result.startResolutionForResult() invokes AccountSelectDialog / DriveAuthorization onConnected() do your stuff Works like a charm. Now repeating with the aim to switch accounts: Menu: SELECT ACCOUNT connect(); onConnected() Here, I have no chance to get to the AccountSelectDialog since I never get onConnectionFailed() with 'result' to invoke startResolutionForResult() . What am I missing this time? Just call mGoogleApiClient.clearDefaultAccountAndReconnect(); have a

I have folders on my Google Drive account and i want to add files in specific folder. How can I do it? In example needed DriveId (EXISTING_FOLDER_ID), but I don't know DriveID my folder, I know name only. If you have the metadata for the folder (or a DriveFolder object, from which you can get the metadata), you can just call getDriveId . If you have the web resource, you can get the DriveId using that resource id using fetchDriveId OK. I experienced the same issue with the Drive demos on Github: https://github.com/googledrive/android-demos At the bottom of the readme, it says: If you actually

I've run into this issue a few times, but could never point my finger on it, attributing it to GDAA's latency, my buggy code, etc... I finally managed to come up with a scenario where I can safely reproduce it, so I would like to ask people who know if it is a feature I don' understand or a plain bug. If latter is the case, please point me to the place where I can nag about it. I will discuss it on the REST API's background for simplicity. 1/ Let's have a Drive API authenticated app that runs under DRIVE_FILE scope com.google.api.services.drive.Drive svc = new Drive.Builder( AndroidHttp

This issue has been bugging me since the inception of the new Google Drive Android Api (GDAA). First discussed here , I hoped it would go away in later releases, but it is still there (as of 2014/03/19). The user-trashed (referring to the 'Remove' action in 'drive.google.com') files/folders keep appearing in both the Drive.DriveApi.query(_gac, query), and DriveFolder.queryChildren(_gac, query) as well as DriveFolder.listChildren(_gac) methods, even if used with Filters.eq(SearchableField.TRASHED, false) query qualifier, or if I use a filtering construct on the results for (Metadata md : result