Fictura
SDK reference

iOS

What the SDK does on iOS specifically — mostly TypeScript, plus one small native module that autolinks into your build.

@fictura/sdk is almost all TypeScript. It also carries one native module, FicturaNative, in Swift with a FicturaSdk podspec. It autolinks through Expo, so run npx expo prebuild or pod install after upgrading. An app built without it, such as Expo Go, still runs, and those native features quietly turn off. On iOS it behaves as follows:

  • Device identity lives in the Keychain via expo-secure-store (accessible after first unlock), so it survives reinstalls; Android uses the SSAID via expo-application.
  • StoreKit is reached through your adapter, never directly. With react-native-purchases in the app, the SDK detects it and uses a built-in adapter. Otherwise you hand it a PurchasesAdapter wrapping whatever billing SDK you run, and purchases execute natively through it.
  • Web checkout opens Safari — the system browser, via Linking.openURL, never an in-app webview. That is the compliance-load-bearing rule; see How web checkout works.
  • Push uses Expo's push service: registerForPush() obtains the Expo token (the EAS projectId is picked up from your app config when present) and registers it. No APNs keys touch Fictura.
  • Native crashes and hangs are read from MetricKit on iOS 14+, on the next launch. The module installs no signal or exception handler, so it runs safely next to another crash reporter. See Native crashes.

Testing identity on device

Because the device id lives in the Keychain, deleting the app does not mint a new user. For QA runs set EXPO_PUBLIC_GROWTH_TEST_IDENTITY=1, which keeps the id in plain storage so an uninstall starts fresh.