921316 - [Homescreen] When selecting app in homescreen, app is not launched

Status: RESOLVED DUPLICATE of bug 911643

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

Description

[Leo]

1. Title : When selecting app in homescreen, app is not launched
2. Precondition : 
3. Tester's Action : Drag and drop app icon serveral times >> Select icon
4. Detailed Symptom : App is no launched
5. Expected : App is launched
6. Reproducibility: Y
1) Frequency Rate : 100%

When this issue is shown, "this.olist.getAttribute('disabled')" value is always true in page.js

Comment 1

[Leo]

Attachment: VID_0011.3gp

Comment 2

[Leo]

Attachment: logcat

Comment 3

[Leo]

And, when I close app via card view, below log is occured

E/GeckoConsole(  135): [JavaScript Error: "TypeError: currentCard.addEventListener is not a function" {file: "app://system.gaiamobile.org/js/cards_view.js" line: 528}]

Comment 4

[Wayne Chang [:wchang]]

Hi reporter,

How do you get the screen into the initial state in the video? Was it done via the STR in bug 911643?

Comment 5

[Leo]

We don't have any STR. So, we are finding STR

Comment 6

[Leo]

We have one question.
Does't device execute "setTimeout" function in specific time?

We saw that "this.olist.getAttribute('disabled')" value is always true.
We think below "setTimeout" function is not run in specific time.

https://github.com/mozilla-b2g/gaia/blob/v1-train/apps/homescreen/js/page.js#L810

Because "setTimeout" function is not run, "this.olist.getAttribute('disabled')" value is true...

So, please check this question.

Comment 7

[Wayne Chang [:wchang]]

need info Cristian here for comment 6

Comment 8

[Cristian Rodriguez (:crdlc)]

please change time || this.DISABLE_TAP_EVENT_DELAY -> 600. If the callback is not fired it shouldn't be because of homescreen

Comment 9

[Cristian Rodriguez (:crdlc)]

BTW, it is working in my leo device. It seems a problem related to build what you are checking because this code was landed several months ago

Comment 10

[Leo]

Sorry, I write wrong frequency.

It is hard to reproduce. So, I change frequency rate

1) Frequency Rate : 100% -> rarely

Comment 11

[Leo]

We think that if "this.olist.getAttribute('disabled')" value is true, change "this.olist.getAttribute('disabled')" value to false not using "setTimeout" function.(We guess "setTimeout" function have some errors)

Comment 12

[Leo]

(In reply to Cristian Rodriguez (:crdlc) from comment #8)
> please change time || this.DISABLE_TAP_EVENT_DELAY -> 600. If the callback
> is not fired it shouldn't be because of homescreen

what effect to the homescreen or setTimeout if it's not homescreen problems?

We hope to get the reason why this issue is happened.
It's rarely to reproduce but we should find the root cause. 
Please check again.

Comment 13

[Cristian Rodriguez (:crdlc)]

This video doesn't make sense and as you can see there are scaled icons and it is due to drag problems. So the test is not valid and suffer from bug 911643. Please apply this bug 911643 comment 42

Thanks

Comment 14

[Leo]

We think that this issue is different from Bug-911643. When we reproduce Bug-911643, we can touch the app icon and launch it. But this issus is reproduced, we can't touch the app icon and launch it. Please consider it. 

Regarding the attached video contents,
1. Already happened about app launch issue. Can’t launch any apps
2. Drag and release the icon and then the icon is overlapped with other icons
3. Repeat step 2
4. No action about touch event.

Comment 15

[Jason Smith [:jsmith]]

(In reply to Leo from comment #14)
> We think that this issue is different from Bug-911643. When we reproduce
> Bug-911643, we can touch the app icon and launch it. But this issus is
> reproduced, we can't touch the app icon and launch it. Please consider it. 
> 
> Regarding the attached video contents,
> 1. Already happened about app launch issue. Can’t launch any apps
> 2. Drag and release the icon and then the icon is overlapped with other icons
> 3. Repeat step 2
> 4. No action about touch event.

I think what Cristian is saying here is that at the point of reproduction of the bug, the phone is in a bad state with a known bug. That might mean other areas of functionality might not work by caveat, which could up the severity of the root cause bug. The best way to figure out if this is truly a separate bug is to confirm a fix for the other bug (bug 911643). Then, retest this to see if it still happens. If it does, then yes, it's a separate bug.

Could you try Cristian's suggestion in comment 13? Try applying his patch, see if it fixes bug 911643. If it does and you can still reproduce this bug, then this could be a separate problem found here.

Comment 16

[Cristian Rodriguez (:crdlc)]

Exactly Jason, I meant that. According to recorded video the phone is in a bad state with a known bug.

(In reply to Jason Smith [:jsmith] from comment #15)
> (In reply to Leo from comment #14)
> > We think that this issue is different from Bug-911643. When we reproduce
> > Bug-911643, we can touch the app icon and launch it. But this issus is
> > reproduced, we can't touch the app icon and launch it. Please consider it. 
> > 
> > Regarding the attached video contents,
> > 1. Already happened about app launch issue. Can’t launch any apps
> > 2. Drag and release the icon and then the icon is overlapped with other icons
> > 3. Repeat step 2
> > 4. No action about touch event.
> 
> I think what Cristian is saying here is that at the point of reproduction of
> the bug, the phone is in a bad state with a known bug. That might mean other
> areas of functionality might not work by caveat, which could up the severity
> of the root cause bug. The best way to figure out if this is truly a
> separate bug is to confirm a fix for the other bug (bug 911643). Then,
> retest this to see if it still happens. If it does, then yes, it's a
> separate bug.
> 
> Could you try Cristian's suggestion in comment 13? Try applying his patch,
> see if it fixes bug 911643. If it does and you can still reproduce this bug,
> then this could be a separate problem found here.

Comment 17

[Jason Smith [:jsmith]]

Is this possible to reproduce on 1.2? That will help figure out if bug 885625 fixes this issue as well.

Comment 18

[Sarah Parsons]

Unable to reproduce on the Buri 1.2 Aurora Build ID: 20131001004003

Device: Buri
Build ID: 20131001004003
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/5689e4237ab7
Gaia: 5e0d0df6a762cf1e1812eeb735fba72e2539dc0c
Platform Version: 26.0a2

Comment 19

[Jason Smith [:jsmith]]

Given the testing above and the comment I made above, I'm going to move this back to a dupe. If something similar reproduces post a fix of bug 911643, let's open a new bug with STR not in relation to bug 911643.