Databases
StackOverflow2013
Postsdbo
PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
    primarykey
    data
    text
    <p>I have a storyboard, which includes navigation between views. Back and forth, and there is also the possibility to jump all the way to the home screen.</p> <p>Basically, it works like this:</p> <ul> <li>View 1 shows a simple menu.</li> <li>View 2 shows input fields and automatically shows the keyboard.</li> <li>View 3 shows a results table. In this view one can go one step back (to view 2) or back to the home screen (view 1).</li> </ul> <p>The keyboard and everything works perfectly the first time, when the user moves from view 1 to view 2. However, when moving either back from view 3 to view 2, or from view 3 and starting all over again, the keyboard does not show.</p> <p>In the code, I have becomeFirstResponder in the viewDidAppear method. Also, it will resignFirstResponder when loading view 3. Another interesting fact is that when calling the becomeFirstResponder for the second time, it does return NO (while it returns YES the first time). Also, when returning back to this view the textfields are not possible to select, even though they are userInteractionEnabled.</p> <p>I am really stuck here, so any help is highly appreciated. I have seen several similar questions to this one, but not found a solution:</p> <ul> <li><a href="https://stackoverflow.com/questions/1282090/becomefirstresponder-seems-to-work-only-1st-time-for-shake-gesture">becomeFirstResponder seems to work only 1st time for shake gesture</a></li> <li><a href="https://stackoverflow.com/questions/9221601/adding-myuitextfield-becomefirstresponder-does-not-bring-up-keyboard">Adding [myUITextField becomeFirstResponder]; does not bring up keyboard</a></li> <li><a href="https://stackoverflow.com/questions/10051402/keyboard-not-responding-to-resignfirstresponder">keyboard not responding to resignFirstResponder</a></li> <li><a href="https://stackoverflow.com/questions/9711929/uitextfield-becomefirstresponder-works-only-once">UITextField becomeFirstResponder works only once</a></li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USJarle Hansen
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
      1. USMCKapur
      1. VTFavorite
    2. VO
      singulars
      1. PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
      1. USbarley
      1. VTFavorite
    1. COhas anyone had any luck solving this ? I have looked all over and tried a bunch of things, but nothing works.. the keyboard will only show up 1 time per uitextfield
      singulars
      1. PObecomeFirstResponder does not show keyboard second time (ios 6 + storyboard)
      1. USuser353877
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload