Skip to content

[Bug]: autocorrection for "I'm" broken after update #861

Closed

Description

@blind-confused

Preliminary Verification

  • I have searched existing open and closed issues and discussions to verify this bug is not already reported.
  • I have tested or verified this behavior on the latest release or beta version.
  • I have tried clearing app cache or testing with default settings.
  • If the issue is related to an external plugin (e.g. Voice Plugin, OCR, CJK, Handwriting, Offline AI), I have verified that I am using the latest release of that plugin.

Description of the Bug

after one of the latest updates, the word "I'm" no longer works with autocorrect. Previously, when I would type "im" or "in", they would get autocorrected into "I'm", but now this no longer happens - they get autocorrected into other words. "I'm" is missing even in extended suggestion list. I do not remember blocking it, maybe only by accident, since I use it very often. But I have disabled personalized suggestions in order to clear their history (I hope this counts as "cleaning app cache?), and this bug still persists. This started happening around a week ago, so it's one of the previous updates (not the very last one). Other words with an apostrophe like "don't", "haven't", "you're" etc. work correctly, but specifically "I'm" stopped working. I also had a weird autosuggested option "I,m" which I manually deleted.

Steps to Reproduce

  1. Update LeanType
  2. Disable personalized suggestions to clear their history, enable them again
  3. Type "um" or "im"
  4. They do not get autocorrected into "I'm"

Expected Behavior

words like "um" or "im" would get autocorrected into "I'm" like they used to in the past

Logs / Crash Report

No response

Build Flavor

Offline (zero network permissions, privacy focused)

App Version

4.3.4

Plugin Version (if applicable)

No response

Device & Android Version

Pixel 9a, GrapheneOS on Android 17 (latest stable release with security previews enabled)

Target App (if applicable)

No response

Screenshots or Screen Recordings

No response

Activity

  1. LeanBitLab commented on Nov 18, 2026

    @LeanBitLab
    Owner

    I'm" broken after update
    im broken after spending too much time on developing :)

  2. blind-confused commented on Nov 18, 2026

    @blind-confused
    Author

    I'm" broken after update im broken after spending too much time on developing :)

    for real though, feel free to take a break, you've already done a tremendous work, we won't mind if it goes a bit slower (well I won't)

  3. LeanBitLab commented on Nov 18, 2026

    @LeanBitLab
    Owner

    I'm" broken after update im broken after spending too much time on developing :)

    for real though, feel free to take a break, you've already done a tremendous work, we won't mind if it goes a bit slower (well I won't)

    I'd love to , but I've just started a new Zig-based file manager project. I’m currently balancing it alongside the other 4 projects, and it’s proving to be more challenging than all of them combined :)

  4. LeanBitLab commented on Nov 18, 2026

    @LeanBitLab
    Owner

    Preliminary Verification

    • I have searched existing open and closed issues and discussions to verify this bug is not already reported.
    • I have tested or verified this behavior on the latest release or beta version.
    • I have tried clearing app cache or testing with default settings.
    • If the issue is related to an external plugin (e.g. Voice Plugin, OCR, CJK, Handwriting, Offline AI), I have verified that I am using the latest release of that plugin.

    Description of the Bug

    after one of the latest updates, the word "I'm" no longer works with autocorrect. Previously, when I would type "im" or "in", they would get autocorrected into "I'm", but now this no longer happens - they get autocorrected into other words. "I'm" is missing even in extended suggestion list. I do not remember blocking it, maybe only by accident, since I use it very often. But I have disabled personalized suggestions in order to clear their history (I hope this counts as "cleaning app cache?), and this bug still persists. This started happening around a week ago, so it's one of the previous updates (not the very last one). Other words with an apostrophe like "don't", "haven't", "you're" etc. work correctly, but specifically "I'm" stopped working. I also had a weird autosuggested option "I,m" which I manually deleted.

    Steps to Reproduce

    1. Update LeanType
    2. Disable personalized suggestions to clear their history, enable them again
    3. Type "um" or "im"
    4. They do not get autocorrected into "I'm"

    Expected Behavior

    words like "um" or "im" would get autocorrected into "I'm" like they used to in the past

    Logs / Crash Report

    No response

    Build Flavor

    Offline (zero network permissions, privacy focused)

    App Version

    4.3.4

    Plugin Version (if applicable)

    No response

    Device & Android Version

    Pixel 9a, GrapheneOS on Android 17 (latest stable release with security previews enabled)

    Target App (if applicable)

    No response

    Screenshots or Screen Recordings

    No response

    Screenshot_20261119-044753_LeanType debug.png
    Check if I'm is accidentally added to blocked words

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions