Bug 38386 - Opening AndroidManifest.xml after creating FormsApp leads Manifest being marked as dirty
Summary: Opening AndroidManifest.xml after creating FormsApp leads Manifest being mark...
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: (C7)
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2016-02-03 18:03 UTC by Manish Sinha
Modified: 2016-04-18 17:39 UTC (History)
5 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 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:
Status:
VERIFIED FIXED

Description Manish Sinha 2016-02-03 18:03:57 UTC
Steps to reproduce

1. Create Multi-platform > Forms App
2. Open AndroidManifest.xml file
3. Close it

Expected: Since there have been no changes to the manifest, it should close cleanly
Actual: The manifest file is marked dirty and a dialog shows up asking if we want to save it

XS Info: https://gist.github.com/anonymous/7ca46df4a6d7b306ed08

Screenshot: http://i.imgur.com/pkqU8am.png
Comment 2 xamarin-release-manager 2016-02-08 14:58:43 UTC
Fixed in version 6.0.0.3343 (master)

Author: Matt Ward
Commit: 3d1067c825aef525667258d8f79c2578a96a9fdc (xamarin/md-addins)
Included in Commit: 30d2e6e933657de034ca73626259cd5feff3b234 (mono/monodevelop)
Comment 3 Abhishek 2016-04-18 17:39:06 UTC
I have tried this issue and able to reproduce this issue at my end with the following build: XamarinStudio-6.0.0.3258_4a40d2673da583d007f409b8197293676e1b3e3d

Screencast: http://www.screencast.com/t/JqFJ97rdwz

To verify this issue, I have checked this issue with latest C7 build:
XamarinStudio-6.0.0.5044_89a1f5ab1d36cdc19f7e1b9b2a60a69a8a599b0d. Now this issue is working fine. Here is the screencast for the same: http://www.screencast.com/t/QlLanqP8eOt

Hence closing this issue.

Thanks!