Skip to main content
Question

Paywall not showing sometimes, but is showing other times.

  • September 7, 2026
  • 1 reply
  • 17 views
Forum|alt.badge.img+2

On android, in a .aab internal testing build, sometimes the paywall will show and sometimes it won’t. When it doesn’t show, just the loading skeletons display indefinitely. At other times the paywall will show. Restarting the app doesn’t help, and reinstalling doesn’t either. Then at other times the paywall will work perfectly. Another app (installed through the Play store) on my phone that uses revenuecat seems to be out at the same times, and working at the same times. 

    1 reply

    Tarek
    RevenueCat Staff
    Forum|alt.badge.img+6
    • Tarek
    • RevenueCat Staff
    • September 7, 2026

    Hi Jeremy,

    I'm Tarek from Developer Support, thanks a lot for reaching out. 

    I took a look. RevenueCat had no related incident recently, and our logs show normal offerings responses for your Android app on each day since September 1. So from what I can see, the cause seems to be on the device or on its network, not on our servers.

    Here is what happens. The paywall shows the skeleton placeholder while the SDK waits for two answers: the offerings from RevenueCat, and the product details from Google Play Billing. If Play Billing does not answer, the SDK waits and the skeleton stays on screen. A restart or a reinstall of the app does not change the Play Store state on the phone. Every app with RevenueCat on that phone uses the same Play Billing service. This is why the two apps fail and recover at the same times.

    The SDK must return an error in this case, not wait forever. A fix is in review, and no release contains it yet.

    A network block is a second possible cause. A VPN, a Private DNS resolver or an ad blocker can block api.revenuecat.com. In that case the paywall normally shows an error dialog, not an endless skeleton. So this cause is less likely, but the test is quick.

    To help investigate, could you please run these tests when the skeleton is stuck:

    1. Send the app to the background. Then return to it. Tell me if the paywall then loads.
    2. Turn Wi-Fi off. Test on mobile data. Also turn off VPN, Private DNS and ad blocker apps.
    3. Open the Play Store on the phone. Confirm that your Google account is signed in. Install any Play Store update that is available.
    4. Confirm that the app does not include a second billing library, for example react-native-iap, expo-in-app-purchases or a direct Play Billing dependency.
    5. Set the SDK log level to debug with Purchases.setLogLevel. Then send me the logs of one failed session.

    Two more recommendations:

    • You can add diagnosticsEnabled: true to your Purchases.configure call. The SDK then sends the Play Billing results to RevenueCat, and I can see them from my side.
    • Update to the latest SDK version. The update does not contain a fix for this wait, but it contains other fixes.

    Let me know if that makes sense and if there's anything else I can help with!

    Have an excellent day.

    Best regards,

    Terms & ConditionsAccessibility statement