Finalize button IAP

Need help
1

Need urgent clarification from Bubble team / Native Mobile users.

My app is fully ready for launch, but I cannot find the “Finalize variant” flow for subscriptions.

Current state:

  • Apple + Google IDs mapped correctly
  • deploy/build is NOT blocked
  • switched to the new property editor
  • still no:
    • Draft badges
    • Ready for Sale badges
    • Finalize variant button

Bubble support keeps referencing documentation, but nobody can confirm whether this is:

  • a UI rollout/version issue,
  • or whether variants are already finalized in this editor version.

Is anyone else seeing this behavior in Native Mobile subscriptions? @nick.carroll

2

congrats! We actually recently removed the finalize variant button because it was causing more issues than it was solving. I need to update the documentation to reflect the new flow.

In your case, I would recommend pushing a build to testflight / android testing track and test your payment flows in their sandbox environments.

3

Can you please help me with one more thing.

In my Bubble Native Mobile app:

  1. User taps “Initiate Subscription Purchase”
  2. Apple native purchase flow completes successfully
  3. User returns to Home page
  4. Subscription Purchase record exists in the database
  5. But UI conditions based on active subscription still evaluate as false

Interestingly, running “Restore Purchases” immediately afterwards makes the subscription state available and premium content appears correctly.

This only happens in TestFlight with the native Apple purchase flow. In BubbleGo everything appears to work correctly.

Why is that? @nick.carroll

4

I’m assuming you are using the out of the box data sources around a users subscription status? Or did you set up custom logic here?

5

Hi Nick,

Thanks for looking into this.

I’m using Bubble’s built-in subscription data, not custom subscription logic.

My premium content is displayed using Bubble’s native subscription state (Current User’s active subscriptions / subscription status).

The issue is that after a successful native Apple purchase in TestFlight:

  • the Subscription Purchase record is already created in the database,
  • but the built-in subscription state used by Bubble UI still evaluates as if the user is not subscribed.

Only after running Restore Purchases does the built-in subscription state immediately become available and all premium conditions evaluate correctly.

This only happens in TestFlight with the real Apple purchase flow. In BubbleGo everything works as expected.

So I’m not overriding Bubble’s subscription logic—I am relying on the native Bubble subscription state.