[Android 14] [Samsung S22+] App icon appearing on launch screen before launch screen icon about react-native-bootsplash HOT 23 CLOSED

Other thing I just noticed. When updating my manifest according to the new README i.e. when I put android:theme="app/AppTheme" on <application> and android:theme="app/BootTheme" on <activity>, I see the splash screen switching from app icon to the one I want and I see the 'Double Splash Screen issue' on the play console

If I only put android:theme="app/BootTheme" on <application, the issue disappears

from react-native-bootsplash.

Looking back to the history of my builds on play store, it seems the double splash issue appeared when introducing this new architecture. So the is an issue with multiple res dirs on Android 14 I assume

from react-native-bootsplash.

Not able to reproduce it on Android 14:

from react-native-bootsplash.

I see that your icon is distorted, that's probably what you are seeing here:

from react-native-bootsplash.

It's only from time to time, not every time I launch the app. Can it be a Samsung thing ?
I posted this 'testapp' to not show the actual app I am working on but our logo is not distorted

from react-native-bootsplash.

Yeah, Samsung is terrible at respecting the SplashScreen API. A lot of issues are coming from them.

If you are not able to reproduce it on Pixels, I recommend you to publish the issue to https://issuetracker.google.com/issues, as we will not be able to perform magic here (the first frames are handled by the system, not your app / this library)

from react-native-bootsplash.

Ok thank you :)
To be noted that I cannot repoduce it on Android 13 even on a Samsung
So it's probably the new version of UI 6.0

from react-native-bootsplash.

Unfortunately Samsung fork a lot of Android things in OneUI, but don't provide a simulator for developers to test. I wish those phones could disappear 😅

from react-native-bootsplash.

What I find surprising is that the transition is like bad -> good (right background color) -> bad and then good
See:

from react-native-bootsplash.

Could you publish the content of your android/app directory in a zip, just in case?

from react-native-bootsplash.

Do you need something specific ? I don't think I can upload the whole content publicly

from react-native-bootsplash.

Just the content of android/app. If you can't publish it, send it to me via email (the address is available in package.json)

from react-native-bootsplash.

Just the content of android/app. If you can't publish it, send it to me via email (the address is available in package.json)

Done :)

from react-native-bootsplash.

@AlixH Another things that does not seems to happen on non-Samsung phones.

Just checked your dir, and it's kinda weird, you don't have a styles.xml in res/values, but you have one in res-core (and also have two AndroidManifest).

Could you tried with a normal architecture / a clean react-native app to be sure that this is indeed a bug and not an issue you introduced? Because, if the system pick the necessary resources before your app booting, how would it know it has to search in your custom named directories?

from react-native-bootsplash.

Can you explain why the two android:theme are important ? From my understanding, the one on <application> is enough because we already define postBootSplashTheme in the styles

from react-native-bootsplash.

If set on application theme, the splash screen will be used on new activities / dialogs by default: #516

Please fix your config according to the latest comment to see if this issue is not simply related to your file architecture.

from react-native-bootsplash.

@AlixH Another things that does not seems to happen on non-Samsung phones.

Just checked your dir, and it's kinda weird, you don't have a styles.xml in res/values, but you have one in res-core (and also have two AndroidManifest).

Could you tried with a normal architecture / a clean react-native app to be sure that this is indeed a bug and not an issue you introduced? Because, if the system pick the necessary resources before your app booting, how would it know it has to search in your custom named directories?

In build.gradle, I specify to use both directories:

 sourceSets {
        main {
            res.srcDirs = ["src/main/res-core", "src/main/res"]
        }
    }

As of the manifest, AndroidManifest.xml is generated at build time by copying AndroidManifest-core.xml and simply replacing some placeholders

I will try what you said

from react-native-bootsplash.

To be precise, it occures that the issue only happens on Release builds

from react-native-bootsplash.

Makes sense actually. Your app is defining the additional res folders, but the system is not aware of them. Closing this as following the default install does not create an issue.

from react-native-bootsplash.

In the end, the only reason I intoduced res-core is because I had no solution to avoid having git changes when generating the splash screen during build with this library because it adds the splash screen background color to res/colors
This is why I opened this other issue first #504

from react-native-bootsplash.

Jut being able to specify outputDir in the command line generator would be a massive feature

from react-native-bootsplash.

Having only one res directory does not solve the issue

from react-native-bootsplash.

In the end, the only reason I intoduced res-core is because I had no solution to avoid having git changes when generating the splash screen during build with this library because it adds the splash screen background color to res/colors

generate && git checkout path/to/the/file to reset the changes

from react-native-bootsplash.