Were the two apps deployed in exactly the same way  (e.g. some options in app policy, installed when kiosk/lockdown-menu is disabled, etc.)?

Have you tried testing the same two apps on different device models from Samsung and other brand(s)?  If so, is there similar problem?

If the two apps are from Google Play store, please provide their Bundle-ID's.

Hi Mark,

Thanks for posting on SOTI Pulse.

And thank you, Raymond, for responding to the post — your expertise and willingness to help are greatly appreciated!

Mark, could you please share the information requested by Raymond.

Dear Mark,

Thank you for posting on SOTI Pulse.

And thanks , Raymond, for responding to the post — your expertise and willingness to help are greatly appreciated!

Mark, could you please share the information requested by Raymond so we can further proceed with the issue.

Dear @Mark Henshaw

Hope you are well.

As per records it seemed a app related issue and below chnagees were recommended.

1. Increase targetSdkVersion from 30 → 34.
2. Keep legacy Bluetooth permissions (BLUETOOTH, BLUETOOTH_ADMIN) with maxSdkVersion="30" for backward compatibility.
3. Ensure BLUETOOTH_CONNECT and BLUETOOTH_SCAN remain in the manifest.
4. Add location permissions (ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION) if scanning/discovery is used, as some devices still require them for Bluetooth scanning.
5. At runtime, explicitly request BLUETOOTH_CONNECT and BLUETOOTH_SCAN when running on Android 12+.

If you have any additional questions or concerns, please don't hesitate to reach out. 

 We're dedicated to providing assistance and support

Also, if this post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

 Kind regards,

     SOTI