08-14-2012 04:22 AM
I've noticed a few day ago, that all WebWorks apps I had in my PlayBook stopped working!
I have two such apps installed: my application which I'm developing and debugging, and "Solitaire Free".
With no Internet connection, my app at startup shows the spash screen and then it freezes with a blank white page (bbui is supposed to load the start page so probably it never has a chance to do so).
The other app shows the splash screen and then a white page with a few texts (menu, buy, cancel, ...) but with no styling etc. Just white background and black text.
Restaring the device doesn't work, disablling web inspector in the browser settings doesn't work. There is no information on the web inspector console. My app works on the simulator with no Internet connection. I'm puzzled.
Has anyone had such a behaviour? How to fix it?
08-14-2012 05:54 AM
08-14-2012 08:20 AM
As I mentioned before, it's the lack of Internet connection that causes apps to stop working. As soon as I connect to the Internet, all webworks apps start to work again.
08-15-2012 02:47 PM
I have the same problem with my Webworks applications.
They work fine when connection is ON, but showing white or black screen without internet connection.
It worked fine before, so I suspect it is related to the recent playbook update 220.127.116.118
Does anyone have a solution for the problem?
08-15-2012 03:20 PM
I have also upgraded my PlayBook to 18.104.22.1688. This update isn't available anymore so maby it really had such a bug? Any help / comment is still greatly appreciated.
08-16-2012 06:14 AM - edited 08-16-2012 06:17 AM
My webworks app still functions properly on 22.214.171.1248, so maybe it is particular features you are using?
As for why this update was pulled: as far as I have heard it was pulled because of an issue upgrading from v1.0.7 nothing more. Not to say there weren't other bugs that could be causing problems for you.
08-17-2012 07:22 AM
All webworks apps stopped working, not just mine. So it looks more like a system issue.
This shouldn't be underestimated - it may happen to people that buy our apps.
08-17-2012 07:35 AM
FYI Some good news: RIM was able to reproduce the problem with the latest update and they are working on the fix.
We don't have timelines when it will be resolved.