IFU040(01) v3.0.1

1. Overview

This is a patch release for the NovarumDX Reader SDK addressing a critical bug fix on Android and a minor bug fix on iOS. The Android release (3.0.1 Android Core) resolves a high-severity usability issue where the scan wireframe overlay disappeared after app backgrounding, which could lead to invalid or failed test results. The iOS release (3.0.1 iOS Core) addresses a missing data field in the onFrameCaptured callback. Only the iOS version (3.0.1 iOS Core) is provided as a customer-facing release; the Android version (3.0.1 Android Core) is an internal development version only.

2. New Features (Shared)

There are no new shared features in this release. All changes are bug fixes specific to individual platforms.

3. Breaking vs. Non-breaking Summary

4. When to Upgrade

Recommended For:

• Android integrations where users may background the app during scanning (for example incoming calls, notifications) — the wireframe overlay fix prevents misalignment and invalid test results.

• iOS integrations that consume the onFrameCaptured callback and require the strip status list data for test-side logic or diagnostics.

• Any integration targeting Android that requires compliance with 16 KB page-size restrictions and SVG visualisation, as previous versions cannot be used.

Not Required For:

• iOS integrations that do not use the onFrameCaptured callback or do not require strip status data.

• Expo integrations — the Android wireframe bug does not manifest in the Expo lifecycle, and the iOS callback fix will be delivered in a separate Expo Core release (3.0.2 Expo Core).

5. Compatibility Notes

• Android: No changes to minimum toolchain requirements from v3.0.0. Existing build configurations are fully compatible.

• iOS: No changes to minimum Xcode or Swift version requirements from v3.0.0. Existing build configurations are fully compatible.

• Expo: This release does not include an Expo SDK update. The iOS callback fix will be delivered in 3.0.2 (Expo Core). The Android wireframe bug does not affect Expo due to its different lifecycle handling.

6. Summary of Developer Actions

7. Platform-Specific Notes

7.1. Android — Release Notes (Internal Development Version)

7.1.1. Wireframe Overlay Fix After App Backgrounding

Changed: When the app was backgrounded during a scan and then foregrounded, the wireframe overlay used for cassette alignment would disappear and not return. The overlay view is now re-initialised when the layout has previously been calculated, ensuring it is always restored on resume.

Developer Action: Update the Reader SDK Android Core dependency to v3.0.1. No code changes are required — the fix is entirely internal to the SDK.

Impact Analysis: This was a critical usability bug with a very high reproduction rate and met the internal hot-fix threshold. Without the wireframe, users could misalign the test cassette, leading to invalid or failed test results with potential regulatory implications for diagnostic use. The fix resolves the underlying defect and has been assessed as acceptable under the applicable software lifecycle and risk management processes. Verification included risk assessment, unit tests, merged code branch, code review, and manual test reports.

Note: This bug does not affect the Expo SDK due to its different lifecycle handling. Related Expo sub-tasks were archived after testing confirmed the issue was not present.

7.2. iOS — Release Notes

7.2.1. Strip Status List Added to onFrameCaptured Callback

Changed: The onFrameCaptured callback was missing the strip status list field as specified in the original requirements. This field is now included in the callback payload.

Developer Action: No mandatory code changes. The strip status list is now available in the onFrameCaptured callback payload. If your integration requires strip status data during frame capture, update your callback handler to read the new field. This is optional but recommended when you need more detailed diagnostics or side-channel logic.

Impact Analysis: This is an additive, non-breaking change. Existing integrations that do not consume the strip status list will continue to function without modification. The issue was assessed as low severity with a low risk score. The same fix will also apply to the Expo SDK in a future release (3.0.2 Expo Core) and is currently in verification status.

7.3. Expo — Release Notes

No Expo SDK changes are included in this release.

• The Android wireframe overlay bug does not affect Expo due to its different lifecycle handling.

• The iOS onFrameCaptured callback fix will be delivered in a future Expo Core release (3.0.2 Expo Core).