Weird console message but no crash error

Solar2D Daily Builds and Public Releases
#1

I am running a custom search function through the text input and this is what shows in the corona console using the now available text input via corona simulator. There is no error message but I am not sure what this means.

I have tried this on the xcode simulator and ios device and the console for those does not show any errors or messages like this.

Can anyone share any light on this below?

2011-11-24 17:30:22.847 Corona Simulator[23179:903] HIToolbox: ignoring exception '\*\*\* -[NSBigMutableString substringWithRange:]: Range or index out of bounds' that raised inside Carbon event dispatch ( 0 CoreFoundation 0x93e1d6ca \_\_raiseError + 410 1 libobjc.A.dylib 0x9706c5a9 objc\_exception\_throw + 56 2 CoreFoundation 0x93e1d3f8 +[NSException raise:format:arguments:] + 136 3 CoreFoundation 0x93e1d36a +[NSException raise:format:] + 58 4 Foundation 0x99c361ba -[NSString substringWithRange:] + 155 5 AppKit 0x936957ff -[NSTextStorage(NSUndo) \_undoRedoAttributedSubstringFromRange:] + 177 6 AppKit 0x93695675 -[NSUndoTyping initWithAffectedRange:layoutManager:undoManager:replacementRange:] + 176 7 AppKit 0x9369544b -[NSTextViewSharedData coalesceInTextView:affectedRange:replacementRange:] + 720 8 AppKit 0x93693e48 -[NSTextView(NSSharing) shouldChangeTextInRanges:replacementStrings:] + 1710 9 AppKit 0x93692560 -[NSTextView insertText:replacementRange:] + 667 10 AppKit 0x93690217 -[NSTextInputContext handleTSMEvent:] + 2657 11 AppKit 0x9368f7a5 \_NSTSMEventHandler + 209 12 HIToolbox 0x9a29fc2f \_ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567 13 HIToolbox 0x9a29eef6 \_ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411 14 HIToolbox 0x9a2c17f3 SendEventToEventTarget + 52 15 HIToolbox 0x9a3239de SendTSMEvent + 82 16 HIToolbox 0x9a32335b SendUnicodeTextAEToUnicodeDoc + 700 17 HIToolbox 0x9a322f65 TSMKeyEvent + 998 18 HIToolbox 0x9a313e32 TSMProcessRawKeyEvent + 2515 19 AppKit 0x9368f084 -[NSTextInputContext handleEvent:] + 1453 20 AppKit 0x9368aed1 -[NSView interpretKeyEvents:] + 209 21 AppKit 0x9368e9a1 -[NSTextView keyDown:] + 751 22 AppKit 0x935bfb28 -[NSWindow sendEvent:] + 5757 23 AppKit 0x934d860b -[NSApplication sendEvent:] + 6431 24 AppKit 0x9346c253 -[NSApplication run] + 917 25 AppKit 0x93464289 NSApplicationMain + 574 26 Corona Simulator 0x00002515 0x0 + 9493 27 ??? 0x00000001 0x0 + 1 )
As mentioned the app does not error and I am still able to use it. This only appears on the very first call to [lua]“editing” == event.phase[/lua] of the textfield, not on any subsequent calls to the editing phase. [import]uid: 69160 topic_id: 18185 reply_id: 318185[/import]

#2

I see the same giant message on Simulator terminal every time I start entering text into native.newTextField object. It doesn’t seem to affect the app itself, and it doesn’t show up on console when using device build.

Unless this message is something we need to understand and work out a solution to avoid getting the warning, it would be nice if we don’t have to see it at all, because it takes up a lot of terminal space and buries other print-statements.

Naomi

P.S. @dale7, have you filed a bug report for this? If not, please let me know, and I’ll file one. [import]uid: 67217 topic_id: 18185 reply_id: 119474[/import]

#3

No I haven’t feel free! [import]uid: 69160 topic_id: 18185 reply_id: 119475[/import]

#4

I filed the bug report (Case #16536).

Naomi

Edit: This has been looked at and I received a reply to my bug report from Tom as follows:

_We did some testing and were able to reproduce the problem and believe it’s an Apple bug because the error is coming from internal Apple code.

We found that if you clear the text field in the “editing” phase instead of “began”, there is no exception.

In addition, we added a “o.placeholder” property to native.newTextField that should achieve what you are trying to do with your existing code. This feature is already in iOS and will be in the Mac Simulator in the next Daily Build (886?). We currently don’t have it in Android, but it’s on our to-do list._

Thank you, Tom and Corona Labs Team! [import]uid: 67217 topic_id: 18185 reply_id: 119487[/import]

#5

I filed the bug report (Case #16536).

Naomi

Edit: This has been looked at and I received a reply to my bug report from Tom as follows:

_We did some testing and were able to reproduce the problem and believe it’s an Apple bug because the error is coming from internal Apple code.

We found that if you clear the text field in the “editing” phase instead of “began”, there is no exception.

In addition, we added a “o.placeholder” property to native.newTextField that should achieve what you are trying to do with your existing code. This feature is already in iOS and will be in the Mac Simulator in the next Daily Build (886?). We currently don’t have it in Android, but it’s on our to-do list._

Thank you, Tom and Corona Labs Team! [import]uid: 67217 topic_id: 18185 reply_id: 119487[/import]