When pressing Caps key, sometime next letter isn't capitalized

[CelianGdfrd]

Please see the appropriate readme section for issue reporting guidelines: https://github.com/Helium314/HeliBoard?tab=readme-ov-file#reporting-issues
tl;dr:

• search for duplicates, also in closed issues
• a single issue per topic
• reduce screenshot size

Describe the bug

After pressing Caps key to capitalize the next key, sometimes the key isn't capitalized, and Caps key disables as if it has worked normally.

To Reproduce

• Press Caps key
• Type a letter

Expected behavior

• next letter should always be capitalized

Screenshots
ONLY add screenshots when they add real value.
If you add screenshots, reduce the size or use thumbnails to keep the issue nicely readable.

App version
2.3-beta1

Device:

• Model: OnePlus 7T Pro
• OS: LineageOS 21

[Helium314]

Is this new to 2.3-beta1, or did it also happen on older versions?

[CelianGdfrd]

I didn't notice it before updating to 2.3-beta1

[Helium314]

In that case it might be related to the fix for #994.
Could your try this version with the fix removed?
HeliBoard_2.3-beta1-release.zip

Does the issue appear any time, or is it related to quick typing, or on start of input field, ...?

[CelianGdfrd]

Maybe it's related to me typing a bit fast, but I can't say for sure. It happens whether I manually press the Caps key, or for the automatic caps at the beginning of a sentence.

I'm trying right now the beta version you provided. On this present message I didn't encounter the bug once. That's a good sign.

[BlackyHawky]

@Helium314
I confirm this (annoying) bug and point out that you don't need to press the shift key.
It appears, for example, in the Github application or in the Fossify Message application when a line break occurs.

[Helium314]

in the Fossify Message application

Can you post steps to reproduce, and potentially relevant settings?
So far couldn't get this bug even once, but digging into it is necessary to fix this without re-introducing #994.

[CelianGdfrd]

Can confirm I haven't encountered the bug since the new beta.

[BlackyHawky]

The bug appeared when using the release version (not with the proposed beta version).
I don't know how to reproduce it because it appears randomly.
In any case, what I'm sure of is that this bug does occur occasionally.

[Helium314]

So it's likely a different cause, as @CelianGdfrd's bug seems to be fixed by reverting that part back to what it was in 2.2.