Bug 28511 - can't deploy to device anymore
Summary: can't deploy to device anymore
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-03-27 21:01 UTC by George Cook
Modified: 2015-03-30 15:15 UTC (History)
2 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 George Cook 2015-03-27 21:01:01 UTC
starting today I can't deploy app to any device from any of my computers.

apps that previously deployed no longer deploy,
new apps that previously deployed fine, nolonger deply,

same on my laptop and desktop,

I get the error

/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" -installdev "/Users/georgecook/Desktop/test/iOS/bin/iPhone/Debug/test.iOS.app" "--devname=Gandalf the white"
Please ensure your device is connected...
Connected to: Gandalf the white
Installing application bundle
writeDictToFile:1241 open failed for /Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist : No such file or directory
MDMCacheDirectoryManifest:1315 writeDictToFile failed to write to /Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist : No such file or directory
error MT1006: Could not install the application '/Users/georgecook/Desktop/test/iOS/bin/iPhone/Debug/test.iOS.app' on the device Gandalf the white: Your application failed code-signing checks.  Check your certificates, provisioning profiles, and bundle ids.   Probably your device is not part of the selected provisioning profile (error: 0xe8008015).
The application was terminated by a signal: SIGHUP
Comment 1 Sebastien Pouliot 2015-03-30 14:24:25 UTC
This is not a bug,

> Check your certificates, provisioning profiles, and bundle ids.   Probably your
> device is not part of the selected provisioning profile 

The error message tells you that your Apple developer certificates and/or your Provisioning profiles are outdated. Apple tools won't allow you to upload to device without a correct signing identity.

You'll need to update them on Apple developer centre (and then upload them to devices) to continue developing.
Comment 2 George Cook 2015-03-30 14:57:44 UTC
But I am debugging on the device form xcode just fine on the same machine.

I can debug on the devices using appcode too.

It's only xamarin that doesn't work. It stopped working after Apple asked me to accept their updated terms and conditions. From that point on Xamarin doesn't deploy.

Profiles are present and correct - and like I say, deploying fine from xcode and appcode.
Comment 3 Sebastien Pouliot 2015-03-30 15:04:51 UTC
The certificates/provisioning profiles selection is likely different across your tools, i.e. it's configurable, and the one (from many*) you're using with Xamarin is likely out of date.

Please include the full build logs for Xcode and your application and we'll have a look.

* old profiles are needed so an old application can still work (if it was signed while valid).
Comment 4 George Cook 2015-03-30 15:14:24 UTC
Ok - I found out what it was. 

I had to restart xamarin *after* doing a  build in xcode. appears to be fine now.

Sorry for noise chaps/chappettes.
Comment 5 Sebastien Pouliot 2015-03-30 15:15:24 UTC
np :) that restart likely caused XS to reload the existing certificates and profiles from disk.