Android Crosswalk build failing

[Gary_H_2]

I built my app 10 days ago and submitted it to the Play Store but today when I tried to build it again to make an update the build failed. This is happening in a plugin where it can't find this package anymore. 

import org.xwalk.core.internal.XWalkCookieManager;

Did something change on the Crosswalk build system to cause this?

[Amrita_C_Intel]

Hello,

Can you try building again as one issue has been fixed if that might have affected. Are you using cordova plugin? If yes then which plugin?

[Gary_H_2]

Unfortunately, still failing.

I'm using a couple of local Cordova plugins (FileTransfer & CookieMaster) that I modified to use the XWalkCookieManager. As I said. it was building ok a week ago but now the same files fail.

[Gary_H_2]

I don't know if this has anything to do with it but I have noticed this line in my intelxdk.config.crosswalk.xml file:-

<intelxdk:cordova-cli version="3.5"/>

[Gary_H_2]

Crosswalk build still failing for me. Any ideas what changed since 2 weeks ago?

[Gary_H_2]

Some more info.

If I build with Crosswalk 12 it works but with Crosswalk 14 I'm getting the following:-

    [javac] .../Wispeo/platforms/android/src/com/cordova/plugins/cookiemaster/CookieMaster.java:16: error: package org.xwalk.core.internal does not exist
    [javac] import org.xwalk.core.internal.XWalkCookieManager;
    [javac]                               ^

[Gary_H_2]

So I upgraded to XDK 2496 and after some fun and games re-installing all my plug-ins I tried building again with the 5.1.1 CLI and Crosswalk 15 but got the same build error. The only way I can compile my plugins that use the XWalkCookieManager is if I use the 4.1.2 CLI and version 12 of Crosswalk. Up until this week I have been using Crosswalk 14 and having to go back to 12 seems a backward step. 

[Gary_H_2]

In fact turns out its a huge backward step because I can't inspect the device with the Chrome dev tools anymore which was my main debugging method previously.

Any help appreciated.

[Gary_H_2]

To summarize my issue.

Previously building for Crosswalk 14 worked fine. On Monday it started failing when trying to import XWalkCookieManger in my local plugins. Nothing on my side changed but now it only builds if I build for Crosswalk 12. I suspect this may have something to do with the switch from CLI 3.5.

My question therefore is why does it only build for 12 now and not 14 yet used to build 14 ok and how do I get back to where I was last week? 

[Gary_H_2]

Hi, I'm sure you are swamped with all the problems people seem to be having with the new version of the XDK but if someone could help me out with my issue that would be appreciated. I published an app in the Play Store 2 weeks ago and now I'm in the position where if I need to make a change I can't actually build it anymore with the XDK.

[Gary_H_2]

Some more info.

When I successfully build for Crosswalk 12 the build log contains this:-

-pre-compile:
     [echo] Set jars path to: .../Wispeo/CordovaLib/ant-build/classes.jar:.../Wispeo/CordovaLib/xwalk_core_library/ant-build/classes.jar:.../Wispeo/CordovaLib/xwalk_core_library/libs/xwalk_core_library_java_app_part.jar:.../Wispeo/CordovaLib/xwalk_core_library/libs/xwalk_core_library_java_library_part.jar

When I build for Crosswalk 14 the build fails and the log contains this:-

-pre-compile:
     [echo] Set jars path to: .../Wispeo/CordovaLib/ant-build/classes.jar:.../Wispeo/CordovaLib/xwalk_core_library/ant-build/classes.jar:.../Wispeo/CordovaLib/xwalk_core_library/libs/xwalk_core_library_java.jar

Why doesn't xwalk_core_library_java.jar contain org.xwalk.core.internal?

[Gary_H_2]

Good news, I found my issue.

Seems like somewhere along the way between Crosswalk 12 and 14 they changed the name of XWalkCookieManager to  XWalkCookieManagerInternal.

Not sure why my builds used to work with CLI 3.5 but I'm just glad its building again now.

[PaulF_IntelCorp]

Gary -- I apologize that nobody responded to your posts over the past few days. The forum has been very busy, but that still is no excuse. I'm trolling through the backlog to make sure nothing has been lost in all the commotion. Very glad to find that you figured out the source of the problem. Paul

[Gary_H_2]

No problem Paul, I guessed everyone was busy and it did force me to persevere until I finally found the right things to Google. It turned out to be something in my code anyway so I'm glad I didn't take up anyone else's time figuring it out.