Bug 36538 - Error editing manifest
Summary: Error editing manifest
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: 4.2.0 (C8)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-03 16:39 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-08-23 07:32 UTC (History)
10 users (show)

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

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 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:
Status:
VERIFIED FIXED

Description Mikayla Hutchinson [MSFT] 2015-12-03 16:39:33 UTC
To repro:

1. Create new Xamarin Forms (Portable) solution.
2. Open Project Options.
3. Click on one of the permission checkboxes.

The following error is shown:

Value cannot be null.
Parameter name: packageNameOrAssemblyName

The Project Options cannot be closed. Had to kill VS.
Comment 1 AndroidePhone 2015-12-16 14:35:41 UTC
same here
Comment 2 androidedev 2016-02-25 13:31:49 UTC
Exactly same as mhutch : 

1. Create new Xamarin Forms (Portable) solution.
2. Open Project Options.
3. Click on one of the permission checkboxes.


Value cannot be null.
Parameter name: packageNameOrAssemblyName

I can check/unckeck the checkboxes but the error appears with every click in checks.

VS must be killed couse you cannot save nor close the properties page due to the dialog error showing.

I have tested with VS2015 and VS2013 and the error raises in both.


Is this bug open since 2015-12 w/o any coment or workaround ?
Comment 3 androidedev 2016-02-25 13:47:36 UTC
Workaround :

For the post of ScottNimrod :

https://forums.xamarin.com/discussion/53878/bug-unable-to-set-access-fine-location-permission-for-android-app

you must set the app name and package manually in manifest and then it works, example of manually edited manifest for the PhoneWorrd of xamarin examples :

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="Phoneword.Phoneword" android:installLocation="auto">
	<uses-sdk android:minSdkVersion="15" />
	<application android:name="Phoneword.Droid"></application>
</manifest>



After that you can touch the permissions again via properties page and it works :

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="Phoneword.Phoneword" android:installLocation="auto">
	<uses-sdk android:minSdkVersion="15" />
	<uses-permission android:name="android.permission.CALL_PHONE" />
	<application android:name="Phoneword.Droid"></application>
</manifest>
Comment 4 Josh Williams 2016-03-09 05:25:16 UTC
Still happening. This is easy to fix but ...

This was my very first time trying Xamarin.Forms, in VS (one of the main selling points of a Business license). And it barfed. 10 minutes into the tutorial. Reported 3 months ago.




........
Comment 5 Mike 2016-06-04 04:42:07 UTC
The problem still exists......
Comment 6 Ilyas Rima 2016-06-14 09:35:49 UTC
I manually modified the AndroidManifest.xml just as androidedev@gmail.com  suggested and it worked
 
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
  <uses-sdk android:minSdkVersion="15" />
  <uses-permission android:name="android.permission.CAMERA" />
  <uses-permission android:name="android.permission.FLASHLIGHT" />
  <application></application>
</manifest>
Comment 7 Mike 2016-06-14 09:37:27 UTC
But if you open it from visual studio, it will still change.
Comment 8 Juan Marcelo Tondato 2016-08-19 18:44:56 UTC
Hi,

This issue was resolved in our current public Beta bits (XVS 4.2.0).

Thanks!
Comment 9 Mike 2016-08-20 14:22:33 UTC
@Juan, Are you sure it's fixed because update Xamarin, not Visual studio?   I thought it fixed because visual studio 2015 sp3