I updated my app from Xcode 7 to Xcode 8 and now I am facing a problem with my password input field.When the password is longer than the provided field, my app freezes and starts to consume memory until it crashes.Fun fact, it just happens when I set the text to "secure text".My field is vertically centered and has a fixed width (not sure if thats imporant), and when my password is longer than the number of characters, the input field can take (and where it should move to the left) I get the crash.
Did anybody experience smt like that?(as I said I just updated to a newer XCode - running on a 10.0.2 real device, didnt have that problem on the old one ...)
Thanks,
Regards
Yes, it is a bug.
Bug is like :
An app can freeze when a user types a large password into a textfield that tries to scale down the text to fit.
Check it : https://openradar.appspot.com/28590124
Possible solution :
change the secure password character in UITextfield
Secure UITextField text change to (*) asterisk character
Related
I have set the passwordTF.secureTextEntry = true and everything is working fine the UITextField is getting masked . But I see that if take a screenshot with the numeric keypad and masked input then the screenshot doesn't contains any keypad or text. Everything is blank . Is it the security feature of iOS for secureTextEntry ?
I tried to search but could not find any specific documents and I am using iOS 14.6
Sorry for being late actually I found out that it is a security feature which is in action since iOS 13 itself so if you have a keyboard which is numeric and in case you have a text field with secure text masking on then the screenshot captured will not show the keyboard or the textfield contents
Apple Discussion 1
Apple Discussion 2
On iOS 10 in a UILabel, the letter יִ (a yud with a chirik under it) is getting displayed as a circle instead of the way it's supposed to appear.
Other vowels and letters (e.g. יֵ יַ יֶ יֹ) are being displayed ok.
I submitted this as a bug to apple (bug id 28561355 on https://bugreport.apple.com).
Even if apple can fix this in a future version of iOS, is there anything I can do now, to hack this to work? I can just replace the yud-chirik with a plain yud, but I'd rather try and keep the display as it's supposed to be.
Thanks.
UPDATE: It seems that if I change the font to the default apple font (instead of a custom font that I was using), then the yud-chirik appears, but the chirik appears in the wrong place. It appears directly under the yud instead of at the bottom with all the other vowels.
When I write arabic text containing the letter kasra (unicode character 0x650, phonetic equivalent i) to a button, the kasra is not displayed. Thus, the word mumkin appears as mumkn. If I inspect the NSString in Xcode, the kasra is present, but the kasra is not displayed in the iPhone simulator or on a real iPad. The other two short vowels (fatha and damma) are displayed correctly.
The arabic letter kasra (unicode character 0x650) is missing from all of the built-in IOS7 fonts that i have tried.
The solution was to build a different font into my app- I used AGA-Rasheeq-Bold.
This may be a bug. I just tried it in the storyboard editor and it does not seem to work. I created a string in the MAC Notes application, copied and pasted. It displays correctly in the left hand properties panel, but not in the button itself. Could you provide the exact Unicode string? You may need to open a bug report with Apple.
I can confirm that it works correctly in a Label field, but not a Button (IOS 6.1 and Xcode 4.6.3)
Try attributed text. This seems to work around the issue.
Playing around with my web application in the iOS 5 simulator, I noticed that iOS 5 doesn't clear placeholders immediately, only after the first input. On all other version of iOS as well as on all desktop browsers, the placeholder is immediately cleared when the user focuses on the input. I don't have access to an iOS 5 device right now but I highly doubt this is a simulator error.
Is this a bug or intended? Oddly I only found one reference to this behavior on the net, right here on SO: clearing input placeholder in iOS5
Is there a workaround for this problem? It's quite frustrating for the user when the placeholder doesn't clear immediately.
I think you are mistaken - iOS text fields always behave this way.
I don't see why this would be frustrating for the user. If anything it is helpful that the helper text stays visible until they begin typing, in case they missed it before selecting the field.
What may be confusing you is that iOS fields have a separate optional behaviour where the text is cleared when the field is selected, but note that this is the actual text that clears, not the placeholder text.
Placeholder text is the light grey text, and this always appears until the user types something.
Content text (usually black) sometimes clears when the field is focussed and sometimes doesn't, depending on how the UITextField was configured.
The jQuery solution in the SO question you linked to should let you replicate any variant of this functionality that you desire, but personally I'd advise sticking with the iOS convention of not clearing helper text until the user types something.
It is not a bug, it is a feature. You can use delegate methods to clear placeholder. (UITextFieldDelegate http://developer.apple.com/library/ios/#documentation/uikit/reference/UITextFieldDelegate_Protocol/UITextFieldDelegate/UITextFieldDelegate.html)
- (void)textFieldDidBeginEditing:(UITextField *)textField
{
[textField setPlaceholder:#""];
}
adn you should control its emptiness after finish editing.
- (void)textFieldDidEndEditing:(UITextField *)textField
{
if ([textField.text isEqualToString:#""])
[textField setPlaceholder:#"Placeholder Text"];
}
On the iOS platform, I have a UITextField where I am using the ASCII keyboard layout. I notice (like the keyboard works in other apps) that when I type space + space, a period '.' is inserted into the text field. This is all normal iOS stuff...
But can I configure the text field or the keyboard somehow so that this "two spaces == period" behavior is turned off?
One possible solution (albeit not a perfect one) has been posted here ... http://www.mailinglistarchive.com/phoenix-iphone-developer-group#googlegroups.com/msg00037.html