I am on OS X Yosemite using Xcode 6.1.1 and on any project when I try to Run it to my device it tells me:
Validating Application example...
I have already tried to clear cache on my device and I have tried to reboot my computer. Possibly a fresh Xcode install might work? Not sure.
Has anyone experienced this or know how to fix this?
Related
I am not able to boot the simulator, this is what I got:
I tried many ways to solve it:
Uninstalled and reinstalled Xcode 7.3 from dmg.
Uninstalled Xcode 7.3 and reinstalled Xcode 7.0 from dmg.
Removed simulators and added again.
But nothing is working in my case, totally frustrated. Can anyone please advice in this?
Thanks.
I had the same problem and got it working by this 3 simple steps :-
1-restart your mac and when the mac is about to start keep holding (Command + R)
2-open terminal from utilities and type this command "csrutil disable" and then restart
3- open the simulator now and check if its working if so do the same steps u did in 1,2 but use this command instead "csrutil enable"
I'm using MAC OS X mountain lion (10.8.4) and xcode 4.6. My IOS simulator gives error that "The simulated application quit, switch sdk"..........
Firstly I tried to reset ios simulator, but its not working.
Secondly, I tried to delete folder "6.1" under ~/Library/Application Support/iPhone Simulator
But i'm unable to find iPhone Simulator folder under Application support.
Thirdly, I uninstalled the xcode 4.6 by draging it to trash. And then installed it again, but the same error appears whenever i try to run any application.
I think, i'm not uninstalling the xcode properly. To uninsatll completely when I type following command
/Applications/uninstall-devtools --mode=all In resoponse I get "Command not found" tried with different commands. Nothing worked. I have wasted my last 12hours to get this work but couldn't.
The problem was in Mountain Lion the Library folder that is situated in the user's account folder is hidden by default. I just unhide it then deleted the iPhone Simulator folder situated in the Library/Application Support and then restarted the xCode everything is OK.
So, stupid problem if you know just 10sec are enough to solve this. Thank God I found myself.
May be someone can find help from this.
Something's changed recently with iPhone Configuration Utility, and I can't install an application on the device. It used to work well, but everything's changed (I suppose) after I updated iTunes to 11.0.2 and iPhone to 6.1.2.
The symptoms are:
Every time I start iTunes I got "Unknown error (-42110)" message.
iPhone Configuration Utility often lags and freezes.
iPhone Configuration Utility shows error "Could not transfer application to device. Error: kAMDUndefinedEror."
Any ideas how to solve it?
PS: Mac mini, Windows 7 Home Premium 64 bit
UPD: Fixed iTunes "Unknown error (-42110)" issue by removing C:\ProgramData\Apple Computer\iTunes\SC Info folder. But iPhone Configuration Utility still can't install an application.
Ohh.. you have updated your device to 6.1.2 so i think you need a Mountain Lion OS for MAC. since it is not able to work with lion 10.7.5 also. Update your system to mountain lion. it will be fine again.
While executing the project on an iPhone, I am getting an error while installing the project through Xcode:
This device is no longer connected.
Whereas I can see the device summary and a green dot if I open the Xcode organiser. What is the problem?
Try quitting Xcode totally and reopening it.
I faced the same situation. I tried
Clean and build
Restarted Xcode
Deleted derived data
Rebooted system
nothing worked for me
I switched the usb port(from left to right port), It just worked.
I know it sounds weird, but it worked for me
The answer is to restart your iPhone and Mac. By doing this your issue will be resolved. This you can try on any version of Xcode
The error comes only after trying to run the project many items, instead of solving the Provisioning Profile issues.
So, it's better to solve the basic error first, or else it will create another hectic problem.
Try to disconnect the device and reconnect it. Sometimes this fixes such kind of problems.
If that does not work, closing and reopening Xcode may help.
Although, since you are mentioning a virtual machine, you might check and see whether there are any conflicts in the attribution of the USB port to one system or another (Windows vs. MacOS).
iPhone/iPad USB connectivity is finicky as it is, and you're running OS X in an unsupported way. I'd suspect that this is the problem.
If you're running VMware, this may help: DEBUGGING ON THE IPHONE & IPAD WITH VMWARE
Basically it's this: Install iTunes on both your host and client OS, as the Apple Mobile Device USB driver for Windows may help your cause.
However, if you're serious about developing for iOS, using a "real" Mac is definitely the easier way.
UPDATE: From your comments, I gather that you need to be able to use Accelerometer input in your app. You could use iSimulate (in the App Store) to send this data from your device to the iOS Simulator.
I got this issue after installing Xcode 5. The solution I found is to restart your system and it works fine.
I had the same problem. It was a broken cable.
I am having some problem in installing my app on the iphone as I am constantly getting the following error message
The service is invalid
Please check your setup and try again
(0XE8000022)
It was running perfectly well till yesterday but since yesterday I am having this problem.
Xcode and the GDB connection is quite temperamental. The device and your Mac can become unsynchronised with each other. My checklist for this sort of thing:
Restart Xcode.
Delete the .app from your iOS device, do a Clean then Rebuild.
Disconnect, reconnect device.
Restart iOS device (90% of the time it fixes things)
If all else fails, restart your Mac (unlikely but it did fix an issue once for me).
I have solved the problem... Only needed to restart the iphone...
Restarting the Xcode wont work in this case. So just restart your iPhone and everything will be fine.
EDIT:
If you have an iPhone 5 running iOS 6.0 and have installed the "iOS Updater" app, you will also have this message.
Finishing the update process to iOS 6.0.1 will resolve the problem.
If you have an iPhone 5 running iOS 6.0 and have installed the "iOS Updater" app, you will also have this message.
Finishing the update process to iOS 6.0.1 will resolve the problem.
This error also happens if the iPhone provisioning profile has expired.
It can be a couple of things, the first and inmediate thing I'd check is to see if your IPhone is currently Downloading or "Preparing Update..." whilst this is running you generally get the "Device is invalid (0xe8000084)" / Error MT1006.
This i found to be the most common thing. so try this first.
And if that fails: Restart your IPhone, and then if that fails restart your Mac/Xcode
and do a clean then Rebuild and deploy..
Hope this helps
This error happens when you try to debug an application in your IPod/IPhone and the device is code-locked or executing another application.
Make sure you can see the menu with all the app icons on the device and try to run again.
Regards
If nothing works then check if your device os is compatible with your Xcode version.
I confirm that restarting your device solves the issue.
But if your device is jailbroken with a Semi-tethered jailbreak you will loose it after a reboot.
To prevent this, do a ldrestart(soft reboot).
In order to perform it, download a terminal application from Cydia, then type:
su
Input your password when asked, the default password is "alpine".
Then type
ldrestart
Unplugged the device and connected again with Mac solved my issue. Did not need to clean, build or restart XCode. XCode 10.2.1, iOS 12.3.1 version.
First remove the app from iPhone before building the app from xcode.
Then Clean All Targets from xcode and then try to build your app again.
SnowLeopard w/ XCode 4.2's Instruments will give this message on newer iOSes.
I had luck by disconnecting my iPhone from my mac, and then Analyzing (Shift + Command + B or Product -> Analyze).
After that I plugged my iPhone back in and did a clean (Command + k) and then run. Worked!
Simply restarting the device (as the alert suggests) fixed the problem, at least on iOS 12.