Bug 38870 - multiple "data" IntentFilterAttribute does not generate valid AndroidManifest.xml
Summary: multiple "data" IntentFilterAttribute does not generate valid AndroidManifest...
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 6.0.1 (C6SR1)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2016-02-18 11:26 UTC by Petar Panic
Modified: 2016-02-19 02:24 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

example (1.06 KB, text/plain)
2016-02-18 11:28 UTC, Petar Panic

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Petar Panic 2016-02-18 11:26:37 UTC
When specifying IntentFilter attributes DataSchemes, DataMimeTypes and every other Data* intent attribute that can be used to specify multiple entries, generates an empty <data/> tag.

This beats the purpose of those attributes as there is again the need to use multiple intent filters to make this working.

In the attachment are :
- the intent and the intent filter attributes that we used
- the part of the AndroidManifest.xml that is being generated from the intent filter code

I'm using Visual Studio 2015 with Xamarin.VS extension if that matters.
Comment 1 Petar Panic 2016-02-18 11:28:41 UTC
Created attachment 15084 [details]
Comment 2 Atsushi Eno 2016-02-19 02:24:50 UTC
Yes we were aware of this bug, and it was fixed for the next release. Thanks for the report. [master bbf82a0]