UITextField sends webVisiblePosition to custom UITextPosition subclass

Originator:nrbrook
Number:rdar://15004430 Date Originated:17-sep-2013
Status:Open Resolved:
Product:iOS SDK Product Version:6, 7
Classification:Crash Reproducible:Yes
 
Summary:
I have a UIView which conforms to the UITextInput protocol.  I have a subclass of UITextRange (NBTextRange) and UITextPosition (NBTextPosition) which I use with it.
If I press the up key 4 times, then the down key 3 times, then tap in a UITextField and press the down key Apple's SDK seems to be hanging on to one of my NBTextPosition objects and sending it a message it can't respond to - webVisiblePosition in iOS 6, offset in iOS 7.  Logs attached

Steps to Reproduce:
I haven't tested this so simplistically, but basically:
1. Create a UIView subclass which conforms to the UITextInput Protocol and uses custom UITextPosition and UITextRange classes
2. Make it first responder
3. Up 4 times, down 3 times
4. Make a UITextField first responder
5. Hit down

Expected Results:
Not crash

Actual Results:
Crash

Version:
6, 7

Notes:


Configuration:
iOS 6 and 7 simulator (tested)

Attachments:
'logs.txt' was successfully uploaded.

17-Sep-2013
I said 4 and 3, but if I go up once, tap the UITextField and use the down key it crashes the same.

31-Oct-2013
Please could I have a status update on this bug report as it has been nearly 2 months since opening with no response

22-Nov-2013
Thank you for contacting us. At this time, there isn't any new information available for this issue.  

We will do our best to keep you informed as new information becomes available. Please be sure to regularly check the seed and release notes for potential or related fixes that might affect this issue. 

We sincerely appreciate your patience and thank you for your support.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!