Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

LeanType crashing while trying to reconfigure toolbar

Ouverte
  • Quelque chose ne va pas ?
#745 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
android, kotlin
Domaine
frontend, mobile

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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
Langage dominant
Kotlin
Étoiles
1k
Forks
59
Merge moyen
14 h 46 min
PR mergées (30 j)
56

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de LeanBitLab/LeanType

Toutes les issues de LeanBitLab/LeanType

Issues similaires

Plus d'issues Kotlin

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.