-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Image] Retina Assets - Image component does not resolve images with filenames that include '@' symbol #14980
Comments
When did it break? Did you upgrade from 0.46 or from an earlier version? |
I had the same issue. Upgrade from 0.44.3 |
I upgraded from 0.45.1. |
I'll check 0.46.0 right now. |
The bug exists in 0.46.0, so something changed between 0.45.1 and 0.46.0. |
I have the same problem images not loading now Icon-83.5@2x.png' as a folder: it did not contain a package, nor an index file" |
this is also blocking us. upgraded from 0.45.1 to 0.46. |
I'm having the same issues as well |
Any solution for this? Its still a blocker on 0.47.1 |
@pavanpodila Rename images. image@2x.png -> image-x2.png |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
This should remain open because it's a regression and '@' is a common character in image filenames. |
I'm having the same issues as well , version 0.49.3 |
I am facing same issue. I have invest-icon.png, invest-icon@2x.png, invest-icon@3x.png. But each time when i use require. It always show 1x or invest-icon.png image. I have tested one scenario that if i removed invest-icon.png then it will divide @2x image by 2 and show that and i delete @2x image then it will devide @3x image by 3 and use that image. I am testing Iphone 7 and 7 plus. Why it is not picking @2x. It is always trying to get 1x image.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
It's 2018 and I am seeing the exact same issue as @hassanrazakhalid and the others above described. I have import icon from `./icon.png`
<Image source={icon} /> The dimensions of I believe I followed the instructions on https://facebook.github.io/react-native/docs/image.html exactly, but either there's a small nuance I'm missing, or this is a bug. But since there's not a huge outcry it's hard for me to believe the later. |
Did some more digging.
Relevant documentation: https://facebook.github.io/react-native/docs/0.53/images.html I think it's definitely related to the move from |
LOL, so it's not a bug it's a feature! I guess it doesn't make sense to allow the '@' character in filenames if react native is going to add the character itself when choosing an image from the file system. Perhaps this can be closed then. But I'll let a project maintainer close it to be sure. |
Yup, I'm still not sure why it wasn't included in the release notes as a breaking change though. |
Is this a bug report?
Yes, this worked in previous versions.
Have you read the Bugs section of the Contributing to React Native Guide?
Yes
Environment
react-native -v
: 0.46.1node -v
: 8.1.4npm -v
: 5.2.0yarn --version
(if you use Yarn): noneThen, specify:
Steps to Reproduce
(Write your steps here:)
Expected Behavior
Image loaded correctly and displayed.
Actual Behavior
Reproducible Demo
The demo is made from create-react-native-app, eject, and react-native-git-upgrade.
https://github.com/timmywil/react-native-bug-example
I realize the workaround is simple, but I figure a regex got edited somewhere and this is a one-line fix.
The text was updated successfully, but these errors were encountered: