Closed
Bug 1200538
Opened 9 years ago
Closed 9 years ago
[Messages] Can't start the "new" activity from the rocket bar
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(b2g-master affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
b2g-master | --- | affected |
People
(Reporter: julienw, Unassigned)
Details
STR: 1. enter "sms:0123456789" in the rocket bar, press enter. Expected: * The SMS app should be open in the New Message panel, with the phone number prefilled in the recipient panel. Actual: * white screen. There is this error in the logs: 09-01 11:01:10.592 9428 9428 E Messages: Content JS ERROR: Activity request was rejected with "Concurrent activity requests are not allowed" reason QA: can you please do a branch check and provide a regression window if it's a regression?
Reporter | ||
Comment 1•9 years ago
|
||
Actually I reproduce on my aries/dogfood build, but not on my flame/master build from yesterday. So maybe it's been fixed recently.
Updated•9 years ago
|
QA Contact: ddixon
Comment 2•9 years ago
|
||
It appears that this bug is an Aries only issue. I also test Flame 2.5 on multiple memory settings (at 512 MB, 319 MB), but did not see a repro that way either. Issue DOES occur in latest Aries 2.5 Actual Results: The user is taken directly to a white screen. Device: Aries 2.5 Build ID: 20150812231434 Gaia: 52f3ea58df38e5427f6afeb636bc6ad01d24022f Gecko: 7649ffe28b67aa2dad0f67ea01500c0ff91b2bac Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 43.0a1 (Master) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0 ----------------------------------------------- ----------------------------------------------- Issue DOES NOT occur in Flame 2.5, 2.2 builds. Actual Results: The user is taken to the Messages app and the recipient field contains the number that the user inserted in the rocket bar. Device: Flame 2.5 BuildID: 20150901053324 Gaia: 805025801a68f9ddbba6ffd2ed3926c97fa7fcc8 Gecko: dd509db16a138beb777599662ad88e3207bc2d2c Version: 43.0a1 (Master) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0 Device: Flame 2.2 BuildID: 20150901064340 Gaia: 335cd8e79c20f8d8e93a6efc9b97cc0ec17b5a46 Gecko: d91926669834 Version: 37.0 (2.2) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → affected
Flags: needinfo?(jmercado)
Keywords: qawanted
Reporter | ||
Comment 3•9 years ago
|
||
The aries build is quite old. Is it possible to try with a newer aries build ? Or an older Flame build? So that we can compare apples with apples ?
Comment 4•9 years ago
|
||
Duane please check this again on the latest Aries build.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(jmercado) → needinfo?(ddixon)
Comment 5•9 years ago
|
||
I've tested this bug on the latest Aries 2.5 build. The bug DOES NOT repro here. Actual Results: The user is taken to the Messages app and the recipient field contains the number that the user inserted in the rocket bar. Environmental Variables: Device: Aries Master BuildID: 20150901190824 Gaia: c2582f4be03cd12124b96a263c8d14c774f0ffe4 Gecko: e47423c019643792e6de894cfcee598dead4d3ba Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 43.0a1 (Master) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0 I've also tested an old Flame build (20150811030209) against this bug and it DOES occur there. The user is taken directly to a white screen.
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(ddixon) → needinfo?(jmercado)
Comment 6•9 years ago
|
||
This issue is no longer occurring on the latest builds. Please reopen if it begins occurring again.
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(felash)
Resolution: --- → WORKSFORME
blocking-b2g: 2.5? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•