I wasted several hours today trying to understand why my app would not install on the iPhone. Halfway through copying, XCode would throw error message 0xE8000001. A more detailed description appeared in the Console.
MobileDevice: copy_symlink:
Could not create symlink on device: 16
MobileDevice: transfer_package: Could not copy
/Users/username/iphone/MyApp/build/Debug-iphoneos/MyApp.app to PublicStaging/MyApp.app on the device: (null)
MobileDevice: AMDeviceTransferApplication: Could not copy package to device via AFC: kAMDUndefinedError
The app was properly signed and I had installed it on the phone before. After a lot of digging around I found this post.
It turns out that if something prevents XCode from copying an app to the phone, the app is left in this directory:
/private/var/mobile/Media/PublicStaging
Lo and behold I navigated to that folder on the phone and my app was left hanging there. I deleted my app's folder from PublicStaging and ran Build & Go, which installed the app with no problems. I was able to navigate to this folder on my jailbroken iPhone; however, my colleague had the same issue on his virgin iPhone.
To get the app to install on his phone I had to edit the Info.plist file and changed Bundle Name. I also had to change Project -> Edit Project Settings -> Packaging -> Product Name to match the Bundle Name and viola! The app installed successfully. Unfortunately the old app folder will be left lingering in PublicStaging until the next restore.
Hey guys! Are you getting into iPhone dev? You check out our latest 360 event? Not to be a salesy on your blog, I know how weak that is, BUT wanted to point it out, in case you hadn’t seen it. Feel free to delete after reading
Oh Man!!! Great! I found finally a solution!!! Well, I have to say I’m actually green for all this things and it is always complicated to me.
Thanks God for Internet and Cool that you could solve your problem. I have read the other post and it is also very useful. But what I can not understan is why such issues happen with a virgin Iphone.
So..great and very useful Post and nice Blog!!!
Whatup john. I did not burn-after-reading. We are getting heavy with iPhone dev and I did see the 360 event…got anything in the works for the right coast?
Hi! Thanks for the linkage and bravo on getting further with the problem than I did. The 2.2.1 firmware update has (so far, fingers crossed) kept this error out of my life lately. Speaking of the 360 event, I’ll be talking about using Google App Engine with the iPhone there one week from today.
Cheers and thanks again for your post,
Jonathan Saggau