bug(splash-screen): splashImmersive and splashFullScreen have no effect on Android 8–10
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 74/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Área
- backend-api-design, mobile
Línea de trabajo
Read the Android splash screen legacy path in show(), buildViews(), legacyImmersive(), and legacyFullscreen(). Check how the splashImage and spinnerBar windows are added and which window receives system UI flags; reproduce on Android API 26–29. Done when the configured immersive and fullscreen modes hide the expected system bars and the splash covers the status bar area from its first frame.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
🤖 Automated review by Claude — posted via @ibrahimkhatib365's account; not written by them personally.
Bug Report
Plugin(s)
@capacitor/splash-screen 8.0.2. The same code is in the current main.
Capacitor Version
Installed Dependencies:
@capacitor/cli: 8.5.2
@capacitor/core: 8.5.2
@capacitor/android: 8.5.2
@capacitor/ios: 8.5.2
Platform(s)
Android 8–10 (API 26–29), the legacy splash path. Reproduced on API 28.
Current Behavior
With splashImmersive: true (or splashFullScreen: true), the launch splash keeps the navigation bar and status bar visible below Android 11.
In show(), the legacy path adds two windows: splashImage first, then spinnerBar. spinnerBar is always created in buildViews() and always added, even with showSpinner: false. legacyImmersive() and legacyFullscreen() then set the system UI flags on splashImage only. Below Android 11 the focused window decides the system bars, and that's spinnerBar, the window added last, which has no flags. So the flags never take effect.
A related gap: both windows are added with the activity's flags, without FLAG_LAYOUT_NO_LIMITS, so the splash image starts below the status bar. While it shows, the status bar area shows the activity window behind it. During startup that window changes colour (theme background, then the WebView), so the status bar flickers before settling on the splash colour.
Expected Behavior
Below Android 11, splashImmersive hides the system bars and splashFullScreen hides the status bar while the splash shows, the same as on Android 11+. The splash covers the status bar area from the first frame.
Code Reproduction
npm init @capacitor/appand add@capacitor/splash-screen. SetSplashScreen.launchShowDuration: 3000andsplashImmersive: trueincapacitor.config.- Run on an Android 9 (API 28) emulator. The plugin takes the legacy path there (see #2635).
- Launch the app: the navigation buttons, and the status bar above the splash, stay visible for the whole splash.
Other Technical Details
- Reproduced on an Android 9 (API 28) emulator
minSdkVersion26
Additional Context
We work around it with a patch, which applies flags to the focused window and lets the image draw under the status bar:
// Required to enable the view to actually fade
params.format = PixelFormat.TRANSLUCENT;
+ if (Build.VERSION.SDK_INT < Build.VERSION_CODES.S) {
+ params.flags |= WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS;
+ }
+
try {
windowManager.addView(splashImage, params);
...
windowManager.addView(spinnerBar, params);
+ if (Build.VERSION.SDK_INT < Build.VERSION_CODES.S && config.isImmersive()) {
+ spinnerBar.setSystemUiVisibility(
+ View.SYSTEM_UI_FLAG_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_LAYOUT_STABLE
+ );
+ }
We only hide the navigation bar, because we wanted the status bar kept. A general fix would apply the same flags as legacyImmersive() / legacyFullscreen() to spinnerBar too, or to whichever window is added last. Avoid IMMERSIVE_STICKY on the spinner, because on some versions it shows the system's "Viewing full screen" hint over the splash.
We haven't checked Android 11 (API 30). Its insets-controller branch also targets splashImage's window, so it may have the same problem.
Related: #2635 (the same legacy path, on reopen).
- Lenguaje dominante
- Java
- Estrellas
- 688
- Forks
- 691
- Merge medio
- 1 d 5 h
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ionic-team/capacitor-plugins
-
platform: android
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
ionic-team/capacitor-plugins#2635 ·
Los mantenedores suelen responder en 1 día
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ionic-team/capacitor-plugins#2627 ·
Los mantenedores suelen responder en 1 día
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ionic-team/capacitor-plugins#2616 ·
Los mantenedores suelen responder en 1 día
-
[@capacitor/app] iOS: 'Expression implicitly coerced from String? to Any' warning in getAppLanguageAbiertotriage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
ionic-team/capacitor-plugins#2604 ·
Los mantenedores suelen responder en 1 día
-
triage
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
ionic-team/capacitor-plugins#2634 ·
Los mantenedores suelen responder en 1 día
Todos los issues de ionic-team/capacitor-plugins
Issues similares
-
Test: Verify vault unlock max failed attempts and PIN brute-force protectionPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
wultra/powerauth-tests#980 ·
-
account bug communication lecture
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
line/centraldogma#1397 ·
Los mantenedores suelen responder en 2 días
-
[Bug]: Fixed/recurring deposit accounts are treated as savings in ownership and listingsPosiblemente ocupada @Aana123 la tomó hoy. Abiertobug Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
apache/fineract-consumer-facing#252 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 76/100
ShaftHQ/SHAFT_ENGINE#7946 ·
Los mantenedores suelen responder en 1 día