{"id":48151,"date":"2020-10-15T11:38:30","date_gmt":"2020-10-15T18:38:30","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/xamarin\/?p=48151"},"modified":"2020-10-15T08:40:33","modified_gmt":"2020-10-15T15:40:33","slug":"android-11-package-visibility","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/xamarin\/android-11-package-visibility\/","title":{"rendered":"Query & Interact with Apps in Android 11 with Package Visibility"},"content":{"rendered":"

Android 11 introduced several exciting updates for developers to integrate into their app experience including new device and media controls, enhanced support for foldables, and a lot more. In addition to new features there are also several privacy enhancements that developers need to integrate into their application when upgraded and re-targeting to Android 11. One of those enhancements is the introduction of package visibility that alters the ability to query installed applications and packages on a user’s device.<\/p>\n

\"App<\/p>\n

When you want to open a browser or send an email then your application will have to launch and interact with another application on the device through an Intent<\/code>. Before calling StartActivity<\/code> it is best practice to QueryIntentActivities<\/code> or ResolveActivity<\/code> to ensure there is an application that can handle the request. If you are using Xamarin.Essentials<\/a>, then you may not have seen these APIs because the library handles all of the logic for you automatically for Browser(External)<\/a>, Email<\/a>, and SMS<\/a>.<\/p>\n

Before Android 11 every app could easily query all installed applications and see if a specific Intent<\/code> would open when StartActivity<\/code> is called. That has all changed with Android 11 with the introduction of package visibility. You will now need to declare what intents and data schemes you want your app to be able to query when your app is targeting Android 11.<\/p>\n

\"Android<\/p>\n

Once you retarget to Android 11 and run your application on a device running Android 11 you will receive zero results if you use QueryIntentActivities<\/code>. If you are using Xamarin.Essentials you will receive a FeatureNotSupportedException<\/code> when you try to call one of the APIs that needs to query activities. Let’s say you are using the Email feature of Xamarin.Essentials. Your code may look like this:<\/p>\n

public async Task SendEmail(string subject, string body, List<string> recipients)\n{\n    try\n    {\n        var message = new EmailMessage\n        {\n            Subject = subject,\n            Body = body,\n            To = recipients\n        };\n        await Email.ComposeAsync(message);\n    }\n    catch (FeatureNotSupportedException fbsEx)\n    {\n        \/\/ Email is not supported on this device\n    }\n    catch (Exception ex)\n    {\n        \/\/ Some other exception occurred\n    }\n}\n<\/code><\/pre>\n
If your app targeted Android 10 and earlier, it would just work. With package visibility in Android 11 when you try to send an Email, Xamarin.Essentials will try to query for pacakges that support email and zero results will be return. This will result in a FeatureNotSupportedException<\/code> to be thrown, which is not ideal. To enable your application to get visbility into the packages you will need to add a list of queries<\/code> into your AndroidManifest.xml<\/code>.<\/p>\n
<manifest package=\"com.mycompany.myapp\">\n  <queries>\n    <intent>\n      <action android:name=\"android.intent.action.SENDTO\" \/>\n      <data android:scheme=\"mailto\" \/>\n    <\/intent>\n  <\/queries>\n<\/manifest>\n<\/code><\/pre>\n
If you need query multiple intents or use multiple APIs you will need to add them all into the list.<\/p>\n
<queries>\n  <intent>\n    <action android:name=\"android.intent.action.SENDTO\" \/>\n    <data android:scheme=\"mailto\" \/>\n  <\/intent>\n  <intent>\n    <action android:name=\"android.intent.action.VIEW\" \/>\n    <data android:scheme=\"http\"\/>\n  <\/intent>\n  <intent>\n    <action android:name=\"android.intent.action.VIEW\" \/>\n    <data android:scheme=\"https\"\/>\n  <\/intent>\n  <intent>\n    <action android:name=\"android.intent.action.VIEW\" \/>\n    <data android:scheme=\"smsto\"\/>\n  <\/intent>\n<\/queries>\n<\/code><\/pre>\n
And there you have it, with just a small amount of configuration you are app will continue to work flawless when you target Android 11.<\/p>\n
Learn More<\/h2>\n
Be sure to browse through the official Android 11 documentation<\/a> on package visibility, and of course the newly updated Xamarin.Essentials documentation<\/a>. Finally, be sure to read through the Xamarin.Android 11 release notes<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
There are several exciting new APIs and enhancements in Android 11. One of the more interesting changes for developers is changes to package visibility. In this post we will see what package visibility is and what changes need to be made to apps to query and interact with apps installed on the user’s device.<\/p>\n","protected":false},"author":544,"featured_media":48149,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[313,556,1],"tags":[9174,9175,24],"class_list":["post-48151","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-android","category-integrations","category-xamarin","tag-android-11","tag-package-visibility","tag-xamarin-essentials"],"acf":[],"blog_post_summary":"
There are several exciting new APIs and enhancements in Android 11. One of the more interesting changes for developers is changes to package visibility. In this post we will see what package visibility is and what changes need to be made to apps to query and interact with apps installed on the user’s device.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/48151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/users\/544"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/comments?post=48151"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/48151\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/media\/48149"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/media?parent=48151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/categories?post=48151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/tags?post=48151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}