[hejsztynx]

Summary

Fixes #826

With CocoaPods dynamic frameworks enabled, the build failed. Eg. by using an expo build and a plugin in app.json:

  [
        "expo-build-properties",
        {
          "ios": {
            "useFrameworks": "dynamic",
            "usePrecompiledModules": false
          }
        }
      ]

We reference an external framework UniformTypeIdentifiers in our code, and it worked with static frameworks, because this package was loaded by a different pod. When using the dynamic frameworks, we actually every pod need to have explicitly defined what frameworks it depends on, so they will be successfully resolved at runtime.

I've setup an example app with Expo SDK 58, with dynamic frameworks enabled, and the failure was gone.

After that change, our example app builds successfully with CocoaPods and SPM.

Test Plan

Setup an Expo app, and apply this patch

Compatibility

OS	Implemented
iOS	✅
Android	❌
Web	❌

Checklist

• E2E tests are passing
• Required E2E tests have been added (if applicable)

[Copilot]

🟢 Approval recommended

The narrow dependency declaration matches existing native usage and the verified fix in #826, with no unresolved findings.

No open issues 🎉

What changed in this PR

This PR fixes the iOS dynamic-framework linker failure reported in #826 by explicitly declaring the system framework already used by the native clipboard implementation.

Changes:

• Adds UniformTypeIdentifiers to the CocoaPods specification’s framework dependencies so dynamic-framework consumers can link successfully.

File	Description
ReactNativeEnrichedHtml.podspec	Declares the UniformTypeIdentifiers framework dependency.

_{Review effort: Balanced}