Hi Ayaskant,
In order to do this, your app will need some way of distinguishing between an AirWatch / Non-AirWatch device. If the device is operating in an AirWatch context then call start, if not don't call start in AWController. There are a few ways to distinguish depending on what services are available to your app, some of our customers have built their own mechanism via an API which can tell their app is the device is in an AirWatch context. Another way to do this is to check for existence of the Workspace ONE or Agent app on the device (but this approach is not as reliable depending on the use case, for example...the customer may not be in YOUR AirWatch environment but may be enrolled in another environment and has the WS1 app or Agent installed).
Hope this helps.
Thanks,
Lucas
What URL scheme can i use to check for existence of workspace one?
awws1enroll can be used to check for existing of WS1
Thanks,
Lucas