Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

LeanType crashing while trying to reconfigure toolbar

Open
  • Is something wrong?
#745 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
frontend, mobile

Research direction

Start by reproducing the crash in Settings > Toolbar while enabling or disabling icons on LeanType 4.3.0-beta2 PR. The issue does not include a crash report, stack trace, or source file, so inspect the app's toolbar customization flow and capture a redacted exception trace to locate the failure. Done means toolbar changes save and can be made without a crash.

Written by the indexing model from the issue text.

Description

bug

Description of the bug

Context-Aware Custom AI Toolbar Keys: Automatically hides unconfigured custom AI prompt keys in toolbar customization and pinned keys dialogs until configured in AI settings, reducing clutter.

After the above, my previously set toolbar icons were found changed. I tried to reconfigure the toolbar to my requirement, but every time I try to do that the app crashes.

To Reproduce
Go to Settings >> Toolbar and try to reconfigure (enable or disable) icons.

Expected behavior
The changes I make should stick and I should be able to reconfigure the toolbar to my liking.

Screenshots
The key indicated in the screenshot, although not configured, used to be displayed and worked well to bring up Gboard keyboard in my chosen language. How can I get it back working in 4.3.0 Beta 2 PR?

App version & Flavor
LeanType 4.3.0-beta2 PR

Device Info

  • Model: OnePlus 11
  • OS version: OxygenOS Android 14

I would prefer to retain direct switching to my selected Gboard language without having to configure an unnecessary AI prompt. Is this a regression, an intentional change to unconfigured custom AI keys, or should I continue to use the Direct Switch Target IME feature with custom keycode -10076?

Can the new visibility rule be made optional, or the old behaviour restored? I couldn't verify a user-facing setting that reverses the Beta 2 change.

Question to developer from a not-very-knowledgeable user:

What information can a crash report file contain beyond the exception and stack trace? In particular, could it include custom AI provider URLs, API keys, account identifiers, typed text, clipboard contents, learned words or personal dictionary entries?

Which specific fields or sections should be redacted before sharing the report? I want to be sure that the file being uploaded does not contain any sensitive information.

Is there a private avenue for submitting the original report directly to you, such as a private GitHub communication channel or another developer-approved method?

If public issue reporting is preferred, would a redacted report containing the relevant exception and stack trace be sufficient for diagnosing this crash?

I am happy to provide the diagnostic information needed to resolve the crash, but I would prefer not to publish potentially sensitive data unnecessarily.

Thank you.

Image
Dominant language
Kotlin
Stars
1k
Forks
59
Avg merge
14h 46m
Merged PRs (30d)
56

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LeanBitLab/LeanType

All issues in LeanBitLab/LeanType

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.