React Native survey not displaying on Android despite successful initialization

[omdam]

Hi Formbricks team 👋

I’m trying to use @formbricks/react-native in my React Native app, but surveys are not being displayed on Android even though the SDK initializes successfully.

Here’s what I see in the logs when the app starts:

LOG 🧱 Formbricks - 2025-09-03T10:33:21.018Z [DEBUG] - Found existing configuration.
LOG 🧱 Formbricks - 2025-09-03T10:33:21.019Z [DEBUG] - Start setup
LOG 🧱 Formbricks - 2025-09-03T10:33:21.019Z [DEBUG] - Configuration fits setup parameters.
LOG 🧱 Formbricks - 2025-09-03T10:33:21.024Z [DEBUG] - Fetched 2 surveys during sync: Site Abandonment Survey (copy), Site Abandonment Survey
LOG 🧱 Formbricks - 2025-09-03T10:33:21.025Z [DEBUG] - Adding event listeners
LOG 🧱 Formbricks - 2025-09-03T10:33:21.027Z [DEBUG] - Set up complete

So it looks like the SDK connects to the environment and fetches surveys, but nothing is shown in the Android app.

Steps to Reproduce

Install @formbricks/react-native.

Add the Formbricks component to the app:

Run the app on Android.

Observe logs → surveys are fetched, but no survey UI is displayed.

Expected Behavior

The survey should be displayed automatically (similar to the web SDK) when the trigger conditions are met.

Actual Behavior

No survey is displayed, even though surveys are fetched successfully.

Environment

@formbricks/react-native version: [your version here]

React Native version: [your RN version here]

Platform: Android

[fanion]

Bug Report

Description

As @omdam wrote, surveys are not rendered on Android, despite successful initialization.

Platform

• iOS
• Android
• Both

Steps to Reproduce (In our app)

1. Launch app.
2. Navigate to Account tab.
3. Navigate to Development Menu
4. Open "Surveys" collapsible.
5. Click button to trigger code action.

Expected Behavior

We expect to see the same functionality on Android as on iOS.

Actual Behavior

The survey is shown in the iOS simulator, but not on the Android emulator.
(Same behavior on the physical devices we've tested on - Pixel 9a & iPhone 11 (both with iOS18 & iOS26).

Environment

• SDK Version: 2.3.0
• React Native Version: 0.76.9
• React Native Architecture: New Architecture
• Expo: Yes (SDK 52.0.46)
• iOS Version: 18.2
• Android Version/API Level: Android 16 / API 36
• Device: iOS Simulator/Android Emulator
• Node Version: v20.9.0

SDK Configuration

<Formbricks
  environmentId={process.env.EXPO_PUBLIC_FORMBRICKS_ENVIRONMENT_ID}
  appUrl="https://app.formbricks.com"
/>

Logs

The only logs available, are the ones that indicates that the action has been triggered.

JS Console Output

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.021Z [DEBUG] - Found existing configuration.

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.021Z [DEBUG] - Start setup

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.021Z [DEBUG] - Configuration fits setup parameters.

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.023Z [DEBUG] - Fetched 2 surveys during sync: Action:SurveyTrigger Expo, Init 2

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.024Z [DEBUG] - Adding event listeners

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.024Z [DEBUG] - Set up complete

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:05.634Z [DEBUG] - Check if set up

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:45.830Z [DEBUG] - Check if set up

(NOBRIDGE) LOG 🧱 Formbricks - 2026-01-08T22:21:45.887Z [DEBUG] - Formbricks: Action "Action:TriggerSurvey" tracked

Screenshots/Video

https://drive.google.com/file/d/1IIfrAk85Sft7ntqQkWdnfCuUL2YjAPfq/view?usp=sharing

Additional Context

• We've tested with multiple surveys.
• Specific survey tested in above video, has "Keep showing while conditions match" enabled.

[pandeymangg]

Hey! @omdam
I tested the React Native SDK and was able to reproduce the issue on Expo SDK 52 - the Formbricks component initializes and track() calls succeed (I can see the events logged), but the survey modal doesn't appear. It seems the WebView loads but no content gets rendered as I can see in the chrome local inspector

I also tested on Expo SDK 54 and everything worked fine there - surveys displayed correctly after tracking events.
Would upgrading to Expo 54 be an option for you? This seems like a compatibility issue between the SDK and the WebView version bundled with Expo 52.

We're continuing to investigate the root cause and will report back with more findings.

[fanion]

@pandeymangg I assume your comment was meant for me 🙂

We’d very much like to upgrade to Expo SDK 54, but unfortunately that isn’t in our pipeline for the coming months, as we have other priorities at the moment.

We’re currently using react-native-webview@13.13.1 ourselves. Since your package depends on react-native-webview >=13.0.0, that could very well be the cause.

[pandeymangg]

@fanion Thanks for the clarification!
After some debugging, I think I got close to fixing this. The issue stems from how Android's WebView handles touch events differently than iOS.
The survey overlay uses pointer-events: none in CSS, which works correctly on iOS since WKWebView respects CSS pointer events at the native layer. However, on Android, the WebView component captures touch events at the React Native level before the CSS properties are evaluated - essentially blocking all touches to the underlying app, even though the CSS says otherwise.

In my local testing, I was able to get it working using pointerEvents="box-none" on the container:

<View pointerEvents="box-none"> 
    <Formbricks appUrl={FORMBRICKS_APP_URL} environmentId={FORMBRICKS_ENVIRONMENT_ID} />
</View>

This allows touches to pass through to the app while still letting the survey receive interactions when it's actually visible.
Could you please verify this works on your end? If so, we can include a fix for this in a newer release otherwise we'll debug this more 🙏

[fanion]

@pandeymangg Sorry for the late response.

I have tested it both in the Android emulator & on my physical Android (Pixel 9a) and the workaround seems to just fine.
Thank you for prioritizing this :)

[jobenjada]

@pandeymangg let's make sure this works out of the box :)