I'm using Xcode 4.3.2 with the deployment target set to 4.1 and the iOS is 4.2.1 on an iPhone 3Gs. Whenever I build and run the application with the iPhone 3Gs as the target, it says "finished running 'app name' on 'iPhone 3Gs'.
I have a provision profile setup for this iPhone 3Gs
I checked organizer, and the circle to the right of the iPhone name is green
I ran the same app on my iPhone 4s with the deployment target set to 4.1 and it installed and runs on my iPhone 4s.
Any ideas as to what might be going on that is not installing the app on the iPhone 3Gs? I even tried searching for the app using spotlight, and nothing came up.
Thanks!
EDIT:
this is what appears in my device console log:
Fri May 18 15:27:39 unknown lockdownd[16] <Error>: 2ff68000 handle_connection: Could not receive USB message #6 from iTunes. Killing connection
Fri May 18 15:27:39 unknown com.apple.mobile.lockdown[16] <Notice>: Could not receive size of message
Fri May 18 15:27:51 unknown MobileStorageMounter[4978] <Notice>: (0x3e7518b8) platform_supports_camera_import: Platform is NOT configured for camera import
Fri May 18 15:28:01 unknown MobileStorageMounter[4978] <Notice>: (0x3e7518b8) idle_timer_callback: Exiting after idle
Make sure you have armv6 and armv7 for your 'Valid Architectures' in Build settings, because the 3Gs won't work on the defaulted armv7 only
Related
Whenever I try to debug on devices with iOS 4.x (iPhone 4 and 3GS) I get the following error:
error: failed to launch '/XXX/Library/Developer/Xcode/DerivedData/XXX-fytptbaixvmoweacfsniqxtvjkst/Build/Products/Debug-iphoneos/XXX.app/XXX'
-- Bad CPU type in executable
On devices with iOS 5.x it works.
I am using xCode 4.3.3 and my configurations are:
Architectures: Standard (armv7) (also tried armv6,armv7 to no avail)
Base SDK: Latest iOS (iOS 5.1)
Valid Architectures: armv6, armv7
Deployment Target: iOS 4.0
What do you think?
In your Xcode preferences, go to downloads tab and install "iOS 4.0 - 4.1 Device Debugging Support".
This package includes information and symbols that Xcode needs for
debugging your app on iOS devices running versions of iOS prior to iOS
4.2. If you intend to debug your app on a device running one of these versions of iOS you should install this package.
Xcode crashes on launch, and I do not have any idea why. I downloaded 4.0.2 + iOS SDK (4.3) and installed it. Then I tried to open it and it crashed on launch... Here is my console log that relates to the crash
enter cdyld: Library not loaded: /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 6/14/11 6:10:55 PM [0x0-0x287287].com.apple.dt.Xcode[18402]
Referenced from: /iPhoneSDK/Applications/Xcode.app/Contents/MacOS/../../../../Library/PrivateFrameworks/DVTFoundation.framework/Versions/A/DVTFoundation 6/14/11 6:10:55 PM [0x0-0x287287].com.apple.dt.Xcode[18402]
Reason: image not found 6/14/11 6:10:55 PM [0x0-0x287287].com.apple.dt.Xcode[18402]
catch_mach_exception_raise_state_identity(): PID: 18405 thread: 0x16c77 type: 0xa code: 0x1000f7044 codeCnt: 0x2 flavor: 0x1000f7054 old_state: 0x1000f705c old_stateCnt: 0x2c new_state: 0x1000f802c new_stateCnt: 0x1000f8028 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]
(com.apple.ReportCrash.Self[18405]) Job appears to have crashed: Trace/BPT trap 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]
catch_mach_exception_raise_state_identity(): PID: 18404 thread: 0x17037 type: 0xa code: 0x7fff5fbfdf14 codeCnt: 0x2 flavor: 0x7fff5fbfdf24 old_state: 0x7fff5fbfdf2c old_stateCnt: 0x2c new_state: 0x7fff5fbfe43c new_stateCnt: 0x7fff5fbfe438 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]
(com.apple.ReportCrash[18404]) Job appears to have crashed: Trace/BPT trap 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]
catch_mach_exception_raise_state_identity(): PID: 18402 thread: 0x1703b type: 0xa code: 0x7fff5fbfdf14 codeCnt: 0x2 flavor: 0x7fff5fbfdf24 old_state: 0x7fff5fbfdf2c old_stateCnt: 0x2c new_state: 0x7fff5fbfe43c new_stateCnt: 0x7fff5fbfe438 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]
([0x0-0x287287].com.apple.dt.Xcode[18402]) Job appears to have crashed: Trace/BPT trap 6/14/11 6:10:55 PM com.apple.launchd.peruser.501[167]ode here
It looks like CoreSymbolication does not exist on your machine. I would uninstall and reinstall.
I had a similar problem with two Xcode versions which both failed to start.
I initially had Xcode 4.0.1 (back then the world was still a good place).
I wanted to see how our App looks when compiled with the current iOS SDK 5.0
So I installed Xcode 4.2 on top of Xcode 4.0.1 (overriding it completely)
I tested some stuff in my app and realized that I need to fallback to Xcode < 4.2
I installed Xcode 4.1. During the installation process the installer told me that the current installation would move from /Developer to /Developer-4.2
After all this neither of installed Xcode versions worked anymore which is bad.
I decided to uninstall Xcode 4.2 first and then reinstall Xcode 4.1 again.
I uninstalled Xcode 4.2 with the command sudo /Developer-4.2/Library/uninstall-devtools
I run the Xcode 4.1 installer again from /Applications/Install Xcode.app
After the installation Xcode 4.1 opened so it worked again...
I reinstalled via sudo /Developer/Library/uninstall-devtools and the App Store
But the offending source was restored, so Xcode crashed again. Boo!
I renamed the offending source's folder so Xcode couldn't find it.
Xcode couldn't find the source, and never crashed, which allowed me to get back to work.
Extremely Obvious Feature Request to Apple: hold 'option' to suppress previous projects from loading, plus a command line to do the same.
I am trying to download my application over the web on my iOS 4.2 device.
I have verified that the application I have built installs and runs correctly on my device through XCode - i.e. The application should be built and signed correctly. I package it through "Build and Archive" and "Share..." it - then upload the .plist and .ipa files to my server, which I have the correct links to, etc..etc...
When I try to install it (over-the-air), it says "Waiting...", then "Loading..." then "Installing...", then I get an error: "Unable to Download 'myAppName'" - (Done) (Retry).
Checking the console on my iPhone, I get the following:
Sat Jan 8 18:30:50 unknown
installd[26090] : 2ff66000
extract_package: Could not extract
archive Sat Jan 8 18:30:50 unknown
installd[26090] : 2ff66000
stage_package: Could not extract
/var/tmp/install_staging.ReUsa4/foo.zip
to /var/tmp/install_staging.ReUsa4/foo_extracted
Sat Jan 8 18:30:50 unknown
installd[26090] : 2ff66000
MobileInstallationInstall: Could not
stage the package Sat Jan 8 18:30:50
unknown installd[26090] :
2ff66000 handle_install: API failed
Sat Jan 8 18:30:50 unknown
com.apple.itunesstored[26087]
: MobileInstallationInstall:
failed with -1
Looks like a bunch of problems "Extracting Archive". Anyone know what this means?
Any ideas???
UPDATE: I the Diawi web site to install this - and it worked fine. So, it's not a code signing issue.
Are you positive that the URL you entered when you did the Enterprise distribution, points to your IPA file? The fact it is showing foo.zip in there seems to point in that direction.
Another thing one may check is the deployment target version vs. iPad iOS version. In my case I was building 4.3 target, while my iPad was at 4.2.1. After I built 4.2 and upload, things works fine.
Yes we had same problem
WRONG
Application URL:http://www.mycompany.com/
RIGHT
Application URL:http://www.mycompany.com/MyApp.ipa
A clue is in the progress bar under the icon:
if you see Unable to Download and the bar is at 0 then I found that something in the plist is wrong.
Test All URLS in plist. They should be openable/downloadable in a browser.
If the progress bar moves too quickly it can find the images but the IPA is a problem, check the URL.
If it moves slowly I found its downloding the IPA ok.
If it gets to 75% and fails it usually mean its downloaded what it can and is now failing on install.
Open organizer/Your device/Console logs
if you see unzip error - "cant unarchive" theres something wrong with ipa.
We had wrong URL http://www.mycompany.com/ so think it downloaded default.htm because we said this was the application URL then tried to unzip it and failed.
NONE OF THIS IS HELPED BY APPLES CRAPPY DOCs NOT GIVING AN EXAMPLE!!!!
Go to Product -> Edit Schema -> Build Configuration
Change Debug to Release and try it.
I figured my problem out, maybe you are having the same issue. When uploading the .ipa file to my website I was doing so as an ASCII file when it should have been as a binary. Whatever way you are using to upload the files make sure you can specify the transfer type used to upload them. Hope this helps
I was uploading my ipa to a shared host that I use for tinkering. I tried another host and it worked fine.
For future googlers, here's the errrors I was getting on my device in Organizer
unknown installd[1595] <Error>: 2fff9000 bom_file_error_handler: Payload/MyApp/thumb#2x.png:No such file or directory
unknown installd[1595] <Error>: 2fff9000 : Can't stat Payload/MyApp/thumb#2x.png: No such file or directory
unknown installd[1595] <Error>: 2fff9000 : Can't stat Payload/MyApp: No such file or directory
unknown installd[1595] <Error>: 2fff9000 extract_package: Could not extract archive
unknown installd[1595] <Error>: 2fff9000 stage_package: Could not extract /var/tmp/install_staging.mqnjNY/foo.zip to /var/tmp/install_staging.mqnjNY/foo_extracted
unknown com.apple.itunesstored[1605] <Notice>: MobileInstallationInstall: failed with -1
unknown installd[1595] <Error>: 2fff9000 MobileInstallationInstall: Could not stage the package
unknown installd[1595] <Error>: 2fff9000 handle_install: API failed
unknown installd[1595] <Error>: 2fff9000 send_message: failed to send mach message of 71 bytes: 10000003
unknown installd[1595] <Error>: 2fff9000 send_error: Could not send error response to client
I had the same problem.
I had created an Ad-Hoc Distribution release of my iPad app, had the URL correct, but then copied the .plist and .ipa files into the wrong directory on my FTP site.
Copying it to the correct place (which corresponded with the "Application URL" setting when I created the Archive) fixed this issue.
Sigh. Wouldn't it be nice if the Terminal gave us an easy-to-read description of why such apps had failed to install...
I have a 3.1 xcode project that has been running my app just fine under the 3.1.3 version of the OS. I've been testing this app on my iphone 3G ( not running IOS 4 ).
I just copied over the XCode project and files, downloaded the latest XCode 3.2.4 with the 4.1 SDK. When I run my application via the simulator it just comes up blank instead of showing my app. I can see via the NSLog statements that it's actually getting to my initWithFrame() and viewDidLoad() methods but it's like it didn't load the images correctly.
I've tried copying the files back into the xcode project and allowing it to update references. I've also tried using 4.0 and 4.1 of the SDK along with the iphone 4 and iphone simulators under hardware.
I do see some errors from system.log:
Sep 20 21:59:01 s-macbook-pro-17 [0x0-0x18018].com.apple.Xcode[484]: Xcode(484,0x7fff70216c20) malloc: reference count underflow for 0x2019c0a40, break on auto_refcount_underflow_error to debug.
Sep 20 21:59:01 s-macbook-pro-17 Xcode[484]: Xcode(484,0x7fff70216c20) malloc: reference count underflow for 0x2019c0a40, break on auto_refcount_underflow_error to debug.
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.profiled): Bug: launchd_core_logic.c:4598 (24108):2
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.profiled): Path monitoring failed on "/Users/m/Library/Application Support/iPhone Simulator/4.1/Library/ConfigurationProfiles/profiledRunning": No such file or directory
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.profiled): Bug: launchd_core_logic.c:4598 (24108):2
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.profiled): Path monitoring failed on "/Users/m/Library/Application Support/iPhone Simulator/4.1/Library/ConfigurationProfiles/MCOutstandingNagComputation": No such file or directory
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.mdmd): Bug: launchd_core_logic.c:4598 (24108):2
Sep 20 21:59:03 s-macbook-pro-17 com.apple.launchd.peruser.502[127] (com.apple.iPhoneSimulator:com.apple.managedconfiguration.mdmd): Path monitoring failed on "/Users/m/Library/Application Support/iPhone Simulator/4.1/Library/ConfigurationProfiles/MDMOutstandingActivities.plist": No such file or directory
Sep 20 21:59:03 s-macbook-pro-17 vot[929]: ******** AX INSPECTOR MODE ************
Sep 20 21:59:03 s-macbook-pro-17 vot[929]: **** Running VoiceOver Lite ****
Sep 20 21:59:06 s-macbook-pro-17 app[935]: MainView alloc
Sep 20 21:59:06 s-macbook-pro-17 app[935]: MainView alloc complete
Sep 20 21:59:06 s-macbook-pro-17 app[935]: loadView complete
I set the "Visible at launch" property on the main window via interface builder. I didn't have this set in my xcode project on my other macbook pro when using XCode 3.1.
I came across this thread that helped me:
iPhone SDK4.0 and xcode 3.2.3 issue
Similar situation in my app, but my problem was that somehow, in the MainWindow.xib in IB, the File Owner's delegate was no longer linked up to my app delegate (right click on File Owner in IB and check the delegate button). Was working in Ipad simulator because I have 2 different MainWindow xib files, one for iphone/ipod and one for ipad.
Hope this helps someone experiencing a blank screen on startup.
I'm running Xcode 3.2.3 with the iOS 4.0 SDK. I built my app with Base SDK = iphoneos4.0, Active SDK = iphoneos4.0, Deployment Target = 3.1.3, and Architecture = standard (arm6 arm7). Compiler = GCC 4.2. As I understand it, this is the correct way to build an app for both iOS 4 and 3.
The app runs fine on devices running iOS 4. But it crashes on startup when you try to run it on a device with iOS 3.1.3 (an iPod Touch 1G):
dyld: Symbol not found: __NSConcreteStackBlock
Referenced from: /var/mobile/Applications/192B30ED-16AC-431E-B0E9-67C1F41FD5DA/MyApp.app/MyApp
Expected in: /usr/lib/libSystem.B.dylib
It appears to be an issue with a fairly "low level" dynamically-linked library, BEFORE my main() function even gets called. I have even tried re-starting the device, etc., with no luck. Here's part of the the crash log:
Process: MyApp [60]
Path: /var/mobile/Applications/192B30ED-16AC-431E-B0E9-67C1F41FD5DA/MyApp.app/MyApp
Identifier: MyApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2010-07-22 17:16:17.942 -0400
OS Version: iPhone OS 3.1.3 (7E18)
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x00000001, 0xe7ffdefe
Crashed Thread: 0
Dyld Error Message:
Symbol not found: __NSConcreteStackBlock
Referenced from: /var/mobile/Applications/192B30ED-16AC-431E-B0E9-67C1F41FD5DA/MyApp.app/MyApp
Expected in: /usr/lib/libSystem.B.dylib
Dyld Version: 149
Binary Images:
0x1000 - 0x80fff +MyApp armv6 <d5f0ff6f233b4b034c222c16438c88d9> /var/mobile/Applications/192B30ED-16AC-431E-B0E9-67C1F41FD5DA/MyApp.app/MyApp
0x2fe00000 - 0x2fe26fff dyld armv6 <544395a4b5546114b878d5131a84fd7f> /usr/lib/dyld
0x30410000 - 0x30536fff libSystem.B.dylib armv6 <0373fd64e915a17160732b29d343f95f> /usr/lib/libSystem.B.dylib
Thanks for any advice!
Ben Gottlieb pointed out yesterday that if you use blocks anywhere in your application, you'll see a crash similar to this on a pre-4.0 OS while building with the LLVM compiler. To work around this, you can specify the linker flag -weak-lSystem in your Xcode build settings.
Since most of these answers are specific to Xcode 3.x, just wanted to share what I did to fix this with Xcode 4.2.
Under your target in the "Build Phases" tab in the "Link Binary With Libraries" section I added "libSystem.dylib" and made it optional. This fixed the issue iOS 3.x devices while maintaining support for iOS 4.x and 5.0 devices.
If you happen to be using the cocos2d libraries, there is a cleaner way to do this, you should configure the cocos2d target's Deployment target to 3.0