Notifications such as "could not access source file" appear on top of the keyboard

[marcel263]

Notification bubbles should not be overlaid on the keyboard as it makes password antry difficult.

Version 1.09c Android 11 OneUI 3.1

[NumbGnat]

Are you able to get a screenshot @marcel263 ?

That might help illustrate the problem better.

[marcel263]

Are you able to get a screenshot @marcel263 ?

That might help illustrate the problem better.

Dear,

the video included shows the problem.

Message should not appear on top of keyboard. It is like needless scrollbar or unskippable ads, very cumbersome. Obligatory messages should appear above the keyboard area.

https://user-images.githubusercontent.com/76437842/164773344-3c226d36-7d7f-46a9-88a4-cd583f050dda.mp4

[NumbGnat]

the video included shows the problem.

Ahh... Yes... That helps. I thought perhaps that was the case. I opened Issue #1441 a while back, which is closely related.

@PhilippC didn't comment on it, so I was thinking perhaps he doesn't have any control over where the notice is displayed. That may be controlled by Android. 😕

[AvverbioPronome]

Yeah, this happens every time if your database is somewhere remote and it's not good at all.

[StrontRont]

It happens with WebDav file and Xperia 5 II with a 21:9 screen as well.

[jimmyjimjames]

Yeah, this issue drives me crazy. I use a google drive file for my DB, and it keeps flashing a message up right in the middle of my keyboard as I'm trying to type my password. Relocating the message to the top of the screen would likely solve this problem.

[Dricc123]

I love this app. This is a small thing. But when are they going to do something about this? the bug has been there for long now. or at least give us a statement saying it can't be fixed, so we stop asking.

[NumbGnat]

I'm pretty sure this is a standard Android toast message. Many of my other apps display their toast messages in the same spot.

So I did a little digging and landed on a Codepath Guide for Displaying Toasts

There used to be a way for developers to specify the alignment of Toast messages, by calling setGravity(), but according to the Android Toast Documentation, as of Android 11 (September 2020), that was depreciated. 😕

So, I guess we're stuck with the Toast() messages in the location Android has chosen to force them into. 🙄

I guess this applies to #1441 too.

[Dricc123]

@NumbGnat what you're writing makes perfect sense because I didn't have the issue on my other phone that has an older version of Android installed. Now at least we know.

[d2718nis]

Unfortunately this is an issue on both Android 13 and 14. While I was researching this topic, I stumbled upon two possible solutions:

• The deprecation of setGravity() only applies to text toasts specifically. Unfortunately, the setView() is also deprecated, which means creating a custom Toast is not the most reliable way to solve it (Android developers are most likely to remove it completely in the future)
• Utilize the Snackbar. I believe there are some tools in Xamarin CommunityToolkit that might help with that, although this project doesn't seem to have it among its dependencies

Both options won't allow showing toasts while the app is in the background, since Android R only the basic text toasts are allowed in such fashion. Not sure if this would matter for the current workflow.

Also, this is a related issue: https://github.com/PhilippC/keepass2android/issues/2069