Skip to main content
Question

Paywalls won't launch after logIn(appUserId), but launch fine after config(key, appUserId)

  • December 14, 2025
  • 2 replies
  • 23 views

Forum|alt.badge.img

If I log in then relaunch the app so the RevenueCat SDK initializes with the appUserId populated, the paywalls launch perfectly.

If I log out, paywalls are displayed. If I then log back into the same appUserId (or any other), paywalls aren’t displayed.

If I launch the app logged out, paywalls are displayed. If I then log in (to the same appUserId), paywalls aren’t displayed.

The call to `offerings.currentOffering(forPlacement: “placement_id”)` does return an offering in all cases.

The following is executed in all cases, with a non-nil offering:

```

            Group {
                PaywallView(offering: offering, displayCloseButton: true)
            }
            .onRestoreCompleted { customerInfo in ...

```

Any ideas what might be preventing the paywalls from rendering?

2 replies

Forum|alt.badge.img+8
  • RevenueCat Staff
  • December 19, 2025

Hi ​@chripes could you please open a support ticket here and provide the following?

  • RevenueCat debug logs here for when you reproduce this
  • Your SDK version
  • Your paywall code
  • Can you let me know if calling syncAttributesAndOfferingsIfNeeded here after logIn if it helps with what you are seeing? This method will refresh the cached offering.

Forum|alt.badge.img
  • Author
  • New Member
  • December 23, 2025

Thanks very much Haley, I replied to myself with the solution/issue last Tuesday, the forum said my response would be reviewed then approved. I was displaying my paywall sheet based on `offering: identifiable`, which didn’t change between logins. Displaying based on placement fixed it.

I am using subStatus = customerInfo?.entitlements.. then offerings = try await Purchases.shared.offerings() after logIn or logOut.