For Unity 2017.3 and later: UnityGoogleDrive.unitypackage. Check releases for previous versions support.
In case you're not familiar with the Google Drive API, please read through the official documentation and FAQ, before using this package or opening new issues.
Google Drive API library for listing, searching, creating, uploading, editing, copying, downloading, deleting and exporting files on the user's drive from within Unity game engine.
Supports all the major platforms (including WebGL). Source code is .NET 2.0 profile compatible and portable (no platform-specific precompiled libraries are used).
Two main authentication schemes are used: browser redirection for WebGL builds (because of the sockets limitation) and local loopback requests for other platforms with refresh tokens support. All the credentials are stored in a scriptable object; editor script provides shortcuts to create and manage Google Console App, allows to parse credentials JSON to skip manual copy-pasting and edit common settings:
Automated integration tests cover the main features:
- Import the package;
- In the Unity editor navigate to
Edit -> Project Settings -> Google Drive Settings
; GoogleDriveSettings.asset file will be automatically created atAssets/UnityGoogleDrive/Resources
, select the file (if it wasn't selected automatically); - Click Create Google Drive API app button; web-browser will open URL to setup the app:
- Select Create a new project and click continue;
- Click Go to credentials;
- Click Cancel;
- Select OAuth consent screen tab and enter required info, click Save;
- Return to Credentials tab and click Create credentials -> OAuth client ID;
- Select Web application for 'Application type', give your app a name and enter the following restrictions:
- Authorised JavaScript origins: enter host names wich will serve WebGL builds (not required for platforms other than WebGL);
- Authorised redirect URIs:
- Add redirect URI for the local loopback requests: http://localhost;
- Add full URIs to the WebGL builds locations (not required for platforms other than WebGL).
- Final result may look like that.
- Click Save;
- Close the appeared popup and click Download JSON button to get the credentials json file.
- Return to Unity editor, open Google Drive settings and click Parse credentials JSON file; select the downloaded credentials json file;
- When under .NET 3.5 scripting runtime, make sure to set API compatibility level to the full .NET 2.0 profile (not subset) to prevent JSON parsing issues on AOT platforms.
The design mostly follows the official Google APIs Client Library for .NET:
// Listing files.
GoogleDriveFiles.List().Send().OnDone += fileList => ...;
// Uploading a file.
var file = new UnityGoogleDrive.Data.File() { Name = "Image.png", Content = rawImageData };
GoogleDriveFiles.Create(file).Send();
// Downloading a file.
GoogleDriveFiles.Download(fileId).Send().OnDone += file => ...;
// All the requests are compatible with the .NET 4 asynchronous model.
var aboutData = await GoogleDriveAbout.Get().Send();
For more examples take a look at test scripts.
The following Google Drive APIs are currently implemented:
Most of the response properties are null by default. You have to explicitly require fields in order for the drive API to return them (using Fields
property of the request object). More info here: https://developers.google.com/drive/v3/web/performance#partial.
A folder in Google Drive is actually a file with the MIME type application/vnd.google-apps.folder
. Hierarchy relationship is implemented via file's Parents
property. To get the actual file using its path we have to find ID of the file's parent folder, and for this we need IDs of all the folders in the chain. Thus, we have to traverse the entire hierarchy chain using GoogleDriveFiles.List
requests.
You can find a naive implementation of the aforementioned logic via Unity's coroutine in the example script and use it as a reference for your own solution or utilize the built-in async helpers FindFilesByPathAsync
and CreateOrUpdateFileAtPathAsync
(requires .NET 4.x).
More info about the Google Drive folders: https://developers.google.com/drive/v3/web/folder.
To perform a partial download you have to supply downloadRange
agrument for the GoogleDriveFiles.Download
request specifying the bytes range you wish to get. Here is an example script for a partial text file download. More info on partial downloads can be found in the API docs.
For the chunked uploads you'll have to use resumable upload requests in a special manner. First, create a resumable upload request (via either GoogleDriveFiles.CreateResumable
or GoogleDriveFiles.UpdateResumable
), supply the file's metadata, but don't set the file's Content
property (make sure it's null
). Send the request and get a resumable session URI from the response. Now you can use the session URI to upload the file's content in chunks. See the Drive API docs for detailed instructions on how to perform a chunked upload using a resumable session URI.
When user finishes authorization flow on mobile and standalone platforms, an HTML string is injected to the active browser window. The default content of the HTML contains a message, asking user to return to the app. You can modify the content of the injected HTML in the Google Drive Settings asset using Loopback Response HTML
field. It’s possible to inject a javascript code to this HTML, which will be invoked right after the auth flow is completed. You can use this option to automatically redirect user back to your app using a custom URI scheme. Specific implementation will depend on the platform: for android you’ll have to add an intent filter to the manifest, for iOS use universal links feature and for Windows bind the application to a URI scheme.
Use GoogleDriveSettings.DeleteCachedAuthTokens
method to clear cached authentication tokens which will force the user to login again on the next request. You can always get GoogleDriveSettings
instance using GoogleDriveSettings.LoadFromResources
static method. While in editor, you can also use 'Delete cached tokens' button for the same effect.
To work with anyone's Google Drive, it's mandatory to complete OAuth procedure for that user, which requires opening a browser window to login and allow the app to access their drive. It's a security measure enforced by Google.
It’s not possible. Google is intentionally blocking authorization requests sent from any sort of embedded browsers for security reasons.
The only legit way to allow multiple users share a drive account is to use Team Drives.
This is possible. To access shared resources you'll have to specify "Shared with me" collection when resolving ID of the resource. Additionally, if the shared resource has been added to the user's drive it'll be accessible via the path finding method described above.
I'll consider publishing when (if) it'll be in a more mature state (full API cover, more tests, less bugs); and whether that'll happen depends on the amount of stars feedback it'll receive :) In any case, the plugin will remain free and open-sourced.