Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to build with enabled proguard

See original GitHub issue

Mosby Version: 3.0.2

Expected behavior Should build with proguard

Actual behavior (include a stacktrace if crash) Not building with proguard:

Warning:com.hannesdorfmann.mosby3.mvp.delegate.FragmentMvpDelegateImpl: can't find referenced class edu.umd.cs.findbugs.annotations.SuppressFBWarnings
Warning:com.hannesdorfmann.mosby3.PresenterManager: can't find referenced class edu.umd.cs.findbugs.annotations.SuppressFBWarnings
Warning:com.hannesdorfmann.mosby3.mvp.delegate.ViewGroupMvpDelegateImpl: can't find referenced class edu.umd.cs.findbugs.annotations.SuppressFBWarnings
Warning:com.hannesdorfmann.mosby3.mvp.delegate.ActivityMvpDelegateImpl: can't find referenced class edu.umd.cs.findbugs.annotations.SuppressFBWarnings
Warning:there were 4 unresolved references to classes or interfaces.

Steps to reproduce the behavior or link to a sample repository Build with enabled proguard

Issue Analytics

State:
Created 6 years ago
Comments:17 (7 by maintainers)

Top GitHub Comments

2reactions

sockeqwecommented, Apr 20, 2017

3.0.3 has been released a minute ago. Should be available soon (may take some more minutes to sync it to maven central)

Thanks for your help!

0reactions

dimsuzcommented, Apr 25, 2017

OK, it was enough to just add

compile 'com.hannesdorfmann.mosby3:viewstate:3.0.3'

Disregard my last question, I didn’t notice that you suggested to just explicitly specify 3.0.3 for other artifacts. My current setup used 3.0.3 for mvp but 3.0.0 for a viewstate (transitively) which caused troubles.

Thanks for helping to sort this out! Issue solved (can’t close it, no rights)