Accept asset catalog entries in localResources

[yusuftor]

Changes in this pull request

Generalises SuperwallOptions.localResources from [String: URL] to [String: AssetResource] so customers can register paywall assets that live inside an asset catalog (.xcassets), achieving parity with the Android SDK's PaywallResource.FromResources(R.drawable.*).

Customer ask (Pylon): customers whose assets live in .xcassets had no clean way to register them because asset catalog entries don't expose a file URL.

API

New AssetResource protocol is the dictionary's value type. Three conforming types:

• URL — existing behavior, a file on disk. Conforms out of the box, so existing call sites that assign URL dictionaries compile and behave unchanged.
• UIImage — register an in-memory image directly; served to the webview as image/png via pngData().
• CatalogAsset(name:bundle:) — deferred lookup into an .xcassets. Tries UIImage(named:in:compatibleWith:) first (Image Set, re-encoded as PNG), then falls back to NSDataAsset(name:bundle:) (Data Set, raw bytes + UTI-derived MIME type). Handles both image assets and non-image Data Sets (video, Lottie JSON, etc.).

options.localResources = [
  "hero-image": Bundle.main.url(forResource: "hero", withExtension: "png")!,
  "logo":       UIImage(named: "Logo")!,
  "hero-video": CatalogAsset(name: "HeroVideo")
]

Implementation notes

• LocalFileSchemeHandler switches on the resource type. UIImage and CatalogAsset's Image Set path resolve through UIImage.pngData(); CatalogAsset's Data Set path uses NSDataAsset with a UTI → MIME type conversion.
• UTI → MIME uses UTType.preferredMIMEType on iOS 14+ and falls back to UTTypeCopyPreferredTagWithClass from MobileCoreServices on iOS 13, so Data Sets get a real MIME type across the supported deployment range.
• ObjC keeps a URL-only shim under the same localResources name (@objc(localResources)). Asset catalog and UIImage entries are Swift-only.
• SWLocalResourcesViewController (debug view) previews URL, UIImage, and catalog entries. Non-image catalog assets (e.g. video, JSON) show their UTI and byte count instead of a blank cell.
• CatalogAsset tries UIImage(named:) before NSDataAsset so lookups against Image Sets don't trigger a CoreUI "wrong type" log warning.
• Unrelated cleanup: dropped a stale trailing_closure lint violation in ConfigLogic.swift:310 while in the area.

Tests

Extends LocalFileSchemeHandlerTests:

• URL registered through the unified dictionary still loads bytes and a MIME type.
• UIImage registered directly is served as image/png with bytes matching pngData().
• CatalogAsset whose name is missing from the bundle throws fileNotFound.
• Existing 9 tests continue to pass with the new value type.

CatalogAsset's Data Set success path isn't covered because adding a real .xcassets to the test bundle is non-trivial; the code is small (NSDataAsset.data + UTI MIME lookup) and will be exercised end-to-end via the demo app.

Checklist

• All unit tests pass (12/12 in LocalFileSchemeHandlerTests).
• All UI tests pass.
• Demo project builds and runs on iOS.
• Demo project builds and runs on Mac Catalyst.
• Demo project builds and runs on visionOS.
• I added/updated tests or detailed why my change isn't tested.
• I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
• I have run swiftlint in the main directory and fixed any issues.
• I have updated the SDK documentation as well as the online docs.
• I have reviewed the contributing guide

🤖 Generated with Claude Code

[yusuftor]

@greptileai

[yusuftor]

@greptileai

[greptile-apps]

Image-Set CatalogAsset shows "Asset not found" in debug view

configureCatalogAsset loads asset data exclusively via NSDataAsset, but NSDataAsset only resolves Data Set entries — it returns nil for Image Sets. The scheme handler in LocalFileSchemeHandler.load(resource:key:) tries UIImage(named:in:compatibleWith:) first, so an Image Set CatalogAsset is served successfully in the webview, but the debug preview shows "Asset not found" because NSDataAsset finds nothing. The fix is to mirror the scheme handler's resolution order: try UIImage(named:) first, and only then fall back to NSDataAsset.

Prompt To Fix With AI

This is a comment left during a code review.
Path: Sources/SuperwallKit/Debug/SWLocalResourcesViewController.swift
Line: 265-279

Comment:
**Image-Set `CatalogAsset` shows "Asset not found" in debug view**

`configureCatalogAsset` loads asset data exclusively via `NSDataAsset`, but `NSDataAsset` only resolves *Data Set* entries — it returns `nil` for *Image Sets*. The scheme handler in `LocalFileSchemeHandler.load(resource:key:)` tries `UIImage(named:in:compatibleWith:)` first, so an Image Set CatalogAsset is served successfully in the webview, but the debug preview shows "Asset not found" because `NSDataAsset` finds nothing. The fix is to mirror the scheme handler's resolution order: try `UIImage(named:)` first, and only then fall back to `NSDataAsset`.

How can I resolve this? If you propose a fix, please make it concise.