Build Error

[Spiros_N_]

Today a project that was building without problems 2 days ago returns error 

no problems with IOS build where ca I get a log with more details ?

Thanks

[John_H_Intel2]

What platform are you building for?

Are you signing or unsigning the build? (option in the build settings)

[Spiros_N_]

Crosswalk 10.39.235.15 then build is Signed tried with Crosswalk 11 and got same results. 

[Gary_H_2]

This is the same issue I am having and reported in another thread (https://software.intel.com/en-us/comment/1828967#comment-1828967). Android Crosswalk builds that were working a few days ago now fail with no other log than what you and I have posted. I have smaller projects that will build so it may be as simple as the Intel Android build server has run out of disk space.

[Spiros_N_]

Taking into account the login problems of the last weekend we can assume that there is a problem in their system.
Maybe we have to prepare a local build environment.  

[John_H_Intel2 · Accepted solution]

Are you including any 3rd party plugins? If so, try removing them and reuploading/building and see if the build works then.

[Spiros_N_]

Yes it works without including 3rd party plugin. This plugin working as expected 2 days ago

[Gary_H_2]

How do we get Android Crosswalk builds to work again with 3rd Party plugins?

[PaulF_IntelCorp]

So the purpose of the exercise is to see if there is a specific third-party plugin that is causing the problem. In other words, does ANY third-party plugin cause the failure? Does only a specific plugin cause the failure? Does a specific version of a plugin cause the failure? If you can go through a few variations it will help to uncover what the issue is and get faster action on a fix.

[Spiros_N_]

Thank you Paul for your answer.

Currently there is only one third-party plugin.
It is the com.pushwoosh.plugins.pushwoosh version 3.5.3.
I'll go through some variations and I'll let you know.
A more detailed log could help resolving issues during build.
The same version of plugin with the same settings, crosswalk version and other selected plugins standard and featured, was working for the past 3-4 weeks …
 

[Barry_Johnson]

I earlier posted a problem report related to a third-party plugin at. https://software.intel.com/en-us/forums/topic/560477

The plugin in question was: nl.x-services.plugins.launchmyapp

As I also note in my post, I had checked another plugin to see if ti was a more universal issue, and the ionic keyboard plugin did not cause problems (although I did not bother writing any code to test if it was actually available and operating as expected in a built app).

I cannot speak to whether it worked previously, as I had planned to try it this weekend for the first time (but had to wait until yesterday given that the XDK was unusable over the weekend.)

[Gary_H_2]

The plugin that is causing my build to fail is one that I created myself and is local so I know that hasn't changed. Last week it was building ok but this week only builds if I remove it. Come to think of it I have other 3rd party plugins that are not local and they seem ok. Is it being a local plugin that is the issue?

[Gary_H_2]

I just tried another local plugin and the build failed for that as well. Maybe coincidence or maybe not. Is anyone else using local plugins?

[Gary_H_2]

Another way to approach this is if JOHN H. (Intel) or Paul Fischer (Intel) could ask their tech guys "what the frigging hell did you change last week?" That might give a clue :-) 

[PaulF_IntelCorp]

There is an issue with plugins that have changed their dependencies to Cordova plugin IDs that reference the new Cordova CLI 5.x naming convention (using dashes rather than dots -- it's a long story, the folks in the Cordova Apache project thought it would be a trivial thing, it's turning out not to be...). Anyway, I checked the com.pushwoosh.plugins.pushwoosh repo and it does not reference anything like that, so that's not the likely problem. Will ask the build engineer to take a look. This may take some time, sorry...

[Gary_H_2]

Thanks for the help Paul. This is a show stopper for me at the moment.

[Spiros_N_]

My plugin that fails is also downloaded local in www folder and imported to XDK. 
maybe this is the problem Gary H.

[Spiros_N_]

Yes. For me problem solved when I used "Get plugin from the web" to install com.pushwoosh.plugins.pushwoosh plugin.
So there must be a problem with the local imported plugins.

Thanks everybody in this thread for the help.

[Eirik_N_]

I am experiencing the same issue today, but i am building my android app using legacy hybrid option. The iOs-builds work fine.

The only error message I recieve is the "an error occured while building the application. Verify your build assets are correct and try again".

I don't use any third party plugins and the only change from last time is one edit in an html-file. I can build using the cordova options, but I haven't moved my project to cordova yet because I can't get the touch events to work when I build using cordova. Any pointers in that direction would also be useful to me.

[John_H_Intel2]

@Eirik ~

The legacy builds to not take advantage of any of the plugins that you have setup for you app. The plugins are ONLY used for the cordova builds, not the legacy.

[Eirik_N_]

Yes, I knew that. I just felt like mentioning this since the original posters problem was related to using plugins.

But I still can't build to android using this option. I tried creating a sample project (Blank-> Standard HTML) and I am still getting the same error when building.