[Bugs] Tasker Underscore Issue Not Fixed

[Karthikn341]

Describe the bug
I Check the Latest Version... tasker underscore issue wasn't fixed

Record_2026-09-19-22-32-44_2267f3e96e221f89314935305a79f501.mp4

[LeanBitLab]

Describe the bug I Check the Latest Version... tasker underscore issue wasn't fixed

Record_2026-09-19-22-32-44_2267f3e96e221f89314935305a79f501.mp4

check settings->preference-> app profile-> select tasker app

[LeanBitLab]

• Force Direct Text Commit (forceDirectCommit): Bypasses composing spans and prevents symbol pair wrapping on auto-selected text. (this toggle alone fix your issue)
• Disable Auto-Spacing (disableAutoSpace): Prevents phantom spaces around symbols.
• Allow on Non-Editable Fields (allowTypeNullKeyboard): Guards against transient focus loss during Tasker's syntax validation.

[Karthikn341]

sorry i tried.. its not fixed

Record_2026-09-19-23-24-44_2267f3e96e221f89314935305a79f501.mp4

[LeanBitLab]

sorry i tried.. its not fixed

Record_2026-09-19-23-24-44_2267f3e96e221f89314935305a79f501.mp4

can you try force closing the keyboard once, just in case to confirm its not cache settings issue

[Karthikn341]

Not Issue on variable field (previously and now)

only issue on output variable field

[LeanBitLab]

Not Issue on variable field (previously and now)

only issue on output variable field

did you tried force closing the keyboard once, just in case

[Karthikn341]

yes i tired force stopped and check in tasker twice.. not fixed

[LeanBitLab]

yes i tired force stopped and check in tasker twice.. not fixed

can you share log after clearing log then reproduce the bug-> share log, its in settings-> about

[LeanBitLab]

yes i tired force stopped and check in tasker twice.. not fixed

the next possible scenario is tasker app itself hardcode it, did you tried any other keyboard to test it

[Karthikn341]

`--------- beginning of system
09-19 23:48:48.360 16546 16546 W VRI[InputMethod]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2258), lastSurfaceSize:Point(1080, 2258), format:-2, blastBufferQueue:null
09-19 23:48:48.395 16546 16546 W VRI[InputMethod]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2258), lastSurfaceSize:Point(1080, 2258), format:-2, blastBufferQueue:android.graphics.BLASTBufferQueue@8671033
09-19 23:48:48.409 16546 16546 W VRI[InputMethod]: handleResized abandoned!
09-19 23:48:51.740 16546 16546 W VRI[InputMethod]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2258), lastSurfaceSize:Point(1080, 2258), format:-2, blastBufferQueue:android.graphics.BLASTBufferQueue@8671033
09-19 23:48:52.966 16546 16546 W VRI[InputMethod]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2258), lastSurfaceSize:Point(1080, 2258), format:-2, blastBufferQueue:android.graphics.BLASTBufferQueue@8671033
09-19 23:48:54.364 16546 16546 W VRI[SettingsActivity2]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2378), lastSurfaceSize:Point(1080, 2378), format:-1, blastBufferQueue:null
09-19 23:48:54.372 16546 16546 W VRI[SettingsActivity2]: handleResized, msg:, frameChanged:false, configChanged:false, displayChanged:false, attachedFrameChanged:false, compatScaleChanged:false, pendingDragResizing=false
09-19 23:48:54.576 16546 16546 W VRI[InputMethod]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2258), lastSurfaceSize:Point(1080, 2258), format:-2, blastBufferQueue:android.graphics.BLASTBufferQueue@8671033
09-19 23:48:54.577 16546 16546 W VRI[SettingsActivity2]: handleResized abandoned!
09-19 23:48:54.594 16546 16546 W VRI[SettingsActivity2]: handleResized abandoned!
--------- beginning of main
09-19 23:49:05.532 16546 16546 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
09-19 23:49:05.532 16546 16546 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
09-19 23:49:05.543 16546 16546 W VRI[SettingsActivity2]: updateBlastSurfaceIfNeeded, surfaceSize:Point(1080, 2378), lastSurfaceSize:Point(1080, 2378), format:-1, blastBufferQueue:null

2026-09-19 23:48:41.683559 I LatinIME: onFinishInput
2026-09-19 23:48:43.883527 I LatinIME: onFinishInput
2026-09-19 23:48:48.283312 I LatinIME: onFinishInput
2026-09-19 23:48:48.284666 D LatinIME: onInlineSuggestionsResponse called
2026-09-19 23:48:48.284747 D LatinIME: onCreateInlineSuggestionsRequest called
2026-09-19 23:48:48.295565 I LatinIME: Starting input. Cursor position = 5,5
2026-09-19 23:48:48.295768 I Settings: loadSettings
2026-09-19 23:48:51.726175 I LatinIME: Restarting input. Cursor position = 5,5
2026-09-19 23:48:52.952605 I LatinIME: Restarting input. Cursor position = 5,5
2026-09-19 23:48:54.564560 I LatinIME: onFinishInputView
2026-09-19 23:48:54.566230 I LatinIME: onFinishInput
2026-09-19 23:48:54.571872 D LatinIME: onStartInputViewInternal: suppressing transient TYPE_NULL input view for com.leanbitlab.leantype
2026-09-19 23:48:54.572884 I LatinIME: requestHideSelf: 0
2026-09-19 23:48:54.573947 I LatinIME: hideWindow
2026-09-19 23:48:54.575409 I LatinIME: onFinishInputView
2026-09-19 23:48:54.575528 I LatinIME: onWindowHidden
2026-09-19 23:48:55.074675 I LatinIME: onFinishInput
2026-09-19 23:48:56.892612 I LatinIME: onFinishInput
2026-09-19 23:48:57.187873 I LatinIME: onFinishInput
2026-09-19 23:49:05.590895 I LatinIME: onFinishInput
`

Here is the Log..
i tried uninstalled and install still not fixed..

i only facing this issue with heliboard and LearnType

[LeanBitLab]

ill release an new build tomorrow, i think we might need more info to fix this, on next release ill add an new toggle in app profile, you can try turn on allow symbol composing and disable Force Direct Text Commit on that build

[LeanBitLab]

v4.2.5 will be released in an hour, check if it fixed the issue