Crosswalk Intel XDK experiences

Discussion and feedback on Construct 2

Post » Wed May 13, 2015 6:00 pm

Ashley wrote:According to Intel, you can notify Google that your Crosswalk 7 app is actually secure and avoid it being taken down. See: https://software.intel.com/en-us/xdk/article/crosswalk-7-open-ssl-update



To be honest, why should we do this everytime we release our game under Crosswalk 7. It's kind of frustrating that our games have to rely on the oldest version of Crosswalk to maintain a decent framerate. Yes, exporting and signing is easier than CocoonJS, but the performance is what's killing everything.
Image
B
81
S
16
G
4
Posts: 502
Reputation: 8,936

Post » Fri May 15, 2015 12:14 pm

I tried to notify Google about this issue according to Intel instruction, but they didnt accept.
I will need to fix and upload my app using Crosswalk 10, there is no way.
For sure my rating will go down.. terrible..
B
5
Posts: 13
Reputation: 251

Post » Fri May 15, 2015 2:26 pm

I'm calling bullshit on the smoke and mirrors surrounding this issue for well over 3 months now... chromium introduced gpu-rasterization in the release that came out after the CW7 build, and the real reason CW7 is being quashed isn't because they're too lazy to fix or deal with it( there are 3 seperate divisions that could fix the problem as i understand it: google play,google chromium, or intel), but rather they're really bullish on the gpu rasterization, and that they (Google) doesn't want apps to disable it.

this false- rev- stalling- fodder you've been feeding us is growing stale
B
3
G
1
Posts: 15
Reputation: 855

Post » Mon May 18, 2015 1:41 pm

Is there a particular reason that CW7 is preferred? I've compiled my game under the latest version of CW and it seems to run fine. A few random crashes every now and then though.
B
3
Posts: 5
Reputation: 185

Post » Mon May 18, 2015 4:52 pm

I've contacted Google, but the alert is still here.
This is what I wrote (copied&pasted from Intel page):
This application uses the Crosswalk 7 WebView which is based off of Chromium 36.0.1985.144. This version of Chromium includes the Open SSL fixes found at https://chromium.googlesource.com/chrom ... 25d0b079c3
c5547f07948684f80c4e9c3584

The Chromium team did not rev the Open SSL identifier, so it still reports 1.0.1e as the Open SSL version. You can verify this in the commit log at https://chromium.googlesource.com/chrom ... sl.version

You can find the Crosswalk commit that updates to Chromium 36.0.1985.144 at https://github.com/crosswalk-project/cr ... a3d9e68e05

Thank you

This is what they have replied:
Hi,

Thanks for contact Google Play Developer Support.

To help protect your users, it’s important for you to update your app’s use of TLS/SSL. Apps with vulnerabilities that expose users to risk of compromise may be considered “dangerous products” and subject to removal from Google Play.

For more information and examples on using TLS/SSL on Android, please go to:

https://developer.android.com/training/ ... y-ssl.html

Here are some common areas to look at when troubleshooting:

- If your app trusted a certificate issued for an unrelated hostname for a connection, your app could be using an overly permissive HostnameVerifier or none at all.

- If your app replaces the default TrustManager with one that doesn’t verify the chain of trust, your app could be trusting a certificate that wasn’t issued by a trusted certificate authority

- If you are using a version of your app for debugging that has SSL disabled, it should be guarded using a DEBUG flag that is never turned on in a build published on Google Play.

Please let us know if you have any additional questions.

Regards,
Thomas
Google Play Developer Support
Did you know we offer chat support in English? Chat with us from Monday through Friday, 8 am to 5 pm PT by going to https://support.google.com/googleplay/a ... #contact=1


What can I do?
@Ashley and @imaffett

EDIT: After calling Google 2 times, contacting them via email 3 times, "marking the alert as current", "Dismissing" the alert, selecting "There's a mistake", the alert has gone, I have no problems anymore.
Last edited by grigrizljac on Fri Jun 12, 2015 12:53 pm, edited 2 times in total.
B
32
S
7
G
4
Posts: 397
Reputation: 4,589

Post » Tue May 19, 2015 6:09 pm

@grigrizljac, I'm in the same situation..
B
5
Posts: 13
Reputation: 251

Post » Wed May 20, 2015 8:40 am

Anyone here is using ajax with crosswalk?
It seems to work only when i choose crosswalk version 7, all the new one are not responding to any requests.
Image
B
71
S
28
G
12
Posts: 515
Reputation: 12,284

Post » Sun May 24, 2015 8:05 am

Lof wrote:Anyone here is using ajax with crosswalk?
It seems to work only when i choose crosswalk version 7, all the new one are not responding to any requests.

I'm using AJAX and building with Crosswalk 7. I don't have any problems. I haven't tried any other Crosswalk versions because the build fails.
B
32
S
7
G
4
Posts: 397
Reputation: 4,589

Post » Sun May 24, 2015 8:26 am

Yeah well 7 works for me too, but it's from 8 months ago and i don't see any reports about it so it worries me a little.
Image
B
71
S
28
G
12
Posts: 515
Reputation: 12,284

Post » Sun May 24, 2015 9:21 am

@Lof
No problems with Ajax here on XDK 1995, CW12. All works fine.
ImageImageImageImage
B
157
S
64
G
41
Posts: 2,592
Reputation: 34,644

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 5 guests