fix(macos): guard iOS-only methods in RCTViewComponentView.mm so the file compiles on macOS

[tvinhas]

Summary

RCTViewComponentView.mm did not compile on macOS in 0.83-merge. The upstream 0.83 merge brought in new iOS-only methods that aren't wrapped in #if !TARGET_OS_OSX guards, leaving them visible to the macOS compile where they trip
duplicate-declaration errors against the existing AppKit-flavored methods in the macOS branch + use UIView / UIColor types unknown to AppKit.

Concrete errors blocking xcodebuild -scheme RNTester-macOS:

RCTViewComponentView.mm:810:3: error: unknown type name 'UIView'; did you mean 'NSView'?
RCTViewComponentView.mm:1048:4: error: expected a type (- (UIView )effectiveContentView)
RCTViewComponentView.mm:1371:11: error: unknown type name 'UIColor'; did you mean 'CIColor'?
RCTViewComponentView.mm:2412:43: error: expected a type (transferVisualPropertiesFromView:(UIView))
RCTViewComponentView.mm:2465:1: error: duplicate declaration of method 'handleCommand:args:'
RCTViewComponentView.mm:2478:1: error: duplicate declaration of method 'focus'
RCTViewComponentView.mm:2483:1: error: duplicate declaration of method 'blur'
RCTViewComponentView.mm:2490:1: error: duplicate declaration of method 'becomeFirstResponder'
RCTViewComponentView.mm:2503:1: error: duplicate declaration of method 'resignFirstResponder'

The macOS branch at lines 1846-2381 already provides AppKit-flavored versions of focus, blur, becomeFirstResponder, resignFirstResponder, handleCommand: — the duplicates after that block are iOS-canonical implementations
brought in by the upstream merge.

This PR is surgical: every change is either (a) wrapping iOS code in #if !TARGET_OS_OSX so it disappears from the macOS compile, or (b) swapping UIView* / UIColor* types for the existing fork-wide RCTPlatformView* /
RCTUIColor* compatibility aliases that resolve to the right AppKit class on macOS. No iOS behavior changes — every iOS code path executes identically before and after.

Changes (5 surgical edits)

1. Line 810 — hitTest: local var. UIView *currentContainerView → RCTPlatformView *currentContainerView. The getter (currentContainerView declared at 1107) already returns RCTUIView* which is NSView* on macOS and UIView*
   on iOS; the local just needed to match.

2. Lines 1048-1102 — effectiveContentView method. Return type UIView* → RCTPlatformView*. Wrapped the SwiftUI-filter body in #if TARGET_OS_OSX ... return self; #else ... <existing body> ... #endif. The SwiftUI-filter wrapping
   uses RCTSwiftUIContainerViewWrapper which currently assumes UIKit's UIView surface — not yet ported to macOS. macOS falls back to the trivial return self path (callers continue to work because the type is RCTPlatformView*).

3. Line 1109 — currentContainerView caller. UIView *effectiveContentView = self.effectiveContentView; → RCTPlatformView *effectiveContentView = .... Matches the updated return type from change Update readme #2.

4. Line 1371 — SwiftUI dropShadow color. UIColor *shadowColor = RCTUIColorFromSharedColor(...) → RCTUIColor *shadowColor = .... RCTUIColor is the existing @compatibility_alias defined at
   React/RCTUIKit/RCTUIKitCompat.h:25-29 (UIColor on iOS, NSColor on macOS). RCTUIColorFromSharedColor already returns NSColor on macOS, and RCTSwiftUIContainerViewWrapper.h exposes the updateDropShadow:...color: selector with both
   UIColor (iOS) and NSColor (macOS) overloads — the typed alias picks the right one per platform.

5. Lines 2412-2515 — wrap iOS-only methods in #if !TARGET_OS_OSX. Covers transferVisualPropertiesFromView:toView: (UIView-typed args), canBecomeFirstResponder (UIResponder semantics — macOS uses acceptsFirstResponder
   instead), and the duplicates of handleCommand:args: / focus / blur / becomeFirstResponder / resignFirstResponder that conflict with the AppKit-flavored versions in the macOS branch above.

Relationship to other in-flight PRs

• Depends on fix(fmt): patch base.h consteval gate via prepare_command for Xcode 26.x #2961 (fmt FMT_USE_CONSTEVAL=0) — without it, pod install+xcodebuild fails at Pods/fmt/src/format.cc before ever reaching this file on Xcode 26.x.
• Coexists with fix(macos): three Fabric focus regressions (blur, sendAccessibilityEvent, VirtualView) #2959 (three Fabric focus regressions) — that PR touches the macOS branch of this same file (lines 1886-1924) for focus behavior; this PR touches different line ranges for compile correctness. No merge conflict.

Together, #2961 + this PR + #2959 are the minimum set required for xcodebuild -scheme RNTester-macOS build to succeed on 0.83-merge for Xcode 26.x. Without this PR, the file is rejected at the type-check stage and the whole
React-RCTFabric-macOS target fails to compile.

Closes the macOS-compile half of the "Verify focus changes" + "RNTester validation" items on the Road to 0.83 tracking issue (#2901). With #2960 (pbxproj restore) + this PR + #2961, xcodebuild ... -scheme RNTester-macOS build
now completes with ** BUILD SUCCEEDED **.

Test Plan

• Before: xcodebuild -workspace packages/rn-tester/RNTesterPods.xcworkspace -scheme RNTester-macOS -configuration Debug -destination 'generic/platform=macOS' ARCHS=arm64 ONLY_ACTIVE_ARCH=YES CODE_SIGNING_ALLOWED=NO build fails at
  CompileC .../React-RCTFabric-macOS.build/.../RCTViewComponentView.o with the 9+ errors quoted above. Reproducible on a clean 0.83-merge checkout running Xcode 26.x.
• After: same xcodebuild produces ** BUILD SUCCEEDED ** and a runnable Build/Products/Debug/RNTester-macOS.app. Validated locally with Xcode 26.5 / arm64 / Debug after applying both fix(fmt): patch base.h consteval gate via prepare_command for Xcode 26.x #2961 and this PR.
• iOS regression check: every edit either swaps UIView/UIColor for RCTPlatformView/RCTUIColor (compat aliases that resolve identically to the original types on iOS) or moves iOS code inside #if !TARGET_OS_OSX. No iOS code
  path is removed; iOS RNTester build is unaffected.
• 311 warnings remain after this PR — all pre-existing on 0.83-merge (deprecation notices on AppKit APIs, "build phase runs every build" hints, etc.), unrelated to this change.

Related

• Road to 0.83 #2901 — Road to 0.83 tracking issue (closes the macOS-compile blocker for "Verify focus changes" / "RNTester validation")
• fix(fmt): patch base.h consteval gate via prepare_command for Xcode 26.x #2961 — fmt FMT_USE_CONSTEVAL=0 (prerequisite for reaching this file's compile on Xcode 26.x)
• fix(macos): three Fabric focus regressions (blur, sendAccessibilityEvent, VirtualView) #2959 — Three Fabric focus regressions (touches same file, different lines, no conflict)
• fix(rn-tester): restore RNTesterPods.xcodeproj/project.pbxproj on 0.83-merge #2960 — Restore project.pbxproj (prerequisite for any pod install on 0.83-merge)

[microsoft-github-policy-service]

@tvinhas please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.