This content is likely not relevant anymore. Try searching or browse recent questions.
#AndroidTalksEnterprise - Post 9 - App Development & Quality - Prevent Failed Intents
Hi All,
Welcome back to - #AndroidTalksEnterprise.
Today we start Series 5 of our talks series with a new topic - App development and quality.
If a device has a work profile, the profile's settings are under the control of the IT admin. The IT admin can choose which apps are allowed for that profile, and can control just what device features are available to the profile.
If the device has work profile, there are implications for apps running on the device, such as:
- By default, most intents do not cross from one profile to the other. If an app running on profile fires an intent, there is no handler for the intent on that profile, and the intent is not allowed to cross to the other profile due to profile restrictions, the request fails and the app may shut down unexpectedly.
- The profile IT admin can limit which system apps are available on the work profile. This restriction can also result in there being no handler for some common intents on the work profile.
- Since the personal and work profiles have separate storage areas, a file URI that is valid on one profile is not valid on the other. Any intent fired on one profile might be handled on the other (depending on profile settings). This will mean that it will not be safe to attach the file URLs to the intent.
Your Thoughts:
To best support work profile, your app needs to be able to handle the points highlighted above. Please feel free to let us know below if you require any further information on this post.
Thanks,
Android Enterprise Community Team.
Link to post
Delete post?
This will remove the reply from the Answers section.
Notifications are off
Your notifications are currently off and you won't receive subscription updates. To turn them on, go to Notifications preferences on your Profile page.