Skip to content

RevenueCat entitlement is active but the feature stays locked

Separate CustomerInfo.isActive from a client feature gate that still refuses the unlock.

2 min read · Ropely engineering · not externally reviewed · factual review: internal

Symptom

Why the symptom is ambiguous

Evidence required

Provider-specific state

Step-by-step diagnosis

Example timeline

Safe implementation example

What Ropely can establish

What Ropely cannot establish

Official sources

Source references

Run a free Stripe health check

Related

RevenueCat entitlement is active but the feature stays locked: Ropely