- Home /
Android splash screen not working
I just started working with the new splash screen customization. I have a problem with a custom logo on android where the logo I selected just doesn't show. When I open the app I see a white screen for about 5 to 10 seconds and then the app just starts. The logo is not visible at all, but when I press the preview button in the player settings I get the correct animation I want.
These are my splash image settings:
Anyone got an idea of what might be wrong? Many thanks in advance.
Came looking for a similar issue, but in my case I'm not seeing the default Unity splash screen on Android using 5.5.0f3 (but pretty sure I wasn't seeing it for this project in 5.3.4f1 either).
I am having the same issue on 5.5.2f1. Does someone know if this is fixed in 5.6?
Answer by Gamerdrill · Apr 28, 2017 at 06:02 AM
Hello, I had the same problem, I do not know exactly why this happens, but I think probably the android can not load correctly, because it gets very heavy, so I managed to solve this problem by making a scene with just an initial image of my game, as if it were a loading screen, I placed a timer and then loaded the scene from the game menu.
So the splash screen loaded normal.
I solved the issue by adding an empty scene. Should have posted my own answer but here you go.
Do you mean you just created an empty scene and included it in the build, or like Gamerdrill mentioned above with making your own custom splash screen and then loading your main menu?
I think he just put a scene with nothing and included it as the first scene in the build, because the important thing is to have a very simple scene to load after the splash screen
Answer by roeezi · Jun 09, 2017 at 08:58 PM
I know a lot of time passed, but I'll try to answer anyway. I think the problem was there because the opacity of the overlay is set to 0. Therefore, the logos are fully transparent and won't be visible, and you'll be left only with the white background. I can't check it at the moment, so I'm not 100% sure this is the cause, but this is my guess :)
Answer by Kailric · Apr 27, 2017 at 08:00 AM
I am having the same issue on 5.5.2f1. Does someone know if this is fixed in 5.6?