28

Here's the documentation on UITextField's textContentType property:

Use this property to give the keyboard and the system information about the expected semantic meaning for the content that users enter. For example, you might specify UITextContentTypeEmailAddress for a text field that users fill in to receive an email confirmation. When you provide this information about the content you expect users to enter in a text-entry area, the system can in some cases automatically select an appropriate keyboard and improve keyboard corrections and proactive integration with other text-entry opportunities.

Because the expected semantic meaning for each text-entry area should be identified as specifically as possible, you can’t combine multiple values for one textContentType property. For possible values you can use, see Text Content Types; by default, the value of this property is nil.

This seems pretty straightforward, but I can't figure out how to make this actually do anything. I created a simple demo app, added a text field, and set self.textField.textContentType = UITextContentTypeEmailAddress. Then I ran it on an iPhone 7 with iOS 10.0.1.

At the very least I expected this to automatically select the email keyboard, without having to explicitly set it. It does not—I get the standard keyboard on my iPhone.

I also expected it to show my own email addresses for the QuickType suggestions. I've seen this happen elsewhere—if I'm in Safari and it detects that I'm editing an email field, it shows my home and work email addresses as suggestions. Again, it does not do that here, even though the documentation suggests that it should.

Even if I also set the keyboardType to UIKeyboardTypeEmailAddress, I still don't get the QuickType suggestions I was expecting.

There's a WWDC talk that discusses this new capability, but there's never any suggestion that you need to do anything other than set this single property.

Am I missing some step, or does this not actually do what I'm expecting?

Community
  • 1
  • 1
robotspacer
  • 2,732
  • 2
  • 28
  • 50
  • 1
    FWIW, I'm not seeing it work either. I set it to type 'place' or location or whatever that option is for a field where we enter place names and AFAICT, it has no impact. – Hunter Sep 23 '16 at 20:58
  • Not working here, can't think of any other options or app meta-data that would make it work :( Works in Safari. 3rd party apps: was demo'd at WWDC in Uber - I wonder, does it still work in Uber? – Graham Perks Dec 07 '16 at 16:08
  • still broken in iOS 10.2 – fabb Mar 21 '17 at 07:18

3 Answers3

10

This is finally supported in third party apps in iOS 11. I have an app built using the iOS 10.3 SDK installed on iOS 11 beta 1. It includes fields with textContentType = UITextContentTypeEmailAddress and these correctly suggest the two email addresses on my contact card. I also have fields with textContentType = UITextContentTypePostalCode that correctly suggest my zip code.

In addition to the existing types, iOS 11 also adds UITextContentTypeUsername and UITextContentTypePassword, which can be used to support Password AutoFill for Apps.

robotspacer
  • 2,732
  • 2
  • 28
  • 50
4

Just for info (because i could hardly find it in google and apple docs):

In new ios apple provided a new features (look at image). Here is the description and wwdc about them.

enter image description here

Nike Kov
  • 12,630
  • 8
  • 75
  • 122
  • 1
    Threre's special trick about `smartInsertDeleteType` property. The default value always bring a single space (extra space) between the value inserted. – orafaelreis Apr 04 '19 at 13:30
  • I got burned by this extra space. See the solution provided by DonMag for a way around this: https://stackoverflow.com/questions/60566137/how-do-i-avoid-unwanted-extra-spaces-inserted-by-dictation-into-uitextfield – MikeMayer67 Mar 08 '20 at 02:48
1

I've battled on and off trying to get "auto-complete" to work by specifying .textContentType on a UITextField. It seemed hit or miss and I gave up many times. I revisited the issue today and learned a couple tricks to get it working (better).

• Set .spellCheckingType and .autocorrectionType to .no. When these properties are anything else, autocomplete does not work. To make matters worse, the default value for these properties is .default, so not setting them at all results in no auto-complete.

• keyboardType = .numberPad does not seem to support auto-complete at all. When I switched to .numbersAndPunctuation, auto-complete for phone number started working.

All that done, sometimes a text field will still fail to use auto-complete every time. If I tap into a different field, and then back to the problematic one, auto-complete works. No explanation for this, still some mystery meat I have not discovered. But the tips above got me a lot closer..."

Swany
  • 615
  • 8
  • 14