Created attachment 796477 [details] screenshot for error User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0) Steps to reproduce: 1. import Facebook contacts. 2. select a facebook contact and click the "message" button. Actual results: 1. It displays that the contact is not exitsed(see in attachment). Expected results: 1. go to the UI of edit message.
Related to bug 907740
Severity: normal → blocker
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Priority: -- → P2
Resolution: --- → WONTFIX
This is a bug, if the Facebook message feature is not support, is it better to remove this feature? Thanks!
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Status: UNCONFIRMED → ASSIGNED
blocking-b2g: hd? → leo?
Ever confirmed: true
QA Contact: jmcf
I can conform this is happening now. We were implementing this feature using a hack that has stopped working. The problem is that Facdebook still is not supporting the send message dialog on mobile. We are going to get in touch with Facebook in order to try to find a solution or other workaround.
Ni? Harald as he may have some insight on our communications with Facebook about this. Harald, please remove the flag or reassign as appropriate.
I have just sent a private email to Harald attaching the email sent to Facebook yesterday. thanks
Awaiting Herald's comment to proceed here.
Whiteboard: [NPOTB] → NPTB
Summary: [B2G][Helix][Contacts][wangchao]When click "message" button for facebook a contact, it prompt this contact is not existed. → [B2G][Contacts]When click "message" button for facebook a contact, it prompt this contact is not existed.
leo plus as regression issue and user impact seems high
blocking-b2g: leo? → leo+
Facebook is contacted and escalating. Last contact was today.
Harald, SO this is not an issue any more?
it is still an issue, until FB announces they have an alternative URL ready for sending messages. When that is ready we will have to submit a small patch in order to tweak our app to comply with the new URL used for sending messages. So this bug has to remain open
Minus for now. Please re-nom once the FB announcement is done.
blocking-b2g: leo+ → -
Comment on attachment 812991 [details] 12604.html Thanks a lot
Attachment #812991 - Flags: review?(crdlc) → review+
https://github.com/mozilla-b2g/gaia/commit/d1deec8d52ce46f95cf398b333926e5cbf7ae0b0 This should be leo+ at least and for sure go to koi as well. thanks
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago → 5 years ago
Resolution: --- → FIXED
status-b2g18: --- → affected
status-b2g-v1.2: --- → affected
Dear Jose, Because it's carrier blocking issue, can you land the patch to V1 train ASAP?
Hi, John Ford is responsible for uplifting. thanks
Flags: needinfo?(jmcf) → needinfo?(jhford)
(In reply to Jack Liu from comment #18) > Dear Jose, > > Because it's carrier blocking issue, can you land the patch to V1 train ASAP? We need a leo+ to grant the ability to land on v1-train. Let me followup with release management over email to get someone to triage this bug as soon as possible.
This is a hard blocker for Facebook that prevent sending a message to the Facebook contact.
blocking-b2g: leo? → leo+
[v1.2 3a57f63] [v1-train 680f3b8]
status-b2g-v1.1hd: --- → fixed
status-b2g18: affected → fixed
status-b2g-v1.2: affected → fixed
You need to log in before you can comment on or make changes to this bug.