Build error for legacy android app

[David_S_16]

Since the login issue of the weekend I've been experiencing this following error.

The code that I am trying to build was working last week prior to the login issues.

The build failed.

An error occurred while building the application. Verify your build assets are correct and try again.

[Gary_H_2]

This is the same error i'm getting on Crosswalk builds. Have not been able to build since Friday.

[Michael_O_2]

Hello guys! Try the Cordova Android build.

[David_S_16]

That wasn't working for me last week and isn't working for me this week. Though at least last week I had an error in the build log indicating a plugin didn't load. This week the plugin doesn't even show in the build log.

[Pamela_H_Intel]

David,

FYI - the legacy system will be going away, you might consider switching to Cordova. Also, it is unclear that you are using legacy since you mention using a plugin. Legacy does not allow plugins.

I need more information. Please attempt a build of either a simple sample or a plain empty template. Let's determine if the issue is something in your app or something more basic.

[Eirik_N_]

I am using legacy and the build fails. I tried creating a sample project (Blank-> Standard HTML) and I am still getting the same error when building. The error is just "An error occurred while building the application. Verify your build assets are correct and try again"

[John_H_Intel2]

What platform are you building for? iOS or Android? Can you try building again?

[Eirik_N_]

I tried building both. iOs worked, Android didn't. Both me and my colleague using a different intel account tried building, but none of us could build the Android version. This was the case yesterday and today as well before I just now got a call from my colleague saying that he was able to build the app. I tried as well and it worked for me too. Now I am able to build both an iOs version and an Android version. Was there any problem relating to the Android legacy build from your side?

[John_H_Intel2]

Yes, there was an issue that was fixed this morning.