proguard?

[star-andy]

Expected behaviour

Whether to need to configure the proguard

Actual behaviour

Steps to reproduce

Version of the library

com.karumi:dexter:4.0.0

[Serchinastico]

Hi @qinyang1018,

First of all, thanks for reporting! I'm reading the source code and this is the offending line where the NPE is happening:

void onActivityDestroyed() {
    isRequestingPermission.set(false);
}

I can't see how that line can fail (isRequestingPermission is initialized in the constructor and never null'ed) How are you running Dexter? Have you tried updating to the latest release (4.1.0)?

[star-andy]

this is all server log

Thank you for your answer I will try to 4.1.0 and

void onActivityDestroyed() {
    isRequestingPermission.set(false);
}

[Serchinastico]

We are going to release a new version of Dexter with a proguard configuration so that we don't obfuscate any class in Dexter and we can debug what's happening better.

Thanks for reporting!

[star-andy]

ok thank you

[star-andy]

ok i will try wait new version thank you

[pedrovgs]

@flipper83 @Serchinastico I've seen you've merged a PR adding proguard support but not exporting the proguard configuration with the aar generated during the release.

You should enable consumerProguardFiles param as part of your build configuration.

Here you have an example:

defaultConfig {
    ...
    consumerProguardFiles 'proguard-rules.pro'
  }

[Serchinastico]

Thank you @pedrovgs!

I checked the configuration with the project Demo and didn't really used the generated AAR, I'm including the property just now before doing a release.

Cheers!

[EmmettWilson]

As far as the original exception. This appears to me to be a duplicate of https://github.com/Karumi/Dexter/issues/153?