[@capacitor/splash-screen] Android 8–11: failed Android 12 API attempt leaves a pre-draw hold, so nothing is drawn for launchShowDuration

オープン 初心者向け
#2,635 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
88/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
android, java
領域
frontend, mobile

調査の方向性

showOnLaunch() が showWithAndroid12API() を呼び出し、レガシーの show() パスにフォールバックする Android スプラッシュ画面プラグインのコードを探します。Issue には、SDK バージョンに応じて Android 12 API の呼び出しをガードするパッチが示されています。この変更を既存の動作と比較し、Android 8~11 ではレガシーのスプラッシュ画面が使われ、Android 12 以降では現在のパスが維持されることを確認します。

索引モデルが issue の本文から書いたものです。

説明

platform: android

🤖 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 every version from 4.x through 8.0.3 nightly, 9.0.0-alpha.2 and the current 9.0 dev builds.

Capacitor Version
Latest Dependencies:

  @capacitor/cli: 8.6.0
  @capacitor/core: 8.6.0
  @capacitor/android: 8.6.0
  @capacitor/ios: 8.6.0

Installed Dependencies:

  @capacitor/cli: 8.5.2
  @capacitor/core: 8.5.2
  @capacitor/android: 8.5.2
  @capacitor/ios: 8.5.2

[success] Android looking great! 👌
Platform(s)

Android 8–11 (API 26–30). Android 12+ is not affected.

Current Behavior

On Android 8–11, showOnLaunch() calls showWithAndroid12API() first. On those versions the attempt does the following:

  1. installSplashScreen() succeeds. The compat library supports API 23+.
  2. setKeepOnScreenCondition(() -> isVisible || isHiding) succeeds. Below API 31, the compat SplashScreen.Impl adds an OnPreDrawListener to android.R.id.content right away.
  3. With the default launchFadeOutDuration (200), setOnExitAnimationListener() then throws, because building the compat SplashScreenViewProvider needs Theme.SplashScreen attributes that a normal launch theme doesn't have.

The catch logs Android 12 Splash API failed... using previous method. and falls back to show(..., true). However, the compat pre-draw listener from step 2 is still registered, and the legacy path then sets isVisible = true. As a result, the activity's content is held back from drawing for the entire launchShowDuration. The legacy splash window shares the activity's window token, so it doesn't appear while the activity hasn't drawn either.

The visible result depends on timing:

  • On a cold launch, the first draw usually happens before isVisible flips, so the splash shows normally.
  • When the activity is recreated in an existing process (for example, after closing it with Back and reopening it from the launcher), the hold wins. Nothing of the app is drawn for launchShowDuration, and then the app appears at once.

On an Android 9 emulator with launchShowDuration: 3000, the reopen after Back logs Displayed .MainActivity: +3s426ms, and the next line in the log is SplashScreen was automatically hidden after the launch timeout. With a translucent launch theme, the launcher stays on screen for the whole 3.4 s. With an opaque launch theme, the window background shows instead of the plugin's splash.

The 9.x change to the default launchFadeOutDuration (0, #2526) makes this worse below Android 12. Step 3 no longer throws, so the plugin never reaches the legacy path. It only holds the first frame for launchShowDuration behind the theme's window. With launchFadeOutDuration: 0 on 8.0.2, Android 9 showed no splash at all on either a cold launch (+4.4 s) or a reopen (+3.2 s), only the launcher until the app appeared.

Expected Behavior

On Android 8–11, the legacy splash shows right away and the activity isn't held. That is what happens on a cold launch today.

Code Reproduction

No sample repository yet. The steps on a new app:

  1. npm init @capacitor/app, add @capacitor/splash-screen, and set SplashScreen.launchShowDuration to 3000 in capacitor.config. Keep the other defaults.
  2. Optional, to make the symptom obvious: add <item name="android:windowIsTranslucent">true</item> to AppTheme.NoActionBarLaunch.
  3. Run on an API 26–30 emulator, for example Android 9.
  4. Launch the app and wait for it to finish loading, press Back, then tap the launcher icon again.
  5. The app (and the splash) are not drawn for about 3 s. adb logcat shows Android 12 Splash API failed... and an ActivityManager: Displayed time of about launchShowDuration.
Other Technical Details
  • androidx.core:core-splashscreen 1.2.0 (the plugin default)
  • Reproduced on an Android 9 (API 28) emulator
  • minSdkVersion 26
Additional Context

A guard that only uses the Android 12 API where it applies fixes this, and we now ship it as a patch:

         try {
-            showWithAndroid12API(activity, settings);
-            return;
+            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
+                showWithAndroid12API(activity, settings);
+                return;
+            }
         } catch (Exception e) {

With this guard on Android 9, the reopen after Back shows the legacy splash immediately (Displayed +182ms). The cold launch is unchanged, and Android 12+ runs the same code as before.

Another approach is to remove the pre-draw listener in the catch. However, the compat library doesn't expose it, so skipping the attempt below API 31 seems simpler. This is related to, but separate from, #2627 and #2548, which are about how hide() removes the plugin's own pre-draw listener.

主要言語
Java
スター
688
フォーク
691
平均マージ
1日 5時間
マージ済み PR(30日)
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ionic-team/capacitor-plugins のほかの issue

ionic-team/capacitor-plugins の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。