Bug 7638 - Deployment failed. The assembly directory could not be created.
Summary: Deployment failed. The assembly directory could not be created.
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.2.x
Hardware: PC Mac OS
: --- major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-10-04 06:35 UTC by Chris Hardy [MSFT]
Modified: 2013-05-15 17:10 UTC (History)
8 users (show)

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:

Description Chris Hardy [MSFT] 2012-10-04 06:35:33 UTC
Using the following project: https://github.com/conceptdev/xamarin-samples/tree/master/TaskyProCloned to deploy to an Android emulator, I get the following:

Detecting installed packages

Installing application on device

Deployment failed. The assembly directory could not be created.

ADB Log here: https://gist.github.com/ac750093d342dfae3a4c

This has also been reported as to showing the following error message "Assembly installation failed: The assembly directory could not be created." which is similar to https://bugzilla.xamarin.com/show_bug.cgi?id=6571 but probably not the same.
Comment 2 Jens 2012-10-29 11:55:41 UTC
I have the same problem here on a Samsung Note 10.1
It used to work about a month ago. I don't know if a new firmware or a new MFA version caused this problem here :-/
Comment 3 Jonathan Pryor 2013-01-29 16:23:44 UTC
Which emulator is this seen on? ARM? x86? Which Android version?

Can you provide the device deploy logs: http://docs.xamarin.com/Android/Guides/Deployment%2C_Testing%2C_and_Metrics/Diagnostics#Device_Deployment_Logs

Which IDE are you using? Which platform?
Comment 8 Jonathan Pryor 2013-01-31 23:50:36 UTC
As an attempted workaround, try disabling fast deployment (in Project Options).
Comment 9 Jonathan Pryor 2013-02-01 22:18:22 UTC
Is the shared runtime enabled? If the shared runtime is disabled in Project Options, the app will have a runtime that doesn't create the .__override__ directory by default.
Comment 11 PJ 2013-05-15 17:10:09 UTC
This was fixed. Then it regressed with a certain combination of XS and MFA. It is now fixed for good with MFA 4.6.5.