[gwana]

MobiOne is ok, but I have found it to be Extremely Buggy. For example, I am trying to render out multiple screens, and after I render on screen, the buttons on other screens stop working. So, I re-render those screens, then the first screens buttons stop working. Very strange and I have explored all that I know about code and can’t seem to find the problem.

[support-michael]

@gwana
Sorry to hear there is glitch in your progress with MobiOne. I would need to know more about your UI design, how you’ve linked your pages and then rendered them. I have not see buttons stop working since they are backed by simple html/javascript. Let me throw down a quick scenario and see if it applies to your app:

Let’s say I want to create an app with 3 pages linked as follows: A -> B -> C. Pages B & C have a navbar with a back button. MobiOne supports running any page, A, B or C. But to fully test your app you should concentrate on either running A or exporting the code for A. By doing this, MobiOne will follow the links from A->B and then B->C when it generates code. Also you may want to disable offline support early in development since it can sometimes cause pages to be cached in the Test Center or on your device.

Lastly if you would like to share more details you can send me your design files (.mobi) and your app resources (images, custom js, …. or a link) and I’ll try to investigate it further. Send to support at genuitec dot com with title “MobiOne support resource for wayne”

[Author]

Posts