FilteredMParticleUser.getConsentState() returns null even though the interface function has @NonNull

[gpunto]

Hello!

I'm using ConsentState.withConsentState(user.consentState) to create a builder to update consent in onUserIdentified. However, when user is FilteredMParticleUser this will crash because consentState returns null. Partial stacktrace:

java.lang.NullPointerException: Attempt to invoke virtual method 'java.util.Map com.mparticle.consent.ConsentState.getGDPRConsentState()' on a null object reference
	at com.mparticle.consent.ConsentState$Builder.<init>(SourceFile:15)
	at com.mparticle.consent.ConsentState$Builder.<init>(SourceFile:1)
	at com.mparticle.consent.ConsentState.withConsentState(SourceFile:1)

This should likely be caught at compile-time, since ConsentState.withConsentState requires a non-null ConsentState. However, the problem is that MParticleUser.getConsentState() is annotated as NonNull, so the Kotlin compiler trusts the annotation, while the FilteredMParticleUser implementation returns null.

For reference, I was taking this kit as an example implementation.

[Mansi-mParticle]

@gpunto Thanks for reporting this issue, and sorry for the delay in getting back to you. Could you please check if this behavior still occurs in the latest SDK version (v5.75.1)? We’ve made several updates since the version you referenced, and confirming this will help us identify the next steps.

Thanks again for bringing this to our attention!

[gpunto]

Hey @Mansi-mParticle thanks for the answer! I don't work on that project anymore, but let me tag @rolgalan, maybe he could help with redirecting this to the right people :)

[nickolas-dimitrakas]

Closing — this was addressed by the consent-state resolution rewrite in v6.0.x: the consent lookup chain now always constructs a ConsentState via its builder rather than returning a raw possibly-null value, so getConsentState() should no longer return null. Reopen if you're still seeing this on the latest version.