Skip to content

Conversation

@MCGallaspy
Copy link
Contributor

This builds but does not install on Keyman Android. I cannot for the life of me figure out why. Can anyone please help?

The specific error message I get when attempting to install the .kmp file is "Keyboard package has no touch-optimized keyboards to install."

@keyman-server
Copy link
Collaborator

Thank you for your pull request. You'll see a "build failed" message until the Keyman team has reviewed the pull request and manually initiated the build process.

Every change committed to this branch will become part of this pull request. When you have finished submitting files and are ready for the Keyman team to review this pull request, please post a "Ready for review" comment.

@DavidLRowe
Copy link
Contributor

I'll note that your touch layout won't produce output for the ą longpress key on a for example. The key on the touch layout has ID of T_new_244 assigned by the Keyman Developer program. Unless you put a rule in the .kmn file that is triggered by [T_new_244], no output will be produced. But a better solution is to change the ID to U_0105 which will cause the touch layout to output U+0105. (And so on for the other longpress keys.)

I'll try to look at your question about no touch layout tomorrow.

@LornaSIL LornaSIL changed the title Add touch keyboard for Wyandot [wyandot] Add touch keyboard for Wyandot Nov 4, 2025
@LornaSIL
Copy link
Contributor

LornaSIL commented Nov 4, 2025

I don't know if it will make a difference, but in "targets", select "any" and unselect the others. Then, for sure the longpresses need updating to what @DavidLRowe said, but that doesn't explain "Keyboard package has no touch-optimized keyboards to install."

@DavidLRowe
Copy link
Contributor

I wonder if the problem is the fact that the version number has not been incremented. It may be that Keyman sees that it already has version 1.0 of this keyboard installed. You could try changing the version in the .kmn file to 1.1 (for example) and rebuilding. (You should also change the HISTORY.md file with the new version information.) You'll need to update the version number information eventually for this keyboard revision to be accepted.

An alternative for testing would be to uninstall the keyboard from your Android device, then try installing the updated version. I think in that case it shouldn't matter that the updated keyboard has the same version as the existing one (because the existing one will have been removed).

@LornaSIL
Copy link
Contributor

LornaSIL commented Nov 5, 2025

I was able to build the keyboard and install it on my android. I had to download the .kmp to the phone and then go to settings / Install Keyboard or Dictionary / Install from local file.

FYI: when I clicked on a link and said to "Open with Keyman" it says "Storage permission request failed. Try Keyman Settings - Install from local file."

If you still aren't able to install it on your android, can you give us a screenshot of the message?

Otherwise, I suggest that you fix the issues mentioned above and we'll then check the keyboard to see if it works.

@MCGallaspy
Copy link
Contributor Author

Thanks for the suggestions. I'll take another crack at it and update here, when I get the opportunity.

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

Successfully merging this pull request may close these issues.

4 participants