Software Archive
Read-only legacy content
17061 Discussions

Build failed v1816 - plugins salad

Ivana_B_
Beginner
517 Views

Hi, 

the sole purpose of writing this post is to help someone not to lose whole day investigating as we did. 

On March 2th iOS Cordova build unexpectedly failed for our app. nothing was changed from last build on Friday, so we had no clue.

Anyway...We are using Cordova v3.5 and following plugins: Splasscreen, inapp browser, geolocaton , device and media plugin v0.2.10. we have tried building with various versions of Cordova and plugins with no success.

Finally, we manually included File v1.3.2 plugin to our build path and build worked. But the question remained... what was the change that was blocking us from building today?

A few days ago, if you wanted to build a project with Media plugin included, XDK build server automatically added File plugin for you v1.3.2. but since they have updated build servers, they are adding File plugin v0.2.5 which doesn't work with default v0.2.10 of Media plugin (missing CDVFilesystemURL error in build log).

As said before, I only want to help someone who might be having a problem, and maybe put Intel's attention to this issue as this probably wasn't wanted behavior.

BTW: building with Cordova 4.1.2. doesn't add any dependency plugins, you have to add File manually.

 

0 Kudos
1 Solution
John_H_Intel2
Employee
517 Views

Sorry for the issues we might have caused. I spoke with a build engineer and he informed me of this:

Previously you added the medial plugin and plugman fetched the latest file plugin from the registry.
Now, when you build using the media plugin, the our cached version of plugin gets installed.

We are working on a way to prevent issues like this, but it is not available yet.
 
A fix for you, as you have found, is to specify the particular version of a required plugin and to also specify its dependencies (and version). The version-ing  becomes very important as plugins get updated. A developer could push an update to the plugin, you rebuild, and suddenly nothing works. If you specify a particular version, you can bet that it will be consistent when you build it again in the future. 

View solution in original post

0 Kudos
3 Replies
John_H_Intel2
Employee
518 Views

Sorry for the issues we might have caused. I spoke with a build engineer and he informed me of this:

Previously you added the medial plugin and plugman fetched the latest file plugin from the registry.
Now, when you build using the media plugin, the our cached version of plugin gets installed.

We are working on a way to prevent issues like this, but it is not available yet.
 
A fix for you, as you have found, is to specify the particular version of a required plugin and to also specify its dependencies (and version). The version-ing  becomes very important as plugins get updated. A developer could push an update to the plugin, you rebuild, and suddenly nothing works. If you specify a particular version, you can bet that it will be consistent when you build it again in the future. 
0 Kudos
Ivana_B_
Beginner
517 Views
Hi John, thank you for invastigating this so fast and for your reply. Now that we know how we should approach plugins when building, it's no problem. You are doing a great job and XDK has become valuable platform for developing hybrid apps.
0 Kudos
Ivana_B_
Beginner
517 Views
Hi John, thank you for invastigating this so fast and for your reply. Now that we know how we should approach plugins when building, it's no problem. You are doing a great job and XDK has become valuable platform for developing hybrid apps.
0 Kudos
Reply