Unable to test app in test mode after the recent update

[espressotechie]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

I’m not using RevenueCat Web Billing because it’s a paid feature, and my apps are iOS-only, so I don’t need web billing at all.

The issue I’m facing is that FlutterFlow test mode runs on the browser, and it seems the web billing key is now treated as mandatory, even when the app is not intended for web and RevenueCat was previously disabled on web builds.

Because of this, I’m unable to test the app workflow in the browser and am forced to build in Xcode and test on a real device every time, which is very time-consuming. This was working fine before the recent update.

Expected Behavior

What I’m requesting is:

The Web Billing Key field in FlutterFlow should be optional, or

A way to disable RevenueCat entirely for web/test mode, so iOS-only apps can still be tested in the browser without requiring a paid web billing feature.

This would greatly improve the testing experience for users who are not targeting web at all.

Steps to Reproduce

Run a test mode with RevenueCat enabled and the first page calls the Revenuecat API onLoad. Leave the "web billing key" field empty in Revenuecat settings.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ol+fl4otNsdtY7rX2dsExnSQXJWYhba8708pBZywgfZzzBLN/fPfQP0tWZPWrYW9EImKMp14FpMrokfLDCPkDGxGsfa5A+s12YDyWTTqQbr2TF7WSY3RCI8FQN3Kc0ZjYhyN4XLBfZXAQ7GWTN+i+YAzZGYy0DVQwSq/LZO4=

Visual documentation

Browser Console error - Unable to check RevenueCat entitlements: PlatformException(23, Purchases SDK not configured. Call configure first., null, null)

Environment

- FlutterFlow version: 6.4.81
- Platform: IOS App
- Browser name and version: Chrome 143.0.7499.146
- Operating system and version affected: Windows 10 Home

Additional Information

No response

[Alezanello]

Hello!!

This has always worked the same way: if your app includes the RevenueCat package and you test it on the web, opening any page that uses RevenueCat (iOS/Android) will trigger an error. Those pages must be tested on a physical device using a local run.

You can find more details in our documentation:
https://docs.flutterflow.io/integrations/payments/revenuecat/

[espressotechie]

I can confirm that I have been testing all features of my apps (except Revenuecat functionality) for the last one year on Chrome browser with Revenuecat enabled in settings in flutterflow. It's only since the beginning of this month that I am not able to do so as it's giving a null error when calling the Revenuecat API.

I think that previously the Revenuecat API was disabled during test mode in web therefore I was able to test other features of my apps without Revenuecat throwing an error. But now I am not able to open my apps at all as it throws a null error since all my apps call Revenuecat API during page load.

Previously, Revenuecat settings in Flutterflow had an appstore key, playstore key. But after recent updates, it has a new web billing key. Therefore now we can test Revenuecat functionality for web also. But this is causing conflict if we don't have web billing key and only have appstore key.