AFW app uninstall permission/App login issues

Hi,

Two pronged question for you:

Firstly, we have a number of Android devices enrolled in Android For Work via UEM 12.8, of which I am the administrator. I am more experienced in the admin of iOS devices in MDM software so trying to change polices on an AFW device is blowing my little mind! We push a facilities app onto each device via User Groups, but are experiencing problems with it and so I'd like to uninstall the app from a device but the UEM policies won't allow it. Can someone point me in the direction of what I need to enable/Disable to allow me to uninstall the app?

Secondly, onto the problem we're experiencing...and I don;t believe this to be a UEM problem, but would like to rule it out.

The devices we use are Samsung Xcover 4, all devices setup exactly the same by myself through UEM/AFW. The Facilities app we push onto the devices requires a username and password before it lets the user login. We are experiencing issues with random devices whereby the app won't login unless the device is connected to power, either at the wall or to a computer. As soon as you remove the device from power it stops allowing the user to login. This can happen at 89% battery or 21% battery on different devices, there is no rhyme or reason behind it because it also isn't happening on all devices.

If we wipe a device and re-enroll it, the app works perfectly although we have had two come back with the same problem after around a week.

Anyone any ideas? Thanks in advance

1) if memory serves, the way bb uem is configured for afw app forced install, it locks Uninstall. Only way I know of allowing Uninstall is to remove the force install and leave as optional. Will double check on bb uem 12.11 tonight though as I'm out of office all day.

2) my experience with Samsung xcover4 has been poor as they have numerous bugs in software and basically never update it outside of once or maybe twice a year. Last os on north America sm-g390w for example was a November or October build from 2018.
EU F version apparently has Android 9 now, so W version should receive similar this summer some time.
That said, can attempt to clear app cache by going into system settings >apps, find app and clear cache. If that doesn't work, try clearing data as well.

Have you reported the app oddness to developer? Could be something on their end they can resolve