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): embedded Keyman engine not loading #13312

Open
sentry-io bot opened this issue Feb 21, 2025 · 2 comments
Open

bug(ios): embedded Keyman engine not loading #13312

sentry-io bot opened this issue Feb 21, 2025 · 2 comments
Assignees

Comments

@sentry-io
Copy link

sentry-io bot commented Feb 21, 2025

Sentry Issue: KEYMAN-WEB-M6

TypeError: undefined is not an object (evaluating 'kmw['showKeyboardList'] = menuKeyDown')
  at init (/Users/jahorton/Library/Developer/CoreSimulator/Devices/55DE8FCE-8C08-4889-B803-C4AE32E358D4/data/Containers/Shared/AppGroup/C40B933F-553A-486B-8F52-30A8EC5153C4/keyman/ios-host.js:47:8)

Note that this is the first line in ios-host.js that actually attempts to reference something on the main Keyman Engine for Web object keyman.

@jahorton
Copy link
Contributor

Using the old "Debug + Sentry" configuration for the iOS project, I was able to force this error by changing the filename for the Web engine in keyboard.html to something incorrect. I also relocated the keyman-sentry.js script higher up so that it would load earlier, before the attempt to follow the broken link for the Web engine. This certainly did force the error and gave us a reproduction.

The reproduction:

https://keyman.sentry.io/issues/5464670660/events/5de209735b97434e9601223ccfe278d7/

Note the release entry: [email protected] Clearly a bit outdated, but it's clearly an error from a local, development build. From the same city as our office. It's a repro.

Sadly, it's worth noting that Sentry does not pick up any breadcrumbs whatsoever for us about the failed attempt to load keyman-webview.js. (Or any .jsx variant, as that's how I chose to retool the reference in order to break it.)

@jahorton
Copy link
Contributor

Aside from my artificial "repro", no instances are recorded for 18.0; they're only 17.0.

I'm currently curious if there may be a relationship to #11259 and the other issues I've associated with it. We've seen random keyboard-script failures and model-script failures... so why not random web-engine script failures as well?

Also, it should go without saying that if this error triggers, that'll also present a blank keyboard - this specific case could well underlie #11202.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant