Hi Stephen, I’m afraid that you have to use latest version(canary/beta/stable) of Crosswalk if you want to some fixes get in. There will be no changes for -3 release.
We can't update the version of crosswalk due to Android version issues. > Can I know why? Crosswalk support Android 4.0+ above from very beginning. Thanks, Halton. On Oct 7, 2015, at 5:16 AM, Stephen Post <[email protected]<mailto:[email protected]>> wrote: Hi all, We're about to release our product which uses the Crosswalk webview in an Android application. We use version 10.39.235.16 of the library. We've encountered this issue : https://code.google.com/p/android/issues/detail?id=37031 which in summary, routes requests via the system defined proxy, even if the request is targeting localhost. Now there is an easy fix (or so I thought) which is to apply the patch outlined in the issue and all problems would go away. However this is not the case. Even with the patch applied the request for http://localhost:6333<http://localhost:6333/> (still goes via the proxy (http://127.0.0.1:6333<http://127.0.0.1:6333/> fails also). I've used the proxy ProxyBypassRules::ToString() method to trace the results immediately after adding the bypass proxy, and the result is "<local>;" - which is the correct representation for the BypassLocalRule class. So it looks like the proxy is definitely being added, but it's just not being respected. Is there anything else, or any location I could look into next to get this resolved? (I thought it maybe due to the fact we are using port 6333, but I can't run on port 80) Note: We can't update the version of crosswalk due to Android version issues. Cheers, Steve _______________________________________________ Crosswalk-dev mailing list [email protected]<mailto:[email protected]> https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
