Every device in Bugfender has a unique identifier, but you can associate extra data to a device in order to identify it easily.
Custom device data
If you want to associate a value (String, Integer, Boolean or Float) to a device you can do it with:
Bugfender.setDeviceString("user.email", "[email protected]");
Also you can remove a specific value associated with the device, you can remove it with:
Please note there is a limit of 32 custom keys. Keys can be up to 128 bytes long and values up to 192 bytes long.
How custom keys are seen in Bugfender's UI
Custom keys are shown in the device list as well as in the log viewer:
You can use these details to find the device easily:
Also Bugfender generates a random identifier for each mobile device that has your application installed. This is generated during the first execution and stored in the internal memory for next executions.
You can get that identifier using the getDeviceURL method, so that you can show it on screen, link it in your customer support solution or send it to your server. The device URL can be opened in a browser to jump directly to the logs of this device (authentication required).
On Android, the device serial number is not reliable enough because it can be changed for a specific device or sometimes happened that multiple devices have the same one, but Bugfender collects this ID automatically as the custom key $android_id. You can use it to find a device by Android ID if you want.
Searching for devices
You can find devices using both the Bugfender identifier or any custom data you have associated to the device. You can learn more about searching here.