React Native Guides Troubleshooting

Troubleshooting

Minimum System Versions or Inconsistent Pods Targets

Start with System Requirements. The application must satisfy the higher of the ComPDF native baseline and RN host requirements. Do not lower deployment targets based only on the ComPDF baseline. The current RN 0.85.3 example uses Android API 24 and iOS 15.1.

On iOS, keep deployment targets consistent across the Podfile, application Target, and Pods, and build with .xcworkspace. Do not lower the React-Codegen deployment target to bypass the current RN version's requirements.

Missing Native Methods or Version Mismatches

Confirm that the React Native package, Android SDK, and iOS Pods all use 3.2.0. Reinstall dependencies and rebuild the native application. Reloading JavaScript alone cannot add new native methods. Expo projects require native builds and cannot use Expo Go.

Compression or Reader Restoration Failures

The output path must differ from the source, with an existing writable parent directory. Save edits before processing and run only one compression task per reader. Handle cancellation using cancelled. If OPTIMIZE_RESTORE_FAILED occurs, reopen the document before continuing. See Document Compression and Optimization.

Digital Signature or LTV Failures

Check the certificate path, password, current signature-field UUID, and separate output paths. When using timestamps or collecting revocation material, ensure the services are accessible. Also check returned success, errors, and warnings. Assess material readiness and certificate trust separately. See Timestamps and Long-Term Validation.

If the issue persists, contact technical support with the SDK/RN versions, platform, sanitized error details, and reproduction steps.