feat(view-shot): render options, image disposal and crash fixes

[edusperoni]

Summary

Improvements to @valor/nativescript-view-shot from profiling an app that snapshots offscreen views many times per second. Intended for a minor release.

Crash fixes

• iOS: render with UIGraphicsImageRenderer instead of the deprecated (iOS 17) UIGraphicsBeginImageContextWithOptions. The old API raises an uncatchable NSInternalInconsistencyException on a 0×0 size or a failed bitmap allocation, and leaks its context if rendering throws. No version gate is needed: the renderer exists since iOS 10 and preferredRange since iOS 12.
• Both platforms: renderToImageSource returns null for views with no native view or an empty size (typically a missing measureAndLayout) instead of crashing. On Android, Bitmap.createBitmap(0, …) used to throw.
• Android: background views attach to foregroundActivity ?? startActivity instead of always startActivity.
• Android: disposeBackgroundView no longer throws when the view is already detached.
• Angular: captureInBackground disposes the background views and destroys the Angular view in finally, so a throwing delay callback or render no longer leaks them.

New API

• RenderOptions on every render function:
  • scale: pixels per DIP/point, defaults to the screen scale.
  • opaque.
  • range: iOS only, 'standard' (default), 'extended' or 'automatic'.
  • bitmapConfig: Android only, 'ARGB_8888' (default) or 'RGB_565'.
  • Defaults keep the previous output. The old iOS API always drew into a standard-range buffer.
• renderViewToImage(view, { width, height, host, ...renderOptions }): load, measure, render and dispose in one call.
• withRenderedImage(view, callback, options): releases the native image (Utils.releaseNativeObject) when the callback returns, or when its promise settles. Rendered pixel memory is invisible to the JS GC, so discarded images otherwise pile up until an unrelated collection runs. The README documents calling Utils.releaseNativeObject directly for manual release.
• The Angular ViewShotService forwards RenderOptions in captureInBackground and captureRenderedView.

Typing change

renderToImageSource, captureInBackground and captureRenderedView now return ImageSource | null.

Strict mode

The package (core and Angular entry point) now compiles with strict: true, so the shipped .d.ts files reflect real nullability. The only lib-check finding in strict consumers with skipLibCheck: false is TS2611 on LogicalViewContainer's ios/android getters, which core's own ProxyViewContainer raises identically.

Testing

• nx run nativescript-view-shot:build.all and lint pass (lint now warning-free).
• Typings checked from a strict consumer project: RenderOptions, renderViewToImage, withRenderedImage and the ImageSource | null return types all resolve as expected.
• Not yet verified on device. Suggested check: render a 1200×100 view 100 times in a loop and compare the memory footprint with and without withRenderedImage / scale: 1.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit bedc9b5

Command	Status	Duration	Result
nx affected:lint	✅ Succeeded	1s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-10-10 02:19:23 UTC