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.
Expected behavior: Deploy to device log should indicate that no change was made to the data on the device.
Actual behavior: Deploy to device indicates that the assemblies were re-uploaded.
Nexus 7 JellyBean
MD 184.108.40.206 a4a635018f425d71a253d39114d945c4d6f7cbdb-dirty
MFA 4.2.5 220.127.116.11693106
This was the FastDev issue that was never fixed, so this is not a regression. Not sure if it was ever filed. I did, however, hear that this issue should have been fixed once and for all so I'm filing.
I could reproduce the FastDev issue in the following test environment
HTC flyer with HoneyComb 3.2.1
The presence of this message doesn't indicate that the assemblies were actually uploaded. We don't know in advance whether assemblies will be uploaded or not, this is only determined during the upload phase. The only way you can tell for sure is to look at MonoDevelop's android log which prints each uploaded or skipped assembly.
Maybe the phase could have a better name, like "Synchronizing assemblies with device". Or if we printed all the uploaded or skipped assemblies in the upload pad, it would also be clearer.
This was fixed.