View Source API Reference google_api_firebase_app_distribution v0.3.1

Modules

API client metadata for GoogleApi.FirebaseAppDistribution.V1.

API calls for all endpoints tagged Media.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.FirebaseAppDistribution.V1.

Information to read/write to blobstore2.

A sequence of media data references representing composite data. Introduced to support Bigstore composite objects. For details, visit http://go/bigstore-composites.

Detailed Content-Type information from Scotty. The Content-Type of the media will typically be filled in by the header or Scotty's best_guess, but this extended information provides the backend with more information so that it can make a better decision if needed. This is only used on media upload requests from Scotty.

Backend response for a Diff get checksums response. For details on the Scotty Diff protocol, visit http://go/scotty-diff-protocol.

Backend response for a Diff download response. For details on the Scotty Diff protocol, visit http://go/scotty-diff-protocol.

A Diff upload request. For details on the Scotty Diff protocol, visit http://go/scotty-diff-protocol.

Backend response for a Diff upload request. For details on the Scotty Diff protocol, visit http://go/scotty-diff-protocol.

Backend response for a Diff get version response. For details on the Scotty Diff protocol, visit http://go/scotty-diff-protocol.

A reference to data stored on the filesystem, on GFS or in blobstore.

This is a copy of the tech.blob.ObjectId proto, which could not be used directly here due to transitive closure issues with JavaScript support; see http://b/8801763.

Android App Bundle (AAB) information for a Firebase app.

A feedback report submitted by a tester for a release.

A group which can contain testers. A group can be invited to test apps in a Firebase project.

A person that can be invited to test apps in a Firebase project.

This resource represents a long-running operation that is the result of a network API call.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.