-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] Removing Deprecated Manifest Splash results in blank screen and prevents the app from starting #93668
Comments
Hi @danger-ahead, thanks for filing the issue. May I know what device(s) you experienced this issue with? Thank you |
Hi, it's a Also I found 2 more cases of users having this issue: |
@danger-ahead, do you experience it on any other device apart from the I tested on a |
I ran the tests again on the following devices:
|
This issue could be affecting a small group of devices running android 11, although, there's a chance that it also affects devices running other versions of android, we just haven't found a device that reproduces at this point.
✅ : works just fine Labelling for further investigation as I'm unable to reproduce locally. |
Same Issue on my Android M31s Android 11 UI3.1 Core. |
I'm seeing this on a Galaxy s10+ (android 11). |
The same problem on Samsung Galaxy Tab A Android 11. Recently created an issue #95032 |
I had the same bug on my Galaxy a20. |
Seeing this on a Galaxy M31 |
Similar issue on a Samsung Galaxy A51 (SM-A515F/DSN) running Android 11 & One UI 3.1 The console gets flooded by this message during initial app launch but the app works fine afterwards and the message flood stops. Flutter doctor
|
Same bug on my Galaxy M21s. |
I can confirm this same issue. I only ever emulate on real devices, currently using Galaxy S10 Ultra for phone size and a Galaxy A7 tab for large screen. |
Same issue here. |
Same issue with Galaxy S20U (Android 12). Only in release mode, not in debug. |
@stepanzarubin which JSON? |
Tested on a physical device - Galaxy A50 running on One UI 3.0 based on Android 11 The same message as others 👇🏽is flooded to the console before the first screen is drawn but after it is drawn the "flooding" stops.
|
As you may remember, the following deprecated warning console log message was found on projects created before Flutter 2.8. W/FlutterActivityAndFragmentDelegate(26742): A splash screen was provided to Flutter, but this is deprecated. See flutter.dev/go/android-splash-migration for migration steps. It says that the deprecated warning message will be dismissed when the following XML lines 2 are removed from the AndroidManifest.xml file. <meta-data
android:name="io.flutter.embedding.android.SplashScreenDrawable"
android:resource="@drawable/launch_background"
/> This XML line 2 has already been removed in Flutter 2.8.1 version. Also, the following console log message appears on every new Flutter 2.8.1 project. I tested it on Samsung Note 9 and Galaxy A10. 130
I/ViewRootImpl@ca6d5b1[MainActivity](29058): [DP] cancelDraw io.flutter.embedding.android.FlutterActivityAndFragmentDelegate$2@1a21bed isViewVisible: true
140
I/ViewRootImpl@ca6d5b1[MainActivity](29058): [DP] cancelDraw io.flutter.embedding.android.FlutterActivityAndFragmentDelegate$2@1a21bed isViewVisible: true However, when I replaced the two XML lines in AndroidManifest.xml as before, the "cancelDraw" console log message disappeared (credit - mzohren). Also, the deprecated warning console log message that came before Flutter 2.8 is not displayed. I also changed the splash screen of the project with the flutter_native_splash package and so far no problem. |
I have what I believe is a fix for this issue, call it trail and error. but having released to the play store recently required me to add a few SDK Tools to Android Studio and also upgrade a few to latest. The issue has now disappeared on all my Samsung Devices. My Android studio currently has: CMake and NDK were the 2 I had to install for Play Store. Also recently changed to a windows 11 pro i9 XPS but this shouldn't make a difference |
I was referencing any potential bug in the user app. It happened for me for the second time, and after looking carefully into the console, I have found this:
So the reason of this issue can be not the device type, or not only. |
For those having issue with a specific device, they could use https://awsdevicefarm.info in order to reproduce it. (They have the Samsung S10e for exemple) |
Following this thread |
I don't understand why this issue has been closed if it hasn't been solved yet? |
Hi @andrefedev, this issue is still open |
same issue on samsung galaxy note 20 ultra |
@lukas5450 the problem persists updating to Flutter 3.0? |
@andrefedev yup, tested in Google Pixel 2 XL. Stuck at blank white screen. As soon as I put back the deprecated manifest, it went back to normal. |
@GaryQian if this is happening on Pixel devices too, it is not a device specific bug, it seems. |
Same here, Samsung Galaxy A50 with Android 11 |
same issue, same device |
adding these lines to AndroidManifest.xml file solved this issue for me: but a warning appeared on Run console: credit to @Waruna-Kaushalya |
Same issue with Galaxy Note 10 |
cc @camsim99 |
Same issue Galaxy Tab S6 Lite |
There are two separate issues here: Issue 1: The warning was added by Samsung and is not inherently an issue. It perfectly corresponds to the delay that is invoked by Flutter to wait for the Flutter UI display to load before drawing the If you see the warning, but the Flutter UI does eventually display, please report any further issues to: #111593. Issue 2: App stalls on blank screen and does not display Flutter UI We have not been able to reproduce this and will need more information to debug this further. It is an error that may/may not correlate with the warning. The old splash screen flow essentially hid the error, which is what made this error of the blank screen seem related to the splash screen. Please report any further issues to: #111594. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Description:
[Can be reproduced on Samsung OneUI 3.1 Core devices]
Steps to Reproduce
flutter create bug
flutter run
on the code sampleExpected results: The Flutter app should have started up normally.
Actual results: The app is stuck in a blank screen with the message
I/ViewRootImpl@91023c2[MainActivity]( 2630): [DP] cancelDraw io.flutter.embedding.android.FlutterActivityAndFragmentDelegate$2@a3ede7d isViewVisible: true
repeating itself in the debug console.Code sample
This is the
main.dart
:This is the AndroidManifest.xml:
Logs
The text was updated successfully, but these errors were encountered: