Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6864929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T02:58:28+00:00 2026-05-27T02:58:28+00:00

I have a nice little app on the app store that does pretty well

  • 0

I have a nice little app on the app store that does pretty well for itself. Life was great until iOS 5 came to town. Now, I have a number of issues with my app that I have no way of fixing because I have no clue what is going on, because I feel that they are iOS 5 issues, not mine.

Was there an iOS 5 conversion manual I missed? Or did they just change everything for fun, and want us to figure out where all the easter eggs were?

Here is an issue I am experiencing (that I have wasted so much time trying to fix), that DON’T EXIST AT ALL when I simply say that I want to run the app in good ol’ 4.2:

Disappearing keyboard

So when I pull up a simple modal view, I select a tableView cell, and then I present a textView so that users can enter some text. When the textView becomes visible, I call [textView becomesFirstResponder]; so that the keyboard is up and ready for the user to use. This works the first time. Then, when you dismiss the modalView (and get the weird error I just mentioned above), and then try and go back into the modalView, and pull up the textView, the keyboard flies away! You see it for a fraction of a second, and then POOF it’s gone. I have a textView upon which my cursor is active and I am trying to edit, but my keyboard refuses to show up. Again, this works perfectly in 4.2, but not in 5!

I have tried everything under the sun to get these issues worked out, but I just can’t get them working. What should I do? I feel that these are bugs on the OS side, not mine!

Thanks for your help.

Edit:

To be more clear, I will go over what I am trying to accomplish with my view hierarchy. When I display my modal view, I have two different cells that I fill up with some text. The second cell is supposed to be editable, so when the user taps the cell, I unhide a UITextView that I hid on viewDidLoad, and call [textView becomeFirstResponder]; on the textView, and it works fine. The textView is editable, and it hides and updates the appropriate cell content when the keyboard is dismissed.

The problem is that when I dismiss the modal view, then came back into the modal view, and select the editable cell, the textView shows up just fine, and it is editable, but the keyboard blips onto the screen but then flys away and won’t show. So I have my textView there and editable, but try as I might, the keyboard won’t show! It’s absolutely driving me nuts, especially because it works perfectly on iOS 4.2.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T02:58:30+00:00Added an answer on May 27, 2026 at 2:58 am

    Ok, I was just able to figure out what in the blazes was going on. I had the shouldAutorotateToInterfaceOrientation value set to a BOOL variable that could change from TURE or FALSE, so that when the modalView was coming back, there was a chance that it didn’t know the state/size of the status bar. By manually setting it to TRUE, it fixed the issue, and the problem disappeared.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have this nice little MSBuild-based daily build setup that I use on my
I have a nice page that does everything I need. However one of the
I want to have a nice little icon that, when clicked will clear the
I wonder if that hurts performance. I have an test app which is pretty
I have a little logging app (written in wxPython) that receives data from a
I have this nice report that shows up in my web app. So far
I have a nice little UserControl that is a draggable box with some text
I am using nice little piece of xstream to perform serialization. I have the
Does anyone have a nice solution for GalleryView when I want to display photos
Imagine that I have a nice Deck class, in the best OO fashion. It

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.