Skip to content

fix(ios): forward headers from ImageSource in Image component - #59411

Open
lewando54 wants to merge 1 commit into
react:mainfrom
lewando54:fix/ios-headers-not-being-sent-in-image
Open

lewando54 wants to merge 1 commit into
react:mainfrom
lewando54:fix/ios-headers-not-being-sent-in-image

Conversation

@lewando54

Copy link
Copy Markdown

Summary

On iOS, when headers are provided in an ImageSource prop (either as an object or as the first element of an array source), they were not extracted or passed to nativeProps.headers. As a result, custom request headers defined on image sources (such as Authorization) were not forwarded to native on iOS, unlike Android which handles this in Image.android.js (see #56905).
This updates Image.ios.js to extract headers from resolvedSource and attach them to nativeProps.headers if present, aligning iOS with Image.android.js.

Changelog:

[IOS] [FIXED] - Forward headers from ImageSource in Image component

Test Plan:

  • Flow checks pass: yarn flow (0 errors)
  • Prettier & ESLint checks pass
  • Existing Image tests pass: yarn test packages/react-native/Libraries/Image

Summary:
On iOS, when \headers\ are provided in an \ImageSource\ prop (either as an object or as the first element of an array source), they were not extracted or passed to \
ativeProps.headers\. As a result, custom request headers defined on image sources (such as \Authorization\) were not forwarded to native on iOS, unlike Android which handles this in Image.android.js.

This updates \Image.ios.js\ to extract \headers\ from \
esolvedSource\ and attach them to \
ativeProps.headers\ if present, aligning iOS with \Image.android.js\.

## Changelog:

[IOS] [FIXED] - Forward headers from ImageSource in Image component

Test Plan:
- Verified Flow check passes cleanly (\yarn flow\)
- Verified ESLint and Prettier pass on modified file
- Verified existing Image tests pass (\yarn test packages/react-native/Libraries/Image\)
@meta-cla

meta-cla Bot commented Oct 23, 2026

Copy link
Copy Markdown

Hi @lewando54!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla

meta-cla Bot commented Oct 23, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 23, 2026
@facebook-github-tools facebook-github-tools Bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Oct 23, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant