Closed Bug 1022537 Opened 5 years ago Closed 4 years ago

[search] After killing search app it cannot be relaunched

Categories

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

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jlal, Unassigned)

References

Details

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)
How exactly is the search app being killed here? LMK or simulated by killing the process via adb?
Flags: needinfo?(jlal)
The process was killed via adb ... hard to say if low memory conditions killing the search app would cause this too.
Flags: needinfo?(jlal)
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?
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.
Blocks: vertical-home-next
No longer blocks: vertical-homescreen
QA Whiteboard: [VH-FC-blocking-]
No longer blocks: vertical-home-next
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.
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.
Blocks: 1231115
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.