"failed to get to process -1" - ios

i have this big problem with my iOS Developer (i guess).
Sometimes (every 2 or 3 times) when i run my app on my iPhone 5S it stops and the error "failed to get to process -1" appears. After that my iPhone is stuck and frozen and i have to reset it (Power + HomeButton). I searched through the web and found that it has something to do with the Code Signing.
Something like "Only use iOS Developer" and "code signing entitlements only for debug" i tried like every variant with this, but without success. It is kind of weird, because all the others with the same problem seem to have it all the time. My iPhone only gets stuck every now and then.
I have already reseted it to defaults and tried it again, no success. I deleted the Provisioning Profile and add it again, but again with no success.
It's a real pain.
Here is a screenshot of my settings that i used to use:
And here the error:
I did nothing, it just occurred and it happens in every project,
Can you guys help me? I am really tired of this problem and i am not able to find a solution.
I am running XCode 5.0.1 on the latest OS X Mavericks. On my iPhone 5S i have the latest iOS 7.0.3.
Thanks in advance!

Same problem here, seems related to xcode 5.0.1. Rolling back to 5.0.0 solved the issue.

Related

Can't compile iOS-App in Ad-Hoc mode (Xamarin.iOS)

So basically I'm following this official Xamarin guide to release my app in the AppStore.
However no matter what I try (changing signing profiles, different build options) the solution-process crashes every time after 1-2 minutes with different errors that don't explain what exactly went wrong (signing error, user aborted?!, etc.).
After the error is shown I always have to reconnect to the Mac.
What could be the problem?
EDIT:
Tool exited with code: 1. Output: CSSM_SignData returned: 800108E6
/Users/metadokentwicklung/Library/Caches/Xamarin/mtbs/builds/mWIDAS_iOS/806c20450998d745a5c8df0e4928100f/bin/iPhone/Ad-Hoc/mWIDAS_iOS.app:
errSecInternalComponent mWIDAS_iOS
I tried the publish profiles (Ad-Hoc,AppStore,automatic) and provisioning profile.
Okay solved the problem myself a few days ago. Dumb mistake on my behlaf.
I use the same monitor for the Mac Mini and the Windows PC so I didn't see the popup on the Mac prompting me to accept the use of the keyfile.
After I agreed to it everything worked like a charm.
I resolved this issue by:
Cleaning my solution
Closing VS4Mac
Shut down Macbook Pro
Start Macbook Pro
Reopen my solution
Build iOS head project (I am working in Xamarin.Forms)
And it built successfully this time. I am noticing lots of issues from Windows VS are creeping into VS4Mac by each update. Not sure why this was happening but that resolved my issue

unable to verify mobile app on IOS9 using Xcode 7

I have been trying to take advantage of Xcode now allowing developers to test on devices without being enrolled on the developer program.
This was working just a few weeks ago, no problems at all
however, for no apparent reason, I am getting this error message whenever i try to run my app on the iPhone:
after some googling a website led me to this page in the settings app:
From what i can gather on google, The problem is that the app isn't verified. However when i click verify nothing changes. The text at the top of the screen changes very briefly (i assume it's saying loading)
I have tried deleting the provisioning profile, that Xcode had created, and clicking fix when Xcode tells me it can't find the profile. Nothing changed
so my question is: does anybody know what the problem is here and how to fix it?
I've never seen a problem with that before but with x-code there are usually 3 really annoying but normally foolproof steps to solving a problem such as this.
1) Update your IOS and make sure you are on the most recent version
2) Reinstall X-code
3) Recreate the app
Like I said those 3 steps can normally solve any non code related problem.
Hope that helps!

Xcode 6.0.1 - iOS Simulator Black Screen

I've seen lots of questions about this - however none of them are solving my issue.
The Setup is as follows
OSX Mavericks 10.9.5
Xcode 6.0.1
iOS Simulator 8.0 (550.1)
I've tried now with 5 different Xcode projects, that are working with another machine with identical setups, except this one isn't working.
Every time I launch the simulator, whether or not it's with an App running, or standalone I get the same.
When I run from Xcode I get this message ->
An error was encountered while running (Domain = com.apple.CoreSimulator.SimError, Code = 146)
The things I've tried are:
Reset all Content and Settings (when I click and confirm this - nothing happens at all)
Removed all devices from the simulators, and re-created them
Made sure everything is up to date
Cleaned all projects, SEVERAL times
Restarted machine inbetween doing everything under the sun
Deleted Derived Data
This has been happening for 3 days now.
Suggestions please!
This probably isn't the "official" answer, but my solution to solve this was literally bin xcode, empty trash, then reinstall from the App store.
This post on the Apple Developer Forums has a bunch of highly relevant information. It doesn't appear to directly address your issue, but try this:
Turn up debug logging for the Simulator:
defaults write com.apple.iphonesimulator DebugLogging -bool YES
defaults write com.apple.CoreSimulator DebugLogging -bool YES
Quit and relaunch the iOS Simulator.
Check ~/Library/Logs/CoreSimulator/*.log for more information.

Xcode6 can't run any app in simulator ( Domain = NSPOSIXErrorDomain, Code = 3 )

No app can run in my simulator, although building is good.
Error messsage is below:
Unable to run app in Simulator
An error was encountered while running (Domain = NSPOSIXErrorDomain, Code = 3)
In my case, I tried to run the app on a iPhone 6 simulator when I got this error. Quitted the simulator only and re-ran the app on iPhone 5s (8.1) - it worked fine.
After a while I changed the target back to iPhone 6 (without quitting it), and ran the app against it - no error shown.
As mentioned in the Xcode 6.1 Release Notes and in my sticky post in the Apple Developer Forums for the iOS Simulator, this is a known bug in iOS.
Upon installation of an app, SpringBoard will SIGKILL that app's
process in order to force a relaunch of the app with the new
executable. The problem is that there is a race condition whereby
SpringBoard may accidentally SIGKILL a new process that we just
launched rather than the old process. Which of the various error
messages you get depends on exactly when in the launch process the
SIGKILL was delivered. Normally, this shouldn't happen, so the advise
is to just try again (sorry =/). If you find that this happes to you
all the time or more frequently than you can tollerate, we are
incredibly sorry. We are aware that systems with slower disk I/O will
see this happen more frequently than faster systems, so if you are
using an NFS home directory, you may want to create a local directory
for your simulator data and setup a simlink to it from
~/Library/Developer/CoreSimulator
By Quitting the Simulator and Run the application worked for me.
For me , just Reset Content and setting in your simulator
Restart Mac can solve the problem for me.
This error is less severe than "Domain = DTiPhoneSimulatorErrorDomain, Code = 2" error that I had when I switched to Xcode 6.
For this one, I just reset and cleared contents on my Simulator...quit. Rebuilt and ran my app...and it works.
Every time this has happened to me (as of this writing, still happening on Xcode 6.1) I do not need to restart my mac to fix it. Instead I only had to restart the simulator. I exit the simulator by right-clicking on its icon in the tray and selecting the option to Quit. The I re-run my app and the simulator starts from scratch and runs my app with no error. Much quicker than re-starting the mac.
Well, I had the same error popping up, but since I force quitted the simulator then ran the project again I got it fixed and running fine. Hope that helps you :)
If this error occurs with ionic framework, make sure you have an app id given in your config.xml
This is a generic error which says that it is unable to launch the app. The real error is in the log file. Go to the Simulator menu, Debug / Open System Log. Then press Reveal button to open the folder with actual Simulator logs. In my case it was CoreSimulator.log.
Here you will find the real error. My error was Could not register service com.apple.gputools.agent.producer.sim .
After a lot to struggle and trying all suggestions for half a day, I just went to simulator menu and chose File / GPU Selection / Use External GPU when available. That's it.
please download new xcode_6 beta 4. your project will work in simulator. As i have tested as well.
Sometimes the beta version of XCode is wrongly configured to use the command line tools from the previous xcode version.
This solution should fix the issue for you : https://stackoverflow.com/a/25415781/512504

Xcode does not run the app on simulator. (App exited unexpectedly)

I'm developing for iPad (iOS 7), using Xcode 5.0.2.
Yesterday morning I was playing around with the app (my first app) and every time I ran it, it was displayed in the emulator perfectly. But after some 5/6 runs Xcode just stopped launching my app in the simulator. I started to receive this message:
MagazineManager exited unexpectedly - lost connection
Image:
I've been researching since yesterday morning for a solution with no luck. I even uninstalled and reinstalled Xcode, cleared the cache, delete folders... all that drama thinking it could be some sort of cache problem.
Then, going online I've tried lots of "solutions", none worked.
I've tried all listed here: Xcode suddenly stopped running project on hardware: "Could not launch xxx.app: .. No such file.."
and here:https://discussions.apple.com/message/23431537#23431537
and in more places.
After all my "try this, try that" I'm stuck with the same problem. I can only see a black screen at the simulator (image below) and that message at Xcode!
In my extensive research I've read that people are still able to debug using their iPad's. The problem is that I got the new iPad air, that's only getting here dec, 20th!! So I don't have a place to test my app[s].
Thanks!
UPDATE
Just got this message in the debugger console:
013-12-09 20:23:25.902 sim[607:303] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/usr/bin/sim: Did not find an executable file at the path: '/Users//Library/Developer/Xcode/DerivedData/MagMan-bvhhiijesvrvuteunbmpsxcqgsst/Build/Products/Debug-iphonesimulator/MagMan.app'
My problem was the debugger. Actually, it still is.
The way I solved, and have been doing for every new project, was to disable the debugger and then run the project. That way I'm able to use the app on the simulator but without the debugging functionality.
I don't know what the problem is, what is causing this debugger issue in my case, but for now that's the best I could come up with. Thanks to the friends that replied to my question and helped my research I was able to test it and disable it.
This is how I disabled the debugger:
Project > Edit scheme
Set Debugger to None
If anyone knows a solution for this, feel free to answer this question and I'll make sure to update the selected answer accordingly.
Again, thanks for all your time and patience, specially #Popeye and #HotLicks that spent a lot of their time trying to help me.
Sometimes the simulator can be a bit flaky and just needs resetting. In the navigation bar at the top of the screen when the simulator is visible try:
iOS Simulator --> Reset Content and Settings...
This should reset all the settings and remove the content so all data, images, apps etc will be removed, its like it has never run before.
UPDATE
The answer on XCode5 can't install app on iOS simulator indicates the following
I found a "Fix" for this. After trying everything and getting the same error on "My App", I opened and tried to run "My App 2". "My App 2" ran fine, so I went back to "My App", tried again and this time everything worked fine. Crazy
If that doesn't work leave a comment and I will have another look.
Delete the app and restart your iPad it will work

Resources