Hi all, 

We have around 100 Zebra TC20 and TC51 devices enrolled into SOTI Cloud, enrolled into our MDM using afw#mobicontrol.

The application in question installs perfectly, I deploy it with a pre-install script which removes any old versions and this works as expected. The application launches and allows you to register the app with a QR code.

The QR codes are required to register the device to a physical business site. Within the application there is a "RESET App" option, which clears the cache and allows the app on next launch to re-register using the QR code method to another site. 

Here's the issue we are experiencing: 

1. We enrol the device into SOTI
2. The app is installed
3. Launch app
4. Scan QR code and register to SITE1
5. Reset the app using the settings “RESET App” button,
   1. The app relaunches straight back into SITE1 and begins the database download again.
6. Reboot the device
7. Launch the app
   1. The app launches straight back into SITE1 and begins the database download again.
8. Reset the app using the settings “RESET App” button,
   1. The app relaunches straight back into SITE1 and begins the database download again.
9. Re-install the app
10. Launch the app
11. The app allows us to register the app again using a QR code.

If I try a manual wipe whilst on the MDM Settings->Apps->!D Cloud->Storage and press 'Clear Data' it takes me back into the site which the device was last registered to.

If I take it off our MDM and uninstall the agent:

Unenroll the device from SOTI 

1. Uninstall the MobiControl MDM agent
2. Install the app using the same .apk that is in the package
3. Launch app
4. Scan QR code and register to SITE1
5. Reset the app using the settings “RESET App” button,
6. The app resets and allows us to scan a QR code
7. Scan QR code and register to SITE2

It appears to be the MDM agent which is causing the issue from what I can see. Removing and re-installing the app fixes the issue, however, this is not a feasible solution as our estate grows. I'm wondering if there's anyone that has seen this issue or something like it before? Is there any locations with permissions I can manually change to fix this? 

Thanks

Rob