Skip to main content
You might come across some issues when integrating our client. Here are some common cases and how you can handle them:

​
Something is wrong but you cannot see any logs

We have a debug mode on the client that will output logs to the console. You can enable it by setting the debugMode prop to true when initializing the client. You can control whether to enable it for the message transport and the webview separately. 
createClient({
    environmentId,
    debug: {
      messageTransport: true,
      webview: true
    },
    ...
  })

​
After installing a new package, app fails to initialize with error “Maximum call stack size exceeded”

We have noticed this might happen with some packages due to import order complications. In order to fix this, please ensure you are importing from our @dynamic-labs/ packages before you import other react native related libraries. Known libraries with this issue for now include only react-native-gesture-handler.

​
Expo SDK 54: Pod install fails with “Unable to find a specification for RCT-Folly” error

When using the React Native SDK with Expo SDK 54, you may encounter a pod install failure with the following error: 
Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Unable to find a specification for `RCT-Folly` depended upon by `react-native-passkey`

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

pod install --repo-update --ansi exited with non-zero code: 1
Temporary Fix: Override the react-native-passkey version to 3.3.1 in your package.json:
  • npm
  • pnpm
{
  "dependencies": { ... },
  "devDependencies": { ... },
  "overrides": {
    "react-native-passkey": "3.3.1"
  }
}
After adding the override, run your package manager’s install command and then retry pod install.