Skip to content
Open Screeb

Load one fixed release of the Screeb tag in your mobile app instead of the latest one, when your organization requires an auditable payload.

The SDK renders surveys and messages with the Screeb tag, which it loads in its latest release each time your app starts. You get fixes, new question types and new features without shipping a new build. If your organization requires a fixed, auditable third-party payload, you can pin one release of the tag instead.

The setting lives in the native projects of your app, not in your shared code: the iOS and Android SDKs read it from the host app. Set it on both platforms, in these files:

Framework iOS Android
React Native ios/<YourApp>/Info.plist android/app/src/main/AndroidManifest.xml
Flutter ios/Runner/Info.plist android/app/src/main/AndroidManifest.xml
Kotlin Multiplatform iosApp/iosApp/Info.plist composeApp/src/androidMain/AndroidManifest.xml
.NET MAUI Platforms/iOS/Info.plist Platforms/Android/AndroidManifest.xml

On iOS, add the ScreebTagVersion key:

<key>ScreebTagVersion</key>
<string>0.43.0</string>

On Android, add the app.screeb.sdk.TAG_VERSION meta-data entry inside the <application> element:

<application>
<meta-data
android:name="app.screeb.sdk.TAG_VERSION"
android:value="0.43.0" />
</application>

Write the value as a full version string: Android reads a value such as 0.43 as a number, and the SDK ignores it.

The two settings are independent. If you set only one, your iOS and Android users run different versions of the tag, and a survey can behave differently on each platform.

The value is an exact version, MAJOR.MINOR.PATCH (a leading v is accepted). Ranges, latest and partial versions such as 0.43 are not supported.

To go back to automatic updates, remove the setting and ship a new build.

The version is not checked against the published releases. A version that does not exist (a typo, or a version never released) makes the tag fail to load: Screeb then stops working entirely in your app, with no survey, no message, no session replay and no error shown to your users. There is no fallback to the latest version, by design.

Before you release a pinned build:

  1. Install it with the version set.
  2. Open the app and display a survey.
  3. Check that everything you expect renders.

The published versions and what each one contains are listed in the tag changelog. Pick a version that already has every feature the surveys you plan to run use, and check the changelog again when you design a survey with a newer capability or when a fix you need ships.