I'm using Xcode 7.0.1 and since several days I'm experiencing very frequent crash with the Interface Builder when setting properties of UIStackViews.
I have reproduced the issue with a very simple project created from scratch. This project just contains a Storyboard with a Single viewController that contains a UITableView with a UITableViewCell which contains 5 UILabels with several UIStackViews.
Every time I'm changing several properties of one of the UIStackView Xcode crash, with error below.
Sometime I can reopen the project and sometimes not (Xcode crash at startup). I have the same issue with the same project on my MacBookPro and my old white MacBook, all are running with the same version of Xcode and OS X El Capitain.
Any idea about a workaround or a way to fix it is welcomed.
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 7.0.1 (8228)
Build Info: IDEFrameworks-8228000000000000~5
App Item ID: 497799835
App External ID: 813434267
Code Type: X86-64 (Native)
Parent Process: ??? 1
Responsible: Xcode [2177]
User ID: 501
Date/Time: 2015-10-10 18:29:07.206 +0200
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: 4CEF61B0-80F0-668D-225D-39382C5053E4
Sleep/Wake UUID: C7D655B2-BA3E-4DAF-AC3A-F9AB2B1609DC
Time Awake Since Boot: 13000 seconds
Time Since Wake: 8800 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
IBDocumentDidFinishEditingNotification
ProductBuildVersion: 7A1001
ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/IDEInterfaceBuilder/IDEInterfaceBuilder-8191/InterfaceBuilderKit/Utilities/IBPlatformToolFailureHandler.m:315
Details: Failed to compute auto layout status IBLayoutConstraint, IBUILabel, IBUIStackView, IBUITableViewCell, IBUITableViewCellContentView, and IBUIView.
Encountered an error communicating with Interface Builder Cocoa Touch Tool. If you choose to file a crash report or Radar for this issue, please zip and attach the diagnostics at "/var/folders/q3/g2n6m_1x57583jym4b_808jw0000gn/T/IB-agent-diagnostics_2015-10-10_18-29-07_130000" to your crash report.
Exception name: NSInternalInconsistencyException
Exception reason: {objective 0x7ff0e2677310: <1:20> + <1:1>*0x7ff0e268c6c0.marker{id: 4430}}: internal error. Setting empty vector for variable UILabel:0x7ff0e4c71c20'Last Period'.Height{id: 4185}.
Exception backtrace:
0. CoreFoundation 0x0000000109dfbf4d __exceptionPreprocess
1. libobjc.A.dylib 0x0000000109875deb objc_exception_throw
2. CoreFoundation 0x0000000109dfbe9d +[NSException raise:format:]
3. Foundation 0x000000010944e930 -[NSISObjectiveLinearExpression setPriorityVector:forKnownAbsentVariable:]
4. Foundation 0x00000001095f01b7 __128-[NSISObjectiveLinearExpression replaceVariable:withExpression:processVariableNewToReceiver:processVariableDroppedFromReceiver:]_block_invoke
5. Foundation 0x000000010944b47f -[NSISLinearExpression enumerateVariablesAndCoefficients:]
6. Foundation 0x00000001095f0077 -[NSISObjectiveLinearExpression replaceVariable:withExpression:processVariableNewToReceiver:processVariableDroppedFromReceiver:]
7. Foundation 0x000000010944c5ae -[NSISEngine substituteOutAllOccurencesOfBodyVar:withExpression:]
8. Foundation 0x000000010944f5ed -[NSISEngine pivotToMakeBodyVar:newHeadOfRowWithHead:andDropRow:]
9. Foundation 0x000000010944cf87 -[NSISEngine minimizeConstantInObjectiveRowWithHead:]
10. Foundation 0x00000001095ebe43 -[NSISEngine tryUsingArtificialVariableToAddConstraintWithMarker:rowBody:usingInfeasibilityHandlingBehavior:mutuallyExclusiveConstraints:]
11. Foundation 0x000000010944ae4e -[NSISEngine tryToAddConstraintWithMarker:expression:integralizationAdjustment:mutuallyExclusiveConstraints:]
12. Foundation 0x00000001095f2a09 -[NSLayoutConstraint _addLoweredExpression:toEngine:integralizationAdjustment:lastLoweredConstantWasRounded:mutuallyExclusiveConstraints:]
13. Foundation 0x000000010943f96d -[NSLayoutConstraint _addToEngine:integralizationAdjustment:mutuallyExclusiveConstraints:]
14. UIKit 0x0000000107b31590 -[UIView(UIConstraintBasedLayout) _layoutEngine_didAddLayoutConstraint:roundingAdjustment:mutuallyExclusiveConstraints:]
15. UIKit 0x0000000107b31966 -[UIView(UIConstraintBasedLayout) _tryToAddConstraintWithoutUpdatingConstraintsArray:roundingAdjustment:mutuallyExclusiveConstraints:]
16. UIKit 0x0000000107b31adf -[UIView(UIConstraintBasedLayout) _tryToAddConstraint:roundingAdjustment:mutuallyExclusiveConstraints:]
17. IBCocoaTouchToolFoundation 0x00000001071e0ea0 -[IBCocoaTouchToolAutolayoutEngine tryToAddConstraint:toRepresentedView:roundingAdjustment:mutuallyExclusiveConstraints:]
Related
I'm having trouble with a Mac App Store submission
I have an Application Developed in Xamarin.Forms
I release the App from Visual Studio for MAC in Release mode
When I Install the package manually in my MAC system It is working perfect.
But when i upload the same package to AppleStore same is rejected With reason as
**Binary Rejected
Guideline 2.3 - Performance Your app does not achieve the core functionality described in your marketing materials or release notes.
Specifically, App does not launch from Finder. App icon momentarily appears on Dock but quit itself before being launched.**
Here are the detail of my Visual Studio and MAC Signing
Detail of Visual Studio for MAC
MAC Signing detail
Crash Report of this is as below
Process: MYApp [3341]
Path: /Users/USER/Desktop/*/MYApp.app/Contents/MacOS/MYApp
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? 1
Responsible: MYApp [3341]
User ID: 501
Date/Time: 2019-02-01 12:51:57.589 +0530
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Anonymous UUID: 4C4421D7-C0F8-0B8D-8B82-A6E78F50AE60
Time Awake Since Boot: 9000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
Review the official doc on the reason behind "EXC_CRASH (Code Signature Invalid)" and how to manually sign your app.
Q: When I run my Mac app, it crashes immediately, and the crash log says Exception Type: EXC_CRASH (Code Signature Invalid). What is going on here?
A: The crash log indicates that your app is signed with your Mac App Store distribution identity, with the certificate’s Subject Common Name starting with “3rd Party Mac Developer Application.” Mac apps signed this way can no longer be run directly. Here’s the background on this.
https://developer.apple.com/library/archive/qa/qa1884/_index.html#//apple_ref/doc/uid/DTS40015141
Hi guys I have a strange problem.
Trying to run my app on the iPhone, xcode has a sudden crash. This only happens if I use my university account to develop. If I sign the application with my personal account (the one where the signature expires after 7 days) xcode does not crash.
Why ?!
If I start the app on the emulator with my university account, do not crash.
:O
This is crash log:
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
MainQueue: -[IDEProvisioningManager setDelegate:callbackQueue:]_block_invoke
ProductBuildVersion: 8E3004b
ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-12175.1/IDEFoundation/Provisioning/Mechanic/UserActions/IDEProvisioningUserAction.m:125
Details: method -[IDEProvisioningUserAction userActionName] is a responsibility of subclasses of IDEProvisioningPermissionsFailureUserAction
Object: <IDEProvisioningPermissionsFailureUserAction: 0x7f9f7d82a870>
Method: -userActionName
Thread: <NSThread: 0x7f9f78e00ce0>{number = 1, name = main}
This is a permissions issue, and usually happens because the device UDID needs to be added to the developer account you are using.
Once the UDID is added to the account Xcode should be able to create the provisioning profiles and shouldn't crash. If you're not the administrator of the developer account you're trying to use with the device you'll need to ask them to add the UDID of the Apple device to it's certificate.
Running the simplest, default code in Xcode 7 playgrounds... get the following error
Playground execution failed: Execution was interrupted, reason: EXC_BAD_ACCESS (code=1, address=0x8).
* thread #1: tid = 0x351bc3, 0x00000001062019ca libicucore.A.dylib`utext_clone + 22, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)
* frame #0: 0x00000001062019ca libicucore.A.dylib`utext_clone + 22
frame #1: 0x000000010633ac42 libicucore.A.dylib`icu::RegexMatcher::reset(UText*) + 54
frame #2: 0x0000000106375414 libicucore.A.dylib`uregex_setText + 222
frame #3: 0x0000000103d1b445 Foundation`-[NSRegularExpression(NSMatching) enumerateMatchesInString:options:range:usingBlock:] + 2325
frame #4: 0x0000000103d65d7e Foundation...
Cannot run anything in playgrounds basically.
Running beta 4 (7A165t)
I also have Xcode 6.2 running playgrounds just fine on the same mac.
Complete reinstall of all versions of Xcode plus deleting folder Library/Developer fixes the issues (see https://forums.developer.apple.com/thread/13969).
I just had this issue - before a fresh install check you haven't got IOS simulator running in the background anywhere from another xcode project or previous session. Once I closed the IOS simulator, closed xcode and re-launched and opened the playground again it worked fine. Seems I had a problem with xcode trying to open multiple simulators.
EXC_BAD_ACCESS Exception thrown when you try to send a message to already released object.
Apple provides mechanics with special class NSZombie which replace every released object in memory.
You could find more details on following links:
http://www.touch-code-magazine.com/how-to-debug-exc_bad_access/
http://loufranco.com/blog/understanding-exc_bad_access
execution suspends faithfully on a breakpoint in webkit's debugger, but a few moments later, the app crashes on the simulator (see attached screenshot). I am using
Xcode Version 6.3.2 (6D2105)
iOS Simulator Version 8.3
Safari Version 8.0.2 (10600.2.5, r185482)
It works well on the actual device.
Update: Now its happening in the device as well. The console says:
bool _WebTryThreadLock(bool), 0x16d32e00: Multiple locks on web thread not allowed! Please file a bug. Crashing now...
1 0x2e3ba3d7 <redacted>
2 0x226a5fed <redacted>
3 0x226a36ab <redacted>
4 0x226a39ff <redacted>
5 0x225f0201 CFRunLoopRunSpecific
6 0x225f0013 CFRunLoopRunInMode
7 0x2e3b9183 <redacted>
8 0x31065e23 <redacted>
9 0x31065d97 _pthread_start
10 0x31063b20 thread_start
I just started out programming for iOS. I tried adding an enter button for a simple calculator and changing its size, but Xcode keeps crashing. This is the report:
Process: Xcode [406]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 4.5.1 (1842)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 4G1004
ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch-1929/IBPlugin/Utilities/IBObjectMarshalling.m:651
Details: Failed to arbitrate IBNSLayoutConstraint, IBUIButton, IBUILabel, IBUIView, and IBUIViewController.
Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Exception name: IBAssertionFailure
Exception reason: ASSERTION FAILURE:
Reason: All views needing candidate constraints have already had constraints generated. This most likely indicates a bug involving layout of the following views:
Layout engine frame ({{20, 20}, {282, 36}}) of <UILabel: 0x81f5560; frame = (20 20; 281 36); text = '0'; clipsToBounds = YES; opaque = NO; autoresize = TM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x815cdd0>> does not match canvas frame ({{20, 20}, {281, 36}})
I've already tried reinstalling Xcode and resetting iOS simulator as well. I have Mountain Lion.
Try this steps:
1) Right click on Storyboard in the navigator
2) Click on Show File Inspector
3) Uncheck "Use Autolayout"
Hope this helps