I have googled for two days and still no luck. I am running a Mac OS X 10.5.5 and the iPhone SDK 3.1 beta, running the Aspen Simulator.
My problem is that I can not get any app to work on the Simulator. It builds alright but the simulator shows a black screen and then returns to the main menu. I get this error on Xcode:
Error from Debugger: Failed to launch simulated application. See console.
and in console, it says something about "unable to find springboard (bootstrap lookup error".
Can you please help me?
I think you should think about updating your system. Using an old iPhone SDK 3.1 beta nowadays is really strange, you should update to the latest stable iOS SDK 4.3.3 and test backwards compatibility of your app using the built in iOS SDK 3.2 from iPad. This will help you test the app on this older SDK while getting active support from both Apple and developers.
Tell me if updating solves your issues or not. Thank you!
Related
I am developing an app for iOS and also using Mac Catalyst to run on my Mac. The app runs fine on my iPhone but always shows an error on Catalyst. The code used to run fine before updating to Big Sur Beta 6 from Beta 5. Here's a screenshot of the error: . Also the error in code blocks for anybody who wants to copy it.
The operation couldn’t be completed. (OSStatus error -10670.)
Domain: NSOSStatusErrorDomain
Code: -10670
User Info: {
"_LSFunction" = "_LSOpenStuffCallLocal";
"_LSLine" = 3664;
}
--
System Information
macOS Version 11.0 (Build 20A5364e)
Xcode 12.0 (17210.1)
https://github.com/MysteryCoder456/VegieMato/tree/backend is the GitHub Repo if anybody wants to reproduce this (i.
Faced same issue after upgrading to macOS 11 Beta 6. Reported bug to Apple but meanwhile found workaround - Select Product in Xcode, select 'Show in Finder'. Launch it from Finder. Additional step, hopefully Apple will look into it.
The problem is solved with new Mac OS 11.0 Beta (20A5374g).
If your catalyst app has multi-window support, you may still need to kill your existing app before launching the new one.
I also had the same problem. (I say had, I guess I still do, however I have a workaround) My App had been developed as iOS / iPadOS with Mac support. All has been working great throughout macOS 11 beta builds. Until today that is, when I, as you, updated to Beta 6. Upon attempting to run for macOS target I get the same error as you have posted.
After some googling I found https://www.virusbulletin.com/uploads/pdf/conference_slides/2015/Wardle-VB2015.pdf and had a go at simply opening the app directly from the build folder. Hey presto, it opened without any problems, I even cleaned out the build folder and built it again to make sure.
This would appear to be a problem that the next version of Xcode beta should fix. Until then, unless anybody can suggest a better fix, this will have to suffice for me at least :-(
Sam
-10670
I was having this same error code upon installing a Developer ID Distributed, Auto Signed version of a catalyst app on a test machine, non M1 Chip, Mac Mini(Late 2014) with MacOS Version 12.0 Beta installed.
The solution was to close the previously installed version of the app. Before opening the new version that I Airdrop over to the test Mac machine.
Up until today, I have been able to test my app on my CDMA iPhone, running 4.2.10. I am building against the 4.3 SDK, with a deployment target of 4.0.
After restarting my phone today, Xcode will no longer allow me to test the app on my phone, with this message in the Organizer window: "The version of iOS on "iPhone" does not match any of the versions of iOS supported for development with this installation of the iOS SDK. Please restore the device to a version of the OS listed, or update to the latest version of the iOS SDK"
Unfortunately there are some bugs with location services in the simulator, so I can't use that for testing either.
Can I even install the 4.2 SDK in Xcode 4? Is anyone else having this problem, or (hopefully) does anyone know how to fix it? Thanks for any help!
If you install xcode 4 it will actually gather the build chain from your phone and use it for compiling. You can see this in the organizer window (Window->Organizer?).
You know I had that same issue i found that I had to download the latest xcode and reinstall because for some reason the ios that came with xcode knew how to build on my phone. Sorry man.
I have recently provisioned my IPhone to be a development device when I had version 3.1 of the firmware installed.
I was forced to upgrade firmware last night due to 3.2 being the base supported firmware by the framework I am using. I am now running 4.1 of the iOS firmware.
Before I did this the device showed up in XCode as a valid target to run my application aside from the simulator. Now when I open xcode I never see my device in the list. I also look at organizer and it is enabled for development as I am able to look at the console for the device.
Also the provisioning profiles are still there.
I am at a bit of a loss as to what is wrong. I appreciate any ideas people may have as to how I can fix this.
You're saying it shows up in the Organizer, but not in the "Overview" list in Xcode?
Are you perhaps still running the 4.0 SDK, and does it show up with a "yellow light" in the Organizer along with the error message like "this device's firmware is too new for me"? If so, updating to the 4.1 SDK should fix your problem.
I recently ran into troubles building an app with latest iOS 4.1 SDK and running it on device with iOS 3.x. App works OK on 4.x devices and iPad, but crashes on devices running older 3.x iOS.
Problem appears to be in linker, since crashes are obviously caused by calls to 3rd party libraries used in the project. The linker (or even compiler) suspicion is supported by fact that when I build the app with older 3.1.3 SDK, it works as expected.
My Release configuration uses iOS 4.1 as Base SDK and iOS 3.0 as deployment target platform, compiled with LLVM GCC 4.2. I also tried GCC 4.2 compiler, but it didn't help too.
I've found that there's some bug in linker/compiler in this version of SDK, but none of proposed solutions worked for me.
I desperately need to resolve this issue, so any help is highly appreciated.
Thanks to everyone for any hint or advice.
Just to let you know that if you are using something like iAd framework, you need to add this framework as "weak dependency" in the Target Info Pop-Up :-)
If it's a librairie, could you list them ?
Good Luck !
I guess I am too late at answering this one. But still - If you have the 3.1.3 device with you, doing an in-system debugging by loading an app with a developer profile gives you what caused the crash. I faced a similar problem when my apps used to work fine on the 4.0+ devices but used to crash immediately upon startup when I tried it on 3.1.2 device. I compiled it with a developer profile and then did an in-system debugging. I found out that I was using a class UIPopoverController which was brought in with iOS 3.2 and hence used to fail for my 3.1.2. Putting in the necessary checks for this resolved my problem.
Hope that helps.
I am trying to provision my app to run on my iPad for testing. I have everything set up properly, but in the organizer, Xcode displays this message:
The version of iPhone OS on “iPad” does not match any of the versions of iPhone OS
supported for development with this installation of the iPhone SDK. Please restore the
device to a version of the OS listed below, or update to the latest version of the iPhone SDK;
and then it gives me a list of available iOS versions (3.2.2 is not one of them.)
I have restored it back to the factory settings and done everything I could find online and searched around. Does anyone know what could be causing this problem? It won't let me compile it to the device as a result. Thanks!
Which version of the iOS SDK are you using? Make sure you're using the most recent.