07-12-2012 12:09 PM
Code is not supported by RIM. Correct for BB SDK library. But it's not their issue
Before FB will change their auth page almost noone on BB could use FB authorization.
07-12-2012 03:56 PM
07-13-2012 03:41 AM
Unfortunately 8520 with latest OS doesn't work with this approach.
To give a fix at least for some device. Add this lines in BrowserScreen constructor:
bfc.setProperty(BrowserFieldConfig.ENABLE_COOKIES, Boolean.TRUE); bfc.setProperty(BrowserFieldConfig.USER_AGENT, "Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16");
07-16-2012 06:29 AM
This really reflects NEGATIVELY on RIM. What's the use of all this PR when something so ESSENTIAL goes unnoticed!?
It is not flattering either for RIM that they are ignored like this by Facebook!!
When we noticed that the Facebook SDK was not reliable (a while back) we went another route - I don't claim that this was or was not a wise choice. We externalized the entire FB OAuth process to "browserSession.displayPage(.." where browserSession is a BrowserSession object. In other words, we launched the browser outside of our application (and if you're wondering what we do to get back to the app the answer is we used BrowserContentProvider). Things worked fine.
That is until Facebook introduced this most recent change - when it disabled content type = wap. So it is NOT AN APPLICATION ISSUE. It is a Blackberry Browser/Facebook issue. And one would think that RIM is on top of it!?!
We were just about to launch after a very lengthy development process. But I am not sure now whether I should be happy or sad that this occurred at this time. In any case, it really leads me to question if we are doing the right thing by insisting on publishing a Blackberry version of our app - in addition to the IPhone version we already published and instead of Android!
Some body needs to wake RIM up.. This issue implies that BB apps cannot integrate with FB - in this day and age this is a cause for real concern!
Now. Here's my question. Would this be the correct way to implement the suggested workaround? I tried it but thus far does not seem to work:
HttpHeaders headers = new HttpHeaders();
"Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16");
07-16-2012 07:51 AM
Hey! Nice to see you in my boat.
Unfortunately nor RIM, not Facebook didn't react as expected.
The current issue blocks all thirdparty apps that are using FB authorization.
About your question. You could try, but because there are several redirections I don't know how browser will behave.
We are showing BrowserField inside application, so we could control it much better.
07-16-2012 07:52 AM
Also could you flag FB issue as reproduced. I hope it will give more attention from FB side.
07-16-2012 11:27 AM
Thanks for the clarification. I will also try to flag the issue hoping that someone will notice.
How ironic, though, that BB developers are trying to disguise their work as an IPhone to get by!?!