React Native and Expo Troubleshooting

# For React Native
rm -rf node_modules
npm cache clean --force
npm install

# For Expo
expo r -c

# For React Native
npx react-native run-ios
npx react-native run-android

# For Expo
expo run:ios
expo run:android

const { getDefaultConfig, mergeConfig } = require("@react-native/metro-config");
const nodeLibs = require("node-libs-react-native");

const config = {
  resolver: {
    extraNodeModules: {
      ...nodeLibs,
      crypto: require.resolve("react-native-quick-crypto"),
      buffer: require.resolve("@craftzdog/react-native-buffer"),
    },
  },
};

module.exports = mergeConfig(getDefaultConfig(__dirname), config);

import PolyfillCrypto from "react-native-webview-crypto";

export default function App() {
return (
<>
  <PolyfillCrypto />
  {/* Your app components */}
</>
);
}

</Accordion>

<Accordion title="WebCredentials Configuration">
**Error**: Passkey functionality not working. Errors related to `ASAuthorizationController` or `ASWebAuthenticationSession` on iOS and `CredentialManager` on Android.

**Solution**:
Passkeys requires configuring both the iOS and Android environments with the Para associated domains and web credentials.
Please check Step one of the Project Setup section for the <Link label="React Native" href="/v2/react-native/setup/react-native#add-para-shim" /> and <Link label="Expo" href="/v2/react-native/setup/expo#import-required-shims" /> setup guides for detailed instructions.

</Accordion>

<Accordion title="Apple App Site Association">
**Error**: Passkeys not functioning despite correct configuration.

**Solution**: Ensure your app's bundle identifier and team ID are registered with Para.

<Info>
Contact Para support to associate your app correctly. Provide your app's bundle identifier and team ID. You can find your team ID in the Apple Developer portal.
</Info>

</Accordion>

<Accordion title='Android: "RP ID cannot be validated" (Error 50152)'>
**Error**: `{"error": "Native error", "message": "Error: [50152] RP ID cannot be validated."}`

This is an Android-specific error from Google Play Services indicating your app's signing certificate doesn't match what's registered in the Digital Asset Links for Para's domain.

**Common causes:**
- **Debug vs release key mismatch**: Debug builds use `~/.android/debug.keystore` while release builds use your production keystore. The SHA-256 fingerprint registered in the Developer Portal must match the keystore used to sign the build you're testing.
- **Verification still pending**: After registering your SHA-256 fingerprint, Google can take up to 24 hours to verify. Check the status in the <Link label="Developer Portal" href="https://developer.getpara.com" /> under your API key's Native Passkey Configuration.
- **Incorrect fingerprint**: Verify you copied the correct SHA-256 fingerprint (not SHA-1 or MD5).

**Solution**: Get the correct fingerprint for your current build type and register it in the Developer Portal:
```bash
# Debug builds
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

# Release builds
keytool -list -v -keystore <your_keystore_path>

cd ios
pod install
cd ..
npx react-native run-ios