Page 1 of 1

Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Wed Nov 25, 2015 1:15 am
by Bruce Stuart

I have converted an App to the 3.0 libraries.

Numerous challenges.

Specific to this post - which causes some ODD behavior in the UI I consistently get this message (even though I have not Opened an IAB):

2015-11-24 17:05:01.418 SmartDart[8629:156432] Resetting plugins due to page load.
2015-11-24 17:05:01.419 SmartDart[8629:156432] IAB.close() called but it was already closed.

These errors are consistently appearing in the console - and the app behaves immensely different in IOS that it does in test mode - on the browser.

Can you help?

Best,
Bruce


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Wed Nov 25, 2015 1:28 am
by Bruce Stuart

Ps. - I am using xCode V7.1.1 (most current). And the most troubling issue is not the IAB issue (alhtough that in and of itself is a problem ) - the message about resetting plugins due to page load - IS likely a problem.


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Wed Nov 25, 2015 12:28 pm
by Serhii Kulibaba

Hello Bruce,

Does it work after exporting from the Appery.io?


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Wed Nov 25, 2015 2:47 pm
by Bruce Stuart

The app consistently displays half or broken pages upon export and works irregularly ... So no it does not work. By the way ... The log events I am reporting to you here are from the IOS Xcode debug window ... Not the browser where it works fine. Bottom line the app breaks on the device and on the IOS simulator it breaks ... Browser it's fine .


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Sat Nov 28, 2015 5:45 am
by Illya Stepanov

Hi Bruce -

Is this app is shared with us? If yes, please specify its name.


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Sun Nov 29, 2015 2:16 am
by Bruce Stuart

Hello Illya - yes - the application is shared - the name is 'SmartDart'.

The techs (Yurii ?) will need to export the app to xCode - and then view the console when it starts. You can use the login credentials bstuart3780 and the password 'codehead'.

Please ensure the build number is set to 160 when running in the debugger, launch the app, login as specified about - and then watch the log. The geo-location plugin is loaded in the background at startup - however , with or without this plugin running (you can disable it) - you still get the instability of the the 2 following errors which - when running on the device - cause the app to crash.

The errors are :

  1. Resetting plugins due to page load

  2. Failed to load webpage with error: a server with the specified hostname could not be found

    Screen prints from my xCode session below:


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Sun Nov 29, 2015 2:33 am
by Bruce Stuart

i can also add someone to my beta list - where you can view the errors.

Here is the screen print of the log coming out of the IOS xCode debugger - note the Failed to load Webpage error immediately in the log after the resetting plugins due to page load (when the app navigates pages to page_pay). Which is then followed in the log by the Failed to load webpage with error ....

In xcode this happens with an error in the console - on the device - the app trys to Navigate to an external webpage - AppName.com and 'dies' a terrible death.

Here are the images - first - xcode - second - the navigation attempt from the device:

Image

Image


Version 3.0 Libraries - build on IOS (Via xCode) Persistent page load issue

Posted: Wed Dec 02, 2015 6:50 am
by Bruce Stuart

this issue - is fixed by fixing all the calls - when changing pages - to Appery.navigateTo('page_name' , { array of other parameters on transition and reverse effects })

you can mark this as resolved.... unless of course you want to do the right thing - and update the documentation on this function - to mention that under 3.0 libraries and forward - the second parm is mandatory.