Closed Bug 867357 Opened 12 years ago Closed 12 years ago

Can't upload a media file on m.facebook.com on FF OS

Categories

(Tech Evangelism Graveyard :: Preinstalled B2G Apps, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED FIXED
blocking-b2g -

People

(Reporter: jsmith, Assigned: hsteen)

References

Details

(Whiteboard: [apps watch list1] [3rd Party] [TD-18873] [NPOTB] khepera_43556)

Same bug as bug 709742, but for FF OS specifically.
Blocks: 759986
Hello, Is it ok for b2g?
Whiteboard: [apps watch list]
Whiteboard: [apps watch list] → [apps watch list1]
Whiteboard: [apps watch list1] → [apps watch list]
Blocks: b2g-facebook
Assignee: nobody → hkirschner
Andrew - Please retest this one. Bug 709742 is closed - should this also be closed?
Flags: needinfo?(awilliamson)
(In reply to kward@mozilla.com from comment #2) > Andrew - Please retest this one. Bug 709742 is closed - should this also be > closed? This is the website, right? Not the app?
Flags: needinfo?(awilliamson)
Flags: needinfo?(kward)
(In reply to kward@mozilla.com from comment #2) > Andrew - Please retest this one. Bug 709742 is closed - should this also be > closed? bug 709742 was closed because the issue no longer reproduces on FxAndroid. It didn't work on FF OS, so we opened this bug to track the FF OS work. (In reply to Andrew Williamson [:eviljeff] from comment #3) > (In reply to kward@mozilla.com from comment #2) > > Andrew - Please retest this one. Bug 709742 is closed - should this also be > > closed? > > This is the website, right? Not the app? Remember - the mobile site is the app pretty much (outside of adding the manifest data). You should be able to test this as well with the Twitter web app as well.
Flags: needinfo?(kward)
Whiteboard: [apps watch list] → [apps watch list] [3rd Party] [TD-18873]
Any update on this?
Flags: needinfo?(jsmith)
(In reply to Leo from comment #6) > Any update on this? Harald is driving the communication on this, so I'm redirecting the needinfo request to him.
Flags: needinfo?(jsmith) → needinfo?(hkirschner)
Leo is claiming this is preinstalled apps 1.1 blocker. Noming as such as NPOTB blocker.
blocking-b2g: --- → leo?
Whiteboard: [apps watch list] [3rd Party] [TD-18873] → [apps watch list] [3rd Party] [TD-18873] [NPOTB]
(In reply to Jason Smith [:jsmith] from comment #8) > Leo is claiming this is preinstalled apps 1.1 blocker. Noming as such as > NPOTB blocker. Actually, I'll let leo do the noming here.
blocking-b2g: leo? → ---
Whiteboard: [apps watch list] [3rd Party] [TD-18873] [NPOTB] → [apps watch list1] [3rd Party] [TD-18873] [NPOTB]
Internal task at FB was very recently closed as fixed. Can you confirm?
Component: Mobile → Preinstalled B2G Apps
(In reply to Tobie Langel from comment #10) > Internal task at FB was very recently closed as fixed. Can you confirm? Not working for me on yesterday's unagi build. I'm still seeing: Sorry, the browser you're using doesn't support posting photos.
I'd guess WURFL is still saying that 1.1 can't upload files? Lawrence, is WURFL up to date with the additions in 1.1?
Flags: needinfo?(hkirschner) → needinfo?(lmandel)
I have not yet made any request from WURFL. I'm waiting on the list of items that we need to request as per bug 873385. Can you tell me which WURFL property/value needs to be updated to fix this issue?
Flags: needinfo?(lmandel) → needinfo?(hkirschner)
We have the WURFL list from FB and will work with FB and WURFL to get the values updated for the 1.1. UA.
Flags: needinfo?(hkirschner)
Hi Hallvord, The resolution of this bug is critical for LG V1.1 device preloads. Can you give an estimated completion date? We need this as soon as possible.
Assignee: hkirschner → hsteen
As I understand this issue, the fix will be in WURFL's db and on Facebook's server side. As this is not a fix that needs to be applied on device, we have more time to get the fix into production. Am I missing a closer milestone that needs to be hit?
(In reply to Lawrence Mandel [:lmandel] from comment #16) > As I understand this issue, the fix will be in WURFL's db and on Facebook's > server side. As this is not a fix that needs to be applied on device, we > have more time to get the fix into production. Am I missing a closer > milestone that needs to be hit? We don't have that much time. Any app part of the grid as a preinstalled app has to meet a certain quality bar by a target date. If that quality bar isn't met, then the app gets pulled. To my understanding, the timeline for resolving grid-based apps for 1.1 is extremely low on time - Karen would have the exact date of when this needs to be resolved by.
If they support this the same way on FF Android (input[type="file"]) that you support of b2g, we could useragent spoof?
Karen - Can you please share the required date so that we know how much runway we have? (In reply to Wesley Johnston (:wesj) from comment #18) > If they support this the same way on FF Android (input[type="file"]) that > you support of b2g, we could useragent spoof? AFAIK, this is not an option. Spoofing the UA in this way will revert to Facebook displaying Android app promotions on B2G.
Reply from Facebook as to the required WURFL property/value. xhtml_file_upload is used to determine whether photo uploading is possible. The expected value of this capability is "supported" if the device + browser do support file uploading.
(In reply to Lawrence Mandel [:lmandel] from comment #19) > Karen - Can you please share the required date so that we know how much > runway we have? > > (In reply to Wesley Johnston (:wesj) from comment #18) > > If they support this the same way on FF Android (input[type="file"]) that > > you support of b2g, we could useragent spoof? > > AFAIK, this is not an option. Spoofing the UA in this way will revert to > Facebook displaying Android app promotions on B2G. Regarding the date - LG wanted this fix before their IOT #1 that started on Aug 5. It ends August 23. How much longer is needed?
I have confirmed with WURFL that they will deploy the required update in the next few weeks. Unfortunately, I don't have a specific date.
Just tested on a leo with a 0721 vendor build and it worked. Does someone else want to confirm this in case i wasnt doing it right? Then we can WFM this bug.
Dear Mozilla colleagues, mark leo? since this feature is important to user.
blocking-b2g: --- → leo?
Based on Wayne's note, it looks to be working properly. Once confirmed, resolve the bug.
blocking-b2g: leo? → -
Testing today using latest leo build(V10a) provided by partner, click on "Photo" menu, inside FB application, the message displayed by the app is: "Sorry, the browser you are using doesnt support posting photos...." You cannot attach either a picture to your status. Renominating as it is important feature for end customers.
blocking-b2g: - → leo?
AFAIK, this bug relies upon an update to WURFL and an update to Facebook, both third parties. WURFL has already confirmed that they will be updating their db with the information required for this bug "in the next few weeks" (from Aug 14). Once WURFL updates, we can inform Facebook that they can pick up the update.
This is a tech evangelism issue, which we can't block on.
blocking-b2g: leo? → -
Severity: normal → critical
Priority: -- → P1
Whiteboard: [apps watch list1] [3rd Party] [TD-18873] [NPOTB] → [apps watch list1] [3rd Party] [TD-18873] [NPOTB] khepera_43556
Blocks: 916311
No longer blocks: 916311
Any news about WURFL update?
Flags: needinfo?(hsteen)
All we know AFAIK is what Lawrence said in https://bugzilla.mozilla.org/show_bug.cgi?id=873385#c33 - ETA is approximately september 23rd according to him.
Flags: needinfo?(hsteen)
Status: NEW → ASSIGNED
Lawrence or Hallvord, can you confirm that file upload is not properly detected by WURFL for 1.1 and 1.1hd devices?
Flags: needinfo?(lmandel)
Flags: needinfo?(hsteen)
I can confirm that file upload was previously marked as unsupported for Firefox OS by WURFL. File upload will be marked as supported for Firefox OS 1.1 once WURFL releases their next update. FYI, Mike Taylor is responsible for UA detection issues going forward (although Hallvord did work on the 1.1 update for WURFL.)
Flags: needinfo?(lmandel)
Flags: needinfo?(hsteen)
Thanks Lawrence. Can we confirm from them 100% this will be implemented? It looks like it slipped from mid-aug to sep 23 and now next week so we can't afford any more slips because this would be a disaster..?
The current version for a 1.1 UA [1] yields "xhtml_file_upload" supported. I will doublecheck with FB after I confirmed the Helix UA. [1]: http://www.tera-wurfl.com/explore/index.php?ua=Mozilla%2F5.0+%28Mobile%3B+rv%3A18.1%29+Gecko%2F18.1+Firefox%2F18.1&search=Lookup+User+Agent
FB is notified.
Thanks Harald - what does that mean? Do we need to help apply pressure to FB from our end. We are meeting them next week and they want to do MORE with Telefonica so we have some leverage? WHere is the bottle neck now - WUFRL or FB?
WURFL is returning the right value, so they are finally out of the equation. It is only FB now, which makes things a lot easier. So far FB have just been made aware of this bug. If their reply takes longer I will definitely escalate. We have a few more contacts at FB we can pull into this. I'll update this bug when I have more details. Bringing that topic up in the FB meeting wouldn't hurt anyways, to generally get higher priority on Firefox OS specific bugs.
Thanks Harald. Let us know how we can help.
Our FB liaison identified the issue and should have a fix in production by tomorrow or Wednesday. I will update the bug when I have a final confirmation.
Harald, any progress with this bug? Is it close to be solved? thanks!!
Confirmed as working for me now. FB pushes can have a time difference between clusters/regions. Please re-open if this isn't fixed for you.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Confirmed it is working for me as well in vendor build based in v1.1 ikura device. Thanks!
Just tested and also working in my ikura, great!
Confirmed ability to upload photo on a ZTE device with build 20130828 OS v1.1 Leaving bug as resolved.
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.