Assigned
Status Update
No update yet.
Comments
vi...@google.com
Information redacted by Android Beta Feedback.
ri...@gmail.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Description
I am a developer at Disney+ Hotstar, a customer of the Google Widevine ecosystem, which we rely on to protect our digital content.
In our app, we use the PROPERTY_DEVICE_UNIQUE_ID field to uniquely identify an Android device. According to the Android source code comments, "the device unique identifier is established during device provisioning and provides a means of uniquely identifying each device."
However, in our testing, we have observed that the value of PROPERTY_DEVICE_UNIQUE_ID is not always unique. We have encountered multiple different devices sharing the same PROPERTY_DEVICE_UNIQUE_ID. This behavior contradicts the expectation set by the source code comments.
Could you please clarify whether this is the intended behavior? Additionally, are we correctly using this property as a unique device identifier, or is there an alternative recommended approach?
Looking forward to your guidance.