App Shows blank Screen when in Production Mode

Summary

The app works perfectly when i run it with expo start but as soon as i run it with expo start --no-dev --minify i get a white screen after the splash screen no matter what i do (same happen in apk stand alone builds as well). when i get this white screen i also get no errors or output in the terminal whatsoever just a blank white screen with nothing to go on to fix the problem .

i was running the app on expo SDK 41 and i upgraded to SDK 43 thinking it would solve the problem but it did nothing of the sort (after fixing all of the dependencies and upgrading i came back to the same problem on production mode runs or builds with no errors).

since : 1 - i have no output whatsoever . 2 - i’ve been working on this project for a long time .
i have no idea how to debug this or reproduce the problem in a small sample of code.

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android, iOS

SDK Version (managed workflow only)

Environment

Expo CLI 4.12.1 environment info: System: OS: Linux 5.14 Arch Linux Shell: 5.8 - /bin/zsh Binaries: Node: 16.11.1 - /usr/bin/node npm: 8.0.0 - /usr/bin/npm npmPackages: expo: ^43.0.0 => 43.0.3 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.3 => 0.64.3 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: expo-cli: 4.12.1 Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

the reason why i’m not able to do this is written in the summery…

UPDATE :

i seen to get the white screen after the splash screen on ios and i seem to get the cover screen (the screen expo uses to build my project) again after the splash screen on android -and it just gets stuck there-
also it seems so if i remove some UI elements from the Home Screen the rest of the app renders but the portion i’m removing is like the main point of the home page (the widgets are the only thing that can stay) still though without logs it’s really really hard to debug the app + why do we even have expo start --no-dev --minify if we’re not getting logs anyways ? … it really is just like a standalone build (as in not easy to debug on ?)

Issue Analytics

State:
Created 2 years ago
Comments:5

Top GitHub Comments

1reaction

dlamon1commented, Apr 5, 2022

@ayman-rahmon What was the ui issue? I am having the same issue and cannot track it down, no matter what I remove from the project.

0reactions

ayman-rahmoncommented, Nov 22, 2022

I’m sorry for the late response and I’m very sorry that you’re having this issue.

the issue was that some third party component that i used in the main screen back then caused this weird behavior for some reason. I assumed the problem happened because development mode runs on NPM and all packages that run on NPM work just fine. but once you move to the production mode you can actually see what will be packaged with the app and what can only run on NPM.

this is a huge problem when using EXPO in my opinion … you can’t really know what will work in production mode and what can only run when supported by NPM in development mode. (The same issue happened with me when i tried to use sockets. it didn’t even matter if i used Socket.io or if i used web sockets directly they just are not supported to work with expo, at least at the time they weren’t ).