resizeOnFullScreen is incompatible with new SystemBars plugin

[aeharding]

Bug Report

Capacitor Version

➜  voyager git:(main) npx cap doctor
💊   Capacitor Doctor  💊

Latest Dependencies:

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

Installed Dependencies:

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

[success] Android looking great! 👌
[error] Xcode is not installed
➜  voyager git:(main)

Platform(s)

Current Behavior

When using the SystemBars plugin (vanilla/no config except using --safe-area-inset-x in css) with the following config:

  plugins: {
    Keyboard: {
      resizeOnFullScreen: true,
    },
  }

A weird bug happens when:

1. Using Android < Vanilla Ice Cream (new SystemBars plugin doesn't apply, so need to fall back to old behavior)
2. Go to another app
3. Open keyboard
4. Switch back to capacitor app
5. Observe there is a blank space for the keyboard

Expected Behavior

No blank space for the keyboard

Code Reproduction

https://github.com/aeharding/cap-blank-space-keyboard

Other Technical Details

Additional Context

aeharding/voyager#2198

[sakulb]

I have similar yet possibly the same problem.
When i click on a deep link while keyboard is open, it opens my app with the gap for keyboard present (just like on the image above). I have updated everything that is out to this date.

My workaround is this until they fix the capacitor-keyboard:

App.addListener('appUrlOpen', function (event: URLOpenListenerEvent) {
setTimeout(() => {
    if (window.innerHeight < window.screen.height * 0.75) {
      console.log('Phantom keyboard detected. Applying fix...')
      Keyboard.show().then(() => Keyboard.hide())
    }
  }, 50)
})

[zarko-tg]

Hopefully this gets prioritized for fixing as it has to do with a very common use on an Android device - opening an app by searching for by typing its name (hit the Google home page toolbar, type in an app name and launch it). The issue seems to be reproducible for a cold-started app.
Looks to be the same case as #30

[zarko-tg]

Given the seriousness of the issue and lack of available time to go in depth on it I put AI to solve it and it came up with this simple fix: timegrip@3545fbb
I am not immediately aware of any side effects, but it resolves the problem. We'll be testing it with a local patch on our side.