Closed Bug 1129255 Opened 9 years ago Closed 9 years ago

[NFC] Unable to show BT confirm dialog when NFC headset detected

Categories

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

ARM
Linux
defect
Not set
normal

Tracking

(blocking-b2g:2.5?, b2g-v2.2 unaffected, b2g-master verified)

VERIFIED FIXED
blocking-b2g 2.5?
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- verified

People

(Reporter: ashiue, Assigned: gasolin)

References

Details

(Keywords: regression)

Attachments

(1 file)

Gaia-Rev        dfebaaa8aab43470f482d09d71137bab840c3ae9
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/0c2f7434c325
Build-ID        20150203160231
Version         38.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150203.193141
FW-Date         Tue Feb  3 19:31:52 EST 2015
Bootloader      L1TC000118D0

A phone with NFC. and a NFC-capable bluetooth headset

STR:
1. Enable NFC 
2. Tap the phone with NFC-capable bluetooth headset

Expecteed result:
Show BT confirm dialog

Actual result:
Device vibrate but no BT confirm dialog shows
QA Whiteboard: [COM=NFC]
[Blocking Requested - why for this release]:
Obvious problem
blocking-b2g: --- → 3.0?
Bug 1125019 fix this issue in 2.2.
Bug 1092894 (NFC Core refactor) include the above fix but might introduce other issue around these dialogs.
Depends on: 1092894
The reason is the lazyloader does not work well within `nfc_handover_manager.js`, so the dialogs does not actually loaded into system. 
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/nfc_handover_manager.js#L579

I guess it might be related to how core registry works. I've met the same issue in bt_core for experimental work as well.

Remove the lazyload part and put import back into index.html could fix the problem. 
It's not an elegant solution though. @alive do you have any suggestion?
Flags: needinfo?(alive)
Assignee: nobody → gasolin
(In reply to Fred Lin [:gasolin] from comment #3)
> The reason is the lazyloader does not work well within
> `nfc_handover_manager.js`, so the dialogs does not actually loaded into
> system. 
> https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/
> nfc_handover_manager.js#L579
> 
> I guess it might be related to how core registry works. I've met the same
> issue in bt_core for experimental work as well.
> 
> Remove the lazyload part and put import back into index.html could fix the
> problem. 
> It's not an elegant solution though. @alive do you have any suggestion?

No idea. Please help to debug inside LazyLoader.
I don't think Core will impact LazyLoader though.
Flags: needinfo?(alive)
The initial LazyLoader tracking shows 'js/nfc_connect_system_dialog.js' always trapped in LazyLoader 'isloading' list and not flow into `perFileCallback` function.
QA Contact: bzumwalt
Bug 1092894 cause this issue so no need regressionwindow.
For this specific case the reason is miss-spelling the `system_nfc_connect_dialog` to `nfc_connect_system_dialog`. 

But in experiment the lazyloader only report error with `/js/system_nfc_connect_dialog` (with prefix /), since the system baseURL is `http://system.gaiamobile.org/index.html`. Without the `/` prefix the result just as comment 5, which is interesting...
Status: NEW → ASSIGNED
Comment on attachment 8561183 [details] [review]
[PullReq] gasolin:issue-1129255 to mozilla-b2g:master

test case added
Attachment #8561183 - Flags: review?(alive)
Attachment #8561183 - Flags: review?(alive) → review+
fixed lint issue then try autoland

thanks!
Keywords: checkin-needed
Autolander could not locate a review from a user within the suggested reviewer list. Either the patch author or the reviewer should be in the suggested reviewer list.
Autolander could not locate a review from a user within the suggested reviewer list. Either the patch author or the reviewer should be in the suggested reviewer list.
Component: NFC → Gaia::System
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified on 

Gaia-Rev        0cf517083f7eb5fc269e1236edba50534f65e3cd
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/2cb22c058add
Build-ID        20150209160204
Version         38.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150209.193059
FW-Date         Mon Feb  9 19:31:10 EST 2015
Bootloader      L1TC000118D0
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: