SOTI Pulse Logo

Unable read Config File - Zebra RDP

M
Mifras
Zebra (OVS) - M.H.Alshaya

Hello everyone,

After upgrading a couple of our Zebra TC8300 scanners to Android 11, we've encountered an issue with the Zebra RDP (Remote Desktop Protocol) application on one of the devices. when we opening the application, getting an error "unable to read config file". Typically, the config file is located at "/sdcard/Android/data/com.symbol.remotedesktop/files/MotoRDP.xml". i did the manual verification, and unable to locate the "com.symbol.remotedesktop" folder on the affected device. even tried a factory reset, but the issue persists.

Interestingly, other scanners of the same model and version that underwent the upgrade are working fine, and we i can see the folder and config file on those devices.

Has anyone else experienced a similar issue or have any thoughts on how to resolve it? Any help or suggestions would be greatly appreciated. Thank you.

android11
a year ago
SOTI MobiControl
ANSWERS
RK
Radim Kadlec
a year ago

Hello,

It's the matter of Android 11+ permissions. I'm really surprised you have any devices with A11 where you have access to /sdcard/Android/data/!

See more at https://supportcommunity.zebra.com/s/question/0D56S0000EBpKYVSQ3/zebra-erdp-on-android-11?language=it

MD
Matt Dermody Diamond Contributor
a year ago

Android 11 introduced restrictions on scoped storage (/sdcard/Android/data) that are universal and not limited to Zebra devices or management through SOTI. This is a fundamental change to Android Enterprise management that the entire industry has had to adapt to over the past several years. 

https://discussions.soti.net/articles/impact-of-android-11-scoped-storage-restrictions-on-android-agent

Under the new storage restrictions an individual app can still access it's own scoped storage directory, but other applications cannot, including even a Device Owner EMM agent like the SOTI Agent managing the devices. This means that while the individual app can read a configuration file from that directory, an external app like the SOTI agent can no longer place the configuration files there or interact with them in any way. If you had devices that were configured on A10- with the configuration files in that directory that were then upgraded to A11 the files will likely remain in that scoped storage directory for the individual app to be able to read. Any devices enrolled on A11 from the get go however will not have any configuration files pushed into that directory because the SOTI agent no longer has that ability. Ultimately whatever business app that you are using has to be updated to accommodate A11+ and scoped storage restrictions by providing you with an alternate means of configuration. 

T
TLMOD@SOTI
a year ago

Hi Mifras,


Thanks for posting on SOTI pulse. Thanks Matt for responding to the post, your expertise and willingness to help are greatly appreciated!


Has your query been resolved? If not, or if you have any additional concerns, please don't hesitate to reach out. We are dedicated to providing assistance and support.


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


Kind Regards,

Similar Discussions