02-04-2011 05:14 PM
Just took out from another thread. Let's discuss it here.
02-04-2011 05:40 PM
I hate to say it RIM, but it's not cool at all that you're excluding < 5.0.0 (you really had to use BrowserField2, did you), since our app builds on 4.5.0, you're leaving out most of the install base right there. Is there any way you can merge the critical redirect fixes made in 0.3.1 back into 0.2.0 to maintain legacy compatibility with BF1?
02-04-2011 07:34 PM
So, I checked out the sdk. Tried to register via OAuth 2.0 protocol and it did work fine.
We are implementing FB connection in our app now, so this new SDK is really a big present)))
the previous one (v 0.2) used old authorization way and was a kind of glitch.
02-05-2011 03:45 AM
blackberry sdk 0.3.1 getting classcast exception please help
uncaught exception java.lang.ClassCastException
and the debuuging stops at
fbc = (FacebookContext) store.getContents(); in strawberry.java
please any one solve it as soon as possible
i did not get what is store and persist.
i have downloaded the file from sourceforge and i did not modified any thing in the folder.
02-05-2011 09:12 AM
I've run the test app called 'Strawberry' and it works just fine for me. What i suggest is to clean simulator and ensure you do not have any other strawberry app from the previous sdk if any.
02-05-2011 10:56 PM
There are a couple of reasons why we are not supporting pre-5.0 devices in this release.
First of all, the BrowserContent which is used in pre-5.0 devices are not able to handle cookies correctly. It also has redirection problem for the oauth 2.0 login mechanism. In addition, some CSS are not rendered properly too, so the pages look extremely ugly.
Most importantly, we think that this is a good time for us to move forward and fade out the support of pre-5.0 devices, because according to app world download figures (Nov-2010), 75% of all downloads are from devices with 5.0 or above.
02-06-2011 05:19 AM
For all those developing for 6.0, I would recommend adding the following line to the BrowserScreen constructor:
This is because the 6.0 BrowserField does not seem to render a pointer by default, and a pointer will be necessary to interact with some of the web components such as the login button.
I have also found that the new 6.0 webkit browser does not seem to respect the extent of the screen that contains it. The BrowserField uses the display width as its extent rather than the screen width. Display width and screen width are not the same if you try to render the BrowserField within a PopupScreen. I tried setting the viewport width via the VIEWPORT_WIDTH property and it had no effect.
Also, every talladega sim I've been able to get my hands on has serious issues with the BrowserField. There's something very odd going on with this component that prevents the login process from working at all (login page never loads). I'll post here when I figure out the cause.
David perhaps you could comment on these issues?
02-06-2011 01:39 PM