Adding woogeenConference to project breaks build?

[Zhen_L_]

I am trying to make conference mode to work in my android app.

So I added both woogeenConference.jar and woogeenBase.jar in to the ./lib folder.

But on buildling, i get an error saying 

Error:Execution failed for task ':app:transformClassesWithJarMergingForUserStaging'.

> com.android.build.api.transform.TransformException: java.util.zip.ZipException: duplicate entry: okhttp3/Address.class

I am also using 

compile 'com.squareup.okhttp:okhttp:2.3.0

I believe that one also has okio stuff.

What do i need to do so the build passes?

Is there anyway to have both OkHttp3 from woogeenconference.jar and come.squareup.okhttp to work at the same time in the same project? Or is there some way for me to package another version of woogeenconference.jar that uses a lower version of okhttp?

[Zhen_L_]

It looks like it is some issue with the okHttp version that has been bundled in.

According to the maintainer of okHttp

https://github.com/square/retrofit/issues/2266 ;

We should probably 1. use a newer version of okHttp3. 2. Rename the package that was used (jarjar-ing) ?

[He_Z_Intel]

we are planing to exclude the third-party libs in our release package in the future version.

For now, you could remove the okHttp in woogeenconferece.jar and repackage it.

[John1]

Hi Hank,

According to the okhttp maintainer the version packaged is a pre-release version that won't be compatible with other versions, in part at least since the package name seems to have changed. If we repackage the jar how can we have confidence that things will work? Can you use jarjar or similar technique so as not to conflict with users packages? Do you have an estimate as to when this will be fixed?

https://github.com/square/retrofit/issues/2266

 "No. OkHttp 3's package name is okhttp3.*. That looks like a pre-release version that won't be compatible with anything. "

[Zhen_L_]

@Hank Zhang We manually removed okhttp and okio packages from the included jar.

And added an okhttp-ws dependency. Everything works for now =)

[He_Z_Intel]

Zhen L. wrote:

@Hank Zhang We manually removed okhttp and okio packages from the included jar.

And added an okhttp-ws dependency. Everything works for now =)

glad to hear.

FYI, we don't import okhttp/okio directly, both of them are imported by socket.io that we used directly.