Skip to main content
Projectitis
Inspiring
November 2, 2015
Answered

Conflicting resources in multiple ANEs

  • November 2, 2015
  • 1 reply
  • 430 views

Hi all,

I have an app with around a dozen ANE files and am running into the 'conflicting resources' problem described here (with solution) - Multiple ANEs and conflicting resources

These are all 3rd-party ANEs from multiple vendors.

Solving these dependencies manually is quite a job when I have so many ANE files - and if I later remove an ANE that happens to be the one with the shared resource in it, the other ANEs will stop working. 

My question(s):  Is there really no other way?  If not, has anyone created, or know of, a tool that has automated [some of] this process?

This topic has been closed for replies.
Correct answer Projectitis

In the end it was all down to Google Play Services being included in a bunch of the ANEs.  All vendors had a "no GPS" version of their ANE once I went looking, so I didn't have to delve into the ANEs myself this time! 

FYI - I am using HeyZap ad mediation, and the ANEs that were conflicting were from all the mediated networks (AdMob, Chartboost, AdColony, etc).  I'm also using a bunch of Distriqt ANEs, but the Distriqt team have already pulled common libraries into separate ANEs (core and Google Play Services) so no issue there.

1 reply

Projectitis
ProjectitisAuthorCorrect answer
Inspiring
November 2, 2015

In the end it was all down to Google Play Services being included in a bunch of the ANEs.  All vendors had a "no GPS" version of their ANE once I went looking, so I didn't have to delve into the ANEs myself this time! 

FYI - I am using HeyZap ad mediation, and the ANEs that were conflicting were from all the mediated networks (AdMob, Chartboost, AdColony, etc).  I'm also using a bunch of Distriqt ANEs, but the Distriqt team have already pulled common libraries into separate ANEs (core and Google Play Services) so no issue there.

Projectitis
Inspiring
November 2, 2015

This is a specific error message you may come across (adding it here for future searchers):

UNEXPECTED TOP-LEVEL EXCEPTION:

java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/internal/iv;