Application Build not loaded on device - iphone

When I tried to upload a build on device it give the following error.
Your mobile device has encountered an unexpected error (0xE8000001)
I am unable to solve this problem. Can anyone tell me why this is happening?

Anytime i get an unexpected error i hard reboot my device by holding down the home and lock buttons until the apple logo appears. No idea what causes it, but the reboot usually fixes it.

This seems to be a bug that is puzzling many users. No idea what the error actually is, but on this forum people claim:
this error will require you to restore your iPhone/touch, either through Xcode's Organizer window or iTunes. No way around it".

This basically happens when there's a communications error between Xcode and the iPhone which leaves Xcode confused about the state the iPhone is in. (You can actually make it happen sometimes by unplugging the phone in the middle of installing a build.) As the error message's text suggests, turning the iPhone off and back on will usually clear the error. You may sometimes have to restart Xcode or even your whole Mac, but not often.

To all
The problem get solved. When I set provisioned profile of device. It works.
Thanks for your help & guideline.

Related

Apple rejects our latest App

Our latest app was rejected by giving following reason
"when the user launches the app, a blank black screen is produced"
We had tested this many times and did not notice this issue. We tested again now, but it is working properly for us.
Can someone help us to find out the issue?
I don't think anyone can help you find this issue, My suggestion would be to follow up with the Review Team and try to obtain as much information as you can from them. Such as, what device was it tested on, what OS version and so forth.
Ah, the many woes of the app store process.
Make sure that you have tested your app not only on the simulator but also on a physical device.
Secondly the issue might be that you have made some (false) assumptions about the data on the device, that you might have put there manually, but isn't handled when installing anew.
Therefore a plan of attack might be to remove the application complete from both device and simulator and try running them from a fresh install rather than on top of an already installed installation.
Best of luck!
Try to build and install your app from a clean state. You may not be seeing the same as the reviewer, because if you only "build&run" all the time, old files, which are not part of the final build, are still present on your device or in the simulator.
So clean the build folder, remove the app from your device, and try again. Also, check if you app can live without an internet connection.
Your best bet is to discuss this directly with the Apple guys (Resolution Center).

Application running on iOS4.2 but not on iOS5

I have an application of which i have created .ipa file and tried to run the application on iOS5. If i run it on iOS 5, it works but when i try to run it on iOS4.2 it doesn't work. It opens up, shows black window and then back to home screen. I have tried things like deleting app, installing again, restarting phone, reseting it's setting.
I know most people face vice a versa situation. Let me know if any one of you have good solution for it.
Thank you,
Anks
Your only hope is the console, see what it says about why it is dying. If that doesn't give any messages, stop it in the debugger in AplicationDidFinishLaunching, and step as far as you can...
The console though SHOULD have a message about why the app is terminating early. Without knowing why, we cannot help further.
Did you change your build target immediately before creating the .ipa? If so, do a clean build and then re-create the .ipa file again—that may fix your problem.

iPhone Project Not Running (more than once)

I have an iPhone app that I'm trying to run on my phone via Xcode.
It installs and runs without an issue
I make a change in the source code (negligible, like an NSLog())
It installs without an issue
Running causes the error:
Error Starting Executable 'myApp'
Don't know how to run. Try "help target".
I uninstall the app, and reboot the phone
It installs and runs without an issue (until I make another change; then I have to repeat this dance)
Needless to say, having to uninstall the app, reboot the phone, and reinitialize the environment (i.e. set prefs) takes an unreasonable amount of time, and is probably indicative of a serious problem. The issue is, the only vague error message I receive gets me nowhere on Google. Where on earth could this issue be coming from?
With some help from #iphonedev, I figured it out. Turns out it's a glitch in iOS 5 beta. The way to fix it is to remove the device from Development Devices, then re-add it.
Yeah just restarting the iPhone with the lock and home buttons fixes this. Had it happen a few times to me

No provisioned iPhone connected....!

Hii all,
I tried to test my application on the simulator and it fails. Just the day before it was working fine. i checked in the organizer window.. all the provision certificates are installed, but still the color is Orange,. its not working. and when i try to debug the application it shows "No provisioned iPhone connected" error.
I got the same problem before, at that time i changed the name of the folder which specify the iphone version, but unfortunately i don't remember now where that folder is. Can anyone help me please.. or is there any alternative.
Thanks,
Shibin
There are (at least) two possibilities here. As Alex says, if you are trying to run on the Simulator then you need to switch your active SDK to one of the Simulator options. The screen shot is of a rather old version of the SDK but the principle is the same.
If, on the other hand, you are trying to run on a phone that has worked before you usually just need to reboot your handset. Sometimes the process that the debugger connects to gets in a state and doesn't respond. Restarting usually works.
You can the No provisioned device connected error only when you try to test on the device. Did you check the active configuration of your project? In order to run the Simulator you should have the corresponding build configuration selected. See the screenshot: alt text http://img255.imageshack.us/img255/7594/xcodeconfig.png
So you are seeing orange color status of the iphone in organizer? If it is the problem simply switch off your device and switch-on again. Try reconnecting the device. This solves my same problem most of the time.
Hope this helps.

Error Installing iPhone App on Device

I set up all my certificates and keys today and am trying to run my project on my iPhone.
I'm encountering this strange error:
Your mobile device has encountered an unexpected error (0xE800003A) during the install phase: Verifying application
Poking around the Apple Developer forums, I've attempted to set new certificates and provisioning profiles as well as editing Info.plist, but no matter what I do I can't seem to run the app on my device.
The only think I can currently think of is that my project name in Xcode differs slightly from my development provisioning profile (it uses a question mark), but I've named it according to Apple's conventions: com.mycompany.myapp, so I'm unsure if that's the problem.
Any ideas?
Edit: I've hard restarted the phone, rebooted Xcode, cleaed my targets, set up a new wildcard App ID and respective provisioning profile and still nothing. Any other ideas?
It turned out that I had 2 certs in keychain that were simultaneously overwriting each other! I hope this helps people in the future.
You should create a wildcard app ID; com.mycompany.*. That may help.
I've encountered this on many occasions. What i do is clean all targets, shut down xcode, and hard reboot my phone.
This is a different error than the more common problem of getting the cert wrong...
Restore the phone (using the XCode Organizer to reload the latest OS), to be safe do not restore from backup when you sync with iTunes the first time (it'll still keep your number when you sync even if you don't use the backup). I've had to do this a very few times, the last one was when it was in the middle of deployment when I unhooked the phone from the cable (had to answer a call).
Try the reboot (of the phone) first, hooking it up with XCode off. But if that does not solve things, restore is the way.
The console tab in the XCode Organizer sometimes gives helpful hints as to what happens during the install phase. In one case my problem was my app already existing on the phone. I deleted my app and the install succeeded.
Regardless, it looks like a lot of error messages are bundled into this one cryptic message and to really diagnose what is going on, I found the Console tab very useful...
One other thing to try is reinstalling the iPhone SDK. I ran into an error like this when I first got my developer key and this was the only way around.
Just want to say to everyone, when you go to edit Targets-> be sure to set "configuration" in the top left corner to "All Configurations" or the correct config you are building for (Debug or Release). You might think you have things set correctly but it will be for the wrong configuration.
I've seen that error on a correctly provisioned device that has had success installing apps from XCode before, and I've had luck restarting the device and trying again. Maybe that will help.
Try running in Release mode instead of Debug. I have a working project with this problem. No idea what the issue was, but running it in Release mode works, but Debug mode produces the error code.
I have a support ticket open with Apple dev support for the same problem, and (FWIW) I'll post their recommendations if and when they can get my toolchain working.
Try this: (source: http://ephemera.lifewithalacrity.com/iphone_development/)
Even though this is supposedly only for Distribution builds, it helped me to be able to install my Debug version on my iPhone again, after it mysteriously broke yesterday.
"just triple check that all the code signing in your project properties are clear or default"
Note, this is the PROJECT properties as opposed to the TARGET properties. I set my Code Signing Provisioning Profile back to the default and removed the Code Signing Identity string.