Get desktop application:
View/edit binary Protocol Buffers messages
NEXT_ID=8
Used in:
The app name. This will be sent in introduction.
The size of the all split of apks.
The File payload id that will be sent as a follow up containing the apk paths.
A uuid for the attachment. Should be unique across all attachments.
The name of apk file. This will be sent in introduction.
The size of apk file. This will be sent in introduction.
The package name. This will be sent in introduction.
Attachment details that sent in ConnectionResponseFrame. NEXT_ID=3
Used in:
The attachment family type.
This field is only for FILE type.
LINT.IfChange
Used in:
Represents FileAttachment.
Represents TextAttachment.
Represents WifiCredentialsAttachment.
Represents AppAttachment.
Represents StreamAttachment.
Messages used to create pair bindings between devices. An initiator device requests a new bindingId from the BE using the InitiateBinding rpc. This new bindingId is passed to the peer device using a BindingRequest frame. The peer device will use this bindingId to call JoinBinding rpc. If successful, the peer device is response with a BindingResponse frame with status of SUCCESS.
Used in:
Used in:
Used in:
Used in:
Used in:
TODO: b/485307320 - Add more specific error codes.
A package containing certificate info to be shared to remote device offline. NEXT_ID=2
Used in:
The public certificates to be shared with remote devices.
A response packet sent by the receiving side. Accepts or rejects the list of files. NEXT_ID=4
Used in:
The receiving side's response.
Key is attachment hash, value is the details of attachment.
In the case of a stream attachments, the other side of the pipe. Both sender and receiver should validate matching counts.
Used in:
File attachment details included in ConnectionResponseFrame. NEXT_ID=3
Used in:
Existing local file size on receiver side.
The key is attachment hash, a stable identifier for the attachment. Value is list of payload details transferred for the attachment.
File metadata. Does not include the actual bytes of the file. NEXT_ID=10
Used in:
The human readable name of this file (eg. 'Cookbook.pdf').
The type of file (eg. 'IMAGE' from 'dog.jpg'). Specifying a type helps provide a richer experience on the receiving side.
The FILE payload id that will be sent as a follow up containing the actual bytes of the file.
The total size of the file.
The mimeType of file (eg. 'image/jpeg' from 'dog.jpg'). Specifying a mimeType helps provide a richer experience on receiving side.
A uuid for the attachment. Should be unique across all attachments.
The parent folder.
A stable identifier for the attachment. Used for receiver to identify same attachment from different transfers.
True, if image in file attachment is sensitive
Used in:
A frame used when sending messages over the wire. NEXT_ID=3
Right now there's only 1 version, but if there are more, exactly one of the following fields will be set.
Used in:
An introduction packet sent by the sending side. Contains a list of files they'd like to share. NEXT_ID=10
Used in:
The required app package to open the content. May be null.
Used in:
A paired key encryption packet sent between devices, contains signed data. NEXT_ID=5
Used in:
The encrypted data in byte array format.
The hash of a certificate id.
An optional encrypted data in byte array format.
An optional QR code handshake data in a byte array format. For incoming connection contains a signature of the UKEY2 token, created with the sender's private key. For outgoing connection contains an HKDF of the connection token and of the UKEY2 token
A paired key verification result packet sent between devices. NEXT_ID=3
Used in:
The verification result.
OS type.
Used in:
Metadata of a payload file created by Nearby Connections. NEXT_ID=4
Used in:
NEXT_ID=2
Used in:
The list should be sorted by creation timestamp.
A progress update packet sent by the sending side. Contains transfer progress value. NEXT_ID=3
Used in:
True, if the receiver should start bandwidth upgrade and receiving the payloads.
A public certificate from the local device. NEXT_ID=8
Used in:
The unique id of the public certificate.
A bytes representation of a Secret Key owned by contact, to decrypt the metadata_key stored within the advertisement.
A bytes representation a public key of X509Certificate, owned by contact, to decrypt encrypted UKEY2 (from Nearby Connections API) as a hand shake in contact verification phase.
The time in millis from epoch when this certificate becomes effective.
The time in millis from epoch when this certificate expires.
The encrypted metadata in bytes, contains personal information of the device/user who created this certificate. Needs to be decrypted into bytes, and converted back to EncryptedMetadata object to access fields.
The tag for verifying metadata_encryption_key.
NEXT_ID=2
Serialized ParcelFileDescriptor for input stream (for the receiver).
NEXT_ID=5
Used in: ,
A human readable description for the stream.
The package name of the sending application.
The payload type id that will be sent as a followup containing the ParcelFileDescriptor.
The human-readable name of the package that should be displayed as attribution if no other information is available (i.e. the package is not installed locally yet).
NEXT_ID=8
Used in:
The title of the text content.
The type of text (phone number, url, address, or plain text).
The BYTE payload id that will be sent as a follow up containing the actual bytes of the text.
The size of the text content.
A uuid for the attachment. Should be unique across all attachments.
True if text is sensitive, e.g. password
Used in:
Open with browsers.
Open with map apps.
Dial.
NEXT_ID=9
Used in:
At most one of the following fields will be set.
Used in:
No longer used.
No longer used.
NEXT_ID=3
Wi-Fi password.
True if the network is a hidden network that is not broadcasting its SSID. Default is false.
NEXT_ID=6
Used in:
The Wifi network name. This will be sent in introduction.
The security type of network (OPEN, WPA_PSK, WEP).
The BYTE payload id that will be sent as a follow up containing the password.
A uuid for the attachment. Should be unique across all attachments.
Used in: