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(ios): system keyboard sometimes blank after device unlock #11202

Open
jahorton opened this issue Apr 10, 2024 · 2 comments
Open

bug(ios): system keyboard sometimes blank after device unlock #11202

jahorton opened this issue Apr 10, 2024 · 2 comments
Milestone

Comments

@jahorton
Copy link
Contributor

From general testing of #11179.

Test Results

  • TEST_GENERAL_USE (FAILED): Retested with the attached PR build (Keyman 17.0.305-beta-test-11179) on an iPhone 13 Mobile device (iOS 17.4) and here is my observation: 1. Set Keyman as the system wide keyboard. 2. Opened Safari browser. 3. Switched to Keyman Keyboard. 4. Typed a text on the Search bar. 5. Locked the mobile device by pressing Lock key from the mobile. 6. Unlock the mobile. Here, I noticed that the Keyman Keyboard was no longer visible in the Keyboard panel. Seems to be an issue.

Interesting that we haven't seen this one until now. There always have been odd interactions with that specific use case - see #2300 - and I can see the host-page getting reloaded / restored after locking and unlocking. It's temporarily blank for me, rather than permanently blank... but I'm also not sitting and waiting between locking & unlocking. If something were to prevent the host-page reload, that could certainly cause the issue. Of course, getting evidence of that is an entirely different matter.

Originally posted by @jahorton in #11179 (comment)

It's hard to say that this is a Safari-specific interaction, of course, but #2300 existing does make it a possibility in my mind.

@jahorton jahorton added this to the B17S5 milestone Apr 10, 2024
@jahorton
Copy link
Contributor Author

It may not be fully related, but aspects of this remind me of #6191.

@jahorton
Copy link
Contributor Author

Note that the blank keyboard seen here was after the following instruction/reminder:

As for the third user test, please verify that "Allow Full Access" has been toggled - that would probably affect the system keyboard issue you saw.

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

No branches or pull requests

3 participants