1022537 - [search] After killing search app it cannot be relaunched

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

Description

[James Lal [:lightsofapollo]]

This is probably a keyboard manager bug but I found it while trying to iterate on the search app.

E/GeckoConsole( 7024): Content JS LOG at app://keyboard.gaiamobile.org/js/keyboard/input_method_manager.js:308 in InputMethodManager.prototype.switchCurrentIMEngine/p<: InputMethodManager: Promise is resolved after another switchCurrentIMEngine() call. Reject the promise instead

I did the following:

Launch search app
Search for "n"
press enter

kill search app
(n is still visible)
hit enter
(error appears)

Comment 1

[Jason Smith [:jsmith]]

How exactly is the search app being killed here? LMK or simulated by killing the process via adb?

Comment 2

[James Lal [:lightsofapollo]]

The process was killed via adb ... hard to say if low memory conditions killing the search app would cause this too.

Comment 3

[Kevin Grandon :kgrandon]

Rocketbar.js should handle search crashes :https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/rocketbar.js#L181

Presumably this should handle LMK situations, but I'm not sure if it does when you kill it through ADB?

Comment 4

[Jason Smith [:jsmith]]

Moving to VH next since we won't stop ship of the release with this issue. If it's implemented in time, then we'll get approval.

Comment 5

[Kevin Grandon :kgrandon]

Can you please put a reason when unblocking? I was using the vhomescreen.next bug as a bucket for everything that would make it nicer, this is one of those items.

Comment 6

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.