Get desktop application:
View/edit binary Protocol Buffers messages
The class name of chimera activity.
The Nearby Sharing advertising mode.
Used only for Windows App now.
Thes source where the attachemnt comes from. It can be an action, app name, etc. The first 6 source types are being used as FileSenderType in Nearby Share Windows app.
The status of sending and receiving attachments. Used by SEND_ATTACHMENTS.
The remote response is either missing or has an unknown type.
Breakdowns of FAILED_NULL_CONNECTION (Desktop side)
Breakdowns of FAILED_NULL_CONNECTION (android side) Connection failed due to Wifi is disconnected or Bluetooth setting is off or user turn on airplane mode.
Unexpected connection failure.
Connection failed due to Wifi is disconnected or Bluetooth setting is off or user turn on airplane mode.
Unexpected connection failure due to no response frame.
Connection failed due to Wifi is disconnected or Bluetooth setting is off or user turn on airplane mode.
Connection failed due to the medium is not allowed.
The device role to trigger the server request.
The action type of uploading/downloading files to/from the cloud. Used by CLOUD_UPLOAD_START , CLOUD_UPLOAD_END, CLOUD_DOWNLOAD_START and CLOUD_DOWNLOAD_END.
The action is a normal upload/download.
The action is a retry of a previous failed upload/download.
LINT.IfChange The result of creating a cloud sharing request. Used by CLOUD_CREATE_SHARING_REQUEST.
The request was successful.
The user needs to sign in to perform the request. Resolvable failure.
The sharing id or file id already exists. Resolvable failure.
There is an existing active QR code cloud sharing session.
A network error occurred during the request. Resolvable failure.
The request contains invalid arguments. Resolvable failure.
A remote error occurred during the request. Unresolvable error.
The request contains more than 1000 files.
The request contains more than 10GB of files.
The request was successful but this device cannot be notified for receiver updates.
LINT.IfChange The result of registering a receiver for a cloud sharing. Used by CLOUD_REGISTER_RECEIVER.
The request was successful.
The request contains invalid arguments.
Deadline expired before the request could complete.
An internal error occurred during the request.
The request was rejected due to too many receivers.
The service is currently unavailable.
The caller does not have permission to register a receiver.
Generic result status of NearbyConnections API calls.
No status is available
The operation was successful.
The operation failed, without any more information.
The app called an API method out of order (i.e. another method is expected to be called first).
The app already has active operations (advertising, discovering, or connected to other devices) with another Strategy. Stop these operations on the current Strategy before trying to advertise or discover with a new Strategy.
The app is already advertising; call StopAdvertising() before trying to advertise again.
The app is already discovering; call StopDiscovery() before trying to discover again.
NC is already listening for incoming connections from remote endpoints.
An attempt to read from/write to a connected remote endpoint failed. If this occurs repeatedly, consider invoking DisconnectFromEndpoint().
An attempt to interact with a remote endpoint failed because it's unknown to us -- it's either an endpoint that was never discovered, or an endpoint that never connected to us (both of which are indicative of bad input from the client app).
The remote endpoint rejected the connection request.
The app is already connected to the specified endpoint. Multiple connections to a remote endpoint cannot be maintained simultaneously.
The remote endpoint is not connected; messages cannot be sent to it.
There was an error trying to use the device's Bluetooth capabilities.
There was an error trying to use the device's Bluetooth Low Energy capabilities.
There was an error trying to use the device's Wi-Fi capabilities.
An attempt to interact with an in-flight Payload failed because it's unknown to us.
The connection was reset
The connection timed out
unable to enable consent.
The type of consent page user launches.
launch Constellation consent page.
launch device contact consent page.
Refer to go/qs-contacts-consent-2024 for the detail.
* The type of desktop notification event.
Receive attachments.
Send attachments.
Relationship of remote device to sender device.
The remote device belongs to the same owner as sender device.
The remote device is a contact of sender.
The remote device is a stranger.
TODO(fdi): may eventually include desktop, etc. The type of a remote device.
The Nearby Sharing discovery mode.
The status of establishing a connection. Used by ESTABLISH_CONNECTION.
TODO: b/341782941 - : Annote this status when it's confirmed by Nearby Connections team.
Event category to differentiate whether this comes from sender or receiver, whether this is for communication flow, or for settings.
We use event based logging (an event object can be constructed and logged immediately when they occur). To obtain session based information (e.g. durations, counting incoming introductions), we use flowId (sender/receiver) in NearbyClearcutLogger (for android, or clearcut_event_logger as the equivalence for Windows) for all events (may exclude settings), and session_id for a pair of events (start and end of a session). Next id: 81
When new users accept agreements (like grant permission to contacts for CONTACT_ONLY visibility) and are enrolled into Nearby Sharing. This event is used to count number of new users.
User enables/disables nearby sharing from setting or tile service.
User sets visibility preference from setting.
Describe attachments immediately when Nearby Sharing is opened by another app which is used to generate/attach attachments to be shared with other devices.
Start of a scanning phase at sender.
End of the scanning phase at sender.
Receiver advertises itself for presence (a pseudo session).
End of the advertising phase at receiver.
Sender sends a fast initialization to receiver.
Receiver receives the fast initialization.
Sender discovers a share target.
Sender sends introduction (before attachments being sent).
Receiver receives introduction.
Receiver responds to introduction (before attachments being sent). Actions: Accept, Reject, or (for some reason) Fail.
Start of the sending attachments phase at sender.
End of sending attachments phase at sender.
Start of the receiving attachments phase at receiver.
End of receiving attachments phase at receiver.
Sender cancels sending attachments.
Receiver cancels receiving attachments.
Receiver opens received attachments.
User opens the setup activity.
User adds a contact.
User removes a contact.
Local devices all Fast Share server.
The start of a sending session.
Receiver accepts a fast initialization.
Set data usage preference.
Receiver dismisses a fast initialization
Cancel connection.
User starts a chimera activity (e.g. ConsentsChimeraActivity, DeviceVisibilityChimeraActivity...)
Receiver dismisses a privacy notification.
Receiver taps a privacy notification.
Receiver taps a help page.
Receiver taps a feedback.
Receiver adds quick settings tile.
Receiver removes quick settings tile.
Receiver phone consent clicked.
Devices show a phone consent banner in Nearby Share Settings
Receiver taps quick settings tile.
Receiver Installation of APKs status.
Receiver verification of APKs status.
User starts a consent.
After receiving payloads, Nearby Share still needs to transfer the payloads to correct attachment formats and move files attachments from temporary directory to final destination.
Toggle Show Notification setting item in Nearby Share setting.
Set device name
users dropped off opt-in page.
Request setting permissions (Wifi/BT/location/airplane mode).
Set up a connection with the remote device.
Track device states in Nearby Share setting.
Receiver auto dismisses a fast initialization notification.
App Crash event. Used only for Windows App now.
Sender taps the Send button in quick settings
Devices show a privacy notification
Preference usage event (e.g. load/save preferences, etc). Used only for Windows App now.
Default opt in
The result of the setup wizard flow
Sender taps a QR code
QR code link shown
Sender failed to parse endpoint id.
The device is discovered by fast initialization
Send desktop notification.
User sets account preference
Decrypt certificate failure
Show allow permission auto access UI
UI events for transferring files with desktop applications. It includes event types such as DESKTOP_TRANSFER_EVENT_SEND_TYPE_SELECT_A_DEVICE.
Show accept button on Quick Share receive UI
High quality event setup
RPC call status
A QR code sharing session has started
A QR code URL has been opened in a web client/browser instead of in a native Quick Share app.
A HaTS survey session id has been joined with Quick Share flow id.
Previews received.
QR code cloud sharing events begin.
QR code cloud sharing events end.
Cloud sharing RPC performance result
* The distance of the found nearby fast init advertisement.
A device was found in close proximity. distance < fast_init_distance_close_centimeters(50 cm)
A device was found in far proximity. distance < fast_init_distance_close_centimeters(10 m)
No devices have been found nearby. The default state.
* The type of FastInit advertisement.
Show HUN to notify the user.
Not notify the user.
Refer to go/qs-contacts-consent-2024 for the detail.
The Installation status of APK.
The device sources of the clearcut log.
Represents the devices in Nearby labs.
Represents the devices tested by Nearby engs, in the long term can include any devices with newest feature flags.
Represents the devices testing our in-development features before they're released to the greater public.
Represents the OEM partners (like Samsung) that we're working with to verify functionality on their devices.
Represents the device for debugging.
Represents the device for Nearby Module Food.
Represents the device for BeTo Team Food.
Represents the device for Nearby dog Food.
Represents the device for Nearby Team Food.
Status of nearby sharing.
TODO(fdi): may eventually include windows, iOS, etc. The OS type of a remote device.
Used in:
The type of parsing endpoint id failed type.
NULL advertisement is returned due to sender failing to parse advertisement from endpointInfo byte stream from receiver advertisement.
NULL shareTarget is returned due to sender failing to create shareTarget from a valid parsed advertisement stemming from issues in certificates, QR code tokens or device names.
The action to interact with preferences. Used only for Windows App now.
Primary actions/functions towards preferences
Other actions within the 4 actions above
The status of the action to interact with preferences. Used only for Windows App now.
The status of processing attachments after receiver received payloads successfully.
User's response to introductions.
The type of Nearby Sharing scanning.
The Fast Share server action name.
used for analytics logger to record action name.
The Fast Share server response state.
For StatusException.
For GoogleAuthException.
For Internet connect status.
The status of advertising and discovering sessions. Used by SCAN_FOR_SHARE_TARGETS and ADVERTISE_DEVICE_PRESENCE.
TODO: b/341782941 - FAILED_SESSION_STATUS occurs when the status of advertising or discovering sessions is not successful. It can be due to STATUS_INTERNAL_ERROR, STATUS_INTERRUPTION, STATUS_CANCELLED. More session statuses should be logged to determine the status.
Deprecated. QR code is an addition to existing use cases rather than being a separate use case.
The user was redirected from Bluetooth sharing UI to Nearby Share
The purpose of requesting the server request.
When NearbySharingChimeraService#sync() is called.
Requested by chime notification.
For reqular daily sync.
Wen a device opts into Nearby Share.
Requested when Nearby Share automatically enables a device that shares a single account that has already opted in on another device.
When a device enables Nearby Share.
When a device is in fast init advertising.
When device start discovery.
When device tries to load valid private certificate.
When device start advertiseement.
When device contacts list changes.
When showing the C11 banner in Neary Share setting.
For regular check contact reachability.
When selected contacts list changes in visibility setting.
When switching account.
When regenerate certificates
When Device Contacts consent changes
When Nearby Presence identity model exhaust the salt to use on the contact group visibility credential
When Nearby Presence request broadcast and discovery credential from quick share identity provider
The verification status of APK.