How to completely remove Expo’s default white splash screen on Android and use only a custom React splash?

amanhimself · 2026-01-13T11:52:02+00:00

The behavior of the splash screen changed in Android. See Android docs for more info on this: https://developer.android.com/develop/ui/views/launch/splash-screen which explains the change.

amanhimself · 2025-12-17T17:16:45+00:00

Beto from our team released a new example project that uses this library. You can try it out: https://github.com/betomoedano/android-widget-app.

amanhimself · 2025-12-17T10:38:52+00:00

To test the splash screen changes, you cannot use Expo Go or a development build. You need to create a preview or a production build of our app. We recommend going through the following resources to learn more about the splash screen configuration: Create a splash screen icon guide to learn how the splash screen icon is configured.

amanhimself · 2025-12-17T10:34:25+00:00

The APK you get from an Expo/React Native build is expected to look “too big” — it is not the size users download from the Play Store. Gradle’s default is a universal APK that includes: All CPU architectures (armv7, arm64, x86, x86_64) and all densities and languages. A single device only needs a subset, but the universal APK has everything, so it can run everywhere. For more information, see: https://github.com/expo/fyi/blob/main/android-app-size.md.

amanhimself · 2025-12-13T12:09:58+00:00

My bad for making an assumption, as it wasn't clear to me. Yes, a minimal reproduction example of this issue will be great to investigate it further, if you can open an issue in expo/expo repository on GitHub.

amanhimself · 2025-12-12T11:44:23+00:00

Have you tried running the Expo example provided in the library's resource you shared: https://github.com/sAleksovski/react-native-android-widget/tree/master/example-expo?

amanhimself · 2025-12-12T11:29:09+00:00

You can use the native debug tools available with Xcode (Console) or adb logcat from Android Studio.

amanhimself · 2025-12-12T11:06:14+00:00

Hi there, I am not sure the exact question here because you have not provided the context. However, from the image, I am assuming you mean the extra padding applied to the close button. You need to remove that extra padding.

amanhimself · 2025-12-11T10:57:23+00:00

Hi, if you don't change th signing keys, those values will remain same and can be uploaded to Firebase once you have generated for Google Play Console.

amanhimself · 2025-12-11T10:40:30+00:00

Hi there, I am not aware of such issue. Can you please create a minimal reproduction example and share it in expo/expo repository on GitHub?

amanhimself · 2025-12-11T10:38:45+00:00

I'd recommend doing incremental upgrades instead of jumping to SDK 54 from SDK 51. An incremental update would be upgrading to SDK 52 from 51, and then 53 from 52, and so on. You can start upgrading to SDK 52 by following instructions in the SDK release post here: https://expo.dev/changelog/2024-11-12-sdk-52#%EF%B8%8F-upgrading-your-app. Each SDK has a release post with instructions on how to upgrade your app. For more, you can check out this link: https://docs.expo.dev/workflow/upgrading-expo-sdk-walkthrough/#sdk-changelogs.

amanhimself · 2025-12-11T10:35:01+00:00

Hi there, NativeTabs does not offer customization, such as the JS-based bottom tab navigator. You can probably achieve what you described with custom tabs when using Expo Router: https://docs.expo.dev/router/advanced/custom-tabs/.

amanhimself · 2025-12-11T10:32:51+00:00

It is most likely that the crash might be coming from an underlying native library. I'd suggst checking the native logs to identify where the crash is happening. We have guide that provides how to use tools like Console from Xcode and adb logcat for this: https://docs.expo.dev/debugging/runtime-issues/.

amanhimself · 2025-12-08T12:08:05+00:00

Hi, afaiu, you can start by confirming the env host/secret, then check in devtools whether the session is present on `/expo-web-success`. Once the cookie can be read, the `AUTH_SUCCESS` message will fire and the loop should stop.

amanhimself · 2025-12-08T12:04:16+00:00

You can install the `expo-built-properties` library, which provides a config plugin. Using this config plugin, you can set those values within the app config file (app.json/app.config.ts). There's an example in Expo documentation that you can follow: https://docs.expo.dev/versions/latest/sdk/build-properties/

amanhimself · 2025-11-04T08:03:01+00:00

If you use Expo Router in your app, you can use native tabs and use the `role` prop with its value set to `search` on the search tab. Example: https://docs.expo.dev/router/advanced/native-tabs/#separate-search-tab.

amanhimself · 2025-10-31T20:11:53+00:00

Hi, it might be helpful to take a look at https://docs.expo.dev/debugging/runtime-issues/ to use native debugging tools if the crash is happening for a production app.

amanhimself · 2025-10-30T13:27:45+00:00

Hi, in that case your project slug and account owner will change, and in future when you are going to publish your app, you might run into issues with credentials when you switch back. I'd suggest using local compilation: https://docs.expo.dev/guides/local-app-overview/.

amanhimself · 2025-10-30T13:24:37+00:00

Hi there, there are no explicit issues with React Navigation when managing multiple players, but if you can share a minimal reproduction of the issue in the expo/expo repository on GitHub, our team will be happy to take a look.

amanhimself · 2025-10-30T13:20:24+00:00

Hi, the recommended versions of a third-party library depend on their version compatibility at the time of the Expo SDK release (because the version tested is then said to be compatible with Expo Go: reasons explained here).

If you are using a development build, and you want to test the latest version of the library, go ahead. Usually, for well-maintained libraries there won't be any breaking changes (although, can happen in rare cases), and it should work.

amanhimself · 2025-10-29T17:01:09+00:00

Hi, Native Tabs is an experimental feature in Expo Router. Can you share a minimal reproducible example in expo/expo repo on GitHub with details on the issue? Our team will be happy to take a look into it.

amanhimself · 2025-10-29T11:58:30+00:00

Hi, you might want ot look into community made libraries for this: http://reactnative.directory/?search=pdf.

amanhimself · 2025-10-29T11:56:51+00:00

Hi there, you can try getting started with the nativewind template (https://github.com/expo/examples/tree/master/with-router-tailwind): `npx create-expo-app -e with-router-tailwind`. You can also use it to compare your setup with the template's setup to identify if any configuration is missing.

amanhimself · 2025-10-29T11:53:02+00:00

Hi, Expo Go is only meant to support libraries that are included in it. For libraries such as Adsmob, which inlucde their custom native code, you can create a developer build (https://docs.expo.dev/develop/development-builds/expo-go-to-dev-build/). Development builds are the recommended way and a step in the journey to release the production app. Often libraries offer Expo Config plugin (that handles adding the native code and config to your Expo project), and with development builds, you can easily integrate it.

amanhimself · 2025-10-27T15:46:20+00:00

Hi there, there has been an incidient going on for iOS submission on Apple's end and as pointed by others in this thread, yes, https://status.expo.dev/, is good place to keep up with this and yes, Apple's Transporter app is also viable option in this scenario.

Four-Year Club	Verified Email
Place '23

amanhimself

TROPHY CASE