Embed react-native-bootsplash lite module

[zoontek]

Details

Following #5620

Has the issue still seems present, this PR embed a minimalistic version of the library, hybrid between v3 / v4.
iOS module is based on react-native-bootsplash v4 (meaning it uses RCTRootView.loadingView instead of a UIViewController), Android module is based on v3 (meaning it doesn't use the new SplashScreen API).

But, as opposed to the "full" module, this one is tailored to be as minimal as possible (for your needs):

• The show method does not exists
• No more promises or tasks queue
• No more pause when the app is in background
• No transitioning status on getVisibilityStatus
• 10 secs after the RCTContentDidAppearNotification native event, hide is called no matter what, as a safety measure (👉 this value could be adjusted)

I also updated react-navigation + react-native-screens to the latest versions to prevent some issues (as react-native-screens is enabled by default since 3.0.0 and use native stacks, it's not safe to stay on a version that old, see the changelogs), and fixed the initial loading screens background colors.

Fixed Issues

#5620 (maybe? reproduction steps are not known)

Tests

• Starts the app on iOS, check if the splash screen is visible then disappear
• Retry by starting the app using a push notification
• Retry by putting the app on background before the app init, then put the app on foreground again

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

iOS

Android

[roryabraham]

Hi @zoontek, feel free to merge main into this branch to fix your merge conflicts and the failing tests.

[zoontek]

@roryabraham Done ✅

[NikkiWines]

Sorry for the delay @zoontek - I've been traveling this week and will try to get to this early next week!

[marcaaron]

Took a quick look at @NikkiWines request. Seeing as we are updating react-navigation it would be great if we could do some quick testing on web, desktop, mobile web. The rest of these changes look pretty legit (though someone who is more familiar with native iOS and Android should maybe review).

[Julesssss]

I think you'll need to clear the conflicts and rerun pod install.

[zoontek]

@Julesssss Done ✅

[NikkiWines]

minor style suggestions but overall looks good.

cc: @marcaaron or @roryabraham not sure if either of you wanted to give this one more once over before we

[zoontek]

@NikkiWines I pushed the changes.

[NikkiWines]

👍 Looks good

[NikkiWines]

@zoontek, I've been holding off on merging this because of the increase of discussion in the main issue but was wondering if you think we should just go ahead and see if this resolves the issue.

I'm also happy to hold off for now and see if any of the new voices in that conversation have any suggestions.

[zoontek]

@NikkiWines As there is still no reproduction steps, I would recommend merging it and internal testing, yes 🙂

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by @NikkiWines in version: 1.1.31-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by @AndrewGable in version: 1.1.32-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅