[jcfarsight]

Just a quick query to check whether this is a known issue or not.

Ever since upgrading to 2.2.2 (just recently), I have noticed that any page transitions cause a TypeError on phoneui.js line 1235.
Coincidently I seem to be having new-found problems with code which worked fine before, and I am wondering if this is because the above error, appears to be part of a method called ‘runUserCode’

I have tried multiple transitions (SLIDE_LEFT, SLIDE_UP, FADE, DEFAULT) and they all throw the same error. The issue also occurs from calling the phoneUI.gotoPage method myself, as well as just choosing the ‘Go To Screen’ action in the Design Center.

Any possible ideas on the issue?

EDIT: Fixed in 2.2.3

[support-octavio]

Hi jcfarsight,

Our team conducted some preliminary research and our test cases passed. The line number you referenced can only be accessed if your pretransition function has an error. If you can share your project with us, we will dig in deeper to see if we missed something. You can either attach to thread or send it via support at genuitec dot com. Use title mobione data from jcfarsight

[jcfarsight]

Alright thanks, I have emailed the project to the above email address.

[support-octavio]

Hi jcfarsight,

I’ve tested your app and didn’t find the issue that you mentioned. Could you provide steps to replicate it?

[jcfarsight]

1) Open Home.mobi in the Design Center
2) Project->Run in Test Center
3) Once the application is running, Browser->Web Application
4) Copy the URL (with the query strings removed), and place it in a browser (I used Chrome)
5) Open up the console debugging screen (Ctrl->Shift->J in Chrome)

Expected output on refresh (warnings):
Resource interpreted…
Resource interpreted…
Resource interpreted…

6) Press any of the 5 buttons (login, sign up, browse…), the debug window now reports a TypeError which can be expanded etc.

[Tom Niehoff]

I believe the update put back in the m1- prefix… so it you previously removed that in your project everything breaks. As was the case for me atleast. Go into Settings –> Html Generation –> Prefix.

[jcfarsight]

Whew alright I finally discovered the problem, and it’s certainly a strange one, hopefully you can shed some light on it.

Adding a combobox control to any page, anywhere in the application will cause that error to throw during a transition. After digging around and isolating the problem, I discovered that removing the three comboboxes from the Pre_Browse page, causes the error to stop appearing.

Thinking that I had stuffed up the configuration somewhere, I tried just dropping a default one on the form, no changes. This once again started throwing the error.
No matter which form in the project the combobox is dropped on, it breaks.

Any ideas on a work-around?

PS. Cheers trn579s for the idea, I also looked into this, but I have always used the m1- prefix anyway so this wasn’t an issue.

[support-octavio]

Hi jcfarsight,

Thanks for sharing your files with us, they’ve been very helpful to find the issue. A fix is available on 2.2.3. Please update and let us know how it goes.

[Author]

Posts