We are waiting for QA to finish on the updated crosswalk 10 before updating the build system. You can watch for an update here: https://twitter.com/intel_xdk.

Several people have reported that rebuilding/rebsubmitting with stable (crosswalk 7) gets rid of the warning. We haven't changed anything so I don't know why that works, but it is harmless to try. Crosswalk 7 does not have the webstorage problem.

Where can I check to see when this webstorage issue is resolved?

The link below it says it has been resolved, but I'm guessing that doesn't apply to the end user exporting with IntelXDK?

https://crosswalk-project.org/jira/browse/XWALK-3252

I really want to update my app. For now can I use either Stable or Beta crosswalk build to bypass the webstorage bug?

You can track the WebStorage issue here: https://crosswalk-project.org/jira/browse/XWALK-3252

Just tested the beta build, xwalk 10. Good news, it works, Star Nomad loads fine and runs a bit faster.

BAD NEWS. WebStorage LocalValue is reset. The old saved-game based on WebStorage is deleted, starting afresh.

Xwalk 10 must have changed the way it handles localhost, because by default, WebStorage saves the app data based on the current localhost IP & port, something like 10.0.0.7:50000 (or thereabouts). When that IP/port is changed, WebStorage cannot retrieve saved app data and thus builds a new empty one under the new IP/Port.

I can't update Star Nomad Elite since Xwalk7/8/9 has the security glitch and 8/9 (bug) doesn't load big games with lots of images.

Phuck me. /facepalm

Edit: Stable (7) remains fine for function, but still triggers security alert from Google.

Stable is using crosswalk 7, which has an SSL version that can trigger the message.

I just republished an app with the latest update and the warning has gone, but I had also done the SSL reinstall that some people suggested, and I used Crosswalk stable version..

The build is done on our servers, we install the Android SDK, Crosswalk SDK, etc there. Updating the OpenSSL on your laptop is good to do, but should not affect how the APK is built. My guess is that google play is tweaking their scanning logic and the new apk gets rescanned and gets a different answer. It's a good idea to rebuild with Crosswalk 10, retest, and resubmit, even if you are not getting a warning right now.

I have no idea how the Intel XDK is working, but it maybe using files on your computer to assist in the build, so updating those helps. It maybe that when Intel XDK is updated this has the same effect as updating now with the links I have used.

It maybe none of the above and it might all be magic, but I suggest updating and trying to see if it works for you as it has resolved the issues for me. If this changes to being broken again in the future I will let you know.

Either way looks like it will be fixed if Intel are working on it too.

Oh and you dont need to use Cygwin I just installed that way which gave me the OpenSSL update. You can use the other link

We believe rebuilding with crosswalk 10 and republishing will remove the warning:

Robert

Beta build in XDK has been updated to crosswalk 10. We believe that rebuilding and republishing will eliminate the warning from google play. Go to the project tab, build settings, android-crosswalk tab. Under crosswalk version enter beta. Then go to the build tab, say yes when it asks you to upload, then build. Please retest your app thoroughly before publishing

Potential security vulnerabilities with open OpenSSL are present if you use an older version of the library. We are aware of this issue in Crosswalk versions 7 through 9.

We will notify you as soon as we have a remedy.

Yes, we wanted to make it more secure.

Since the update to 1621, we have to log in to download our APK's??

Yes. Blacklist is disabled.

IntelRobert

I haven't been following this thread lately, but has the WebGL mode blacklist been disabled?

GeometriX

I only tested the properties setting for the project.

A user has reported that when they use the landscape plugin and admob together, they don't see banner ads on ios8 devices. We are investigating.

We are waiting for crosswalk 9 to be promoted to stable. Expected next week and then a little more time for us to put it on the build system and test.

> —

>

> Crosswalk 9 has the patches for the cordova vulnerability. It also has the fix for having too many images problem, which you were seeing on crosswalk 8,

>

>

I've updated to the most recent XDK, build with Beta Crosswalk and it's still stuck on loading bar, so I'm assuming the latest beta is Crosswalk 8.

So Crosswalk 9 in XDK is scheduled for the next release, do you have an ETA?

megapowerskills

GeometriX

I tested the plugin and it works. If you request landscape in c2, and add the 3rd party plugin in XDK:

name: landscape

plugin id: net.yoik.cordova.plugins.screenorientation

repo: https://github.com/yoik/cordova-yoik-sc ... tation.git

Then it will lock landscape

XDK uses the Cordova capability, but that doesn't work for ios https://issues.apache.org/jira/browse/CB-6462 https://issues.apache.org/jira/browse/CB-6182

I see there are some cordova plugins to lock orientation so that would be the quickest solution.

https://github.com/yoik/cordova-yoik-screenorientation

any update on this IntelRobert The landscape mode still doesn't seem to be working for me