814578 - SwiftKey input still completely non-functional

Status: RESOLVED DUPLICATE of bug 805162

(Firefox for Android Graveyard :: Keyboards and IME, defect)

Description

[Richard Newman [:rnewman]]

I see a lot of fixed bugs (e.g., Bug 707350), and some assigned or unconfirmed (Bug 812612, Bug 797590), but the most popular third-party Android keyboard has been completely non-functional in Fennec from 14 through to current Aurora 19 (albeit with different failure modes; this current one has been true for two or three releases, IIRC).

Here's a video, so this doesn't get closed as WORKSFORME.

This was reproducible in every device I've used: Android 2.2/2.3 on an HTC EVO, and now my Galaxy S3 with both 4.1 and 4.2.

  http://people.mozilla.com/~rnewman/swiftkey.m4v

Every word you 'complete' -- hitting space or picking a prediction -- gets replaced by a single space. About the only way you can do input is by:

1. Picking a different input manager (e.g., Samsung keyboard, which started working in ~17)
2. Pasting
3. Entering a single word and not 'completing' the word.

This seems to be similar to Bug 797590.

Comment 1

[Aaron Train [:aaronmt]]

> Here's a video, so this doesn't get closed as WORKSFORME.

No idea. This looks to be a phone-specific issue maybe?

Video (GN, 4.1.2, SwiftKey 3 Trial (en-US/precision setting on setup running Firefox 17 → WFM): 

http://www.youtube.com/watch?v=CUdc-Ke6-24

Need-info, Kevin, can you check your S3?

Comment 2

[(inactive) Jim Chen [:jchen] [:darchons]]

Also, the underlying bug was fixed in Aurora 19 (bug 805162). Make sure you do have Aurora 19 and not 18, or use this link http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android/en-US/fennec-19.0a2.en-US.android-arm.apk

Comment 3

[Kevin Brosnan [Ex-Mozilla]]

Works for me on Nightly and SwiftKey 3.0.6.348

Comment 4

[Richard Newman [:rnewman]]

Huh, apparently all of those updater clicks didn't end up in a happy place; still on 18. Just got 19 to install, and yes, wfm. (Got one more SwiftKey bug to file, tho…)

Thanks, chaps!