sounds like the open ssl issue has been fixed in CW7, it's just that they forgot to change the name,,,, so the bots will see that and throw a flag? has anyone rebuilt in 7 and had any issues/warnings with the playstore?? I've already been warned/suspended by google(admob) for clicking my own ads, and don't want to give them a reason to 86 my game entirely.
imaffett wrote:@lolva - sure, but it's highly unlikely they will change it. It would be better for a user here to raise the issue as a Chromium bug and have everyone star it.
Could you do it? If not, I'll open the issue, but can you help us with it and send me the text which I can use? I'm not really technical and don't know exactly what to write to describe the problem correctly.
Any word on when crosswalk 12 could go stable? After some more playing with your cw testing shells it seems the cw12 does perform best....for devices which can do webGL, if it fails, it's still better to use cw7.
Ok, so, on Intel's page there is an announcement about Crosswalk 7 OpenSSL update. (software.intel.com, search for 'crosswalk-7 open ssl update'. Sorry - I don't have enough rep for posting urls) As imaffett promised, there's also a sample petition text that we can use to explain Google that the openssl issue flag is false positive. Did anyone compile anything in Crosswalk 7 and wrote to Google with that petition? On which address do you send it, and do you send it immediately after you published the app, or after the Google warning appears?