I upgraded to XCode 8, and I am going through hell of being able to run my tests sometimes... For example, I just was testing some code, and was able to run my tests 3 times in a row... and then the 4th time I got:
dyld: could not load inserted library 'PLATFORMS/iPhoneOS.platform/Developer/Library/PrivateFrameworks/IDEBundleInjection.framework/IDEBundleInjection' because image not found
*** If you believe this error represents a bug, please attach the log file at /Users/patrick/Library/Developer/Xcode/DerivedData/MyApp-hjfppqmgxqrprucknvwtakynpqxs/Logs/Test/2B6C2EAE-5C13-40C9-BACE-3A00AA74F3EF/Session-UnitTests-2016-09-20_124123-gk3pW0.log
I have rebooted my iOS device, rebooted my computer, deleted derrived data, etc... It will no longer run tests. ARRRGH!!!!
UPDATE
I should mention, I am trying to run tests on my iPad, I can't run tests on the simulator because I have too much code having to do with NEON intrinsics, and so the simulator wont run.
But what does seem to work is, when this happens, switch to build tests on my iPhone, then it when it builds, it just says "running tests" and the spinner spins forever, but no tests are actually running... I can actually tap on my app and interact with it, which is usually not the behavior I get when running tests... Anyway I then stopped the build, switched back to my iPad and now tests run again.
I get this error consistently with XCode 8.0 running on my iPad (Version 10.0.2 (14A456)) when I run test code that causes an uncaught exception in the code under test. There may be other examples, but it happens any time the code under test fails catastrophically.
When the unit test fails with an exception, XCode does not recover properly.
I believe this is a problem with XCode; this answer provides a workaround. The unit test will fail at the exception, and subsequent runs produce the 'image not found' error.
The simplest recovery I've found is the following:
Set device target to Generic iOS Device
Disconnect my iPad
Reboot the iPad
Connect everything back together
Here is an example failure that demonstrates the problem;
Notice that the core issue in this example is that I have written a bad unit test; I'm passing a nil parameter to a method that is subsequently used to try adding a nil object to a dictionary.
Update: for the sake of accuracy, the issue was that I was passing an immutable dictionary as a parameter when a mutable one was expected, thus producing the 'unrecognized selector' error. In any case, the exception is what causes XCode to behave badly.
Assertions: failed: caught "NSInvalidArgumentException", "-[__NSDictionaryI setObject:forKey:]: unrecognized selector sent to instance 0x1818f200"
(
0 CoreFoundation 0x1dd89e1f <redacted> + 154
1 libobjc.A.dylib 0x1cfef077 objc_exception_throw + 38
2 CoreFoundation 0x1dd8f515 <redacted> + 0
3 CoreFoundation 0x1dd8d589 <redacted> + 700
4 CoreFoundation 0x1dcb2f08 _CF_forwarding_prep_0 + 24
5 tDefense 0x000cd299 +[PlayingPiece addPlayingPiece:atLocation:onBoard:] + 326
6 tDefense 0x000cd5ad +[PlayingPiece addNewPiece:atLocation:onBoard:] + 154
7 tDefenseTests 0x00410777 -[PlayFieldTests testGetNeighbors] + 4594
8 CoreFoundation 0x1dd8e864 <redacted> + 68
9 CoreFoundation 0x1dcaf349 <redacted> + 294
10 XCTest 0x00307de5 __24-[XCTestCase invokeTest]_block_invoke_2 + 472
11 XCTest 0x0033b0dd -[XCTestContext performInScope:] + 312
12 XCTest 0x00307c07 -[XCTestCase invokeTest] + 296
13 XCTest 0x00308439 -[XCTestCase performTest:] + 560
14 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
15 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
16 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
17 XCTest 0x002f1d55 __25-[XCTestDriver _runSuite]_block_invoke + 52
18 XCTest 0x00312325 -[XCTestObservationCenter _observeTestExecutionForBlock:] + 628
19 XCTest 0x002f1bed -[XCTestDriver _runSuite] + 512
20 XCTest 0x002f29b7 -[XCTestDriver _checkForTestManager] + 300
21 XCTest 0x0033c55b _XCTestMain + 690
22 CoreFoundation 0x1dd45bc3 <redacted> + 10
23 CoreFoundation 0x1dd455a7 <redacted> + 230
24 CoreFoundation 0x1dd43a61 <redacted> + 752
25 CoreFoundation 0x1dc93073 CFRunLoopRunSpecific + 486
26 CoreFoundation 0x1dc92e81 CFRunLoopRunInMode + 104
27 GraphicsServices 0x1f43bbfd GSEventRunModal + 156
28 UIKit 0x22e34acf <redacted> + 574
29 UIKit 0x22e2f201 UIApplicationMain + 150
30 tDefense 0x000d690f main + 106
31 libdyld.dylib 0x1d45e50b <redacted> + 2
)
File: <unknown>
I was having exactly the same problem after upgrading to Xcode 8 / Swift 2.3. One of deleting derived data, rebooting the phone and closing and re-opening Xcode just fixed it.
Related
I recently submitted an app update to the App Store. The app runs well in Xcode (on device and simulator) for all versions of iOS including iOS 13+. I was surprised that it was rejected for crashing at startup. I checked using a Testflight build and it only crashed when ran on a device with iOS 13+. I could not replicate crashes from Xcode as it only crashes on the builds from Tesflight.
I've been researching online and see that this is not an uncommon issue, however, I can't identify what's the issue in my case. I've tried changing the build settings in Xcode and building from an older version of Xcode (10.2.1, doesn't work bc I use newer classes not compatible with anything lower than Xcode 11). I also tried changing the swift compiler optimization level to zero in the build settings. To upload a build to Tesflight, I am exporting the archive and uploading to iTunes Connect using Apple's Transporter app.
Using the crash log and podfile description below, can anyone identify the issue and/or make a suggestion on what's going wrong in the build.
Crash Log
OS Version: iPhone OS 13.2.3 (17B111)
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
libsystem_kernel.dylib 0x00000001baaf7ec4 __pthread_kill + 8
libsystem_pthread.dylib 0x00000001baa13774 pthread_kill$VARIANT$mp + 112
libsystem_c.dylib 0x00000001ba967844 abort + 100
libc++abi.dylib 0x00000001baac07d4 __cxa_bad_cast + 0
libc++abi.dylib 0x00000001baac09c4 demangling_unexpected_handler+ 6596 () + 0
libobjc.A.dylib 0x00000001baa28258 _objc_terminate+ 25176 () + 124
libc++abi.dylib 0x00000001baacd304 std::__terminate(void (*)+ 58116 ()) + 16
libc++abi.dylib 0x00000001baacd29c std::terminate+ 58012 () + 44
libdispatch.dylib 0x00000001ba9cd198 _dispatch_client_callout + 36
libdispatch.dylib 0x00000001ba975fd8 _dispatch_block_invoke_direct$VARIANT$mp + 224
FrontBoardServices 0x00000001bfe4e4c8__FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 40
FrontBoardServices 0x00000001bfe4e194 -[FBSSerialQueue _queue_performNextIfPossible] + 404
FrontBoardServices 0x00000001bfe4e6bc -[FBSSerialQueue _performNextFromRunLoopSource] + 28
CoreFoundation 0x00000001bac7d7c4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
CoreFoundation 0x00000001bac7d71c __CFRunLoopDoSource0 + 80
CoreFoundation 0x00000001bac7ceb4 __CFRunLoopDoSources0 + 180
CoreFoundation 0x00000001bac78000 __CFRunLoopRun + 1080
CoreFoundation 0x00000001bac778a0 CFRunLoopRunSpecific + 464
GraphicsServices 0x00000001c4bcf328 GSEventRunModal + 104
UIKitCore 0x00000001bed68740 UIApplicationMain + 1936
OnStation 0x0000000100a553ac main + 103340 (main.m:14)
libdyld.dylib 0x00000001bab02360 start + 4
Podfile
pod 'AWSCore'
pod 'AWSSNS'
pod 'AWSS3'
pod 'AWSCognito'
pod 'AWSCognitoIdentityProvider'
pod 'AWSCognitoSync'
pod 'AWSDynamoDB'
pod 'Flurry-iOS-SDK/FlurrySDK'
pod 'ArcGIS-Runtime-SDK-iOS', '100.2.1'
pod 'SVProgressHUD'
pod 'UICKeyChainStore'
pod 'RangeSeekSlider'
pod 'PubNub', '~> 4'
pod 'MessageKit'
I’m going to guess that this is due to a situation parallel to
iOS11 WKWebview crash due to NSInvalidUnarchiveOperationException
In other words, I'm guessing that you have something in your storyboard that comes from another framework that you need to link explicitly. That sort of thing often doesn’t crash from Xcode but does crash when launching independently.
Ever since Xcode 11 I've not been able to run any apps on my device. They will launch in the simulator just fine. I have an iPhone 11 Max Pro.
I've tried everything I can think of to get it to work and I have no idea what to do at this point. Has anyone figured out a fix ?
I did try setting my project to Legacy build and I still have the same issue.
Here are the details of the failed install to my iPhone.
Details
Unable to install "App Test"
Domain: com.apple.dtdevicekit
Code: -402620395
--
App installation failed
Domain: com.apple.dtdevicekit
Code: -402620395
Failure Reason: A valid provisioning profile for this executable was not found.
User Info: {
DVTRadarComponentKey = 487927;
"com.apple.dtdevicekit.stacktrace" = (
0 DTDeviceKitBase 0x00000001251586e7 DTDKCreateNSError + 109
1 DTDeviceKitBase 0x0000000125158de9 DTDK_AMDErrorToNSError + 792
2 DTDeviceKitBase 0x000000012519856a __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 164
3 DVTFoundation 0x000000010b27cc22 DVTInvokeWithStrongOwnership + 73
4 DTDeviceKitBase 0x0000000125198301 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1589
5 IDEiOSSupportCore 0x0000000125020a25 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.352 + 4523
6 DVTFoundation 0x000000010b3ade8a __DVT_CALLING_CLIENT_BLOCK__ + 7
7 DVTFoundation 0x000000010b3af562 __DVTDispatchAsync_block_invoke + 809
8 libdispatch.dylib 0x00007fff6d6ca583 _dispatch_call_block_and_release + 12
9 libdispatch.dylib 0x00007fff6d6cb50e _dispatch_client_callout + 8
10 libdispatch.dylib 0x00007fff6d6d0ace _dispatch_lane_serial_drain + 597
11 libdispatch.dylib 0x00007fff6d6d1452 _dispatch_lane_invoke + 363
12 libdispatch.dylib 0x00007fff6d6daa9e _dispatch_workloop_worker_thread + 598
13 libsystem_pthread.dylib 0x00007fff6d9256fc _pthread_wqthread + 290
14 libsystem_pthread.dylib 0x00007fff6d924827 start_wqthread + 15
);
}
--
I faced this issue today and I could not fix it either with the proposed solutions that are out there, because they pointed into the wrong direction.
Do you, by any chance, have frameworks included in your project and set them to "embed without signing"? Changing the included frameworks to "embed & sign" fixed this issue for me.
Not properly re-signing external frameworks seems to cause problems when attempting to install the binary to a real device. The executable mentioned in "A valid provisioning profile for this executable was not found." does in this context refer to the insufficiently signed external framework.
I created a HTML5 web app that I’m trying to wrap in a web view and submit to the Mac App Store.
I’ve done the following:
1) Opened Xcode 5.0.1 and selected “Create a new Xcode project”
2) Under “OS X” I selected “Application” then I selected “Cocoa Application” then “Next”
3) I entered a “Product Name” and a “Company Identifier” then selected “Next” (I left all the other settings untouched) then “Create”
4) Under “General” > “Deployment Info” > “Deployment Target” I selected 10.6 — because I want the app to be compatible with all versions of OS X that support the Mac App Store
5) I clicked “MainMenu.xib” and selected “Window - My App”
6) From the “Object library” I drug the “Web View” object into my window and made it fill the window size
7) I saved my project and click the Play button in the upper left corner of Xcode
The app tries to open but freezes. I don’t get an error in Xcode but it does open “main.m” and highlight “return NSApplicationMain(argc, argv);” in green and says “Thread 1: signal SIGABRT”
I was hoping that someone could clarify why this isn’t working? And provide me with the last step to link the web view object? I searched Google and found tutorials for iOS and a few for OS X but for different versions of Xcode.
A couple of things:
In your xib, select the "File Inspector" and make sure your xib deployment version matches your app deployment version. If you don't do this, you will have problems running your application on older deployment versions.
For your crash, if you look in Xcode's debug console, you probably see something that looks like this:
2013-10-31 23:07:10.654 Product[19035:303] *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (WebView)
2013-10-31 23:07:10.654 Product[19035:303] (
0 CoreFoundation 0x00007fff8eeab41c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff97daee75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8eeab2cc +[NSException raise:format:] + 204
3 Foundation 0x00007fff96b83d69 _decodeObjectBinary + 2349
4 Foundation 0x00007fff96b84f2f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
5 Foundation 0x00007fff96b8512b -[NSArray(NSArray) initWithCoder:] + 202
6 Foundation 0x00007fff96b83e22 _decodeObjectBinary + 2534
7 Foundation 0x00007fff96b832dd _decodeObject + 288
8 AppKit 0x00007fff946985bc -[NSView initWithCoder:] + 1949
9 Foundation 0x00007fff96b83e22 _decodeObjectBinary + 2534
10 Foundation 0x00007fff96b832dd _decodeObject + 288
11 AppKit 0x00007fff9469e458 -[NSWindowTemplate initWithCoder:] + 1043
12 Foundation 0x00007fff96b83e22 _decodeObjectBinary + 2534
13 Foundation 0x00007fff96b84f2f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
14 Foundation 0x00007fff96b84567 -[NSSet(NSSet) initWithCoder:] + 203
15 Foundation 0x00007fff96b83e22 _decodeObjectBinary + 2534
16 Foundation 0x00007fff96b832dd _decodeObject + 288
17 AppKit 0x00007fff94670780 -[NSIBObjectData initWithCoder:] + 155
18 Foundation 0x00007fff96b83e22 _decodeObjectBinary + 2534
19 Foundation 0x00007fff96b832dd _decodeObject + 288
20 AppKit 0x00007fff9467059f loadNib + 232
21 AppKit 0x00007fff9466fb9c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 288
22 AppKit 0x00007fff9466f98c -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 197
23 AppKit 0x00007fff9466f77b +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 357
24 AppKit 0x00007fff9466b617 NSApplicationMain + 448
25 Product 0x00000001000012c2 main + 34
26 Product 0x0000000100001294 start + 52
27 ??? 0x0000000000000003 0x0 + 3
)
In this case, this is because the app has no idea what a WebView is when loading the nib. You to fix this you need to link against the WebKit framework.
Go back to your target settings and select "Build Phases". Expand "Link Binary With Libraries" and click "+". Search for the Mac WebKit framework and add it. The app should be able to unarchive the WebView in the nib now.
I added a Git repo as a submodule to my existing project which is also Git managed, I did these in command line, and I use GitBox to manage my projects, then when I open GitBox, it just crashed, I tried many times and even restarted the machine.
Application Specific Information:
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* setObjectForKey: object
cannot be nil (key: _NSTaskExecutablePath)' abort() called terminate
called throwing an exception
Application Specific Backtrace 1: 0 CoreFoundation
0x00007fff92a3c716 __exceptionPreprocess + 198 1 libobjc.A.dylib
0x00007fff8f2b3470 objc_exception_throw + 43 2 CoreFoundation
0x00007fff92acaf07 -[__NSDictionaryM setObject:forKey:] + 135 3
Foundation 0x00007fff8f6cd732
-[NSConcreteTask setLaunchPath:] + 194 4 Gitbox 0x000000010001d779 Gitbox + 120697 5 Gitbox
0x000000010001cfb7 Gitbox + 118711 6 Gitbox
0x000000010005b6eb Gitbox + 374507 7 Gitbox
0x000000010000687b Gitbox + 26747 8 Gitbox
0x000000010005a3cc Gitbox + 369612 9 Gitbox
0x000000010005a6cc Gitbox + 370380 10 Gitbox
0x000000010001c7ec Gitbox + 116716 11 libdispatch.dylib
0x00007fff8e881f3d _dispatch_call_block_and_release + 15 12
libdispatch.dylib 0x00007fff8e87e0fa
_dispatch_client_callout + 8 13 libdispatch.dylib 0x00007fff8e883104 _dispatch_main_queue_callback_4CF + 275 14
CoreFoundation 0x00007fff929de81e __CFRunLoopRun
+ 1614 15 CoreFoundation 0x00007fff929dddd2 CFRunLoopRunSpecific + 290 16 HIToolbox
0x00007fff98145774 RunCurrentEventLoopInMode + 209 17 HIToolbox
0x00007fff98145512 ReceiveNextEventCommon + 356 18 HIToolbox
0x00007fff981453a3 BlockUntilNextEventMatchingListInMode + 62 19
AppKit 0x00007fff93d29fa3 _DPSNextEvent +
685 20 AppKit 0x00007fff93d29862
-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 21 AppKit 0x00007fff93d20c03
-[NSApplication run] + 517 22 AppKit 0x00007fff93cc5656 NSApplicationMain + 869 23 Gitbox
0x00000001000028c1 Gitbox + 10433 24 Gitbox
0x0000000100001d94 Gitbox + 7572 25 ???
0x0000000000000002 0x0 + 2
I wanted to remove the Gitbox settings and make it as a newly installed app, but did not find it. What else can I try?
Thanks!
Get an uninstallation app (e.g. AppCleaner) and remove everything it finds but the gitbox app itself.
Then relaunch gitbox - unfortunately you will have to re-add the repos you were working with to gitbox but this will get you past the crash.
Deleting ~/Library/Preferences/com.oleganza.gitbox.plist resolved the problem here.
Had similar problems with gitbox after xcode updates. This worked for me, these directions are from the app author:
Quit Gitbox.
Delete ~/Library/Preferences/com.oleganza.gitbox.plist
Run in Terminal: defaults delete com.oleganza.gitbox
Run in Terminal: git config --global push.default matching
Open Gitbox.
You may also need to run "git config push.default matching" in your repository if you have other value for "push.default" there.
No need to uninstall Gitbox and lose your repo list - just delete Library/Saved\ Application\ State/com.oleganza.gitbox.savedState/
Got the new Retina MacBook and it has not been playing nice with xCode. If i make a new project it works, but if i ty triggering the assistant editor it will freeze. If i save a new project and reopen it, it will freeze. I did install the 4.5 DP and uninstalled it and the latest nonbeta version of xcode and the problem still persists. Anyone know what could be the issue? If i make a new user account xcode is behaving normally. Anyone know of a fix? Crash large too large for me to post.
Date/Time: 2012-06-30 03:10:29 -0700
OS Version: 10.7.4 (Build 11E2620)
Architecture: x86_64
Report Version: 9
Command: Xcode
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Version: 4.3.3 (1178)
Build Version: 3
Project Name: IDEApplication
Source Version: 1178000000000000
App Item ID: 497799835
App External ID: 8553856
Parent: launchd [111]
PID: 234
Event: hang
Duration: 1.76s
Steps: 18 (100ms sampling interval)
Pageins: 44
Pageouts: 0
Process: Xcode [234]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Architecture: x86_64
UID: 501
Thread 0x810 DispatchQueue 1
User stack:
18 ??? (in Xcode) [0x107b73eec]
18 NSApplicationMain + 867 (in AppKit) [0x7fff85edf244]
18 -[NSApplication run] + 555 (in AppKit) [0x7fff85c630c6]
18 -[IDEApplication sendEvent:] + 366 (in IDEKit) [0x1085c2dd1]
18 -[NSApplication sendEvent:] + 4282 (in AppKit) [0x7fff85ccc536]
18 -[NSApplication _handleKeyEquivalent:] + 526 (in AppKit) [0x7fff85dd3175]
18 -[NSMenu performKeyEquivalent:] + 281 (in AppKit) [0x7fff85dd4524]
18 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 125 (in AppKit) [0x7fff85e56932]
18 -[NSMenuItem _corePerformAction] + 399 (in AppKit) [0x7fff85e56bfb]
18 -[IDEApplication sendAction:to:from:] + 154 (in IDEKit) [0x1085c7096]
18 -[DVTApplication sendAction:to:from:] + 318 (in DVTKit) [0x107e76866]
18 -[NSApplication sendAction:to:from:] + 139 (in AppKit) [0x7fff85d69f7e]
18 -[NSObject performSelector:withObject:] + 61 (in CoreFoundation) [0x7fff8a15270d]
18 -[IDEWorkspaceTabController _changeToEditorMode:] + 361 (in IDEKit) [0x108728088]
18 _NSSetIntValueAndNotify + 259 (in Foundation) [0x7fff86f8353f]
18 -[IDEEditorArea setEditorMode:] + 384 (in IDEKit) [0x108604a61]
18 -[IDEEditorArea _refreshEditorContextsAndPreserveCurrentEditorHistoryStack:] + 642 (in IDEKit) [0x108604d8e]
18 +[DVTLayoutView_ML _recursivelyLayoutSubviewsOfView:populatingSetWithLaidOutViews:] + 108 (in DVTKit) [0x107e858ec]
18 +[DVTLayoutView_ML
For me, the solution was simple:
Close Xcode
Delete the following folders/files from myProject.xcodeproj (or .xcworkspace if you're using cocoapods) (right click on the file and choose “Show Package Contents”)
/xcuserdata
/project.xcworkspace
Reopen Xcode and enjoy
The crash is occurring due to a corruption in project's userdata content.
Also, you should note that after deleting those files, the window size and position will reset and the opened tabs will be all closed.
I experienced similar problems on my Retina MacBook. The workaround is to specify "Open in Low Resolution" for Xcode in the Finder. From http://support.apple.com/kb/HT5266:
Quit the application if it is currently open.
In the Finder, choose Applications from the Go menu.
In the Applications folder that opens, click the application's icon so it is highlighted.
Choose Get Info from the File menu.
Place a checkmark next to "Open in Low Resolution" to enable Low Resolution mode.
Close the window and double click the Application to reopen it.
This does have an impact on text quality, though it's not awful (subjective). Hopefully Apple will update Xcode soon.
I am facing the same problem .... I solve it after make changes as per screenshot -
it works for me.