IFU054(01) v4.0.1 (Expo)

1. Overview

v4.0.1 is the current major Expo React Native Reader SDK release for the private npm package @novarumdx/ndx-imaging-expo. It moves the Expo bridge forward from the v3.0.2 baseline to the current v4 platform line and aligns the module with the modern native Reader SDK stack on Android and iOS.

• Platform compatibility update: upgrades the Expo bridge to the Expo SDK 56 generation and updates the bridge for the React Native new architecture (Fabric / TurboModules).

• Lifecycle and UI reliability: fixes app background/resume issues on iOS and layout sizing issues affecting flexible or partial-screen reader presentations on both platforms.

• Integration baseline refresh: carries forward the modern customer integration path established in the v4 native SDK family, including current native dependency alignment and current reader-file expectations.

• Scope: this release focuses on bridge compatibility, integration reliability, and customer-visible behaviour. The host application remains responsible for workflow, permissions prompting strategy, result handling, persistence, and any external communication.

2. What’s Changed Since 3.0.2

2.1. Expo SDK 56 and React Native new architecture

• Expo SDK 56 compatibility: resolves the incompatibility in v3.0.2 with Expo SDK 56, including updated bridge behaviour required by the newer Expo and React Native toolchain.

• New architecture support: updates and verifies the native bridge for React Native’s new architecture, including Fabric renderer and TurboModules integration.

• Build and runtime alignment: the module is updated so current iOS and Android bridge code works with the newer Expo baseline rather than the earlier v3-era assumptions.

• Reader keep-awake alignment: while the reader is visible, the screen now remains awake on both platforms. iOS already received this behaviour from the inner imaging SDK, while Android required Kotlin handling in the Expo module because that inner dependency behaviour was not applied through the Android Expo integration path.

• Outcome for customers: integrations targeting current Expo applications can adopt the supported bridge rather than remaining pinned to the older v3.0.2-compatible toolchain.

2.3. Reader view layout and presentation fixes

• Flex layout fix: resolves the issue where the Expo reader view did not respect flex-based layout sizing.

• Partial-screen Android layout fix: resolves incorrect fit/fill behaviour when the reader view is hosted inside constrained or partial layouts such as split screens, embedded containers, or other non-full-screen presentations on Android.

• iOS fit positioning correction: resolves the issue where fit-mode scans on iOS were gravitated towards the lower portion of the screen.

• Outcome for customers: the reader view now behaves more predictably when embedded into real application layouts instead of assuming a simple full-screen presentation.

2.4. Lifecycle and scan completion reliability

• iOS background/resume fix: resolves the issue where the reader did not resume correctly after the app was backgrounded on iOS.

• End-of-scan freeze fix: addresses image saving and compression work that could block the main thread and cause a visible UI freeze at the end of scans on Android through the Expo integration path.

• Outcome for customers: scanning flows are more robust during app lifecycle transitions and more responsive at completion.

2.5. API and behavioural continuity from the 3.0.2 baseline

• Preserved bridge model: the package continues to expose the React Native component NdxImagingExpoView, typed callbacks such as onFrameCaptured, onComplete, and onAbort, abort control, permission helpers, and TypeScript models.

• Frame callback continuity: the v3.0.2 additive improvement that surfaced stripStatuses in onFrameCaptured remains part of the current bridge behaviour.

• Native bridge alignment: the Expo module continues to act as the JavaScript / TypeScript bridge above the platform-specific Android and iOS Reader SDKs and the shared NDX Imaging Core.

3. Fixed Bugs Included in This Release

Expo Specific

Android Inherited

iOS Inherited

4. Breaking vs. Non-breaking Summary

5. When to Upgrade

Upgrade from v3.0.2 when your application needs current Expo SDK support, when you are adopting or validating the React Native new architecture, or when you have encountered any of the known v3-era issues around lifecycle resume behaviour, flex layout handling, partial-screen rendering, or end-of-scan UI freezing.

• Especially recommended for: teams moving to Expo SDK 56, teams embedding the reader inside non-full-screen layouts, and teams affected by lifecycle, layout, or scan-completion reliability issues.

• Plan a controlled upgrade if: your integration still uses older reader JSON formats, or your mobile app stack is still pinned to the earlier Expo 52-era assumptions documented for v3.0.0 / v3.0.2.

6. Compatibility Notes

• The SDK remains a private npm package: @novarumdx/ndx-imaging-expo.

• The bridge continues to depend on supported native Android and iOS Reader SDK packages beneath the Expo module.

• The package is intended for Expo / React Native host applications, not for direct standalone end-user use.

• The SDK performs no network communication; upload, storage, workflow, and result presentation remain the responsibility of the host application.

• For the Expo SDK 56 line with the latest bundled native SDK dependencies, the supported minimum platform versions are Android SDK 26+ and iOS 16.4+.

7. Summary of Developer Actions

8. Versioning Summary

9. Known Issues

No additional Expo-specific known issues are listed in this draft note beyond normal release verification activity. Final release publication should confirm whether any verifying items remain open at release sign-off.