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(android): Keyboard error message appear on the screen after installing Keyman 17.0.150 build in Android Lollipop OS #9401

Closed
1 of 8 tasks
bharanidharanj opened this issue Aug 2, 2023 · 1 comment · Fixed by #9409
Assignees
Milestone

Comments

@bharanidharanj
Copy link

bharanidharanj commented Aug 2, 2023

Describe the bug

I noticed that after installing Keyman 17.0.150 alpha build in Android Lollipop OS, it is showing keyboard error message on the screen.

Reproduce the bug

  1. Install Keyman 17.0.150-alpha build.
  2. Open Keyman-InApp.

Here, I noticed that an error message flashes on the screen. Seems to be an issue.

Note: This error message always appear on the scree whenever a new keyboard is installed.

..Error in default keyboard after opening keyman In-App

..After installing a keyboard

Expected behavior

The default keyboard should appear without showing any error message.

Related issues

#7613

Keyman apps

  • Keyman for Android
  • Keyman for iPhone and iPad
  • Keyman for Linux
  • Keyman for macOS
  • Keyman for Windows
  • Keyman Developer
  • KeymanWeb
  • Other - give details at bottom of form

Keyman version

17.0.15-alpha

Operating system

Android 5.1 Lollipop OS

Device

API 22 Android Simulator

Target application

No response

Browser

No response

Keyboard name

No response

Keyboard version

No response

Language name

No response

Additional context

No response

@jahorton
Copy link
Contributor

jahorton commented Aug 3, 2023

Ah, and... Lollipop is Android 5.0, so this is probably the same thing as #9408. I just made the connection after spinning up that issue. Easy enough fix, though.

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

Successfully merging a pull request may close this issue.

4 participants