F-Droid version crashes right after start: Multicaster binderDied

[GoogleCodeExporter]

The new F-Droid version crashes on my phone right after the start with this 
message:


11-27 18:38:25.825 E/dalvikvm(31257): Could not find class 
'javax.jmdns.ServiceInfo', referenced from method 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.getHosts
11-27 18:38:25.875 E/AndroidRuntime(31257): FATAL EXCEPTION: Thread-3349
11-27 18:38:25.875 E/AndroidRuntime(31257): java.lang.NoClassDefFoundError: 
javax.jmdns.JmDNS
11-27 18:38:25.875 E/AndroidRuntime(31257):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.jmDnsListener(Cl
ementineMDnsDiscovery.java:120)
11-27 18:38:25.875 E/AndroidRuntime(31257):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.access$100(Cleme
ntineMDnsDiscovery.java:40)
11-27 18:38:25.875 E/AndroidRuntime(31257):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery$1.run(Clementine
MDnsDiscovery.java:69)
11-27 18:38:25.875 E/AndroidRuntime(31257):     at 
java.lang.Thread.run(Thread.java:856)
11-27 18:38:27.325 E/WifiService(  397): Multicaster binderDied
11-27 18:39:25.885 E/dalvikvm(31295): Could not find class 
'javax.jmdns.ServiceInfo', referenced from method 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.getHosts
11-27 18:39:25.945 E/AndroidRuntime(31295): FATAL EXCEPTION: Thread-3355
11-27 18:39:25.945 E/AndroidRuntime(31295): java.lang.NoClassDefFoundError: 
javax.jmdns.JmDNS
11-27 18:39:25.945 E/AndroidRuntime(31295):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.jmDnsListener(Cl
ementineMDnsDiscovery.java:120)
11-27 18:39:25.945 E/AndroidRuntime(31295):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery.access$100(Cleme
ntineMDnsDiscovery.java:40)
11-27 18:39:25.945 E/AndroidRuntime(31295):     at 
de.qspool.clementineremote.backend.mdns.ClementineMDnsDiscovery$1.run(Clementine
MDnsDiscovery.java:69)
11-27 18:39:25.945 E/AndroidRuntime(31295):     at 
java.lang.Thread.run(Thread.java:856)
11-27 18:39:27.456 E/WifiService(  397): Multicaster binderDied



When I built the app locally myself and tested in an emulator, it worked, so 
I'm not sure what is happening here. Any idea how to fix this?

Original issue reported on code.google.com by [email protected] on 27 Nov 2013 at 7:04

[GoogleCodeExporter]

Hm, it looks like jmdns is not included correctly.

I don't know how they create the apk, the .jar file has to be in the libs/ dir.

Original comment by [email protected] on 27 Nov 2013 at 7:11

[GoogleCodeExporter]

Seems to be some issue with the F-Droid buildserver, when I locally build with 
he exact same process, the app does not crash. Maybe some different jdk version 
or something like that?

Original comment by [email protected] on 28 Nov 2013 at 5:05

[GoogleCodeExporter]

I don't know how the buildserver builds them. The .project file includes the 
jar, so there shouldn't be a problem. Maybe ask the f-droid guys, maybe they 
encountered an issue like this before.

Original comment by [email protected] on 28 Nov 2013 at 5:25

[GoogleCodeExporter]

Any news on this one?

Original comment by [email protected] on 3 Dec 2013 at 11:53

[GoogleCodeExporter]

No real news unfortunately, I build it myself with jdk 6 and 7 release and 
debug builds and it worked every time. But just not on the buildserver. We now 
suspect a over-optimizing proguard.

Original comment by [email protected] on 4 Dec 2013 at 7:37

[GoogleCodeExporter]

This project moved to GitHub. Please continue the discussion here: 
https://github.com/clementine-player/Android-Remote/issues/29

Original comment by [email protected] on 6 Dec 2013 at 11:17

[GoogleCodeExporter]

I've put in a merge request to f-droid. It builds the jmdns jar from source; 
that's I do for my own repo, where I don't accept first party prebuilts. I had 
to import my own build.xml for the jmdns, but it gets there in the end. I 
changed all the urls too.

Original comment by [email protected] on 9 Dec 2013 at 8:02

[GoogleCodeExporter]

If it fails it won't be proguard's fault anyway because proguard is disabled.

Original comment by [email protected] on 9 Dec 2013 at 8:15