Closed
Labels
BugComponent: ImageComponent: ImageBackgroundPlatform: AndroidAndroid applications.Android applications.Priority: MidStaleThere 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.
Description
- Review the documentation: https://facebook.github.io/react-native
- Search for existing issues: https://github.com/facebook/react-native/issues
-
Use the latest React Native release: https://github.com/facebook/react-native/releasesI'm not using the latest release since I use it with expo (see snack down below) but I've read the latest changelogs and saw nothing related to this problem (maybe I'm wrong, please point it out if so)
Environment
I don't think it would help a lot but here it is:
React Native Environment Info:
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 1.39 GB / 7.88 GB
Binaries:
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338
Description
ImageBackground does not fill the full width on Android when the app is either reloaded or paused and resumed. When I fully close the app and reopen it, the problem disappears.

After pause/resume or hot reload, the first element should fill its width.
No problem on iOS.
Reproducible Demo
Reacted by Siyamak Fazleelahi
Metadata
Metadata
Assignees
Labels
BugComponent: ImageComponent: ImageBackgroundPlatform: AndroidAndroid applications.Android applications.Priority: MidStaleThere 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.

Activity
patrickkempff commentedon Feb 17, 2019
It seems somehow that the asset is not repeated despite
resizeMode="repeat"SiSa68 commentedon Apr 24, 2019
I have same issue with RN@0.59.4 on android
I also have this problem when keyboard appears or when I resize my app size
stale commentedon Aug 2, 2019
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
stale commentedon Aug 9, 2019
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.