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 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.
Created attachment 2220 [details]
Example project showing the problem
When the user is in an activity that's not the main activity and then tries to deploy/install a new version of the app (via Visual Studio), the app doesn't get deployed. Instead the old version is run again.
To solve this you need to deploy the app again (i.e. two times in total) which is quite annoying since this happens every time.
I've attached an example project for this problem.
To reproduce it:
1. Launch the app (from Visual Studio without debugger), then click on the "Change" button to switch to another activity. Stay there.
2. Change the text in Activity2.OnStart() (currently reading "Test1") to something else.
3. Launch the app again (again without debugger).
4. Again click on the "Change" button. Now, the text is still "Test1" and not the new text as it should be.
Oh, I'm using MfA 4.2.4 with Visual Studio 2010 x64 on Windows 7 x64, if it matters.
Just another note: The problem with this bug is that there's no error message at all. So, one has no indication whether the deployment was successful or not.
Hi Sebastian, appologies for the late reply. Please retest with latest release and let us know if this is still an issue.
Hi Dominique, unfortunately my license ran out - so I can't test the latest version.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.