LeanType crashing while trying to reconfigure toolbar
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 45/100
調査の方向性
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 の本文から書いたものです。
説明
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.
- 主要言語
- Kotlin
- スター
- 1k
- フォーク
- 59
- 平均マージ
- 14時間 9分
- マージ済み PR(30日)
- 56
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
LeanBitLab/LeanType のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
LeanBitLab/LeanType#760 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 62/100
LeanBitLab/LeanType#763 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 半日 初心者へのやさしさ 62/100
LeanBitLab/LeanType#762 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 半日 初心者へのやさしさ 70/100
LeanBitLab/LeanType#761 ·
メンテナーはふだん 1 日以内に返信
-
Native crash (SIGSEGV in getSuggestionsNative) when typing with a multilingual secondary languageオープン
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
LeanBitLab/LeanType#759 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
LeanBitLab/LeanType の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
liberation-data/drivine4j#547 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
ccch1mneyyy/dsh-Go#381 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
wangzan101/Mika#227 ·
メンテナーはふだん 1 日以内に返信
-
documentation
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
theopenconversationkit/tock#2136 ·
メンテナーはふだん 1 日以内に返信
-
App asks for diameter for emergency=hydrant + water_source=groundwater. But should probably not.オープンfeedback required
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
streetcomplete/StreetComplete#7354 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信