Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Erratic keyboard behaviour on iOS emulator #2283

Closed
esmeetewinkel opened this issue Apr 5, 2024 · 1 comment
Closed

[Bug]: Erratic keyboard behaviour on iOS emulator #2283

esmeetewinkel opened this issue Apr 5, 2024 · 1 comment
Milestone

Comments

@esmeetewinkel
Copy link
Collaborator

esmeetewinkel commented Apr 5, 2024

Issue
When testing on an iOS emulator, the key board does (most of the time?) not pop up properly. This happens on both a text box component and on the template list search box.

App version
Debug iOS emulator release
See in video below that key board is fine initially on template list search box, then doesn't work on text box, and then doesn't work on template list search box either

Screenity.video.-.Apr.5.2024.webm

PLH Facilitator MX emulator release
Template list search box broken, text box works
image
image

Originally posted by @esmeetewinkel in #2281 (review)

@esmeetewinkel esmeetewinkel added this to the iOS support milestone Apr 5, 2024
@jfmcquade
Copy link
Collaborator

I've just tested on a physical device (iPhone SE 3rd gen, ios 17.x), using the version of the Facilitator MX app on TestFlight, and wasn't able to recreate the issue. For both the search box on the template page and pages with embedded text box components, the keyboard reliably appeared as expected.

I think the issue is the one referenced here, namely: when using a simulator (apple's term for emulator), inputting a value using the computer's hardware keyboard causes the on-screen virtual keyboard to disappear. It can be manually made to reappear when running a simulator on desktop, but I can't find a way to do so in Appetize. Either way, I think this issue can be closed as more something to be aware of than a big.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants