Compatibility

Each version of the Contentsquare bridge will be linked to specific, fixed versions of each native SDK. In order to make that clear, here is a compatibility table to consider when choosing your version of the bridge. Refer to the React Native Bridge Changelog to know what the changes are for each version.

Bridge Version	iOS SDK Version	Android SDK Version	Min React Native Version	Max React Native Version
4.5.0	4.32.0	4.27.0	0.70.0***	0.74.x
4.4.0	4.31.2	4.27.0	0.70.0***	0.73.x
4.3.1	4.30.2	4.26.0	0.65.0**	0.73.x
4.2.0	4.29.1	4.24.0	0.65.0**	0.73.x
4.0.1	4.27.0	4.23.1	0.65.0**	0.73.x
3.9.0	4.27.0	4.23.1	0.65.0**	0.72.x
3.8.0	4.25.2	4.20.0	0.65.0**	0.72.x
3.6.1	4.24.0	4.20.0	0.65.0**	0.72.x
3.5.0	4.23.0	4.19.0	0.65.0**	0.71.x
3.4.0	4.22.1	4.18.1	0.59.0*	0.71.x
3.3.1	4.20.0	4.15.0	0.59.0*	0.71.x
3.2.0	4.20.0	4.15.0	0.59.0	0.71.x
3.1.0	4.18.0	4.15.0	0.59.0	0.70.x
3.0.0	4.17.0	4.14.0	0.59.0	0.70.x

*make sure to add this configuration if your RN version is below 0.70.0

**make sure to add this configuration to the Android app if your RN version is between 0.69.0 and 0.70.0, and this configuration to the Android app if your RN version is between 0.65.0 and 0.68.0.

***we support all React Native versions that are currently maintained and listed on the official React Native documentation.

Known limitations and recommendations

For React Native project below 0.70.0

If you have a React Native version below 0.70.0, you must add this specific configuration inside your metro.config.js file

module.exports = {
  // ...your current configuration
  // add the code below
  resolver: {
    sourceExts: ['js', 'jsx', 'json', 'ts', 'tsx'],
  },
};

For React Native project between 0.69 - 0.70

For React Native project between 0.65 - 0.68

Use of PanResponder

If you are using PanResponders in your app, a bug might appear on the element implementing it where it will only move for about a second and then freeze. This bug is caused by a conflict between the React Native SDK and our Bridge related to tracking swipe events. May you encounter this bug, the current workaround is to stop the Contentsquare tracking when the pan gesture starts, and resume it as the gesture ends, as follows:

const panResponder = useRef(
  PanResponder.create({
    [...]
    onPanResponderGrant: (evt, gestureState) => {
 Contentsquare.stopTracking();
 [...]
    },
    onPanResponderRelease: (evt, gestureState) => {
 Contentsquare.resumeTracking();
 [...]
    },
    [...]
  })
).current;

Note that, although this workaround fixes the bug, applying it means that swipes on view using the PanResponder won’t be tracked by Contentsquare.