Closed
Bug 1064917
Opened 10 years ago
Closed 10 years ago
[Facebook] Poke a new friend it's not possible without logging out
Categories
(Tech Evangelism Graveyard :: Preinstalled B2G Apps, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joseenrique.alvarezfernandez, Assigned: mellis)
References
Details
When a new contact becomes friend within a session, the search box in Pokes is unable to find that contact, even after refreshing the page, so there is no way to send the poke. Only after logging out and logging in again the new friend is available in the Pokes search box.
Updated•10 years ago
|
Assignee: colby → hkirschner
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•10 years ago
|
||
Per Facebookβs req: Open bugs should be forwarded to Fbβs new internal bug tracking system. Following their guidelines, all current unassigned bugs will be placed into a single spreadsheet and sent over to Fbβs new system. Michael Ellis will be the assignee for these bugs and will update each as feedback is received from Fb.
Assignee: hkirschner → mellis
Assignee | ||
Comment 2•10 years ago
|
||
Unable to replicate this issue on iOS, Android, or Desktop. Without replication on another platform we will have a hard time getting FB resources to look at this. Perhaps we are looking at a device/build specific issue.
Flags: needinfo?(adora)
Reporter | ||
Comment 3•10 years ago
|
||
HI Michael It was tested on different devices and builds and it was happening in all of them. However, Facebook has made a major update on their app. And so far, the Poke feature now seems to work fine Going to test in other devices before closing this bug
Reporter | ||
Comment 4•10 years ago
|
||
Hi again Tested on ZTE OPEN C with v1.3 and works. I'm going to close the bug but will keep testing and reopen it if necessary
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Flags: needinfo?(adora)
Updated•6 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•