bug: android egde to edge keyboard on API Level 29 or lower / API Level 34

[paulstelzer]

Plugin(s)

• Android Edge-to-Edge Support

Version

7.1.1

Platform(s)

• Android
• iOS
• Web

Current behavior

With this PR the check for API Level was removed: #485

This leads to an unexpected behaviour. It has a reason why there was an API Level check. If you now open the app with API Level 29 or lower / API Level 34 and open the keyboard, you have an extreme space above the open keyboard.

Screenshot API Level 29 (open keyboard):

Screenshot API Level 34 (open keyboard):

Expected behavior

No space above keyboard

Steps to reproduce

1. Activate Edge to Edge
2. Open Device (Api Level 29 or lower)
3. Open keyboard
4. You see space (see screenshot)

[robingenz]

I've tested this exact behavior on my Android 9 device and didn't had any issues. That's why I merged it. Sorry, that you encounter this issue again. Feel free to create a new PR and merge those two bug fixes.

[paulstelzer]

@robingenz Found out why this problem is only happening on my side. So 7.1.1 is correct when NOT using @capacitor/keyboard. if you use this with the following options then it will happen what I have posted:

Keyboard: {
      resize: KeyboardResize.Native,
      resizeOnFullScreen: true,
    },

But if I remove this, then Api Level lower than 34 is working, but not Api Level 35 (the buttons in the footer will be hidden on an open keyboard). So I will stay at 7.1.0 and use the capacitor keyboard plugin.

[robingenz]

@paulstelzer Thanks, this is now documented: db1c711

[developeration1]

@robingenz Had same issue like @paulstelzer , using API level 29, even if trying following instructions of db1c711 , the only solution was to downgrade to 7.1.0 and now it works on higher and lower API levels.

Yet, I'm not pretty sure if everything works fine, since my screen doesn't has a footer like that to prove it.

[robingenz]

@developeration1 Feel free to debug it and create a PR.

[robingenz]

I can now reproduce this issue but only on SDK Level 34.

[robingenz]

Closed since this was an issue with the Safe Area plugin.