Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

LeanType crashing while trying to reconfigure toolbar

未關閉
#745 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
android, kotlin
領域
frontend, mobile

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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
主要語言
Kotlin
星號
1k
分支
59
平均合併
14 小時 46 分鐘
30 天內合併 PR
56

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

LeanBitLab/LeanType 的其他 Issue

查看 LeanBitLab/LeanType 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。