Vaadin not working at all in Blackberry Playbook browser #1635

Open
vaadin-bot opened this Issue Jun 16, 2011 · 20 comments

Projects

None yet

1 participant

@vaadin-bot
Collaborator

Originally by Alberto


Web pages developed with Vaadin are not working at all in Blackberry Playbook (and by now are the only ones I have seen are not working. www.gwt-ext.com/demo is working properly for example)

When go to any web page developed with vaadin get the following error:

Widgetset does not contain implementation for null.Check its @ClientWidget mapping, widgetsets GWT module description file and recompile your widgetset. In case you have downloaded a Vaadin add-on package, you might want to refer to add-on instructions. Unrendered UIDL:

Then you get a tree with this kind of information:
1 id=PID1 height=100.0% width=100.0% margins=0 alignments={} expandRatios={PID16:1,}

.............


Imported from https://dev.vaadin.com/ issue #7189

@vaadin-bot
Collaborator

Originally by @Artur-


You could try adding "?debug" to the url and see if you can get any hints from the debug console.

@vaadin-bot
Collaborator

Originally by @Artur-


Just tested the BlackBerry Playbook Simulator using http://demo.vaadin.com/Calc and http://demo.vaadin.com/sampler without any problems.

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


just tested again and Vaadin isn't working.
This is a real SHOWSTOPPER.

I uploaded 3 screenshots from today at
http://ge.tt/8PEPcx6?c

@vaadin-bot
Collaborator

Originally by @Artur-


Replying to ekke@…:

just tested again and Vaadin isn't working.
This is a real SHOWSTOPPER.

I uploaded 3 screenshots from today at
http://ge.tt/8PEPcx6?c

Can this be reproduced without an actual Playbook (which I don't have)? As mentioned I have tested using the Playbook Simulator and there everything works fine.

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


hmmm just installed Simulator 1.0.6 and your samples are working and also our application. (of course we have still some work adding touch events....)

but using this from real devices it doesn't work as described above
tried from different locations with different PlayBooks

I also asked at BlackBerry Support Forums

@vaadin-bot
Collaborator

Originally by astanley


Hey folks, Adam here from BlackBerry Developer Relations. I can confirm that on Tablet OS v1.0.7 (current in-market OS release), the following error is being displayed for the "Calc" app listed above :

"Widgetset does not contain implementation for null. Check its @ClientWidget mapping, widgetsets GWT module description file and re-compile your widgetset. In case you have downloaded a vaadin add-on package, you might want to refer to add-on instructions. Unrendered UIDL:"

This suggests the Vaadin framework is not able to render the page for this version of the Tablet OS and an error is occurring before any page rendering even occurs. Vaadin - can you confirm the cause of the above error?

I suspect a behavior that Vaadin depends on might have changed between 1.0.6 and 1.0.7. Lets try and identify what the dependency is (need to have the Vaadin folks look into the root cause of the error message above) and then we can confirm whether any behaviors have in fact changed (or whether a bug was introduced in 1.0.7 that can be resolved).

If there is in fact a Tablet OS bug, please file any issues here:
https://www.blackberry.com/jira/secure/Dashboard.jspa

Best,
Adam Stanley

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


hi adam,
thanks jumping into this....
the problem is the folks at Vaadin don't have a PlayBook device -
and using latest Simulator 1.0.6 it works well.
so the problem is how they should know what goes wrong ?

for me the dilemma is, that our software (Open Source project redVoodo.org) depends on Vaadin
and Vaadin runs well in browser, 1.0.6 Simulator, iPad and iPad2
but I have to make an offer for a business software project for a company from canada ;-) where Vaadin / redVoodo is used for web-application running on PlayBook
together with BlackBerry OS 6 SmartPhones Java Applications and I cannot demonstrate the Vaadin-based software on PlayBook :(

perhaps there is a way for RIM to provide a PlayBook for Vaadin team

ekke

@vaadin-bot
Collaborator

Originally by @Artur-


The message "Widgetset does not contain implementation for null." indicates that there is a problem with parsing the JSON data returned by the initial XHR request. Scrolling down in the debug window might give some clue, should contain something like

Making UIDL Request with params: init
Server visit took 121ms
JSON parsing took 0ms
[-] change format=uidl pid=PID0
	[+] com.vaadin.terminal.gwt.client.ui.VWindow id=PID0 height=891px width=1680px caption=Calculator Application name=1 theme= resizable=true main=true
	[+] variables
	[+] com.vaadin.terminal.gwt.client.ui.VGridLayout

Still I have no good guess on what could go wrong without a way to reproduce it. Is there a new version of the simulator coming up where this could be reproduced?

Of course if somebody wants to send us a Playbook device we will be happy to test on that.

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


hi artur,
wasn't easy to expand and copy from the debug window on PlayBook, but here's the beginning. perhaps it helps you

Widgetset does not contain implementation for null. Check its @ClientWidget mapping, widgetsets GWT module description file and re-compile your widgetset. In case you have downloaded a vaadin add-on package, you might want to refer to add-on instructions. Unrendered UIDL:

	1 id=PID321 height=100.0% width=100.0% margins=0 alignments={} expandRatios={PID336:1,}
	2 id=PID322 height=44px width=100.0% style=topbar margins=2 spacing=true alignments={PID329:33,PID323:33,PID330:33,PID324:33,PID333:33,} expandRatios={PID324:1,}
	3 id=PID323 style=link logo caption= description=↶ Home
	variables
state=false
	4 id=PID324 width=100.0% style=breadcrumbs
	2 id=PID325 margins=0 spacing=true alignments={} expandRatios={}
	5 id=PID326 caption=Home src=#
	variables
activated=false
opened=false
	6 id=PID327 trackerid=UA-658457-6 domain=none
	7 id=PID328 immediate=true
	variables
fragment=
8 id=PID329 width=32px style=theme-select immediate=true description=Select Theme pagelength=10 filteringmode=2 totalitems=2 totalMatches=2
	variables
selected=1
filter=
page=0
	options
	so icon=theme://../sampler/sampler/select-bullet.png caption=Reindeer theme key=1 selected=true
	so icon=theme://../sampler/sampler/icon-empty.png caption=Runo theme key=2
	2 id=PID330 style=segment margins=0 alignments={} expandRatios={}
	9 id=PID331 style=quickjump description=Quick jump html=<span></span> hideOnMouseOut=true
	variables
popupVisibility=false
	3 id=PID332 style=tree-switch down description=Toggle sample tree visibility
	variables
state=false
	2 id=PID333 style=segment margins=0 alignments={} expandRatios={}
	3 id=PID334 style=previous disabled=true caption= description=Jump to the previous sample
	variables
state=false
	3 id=PID335 style=next caption= description=Jump to the next sample
	variables
state=false

 	10 id=PID336 height=100.0% width=100.0% style=main-split margins=0 position=250px reversed=false
	11 id=PID337 margins=0
	5 id=PID338 caption=All Samples src=#
	12 id=PID339 style=menu immediate=true selectmode=single nullselect=true
	variables
selected=
expand=
collapse=
newitem=
	node caption=UI Basics key=1 expanded=true
	leaf caption=Tooltips key=2
	leaf caption=Icons key=3
	leaf caption=Runo theme icons key=4
	leaf caption=Error indicator key=5
	leaf caption=Progress indication key=6
	leaf caption=JavaScript API key=7
	leaf caption=Browser information key=8
	node caption=Buttons key=9 expanded=true
	leaf caption=Push button key=10
	leaf caption=Link button key=11
	leaf caption=Checkbox key=12

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


just tested with 1.0.7.2942 from today: same problems as before

@vaadin-bot
Collaborator

Originally by @Artur-


A small HTML test that could show the problem: http://artur.virtuallypreinstalled.com/vaadinjson.html (imitates the JSON parsing that takes place in Vaadin in the HelloWorld example)

Please compare the output from a browser (e.g. Chrome) and a Playbook. I suspect the typeMapping (last part) is the problem.

@vaadin-bot
Collaborator

Originally by ekke@ekkes-corner.org


Artur,
thanx for testing these isuues.
I tried your site on Chrome (OSX), PlayBook Simulator 1.0.6 and real PlayBook device 1.0.7
for me it looks ok
uploaded screenshots here: [http://ge.tt/8PEPcx6]
ekke

@vaadin-bot
Collaborator

Originally by Adun


Attachment added: IMG_00000024.jpg (72.5 KiB)
IMG_00000024.jpg
https://trac-attachments.vaadin.com/trac/7189/IMG_00000024.jpg
Vaadin Calc

@vaadin-bot
Collaborator

Originally by Adun


As you can see, the problem persists. I checked 6 months ago, checked today, and still the same (PlayBook OS 1.08 now, real device).

@vaadin-bot
Collaborator

Originally by Adun


Attachment added: IMG_00000025.jpg (95.7 KiB)
IMG_00000025.jpg
https://trac-attachments.vaadin.com/trac/7189/IMG_00000025.jpg
Vaadin Sampler on PlayBook OS 1.08

@vaadin-bot
Collaborator

Originally by @Artur-


Tried with the latest Playbook Simulator (1.0.8) - everything still works fine using that... One way to debug it seems to be using the "web inspector" which allows you to open another tab and see the Javascript console etc. Maybe there is an error message that could give a hint what is going on?

@vaadin-bot
Collaborator

Originally by mortcj@gmail.com


We are experiencing a similar problem with a blackberry phone. It appears that a blackberry running OS 6 can open the Vaadin sampler and OS 7 cannot. Is there a mapping of the user agent string that needs to be updated?

@vaadin-bot
Collaborator

Originally by @Artur-


Replying to mortcj@…:

We are experiencing a similar problem with a blackberry phone. It appears that a blackberry running OS 6 can open the Vaadin sampler and OS 7 cannot. Is there a mapping of the user agent string that needs to be updated?
More likely something that has change in Blackberry OS 7. There are no special cases for Blackberry in Vaadin

@vaadin-bot
Collaborator

Originally by alberto


Good news!!

It's working on Playbook version 2.0 !!

Regarding BB OS7 I'm afraid is not, I'm afraid a similar error is obtained when trying to see the webpage.

@vaadin-bot
Collaborator

Originally by Adun


I can confirm that Vaadin 6.7.6 works fine now on PlayBook 2.0. (same old device with upgraded firmware). Also dontpush-ozone works fine.

@vaadin-bot vaadin-bot added the bug label Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment