Closed Bug 1043738 Opened 10 years ago Closed 8 years ago

When launching the camera application, two sets of app permission prompts are requested.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- affected

People

(Reporter: djabber, Unassigned)

References

Details

(Whiteboard: [2.0-319MB-bug-bash])

Build Information
Device: Flame
Gaia      29266e18c35f4e72e35f1bba0e34f2fb6b995cc3
Gecko     https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/178fe2efc41d
BuildID   20140724000201
Version   32.0
ro.build.version.incremental=109
ro.build.date=Mon Jun 16 16:51:29 CST 2014
B1TC00011220

Description
Launching the camera app for the first time requests app permissions both for the camera and then for Smart Collections. 

Steps to Reproduce
1. Launch camera
2. Accept App permissions prompt

Expected Results
Go to Camera

Actual Results
An app permission prompt for Smart collections is shown. 

Other Notes


Reproduction Frequency:
QA Wanted for a video & branch checks.
Keywords: qawanted
Unable to repro on the reported buildor on today's build.  After about five attempts, each one only displayed the share request for the camera.

Today's build
Build ID: 20140804060132
Gaia: 4ab7384db7aee130be165a699472cc19405a4456
Gecko: 5e94ab16ec71
Platform Version: 32.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Flags: needinfo?(jmitchell)
Another tester and myself have been unable to repro this - can we get an updated Repro Rate (you left yours blank) and maybe a video so we can determine if we are missing a step in our repro attempts?
Flags: needinfo?(fdjabri)
QA Contact: croesch
Francis, Is it possible you may have accidentally tapped on camera then on a collections icon? I am able to get this bug to occur on the reporters build and the latest 2.0 build only by following my STR below.

Prerequisite:
App permissions for both Camera and Collections must be set to ASK prior to attempting this bug.

***NOTE: Will Provide video in next comment.

STR
1. Tap on Camera app then quickly tap on a collections icon on the Homescreen.
2. Camera app will launch
3. Camera permissions window will be shown. Tap Share
4. Next Collections permissions window will be shown.

Actual Results: Both permissions windows will be seen inside the camera app.

Environmental Variables:
Device: Flame 2.0
BuildID: 20140724000201
Gaia: 29266e18c35f4e72e35f1bba0e34f2fb6b995cc3
Gecko: 178fe2efc41d
Version: 32.0 (2.0) 
Firmware Version: v122
------------------------------------------------
Environmental Variables:
Device: Flame 2.0
BuildID: 20140805022752
Gaia: 4959d1eb92fa82198409c90f471aad6d68c463b3
Gecko: c18fb97addb8
Version: 32.0 (2.0) 
Firmware Version: v122
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
This is not a Camera issue.
Component: Gaia::Camera → Gaia::Homescreen
(In reply to Cody Roesch [:croesch] from comment #4)
> Francis, Is it possible you may have accidentally tapped on camera then on a
> collections icon? I am able to get this bug to occur on the reporters build
> and the latest 2.0 build only by following my STR below.

Cody, yes this is what must have happened. Thanks for checking this out.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Flags: needinfo?(fdjabri)
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: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.