CompletionEvent

Status code indicating that the action referenced by this event was canceled. A canceled action was not applied on the server and was reverted locally.

Status code indicating that the action referenced by this event has failed to be applied on the server because of a conflict. A conflict originates from commitContents(DriveContents, MetadataChangeSet).

When this status code is provided, the metadata and contents that were changed in the original action (if applicable) will be provided through getModifiedMetadataChangeSet() and getModifiedContentsInputStream(), respectively, so that the client can retrieve the data that has failed to upload.

This event provides the context in which a conflict originated, so it can be fixed by the application that caused it. File conflicts are only delivered to the application that committed a change resulting in a conflict, and that application is responsible for resolving the conflict (or the conflicting changes will not be committed).

This class provides access to the base content of the file (the content at the time the file was opened to make the changes in the commit) and the modified metadata and content (that could not be committed due to the conflict). The current metadata and content (the newer values that conflicted with the modified metadata and content) can be obtained using the standard Drive API.

A conflict can be fixed by committing the metadata or content again, possibly with modified further changes that resulted from analyzing the information provided by this class. commitContents(DriveContents, MetadataChangeSet) should be used to commit a conflict resolution. If no such commit is made, the original changes that produced the conflict will be dropped and the current metadata and contents will remain unchanged.

Once the conflict has been fixed by the application, dismiss() should be called so the Drive API can release conflicting resources. If an application requires longer term access to this conflict data (for example persistence of the conflict data across device reboot), the app should handle the persistence of any conflict data provided here, since Drive will delete this conflict data after dismiss() has been called.

Multiple commits by the same application on the same resource may be collapsed by the Drive API. In this case the conflict may refer to multiple collapsed commits. The InputStream provided by getBaseContentsInputStream() will be the very first base version of the content and the InputStream provided by getModifiedContentsInputStream() will be the very last written version of the content.

Status code indicating that the action referenced by this event has permanently failed to be applied on the server. When this status code is provided, the metadata and contents that were changed in the original action (if applicable) will be provided through getModifiedMetadataChangeSet() and getModifiedContentsInputStream(), respectively, so that the client can retrieve the data that has failed to upload.

Status code indicating that the action referenced by this event has successfully been applied on the server.

Indicates to the Drive API that the caller has finished interacting with this event and any related resources should be cleaned up. The client may not continue using this event instance after dismissing.

Returns the account name that was used by the GoogleSignInAccount that requested this notification, or null if the default account was used.

This method is provided so that when a completion event is delivered, the correct GoogleSignInAccount can be built to work with the file.

Returns an InputStream for the initial contents of a file, in the case of a notification with status STATUS_CONFLICT. Returns null for any other status but STATUS_CONFLICT.

This version of the file content is not the current version anymore. In order to get the current version during conflict resolution, the normal flow to read contents should be used. This method may only be called once per CompletionEvent instance.

This can be used in conjunction with getModifiedContentsInputStream() in order to compute the incremental changes that conflicted, so those can be reapplied on top of the current version.

The returned InputStream can be used until dismiss() or snooze() is called.

Returns the id of the Drive resource that triggered the event.

Returns an InputStream for the modified contents that generated this event. If the status of this event is not STATUS_SUCCESS, note that the modified contents provided by this method have not been applied on the server. This method may only be called once per CompletionEvent instance.

The returned InputStream can be used until dismiss() or snooze() is called.

Returns the MetadataChangeSet that was committed during the update that generated this event. The value may be null if the action didn't contain metadata changes. The current metadata can be obtained using asDriveFile() and getMetadata(com.google.android.gms.drive.DriveResource) and be compared with this MetadataChangeSet. If the event has a status other than STATUS_SUCCESS, note that the changes in this change set have not been applied on the server and have been reverted locally.

Modifying the returned MetadataChangeSet will not have any effect unless the set is committed through commitContents(DriveContents, MetadataChangeSet).

Returns a status indicating the result of the action that generated this event. May be one of STATUS_SUCCESS, STATUS_CONFLICT, STATUS_FAILURE, STATUS_CANCELED.

Returns a List of tracking tags provided through setTrackingTag(String). The application can use these tags to relate this event with the specific method execution that generated it.

If the list contains multiple elements, the ordering of the elements is guaranteed to be the one in which the collapsed modifications were applied. Elements in the returned list may not be null.

Indicates that the client could not process the event at the current time, for example because of connectivity issues. The client will be notified again of the same event in the future. The client may not continue using this event instance after snoozing.