Closed
Bug 1022537
Opened 10 years ago
Closed 9 years ago
[search] After killing search app it cannot be relaunched
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
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)
Comment 1•10 years ago
|
||
How exactly is the search app being killed here? LMK or simulated by killing the process via adb?
Blocks: vertical-homescreen
Updated•10 years ago
|
Flags: needinfo?(jlal)
Reporter | ||
Comment 2•10 years ago
|
||
The process was killed via adb ... hard to say if low memory conditions killing the search app would cause this too.
Flags: needinfo?(jlal)
Comment 3•10 years ago
|
||
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•10 years ago
|
||
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.
Updated•10 years ago
|
QA Whiteboard: [VH-FC-blocking-]
Updated•10 years ago
|
No longer blocks: vertical-home-next
Comment 5•10 years ago
|
||
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.
Blocks: vertical-home-next
Comment 6•9 years ago
|
||
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.
You need to log in
before you can comment on or make changes to this bug.
Description
•