- This topic has 9 replies, 3 voices, and was last updated 12 years, 2 months ago by
.
-
Posts
-
Hi
Using 2.1.2, if I have a screen up and I’ve clicked into an edit box so the on screen keyboard of the phone appears and then I click a navigation key to transition to another screen (while the keyboard is still showing), the next screen seems to think the phone height finishes where the keyboard started, so you get a half height screen appear. Its hard to explain but if you dont follow I can send some screen shots to support email. This is happening on a Samsung Galaxy SIII. I will try it on an Apple and a tablet later.
Tony
Hi Tony,
Thanks for your report. I’m able to replicate the issue on android 2.3.6 and I’ve opened a bug. Can you tell me what android version is installed on your device?
Apologies
I’ve been busy developing in mobione and didn’t see the response. It’s android ICS and jelly bean
Do you know when you might have a fix for this? Hoping to release my first app soon and this issue will make the app look poor quality 🙁
Thanks
Tony
Hi dynorodney,
The dev team has worked on it and we are trying to get in the upcoming 2.2 version if it passes tests on all of our android devices.
Hi
I have just installed the 2.2 (love the fact that you now support iphone 5) but still getting the keyboard / screen size issue. This is on a Samsung Galaxy S3 (ICS). Another side effect ive seen is that if you click a combobox spinner on screen while the keyboard is up it then positions the spinner in mid air because i think the keyboard then closes leaving the spinner in mid air – not a big problem just looks a bit wierd. My problem is that I can t really release my app while this keyboard issue exists because even I, who know about the issue am regularly moving to the next screen and only seeing half a screen and have to go back and forward again to see the full screen.
Is the an api call of some kind that i can force the keyboard off during the screen transition stage myself as an interim solution? I was hoping to have the app finished by the end of this week but would be reluctant to release for fear of bad reviews with the keyboard issue. Do you know when your next release with a fix might be? Thanks
Tony.
Hi Tony,
Thanks for your feedback. I’ve tried to replicate the keyboard issue with a 2.2 build and it has not success. I’ve reported to dev team to take a look, will inform you our findings as soon as I know more.
About the spinner issue, I’ve replicated and reported the bug 🙂
Thanks again for your report.
> but still getting the keyboard / screen size issue. This is on a Samsung Galaxy S3 (ICS)
We invested a good amount of effort fixing this problem. We have ICS test cases that passed before we released 2.2. We will run more tests tomorrow to see if we can identify a potential vendor or device specific bug.
Hi
Thanks for indicating that the change did at least make it into 2.2 – I will try again later today to replicate as my phone was also playing up a bit over the weekend and its not inconceivable that the app didnt install properly. I will come back to you later after Ive installed on both ICS and Jelly Bean and tested again.
Thanks
Hi Tony,
We ran more tests including on Galaxy Nexus S3. Could you please try this simple test webapp
http://goo.gl/68TsUClick in the 1st input field then click button in navbar to transition to new page. The transition and repaint is a little sluggish but the 2nd screen should render fully. We are continuing to look for a more performant solution.
Hi
Have re tested in my app and it is working better than it was at the weekend although I am occasionally able to get it to not work I am not able to do it with any regularity to be able to send you the app and say “do this” to see it
On your web app I couldn’t actually see the navbar just an input box and a drop down with an on click showing screen height. Etc but I’m happier now.. As you say it is a bit sluggish but the main thing is that it works most of the time
Thanks
Tony
