fix(android): verify browser before starting activity

[mcdurdin]

Fixes #6899.

@keymanapp-test-bot skip

[keymanapp-test-bot[bot]]

User Test Results

Test specification and instructions

User tests are not required

Test Artifacts

• Android
  • Keyman for Android apk
  • FirstVoices Keyboards for Android apk
  • KMSample1 apk
  • KMSample2 apk

[mcdurdin]

I could be wrong, but wouldn't this cause a lot of errors to simply become 'silent errors' from the user perspective?

True. This scenario seems unlikely to happen in "real life" -- how many Android devices don't have a browser installed? -- but it happens in the Play Store test environment. I could go ahead and add a toast notification, if you think that is important?

[jahorton]

I could go ahead and add a toast notification, if you think that is important?

I'm not sure if it's needed for every case, but that does seem to be wise for at least some of them. For example, if the user's already in a WebView (for help, keyboard search, etc), that's definitely worth a notification - otherwise the user'll be like "why isn't this working?"

I can't say that any of the change locations are spots to not include a Toast. I'm just not clear on role a few of the spots play, thus can't really say one way or the other.

[keyman-server]

Changes in this pull request will be available for download in Keyman version 16.0.51-alpha