Unusual ghosting effect when going in and out of the app
8BallBomBom opened this issue · comments
Before submitting a new issue
- I tested using the latest release of the library, as maybe the bug has been already fixed.
- I checked for possible duplicate issues, with possible answers.
Bug summary
Not exactly sure of the cause as i haven't looked deeply yet.
But i can say the issue does not exist when this library is not being used.
When going in and out of the app you'll see a weird ghosting effect on the left of the screen.
Haven't tested with any other devices other than what i currently have on hand which is a Galaxy S9.
Library version
5.3.0
Environment info
System:
OS: Linux 6.6 Fedora Linux 39 (KDE Plasma)
CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
Memory: 19.34 GB / 31.27 GB
Shell:
version: 5.2.26
path: /bin/bash
Binaries:
Node:
version: 18.18.0
path: ~/.nvm/versions/node/v18.18.0/bin/node
Yarn:
version: 1.22.19
path: ~/.nvm/versions/node/v18.18.0/bin/yarn
npm:
version: 10.3.0
path: ~/.nvm/versions/node/v18.18.0/bin/npm
Watchman:
version: 0.0.0
path: /usr/bin/watchman
SDKs:
Android SDK:
API Levels:
- "33"
- "34"
Build Tools:
- 33.0.1
- 34.0.0
System Images:
- android-26 | Google Play Intel x86 Atom
- android-27 | Google Play Intel x86 Atom
- android-28 | Google Play Intel x86_64 Atom
- android-29 | Google Play Intel x86_64 Atom
- android-30 | Google Play Intel x86_64 Atom
- android-31 | Google Play Intel x86_64 Atom
- android-33 | Google Play Intel x86_64 Atom
Android NDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java:
version: 17.0.9
path: /usr/bin/javac
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.73.2
wanted: 0.73.2
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: false
Steps to reproduce
- Create a new RN app, basic template, currently RN 0.73.2
- Go through the basic integration steps of this library.
- Run the app and experience the issue when going in and out of the app.
- Most likely a Samsung issue as i haven't seen the same on an emulated device.
Easier to see a preview rather than just describe.
Doesn't happen with other apps and doesn't happen with a clean app without this library.
Without this library
without.mp4
With this library
with.mp4
@8BallBomBom Is it running Android 12 or 13? Because Samsung has a very bad implementation of the Android SplashScreen API on Android 12 (OneUI 4), this library already include hacks specific to this OS / version (see https://github.com/zoontek/react-native-bootsplash/releases/tag/5.1.0)
(The hack only targets Android 12 - Samsung fixed it OneUI 5 / Android 13)
Ahhh yes I was looking at that but no, it is running Android 10 with an old version of OneUI v2.5 far as I can tell 🤔
I have same issue on android emulator (Windows, Android 14) & Samsung A13 (Android 13, One UI 5.1)
Redmi 12C (Android 13, MIUI 14.0.3) - no issue