Closed Bug 1383250 Opened 7 years ago Closed 7 years ago

Didn't receive visual notification after sending Desktop to iOS

Categories

(Firefox for iOS :: Sync, defect, P2)

Other
iOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
fxios 9.0 ---

People

(Reporter: ckarlof, Unassigned)

Details

(Whiteboard: [MobileCore][AutoPush])

iOS Beta build 4530. If I open the app *sometimes* it will have loaded the tab (other times, I had to kill it, restart, and force a sync), but I never received a visual notification after sending it.
Build 4530 is really old and a lot of bugs have been fixed around push notifications since. We will try to send out a new build on the Beta channel soon to get Beta users updated.
Marking this as WORKSFORME. Please re-open if this happens in recent builds.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Still no notification on 4826. The experience is really uneven for me. I don't get a notification, and I have to open and close Firefox Beta a few times until it loads the sent tab, but it just sort of feels it's restoring a tab and doesn't give me any feedback that it's the one that was received.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Priority: -- → P2
Whiteboard: [MobileCore][AutoPush]
Catalin, Is this still something that happens?
Flags: needinfo?(catalin.suciu)
Hey Chris, is it possible for you to have the Firefox notifications turned off on your device? 
In this case you will receive the tabs through sync, not push, therefore you will not see any push notifications.

  
I wasn't able to reproduce this issue on v9.0(5725)
Flags: needinfo?(catalin.suciu) → needinfo?(ckarlof)
Whiteboard: [MobileCore][AutoPush] → [MobileCore][AutoPush][needsuplift]
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [MobileCore][AutoPush][needsuplift] → [MobileCore][AutoPush]
I still have this problem, but maybe I'll debug with Stefan in person when I go to TOR in late Sept.
Flags: needinfo?(ckarlof)
You need to log in before you can comment on or make changes to this bug.