[BUG] Device ID not Matched

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

I am attempting to get keepass2android approved for use at work. I use an android phone with a work profile. Keepass2Android works great to access OneDrive for my personal profile. However, there appears to be a bug with the work profile (a separate Google Play Store installation of keepass2android). There is an authentication ID not being passed, according to my security support team. I have included an image that they sent, to help describe what they need to happen. Currently I am able to get this working on the work profile, by means of a temporary bypass in our policy. Once they remove the temporary bypass, keepass2android no longer has access to our work provided OneDrive.

Describe what you expected to happen:

For the Device Identification to be passed back, and match, during authentication. This would allow my security team to avoid making an exception in our security policy.

What version of Keepass2Android are you using?

1.14r4

Which version of Android are you on?

16

No files, tests, or entry points are named. Start by locating the Android authentication and device-identification handling, then reproduce the issue with Keepass2Android 1.14r4 in an Android 16 work profile against OneDrive. Done means the device identification is passed back and matches during authentication without a policy bypass.