Closed Bug 963007 Opened 11 years ago Closed 10 years ago

[NFC] Not receiving URL sharing

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+)

RESOLVED DUPLICATE of bug 961687
2.0 S1 (9may)
blocking-b2g 2.0+

People

(Reporter: wachen, Assigned: dgarnerlee)

References

Details

(Whiteboard: [p=1], [systemsfe])

Using most up-to-date pvt build (2014/1/24) to test STR: 1. Enable "NFC" in "Settings" app 2. tap with another phone 3. send URL from another phone Expected result: FXOS phone launched browser and connect to shared URL Actual result: Nothing launched, no URL connected, nothing works in receiving side
blocking-b2g: --- → 1.4?
Whiteboard: [FT:RIL]
Blocks: 894678
Whiteboard: [FT:RIL] → [FT:RIL] [mwcdemo2013]
blocking-b2g: 1.4? → 1.5?
Blocks: b2g-NFC-2.0
No longer blocks: b2g-NFC-2.0
Per offline discussion, Wesley will discuss this with browser team.
Flags: needinfo?(whuang)
Hi Peter, This is key focus feature in 1.5. Could you put into browser's backlog?
Flags: needinfo?(whuang) → needinfo?(pdolanjski)
Walter, is this using the system browser or the old browser? The system browser NFC implementation hasn't been done yet.
Flags: needinfo?(pdolanjski) → needinfo?(wachen)
This was the bug of previous v1.4 (v1.4 without backing out code).
Flags: needinfo?(wachen)
So, I think that is the old browser
So far I don't see need to fix in 1.4. But for 1.5 if system browser is used, we need it support URL sharing. Should a separate engineering bug be created then?
Flags: needinfo?(bfrancis)
per discussion thru email, need "old" browser to fix this in 1.5 (2.0). Peter, could you find someone to own this?
Flags: needinfo?(pdolanjski)
Saminath, do you have any idea what's going on here?
Flags: needinfo?(bfrancis) → needinfo?(s.x.veerapandian)
Hi Ben, Last time, I face same kind of issue, I tested with help of logging messages. https://bugzilla.mozilla.org/show_bug.cgi?id=961687#c3 As per my understanding, The “onpeerready = nfcPeerHandler” register from browser component. Some time it’s not invoked after Shrink UI Slide to Send. This can be tested by enable log messages in entry/exit of the nfcPeerHandler (). Currently, I do not have the Firefox Device and source code. BR, Sami.
Peter, can you make a call to have this bug be moved into your FT for v2.0 development?
I'm blocking 1.5 on this on the assumption that the overall NFC capabilities make the release. If they do, it cannot ship without this fixed. At the same time, this fix in the current browser will only move forward if it looks unlikely that the System Browser will be ready in 1.5.
blocking-b2g: 1.5? → 1.5+
Component: NFC → Gaia::Browser
Flags: needinfo?(pdolanjski)
Whiteboard: [FT:RIL] [mwcdemo2013] → [FT:RIL] [mwcdemo2013][priority]
Whiteboard: [FT:RIL] [mwcdemo2013][priority] → [FT:RIL] [mwcdemo2013]
Whiteboard: [FT:RIL] [mwcdemo2013]
Whiteboard: [systemsfe]
Given the decision on systems browser, is this still a blocker for 2.0?
Flags: needinfo?(pdolanjski)
(In reply to Candice Serran (:cserran) from comment #12) > Given the decision on systems browser, is this still a blocker for 2.0? Yes, for the current browser.
Flags: needinfo?(pdolanjski)
With no other information, I'd mark this a duplicate once Bug 961687 is verified, since I was testing with URLs for the browser.
Assignee: nobody → dgarnerlee
Depends on: 961687
Whiteboard: [systemsfe] → [p=1], [systemsfe]
Target Milestone: --- → 2.0 S1 (9may)
Seems to be receiving fine right now with the recent string of fixes to ShriningUI. Marking as dup. Please reopen if this is not the case.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(s.x.veerapandian)
You need to log in before you can comment on or make changes to this bug.