Kaljurand / K6nele

An Android app that offers speech-to-text user interfaces to other apps
http://kaljurand.github.io/K6nele/
Apache License 2.0
267 stars 83 forks source link

RecognizerIntent sometimes starts in a wrong activity #17

Closed Kaljurand closed 9 years ago

Kaljurand commented 9 years ago

Original issue 13 created by Kaljurand on 2011-11-04T19:08:41.000Z:

What steps will reproduce the problem?

  1. Start from a launcher icon, and go into a deeper menu, e.g. Demos
  2. Press HOME (leaving the Demos' activity on the top of the stack)
  3. Launch an app with a textfield (e.g. an SMS app)
  4. Try to fill the textfield via SwiftKey X's microphone button

What is the expected output? What do you see instead?

Instead of RecognizerIntentActivity (which provides the recorder/recognizer box), you'll see the Demos' activity, i.e. the current topmost activity in the RecognizerIntent activity stack.

To work around this problem, one must press BACK until reaching the HOME-screen, so that RecognizerIntent is completely destroyed and then go back to filling the textfield.

When called from another app, ALWAYS RecognizerIntentActivity must start.

Kaljurand commented 9 years ago

Comment #1 originally posted by Kaljurand on 2011-11-07T09:10:05.000Z:

I think it should be fixed before release. It seems to happen at the first use: e,g., after installing and checking the settings, and then trying to use the app via Swiftkey (to fill a text field), I'm taken back to the setting screen.

Kaljurand commented 9 years ago

Comment #2 originally posted by Kaljurand on 2011-11-07T09:16:22.000Z:

<empty>

Kaljurand commented 9 years ago

Comment #3 originally posted by Kaljurand on 2011-11-21T08:48:54.000Z:

This bug seems to be specific to SwiftKey X, e.g. it is not triggered by SlideIT Demo Keyboard.

Kaljurand commented 9 years ago

Comment #4 originally posted by Kaljurand on 2011-12-13T13:23:47.000Z:

<empty>

Kaljurand commented 9 years ago

Comment #5 originally posted by Kaljurand on 2011-12-31T13:35:32.000Z:

Fixed in v0.8+