If you publish to iPad using AIR 25, without any other changes, does it then work ok?
If it doesn't work with AIR 25 there may be a security issue in using local files. BTW, do you rely on hosted CreateJS library, or include that in the embedded files?
If it does work with AIR 25 that would point at WKWebView being the issue. I have used WKWebView using an ANE, and all the differences I saw compared to UIWebView were either improvements or bug fixes.
Thank you for the quick response.
Another thing is that we rely heavily on local storage to store and keep track of records locally. If WKWebkit clears all local storage when app exits out, then all web local storage data will be wiped out when app is re-launched again. This will make any user experience not traceable. It looks like a total redo of the HTML content files if we need to use wkwebkit from this point on.
Any insights what to do from this point forward?
I looked into this more and AIR26 still has issue to display HTML through StageWebView.
However, I found that a live URL (http://xxx.xx.com) displays fine through StageWebView, but not a html that is local to iOS (iPad in our case).
In searching for how html is loaded differently between wkWebKit and UIWebKit we came across this link that says wkwebview requires a complete file path (file:///) and not a relative file path - http://stackoverflow.com/questions/41134493/whats-the-difference-between-uiwebview-and-wkw ebview-when-loading-local-resourc
Both my files saved in documentsDirectory and applicationDirectory return the complete file path with "file:///" when I tried to load the HTML through stagewebvew.loadURL(local_html_file). The trace code does not display any error and returns that the load is complete, but the stagewebview displays nothing but a blank screen.
Here is the path name for the local index.html file - file:///var/containers/Bundle/Application/EC5A2106-7263-4202-B358-0F521B945503/Documents/ 1/index.html
Does someone run into the same issue and have any solution?
I saw the most recent release of AIR 26 lists this bug in the KNOWN ISSUES.
Is Adobe going to fix this issue? If yes do you have a time frame?
Thank you! I will look into this.