Repository navigation
Closed as not planned
Labels
Component: ImageNeeds: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.Platform: iOSiOS applications.iOS applications.StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.Type: Unsupported VersionIssues reported to a version of React Native that is no longer supportedIssues reported to a version of React Native that is no longer supported
Description
Description
The image component of ios displays local images in disorder.I'm sure the local path of the Image is ok.It is not necessary, and sometimes it is displayed incorrectly.
For example:
<Image source={require('@assets/icons/m_tabbar/home_select.png')}/>
In most cases it show normal, but sometimes It will display other pictures, even though my picture path has always been this “require('@assets/icons/m_tabbar/home_select.png')”. This is very strange!!
Steps to reproduce
<Image source={require('@assets/icons/m_tabbar/home_select.png')} style={{ width: imageSize, height: imageSize, tintColor: color }} tintColor={color} />
React Native Version
0.76.9
Affected Platforms
Runtime - iOS
Output of npx @react-native-community/cli info
System:
OS: macOS 15.5
CPU: (11) x64 Apple M3 Pro
Memory: 43.40 MB / 36.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 23.5.0
path: /usr/local/bin/node
Yarn:
version: 1.22.22
path: /usr/local/bin/yarn
npm:
version: 10.9.2
path: /usr/local/bin/npm
Watchman:
version: 2025.04.28.00
path: /usr/local/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.5
- iOS 18.5
- macOS 15.5
- tvOS 18.5
- visionOS 2.5
- watchOS 11.5
Android SDK:
API Levels:
- "23"
- "26"
- "27"
- "28"
- "29"
- "30"
- "31"
- "32"
- "33"
- "34"
- "35"
Build Tools:
- 28.0.3
- 29.0.2
- 29.0.3
- 30.0.2
- 30.0.3
- 31.0.0
- 33.0.0
- 33.0.1
- 34.0.0
- 35.0.0
System Images:
- android-34 | Google Play Intel x86_64 Atom
Android NDK: Not Found
IDEs:
Android Studio: 2024.3 AI-243.24978.46.2431.13363775
Xcode:
version: 16.4/16F6
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.12
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 15.0.0
wanted: 15.0.0
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.9
wanted: 0.76.9
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
no error
MANDATORY Reproducer
no git url
Screenshots and Videos
image show wrong:
the image should show that:
Metadata
Metadata
Assignees
Labels
Component: ImageNeeds: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.Platform: iOSiOS applications.iOS applications.StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.Type: Unsupported VersionIssues reported to a version of React Native that is no longer supportedIssues reported to a version of React Native that is no longer supported


Activity
react-native-bot commentedon Jun 3, 2025
Warning
Unsupported version: It looks like your issue or the example you provided uses an unsupported version of React Native.
Due to the number of issues we receive, we're currently only accepting new issues against one of the supported versions. Please upgrade to latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If you cannot upgrade, please open your issue on StackOverflow to get further community support.
react-native-bot commentedon Jun 3, 2025
Warning
Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:
You can read more about about it on our website: How to report a bug.
react-native-bot commentedon Jun 3, 2025
Warning
Unsupported version: It looks like your issue or the example you provided uses an unsupported version of React Native.
Due to the number of issues we receive, we're currently only accepting new issues against one of the supported versions. Please upgrade to latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If you cannot upgrade, please open your issue on StackOverflow to get further community support.
devanshsaini11 commentedon Jun 3, 2025
@sunny635533 Can u verify this on latest react-native-version
0.79.x? If the issue persists kindly provide a valid repro using Reproducer Template.react-native-bot commentedon Jun 28, 2025
This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.
react-native-bot commentedon Jul 5, 2025
This issue was closed because it has been stalled for 7 days with no activity.
sunny635533 commentedon Jul 7, 2025
There is still this mistake in 0.79.3
Gp2mv3 commentedon Sep 10, 2025
I've the exact same issue on 0.80.3. 1 out of 10 the images are mixed, the rest is displayed correctly.
It seems to affect jpg and png, but not svg and the mixed images are always the same.
Did you find a solution ?
sunny635533 commentedon Sep 11, 2025
Using the FastImage component of the react-native-fast-image third-party library can temporarily avoid this problem.
Tadeo-Guerstein commentedon Apr 15, 2026
Hello, I'm having the same issue, it happens with Image component and with ImageBackground. Couldn't find the problem. The versions that i have are:
Also i have the newArch enabled. Did you or someone else found a solution apart from using FastImage?