Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
- In the Android Manifest Editor GUI, there is no checkbox for setting "android.permission.READ_CALL_LOG"
- if manually added to the AndroidManifest.xml, it will be deleted next time the file is updated through the manifest editor GUI
Just an observation/thought: READ_CALL_LOG only appeared in API level 16 (http://developer.android.com/reference/android/Manifest.permission.html#READ_CALL_LOG).
If the application is targeting a lower API, that might explain why Xamarin Studio is remove the permission.
I created a empty "TestBug" project, targeting 4.2 :
In the manifest I've set it it API level 17 in "minimum" and "target" version :
<uses-sdk android:minSdkVersion="17" android:targetSdkVersion="17" />
Still acts the same: checkbox not available and manually inputed permission removed when updating the manifest through the editor.
Michael: XS should not be removing elements from Properties\AndroidManifest.xml.
a) load "unknown" permissions from the manifest into the UI, so we don't remove them when updating the manifest
b) load permissions from Android.Manifest.Permissions (via the code completion system) instead of a hardcoded list, so they'll always be up to date, and match the target SDK too.
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!