I'm aware that Serige and Diethard had posted similar threads. However, since our console outputs are different and since my scenario remains unsolved, I'm posting this here under a similar discussion title.
Everything (making sticker packs) was working as expected until I updated my iPads to iOS11. Upon testing a new sticker pack, Xcode 8 noted that it would be unable to run the sticker simulation on my iOS11 devices and that I should update Xcode to 9. So I did. However, updating to Xcode 9 crashes every simulation and what I mean by that is both the Messages app and Xcode 9 stop running.
I've tried the solution Nink posted to Diethard's thread. Admittedly, I'm unable to find this elusive ellipse.... and it may be because my output is different from the ones posted by both Serige and Diethard. Here's the output I get on my console:
2017-09-23 12:27:47.066858-0700 MobileSMS[540:100016] [Application] hasPhoneNumberAccount: NO, hasRegisteredAccount: YES, all accounts: (
"IMAccount: 0x1050057c0 [ID: D3F39D9B-CC74-4F8B-B67C-BA18079AB8A6 Service: IMService[iMessage] Login: E Active: YES LoginStatus: Connected]"
)
2017-09-23 12:27:47.067035-0700 MobileSMS[540:100016] [Application] Restoring application state. isComposingNew=NO
2017-09-23 12:27:47.067069-0700 MobileSMS[540:100016] [Application] => Looking up conversation with group ID:
2017-09-23 12:27:47.067329-0700 MobileSMS[540:100016] [Application] => Found conversation: CKConversation<0x1c4283840>{identifier:' guid:'iMessage;-;'}(
"[IMHandle: <:<None>:us> (Person: <IMPerson> (Name: <None>) <None> <None> [92]) (Account: E:]"
)
2017-09-23 12:27:47.067770-0700 MobileSMS[540:100016] [Application] => Found composition: (null)
2017-09-23 12:27:47.068056-0700 MobileSMS[540:100016] [Application] => Found composition has non-whitespace: NO
2017-09-23 12:27:47.068103-0700 MobileSMS[540:100016] [Application] => Found composition has content: NO
2017-09-23 12:27:47.068243-0700 MobileSMS[540:100016] [Application] => Restoring to last conversation CKConversation<0x1c4283840>{identifier:' guid:'iMessage;-'}(
"[IMHandle: <:<None>:us> (Person: <IMPerson> (Name: <None>) <None> <None> [92]) (Account: E]"
)
2017-09-23 12:27:47.104709-0700 MobileSMS[540:100016] [Warning] IMBalloonPluginManager. Did not find any plugin for id com.apple.messages.browser.MorePlugin
2017-09-23 12:27:47.104875-0700 MobileSMS[540:100016] [Warning] Could not determine if com.apple.messages.browser.MorePlugin is a recent or favorite!
2017-09-23 12:27:47.104945-0700 MobileSMS[540:100016] [Warning] IMBalloonPluginManager. Did not find any plugin for id com.apple.messages.browser.MorePlugin
2017-09-23 12:27:47.118729-0700 MobileSMS[540:100016] [MC] Loaded MobileCoreServices.framework
2017-09-23 12:27:47.186216-0700 MobileSMS[540:100016] [Warning] Splitview controller <UISplitViewControllerClassicImpl: 0x104d17550> is expected to have a view controller at index 0 before it's used!
2017-09-23 12:27:47.227229-0700 MobileSMS[540:100038] [MobileSMS] Successfully took out backgrounding process assertion!!
2017-09-23 12:27:47.433598-0700 MobileSMS[540:100016] IMSendProgress: 0x1c4672040 (delegate: 0x104d01170, context: 0x10602d600) is updating sending items from (null) to {
}. (removed? 0, inserted? 0, forced? 1, hasSendingMessages? 0)
2017-09-23 12:27:47.513431-0700 MobileSMS[540:100016] [LayoutConstraints] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want.
Try this:
(1) look at each constraint and try to figure out which you don't expect;
(2) find the code that added the unwanted constraint or constraints and fix it.
(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
"<NSAutoresizingMaskLayoutConstraint:0x1c4293600 h=--& v=--& CKMessageEntryView:0x105006740.midX == 544.25 (active)>",
"<NSAutoresizingMaskLayoutConstraint:0x1c4293790 h=--& v=--& CKMessageEntryView:0x105006740.width == 447.5 (active)>",
"<NSLayoutConstraint:0x1c028bb30 H:|-(0)-[CKMessageEntryView:0x105006740](LTR) (active, names: '|':UIInputSetHostView:0x10504bd80 )>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x1c028bb30 H:|-(0)-[CKMessageEntryView:0x105006740](LTR) (active, names: '|':UIInputSetHostView:0x10504bd80 )>
Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.
2017-09-23 12:27:47.521995-0700 MobileSMS[540:100016] +[CATransaction synchronize] called within transaction
2017-09-23 12:27:47.533509-0700 MobileSMS[540:100016] +[CATransaction synchronize] called within transaction
2017-09-23 12:27:47.533685-0700 MobileSMS[540:100016] +[CATransaction synchronize] called within transaction
2017-09-23 12:27:47.625734-0700 MobileSMS[540:100016] [Warning] IMBalloonPluginManager. Did not find any plugin for id com.apple.messages.browser.MorePlugin
2017-09-23 12:27:47.647475-0700 MobileSMS[540:100016] [Warning] Could not determine if com.apple.messages.browser.MorePlugin is a recent or favorite!
2017-09-23 12:27:47.656526-0700 MobileSMS[540:100016] [Warning] IMBalloonPluginManager. Did not find any plugin for id com.apple.messages.browser.MorePlugin
2017-09-23 12:27:47.739998-0700 MobileSMS[540:100016] [Application] hasPhoneNumberAccount: NO, hasRegisteredAccount: YES, all accounts: (
"IMAccount: 0x1050057c0 [ID: D3F39D9B-CC74-4F8B-B67C-BA18079AB8A6 Service: IMService[iMessage] Login: E:Active: YES LoginStatus: Connected]"
)
objc[540]: Class _MSMessageExtensionLoadingView is implemented in both /System/Library/Frameworks/Messages.framework/Messages (0x1b4275ea0) and /System/Library/Messages/iMessageBalloons/MSMessageExtensionBalloonPlugin.bundle/MSMessageExtensionBalloonPlugin (0x1091e0430). One of the two will be used. Which one is undefined.
2017-09-23 12:27:47.922476-0700 MobileSMS[540:100016] refreshPreferences: HangTracerEnabled: 0
2017-09-23 12:27:47.922567-0700 MobileSMS[540:100016] refreshPreferences: HangTracerDuration: 500
2017-09-23 12:27:47.922599-0700 MobileSMS[540:100016] refreshPreferences: ActivationLoggingEnabled: 0 ActivationLoggingTaskedOffByDA:0
2017-09-23 12:27:55.850658-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 0; 0 0); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.852430-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 0; 0 0); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.907522-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.909043-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.913906-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.916606-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.919791-0700 MobileSMS[540:100016] [LayoutConstraints] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want.
Try this:
(1) look at each constraint and try to figure out which you don't expect;
(2) find the code that added the unwanted constraint or constraints and fix it.
(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
"<NSAutoresizingMaskLayoutConstraint:0x1c4293600 h=--& v=--& CKMessageEntryView:0x105006740.midX == 544.25 (active)>",
"<NSAutoresizingMaskLayoutConstraint:0x1c4293790 h=--& v=--& CKMessageEntryView:0x105006740.width == 447.5 (active)>",
"<NSLayoutConstraint:0x1c42938d0 H:|-(0)-[CKMessageEntryView:0x105006740](LTR) (active, names: '|':UIInputSetHostView:0x10504bd80 )>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x1c42938d0 H:|-(0)-[CKMessageEntryView:0x105006740](LTR) (active, names: '|':UIInputSetHostView:0x10504bd80 )>
Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.
2017-09-23 12:27:55.926028-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.927380-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.929529-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.930842-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.962914-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.963387-0700 MobileSMS[540:100016] API error: <CKInputView: 0x104da1ef0; baseClass = UIInputView; frame = (0 96; 768 265); layer = <CALayer: 0x1c0425ca0>> returned 0 width, assuming UIViewNoIntrinsicMetric
2017-09-23 12:27:55.965659-0700 MobileSMS[540:100016] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'attempt to scroll to invalid index path: <NSIndexPath: 0x1c06226a0> {length = 2, path = 0 - 9223372036854775807}'
*** First throw call stack:
(0x183d3fd38 0x183254528 0x183d3fc80 0x18dbca89c 0x18dbcaf30 0x19b2e0074 0x19b27c818 0x183cd212c 0x183cd2090 0x183ce816c 0x183ce7a3c 0x183ce5ca4 0x183c062d8 0x185a97f84 0x18d1b2880 0x104c29814 0x18372a56c)
libc++abi.dylib: terminating with uncaught exception of type NSException
If anyone has any advice, please share.
Thanks.