"naming conflict" runtime error on device

I’m having trouble with my Android builds.  This is the error I receive. 

runtime error jave.lang.illegalArgumentException: naming conflict for module name ‘init’ at ‘init’

I’ve been googling arounds to no avail and I’m wondering if anyone has any hunches for how to approach this. I used to have a module named ‘init’ but I changed the name after getting the above error - just in case that was the problem.  Changing the name did not work.  Any other guesses?

Thanks!

Hi @sporkfin,

Do you try turn off all plugins or 3rd party library and one by one turn on it to detect source of problem? 

Have a nice day:)

ldurniat

@Idurniat Yes and no.   I’ve removed all of the plugins and I’m working to or isolate the libraries but that’s a longer endeavor.  I’ve tried to analyze it in Android Studio but I’m not proficient enough to try to debug it there yet.  I’m also looking for all modules and functions named “init” but I’m not sure if “init” is referring to my direct files or part of the Android compiling/build process.

Are you doing native builds?

OK, I still ave no idea what the error means but @Iduriant was right, it was indeed a 3rd party library.  It took me a while to isolate 15 plugins and external libraries from a 40k line project but I did it and found the culprit!  I’ll notify the developer.

Eventually I was able to trigger another error that left a breadcrumb trail to the suspect library.

@Rob, no native builds just a good old fashioned library error.

Hi @sporkfin,

Do you try turn off all plugins or 3rd party library and one by one turn on it to detect source of problem? 

Have a nice day:)

ldurniat

@Idurniat Yes and no.   I’ve removed all of the plugins and I’m working to or isolate the libraries but that’s a longer endeavor.  I’ve tried to analyze it in Android Studio but I’m not proficient enough to try to debug it there yet.  I’m also looking for all modules and functions named “init” but I’m not sure if “init” is referring to my direct files or part of the Android compiling/build process.

Are you doing native builds?

OK, I still ave no idea what the error means but @Iduriant was right, it was indeed a 3rd party library.  It took me a while to isolate 15 plugins and external libraries from a 40k line project but I did it and found the culprit!  I’ll notify the developer.

Eventually I was able to trigger another error that left a breadcrumb trail to the suspect library.

@Rob, no native builds just a good old fashioned library error.