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.
Created attachment 1310 [details]
Galaxy tab logcat
Getting a "Failed to install assemblies" message when trying to debug an application on an android device (not emulator) and therefore the application cannot be debugged
Steps to reproduce:
1. Create a new "hello-world" type android solution
2. Debug the application on the device in Active Configuration: Debug
(Make sure it is on a clean device - no MonoAndroid API Support or MonoShared runtime on device)
Get error saying "Failed to install assemblies" when deploying to device and user cannot debug
No error, assemblies installed and user can successfully debug
Samsung Galaxy Tab: 7.0 Plus, Honeycomb
Things to note:
- Will test on a different device, as it may be a device specific issue, and modify the severity accordingly
- When you debug the first time this error occurs, if you attempt to debug again everything gets deployed successfully and the user is able to debug
Created attachment 1311 [details]
*** Bug 3427 has been marked as a duplicate of this bug. ***
Repro'd on HTC Flyer with Gingerbread (that's the duplicate)
Important info to gather for this issue:
- run "adb shell ls -l /data/data/[app name]/files/"
Hopefully this will list all the files and directories inside, one of which is going to be a directory called .__override__ . If this directory doesn't show up, run adb shell ls -l /data/data/[app name]/files/.__override__
The objective is to figure out what are the permissions for the files and for the .__override__ directory, particularly who the owner is (root or app## (where ## is a number)). If the owner is root, this can cause fastdev to fail.
- try deploying from the command line
In the project directory, run "xbuild project.csproj /t:Install /verbosity:detailed" (replace project.csproj with your project filename)
This will do much the same thing that MD does (with lots more logging), but the codepath is slightly different. If this works consistently, then it's an MD-only bug and will require some additional testing.
360 Logica is experiencing this issue with
LG-P500 2.2 Froyo on RELEASE
Waiting for packaging processing to complete
Getting package list from device
1938 KB/s (5715942 bytes in 2.880s)
74% complete74% complete
Failed to install assemblies
on MFA 4.0.5, MD 220.127.116.11
Shana will send a new build to QA to help identify this issue.
Additional environment, slightly modified behavior (100%Completed100%Completed, then Failed to Install Assemblies)
Release mode deploy to Galaxy Tab using MfA4.0.3, MD18.104.22.168, Windows 7:
Despite saying Failed to Install Assemblies, the app is loaded on device and works correctly. Without cleaning device or solution, reloading MD and re-running will work fully without generating an error.
To re-experience crash, delete all app data from device then clean/rebuild/run
This behavior is not seen by me using Visual Studio.
I am unable to reproduce on debug and release with fastdev enabled on our current stable of XA (4.6.6 - 6d7480e9). Considering some of the more recent fastdev issues encountered and fixed, I am marking this as resolved.