The latest version of QT6 has a bug

[vcplay]

I am using qt6.7.1 for Android.
When the app is being built and running.
When I use QInputDialogue:: getText.
The app sometimes crashes！
Error content：
E libEGL : eglGetCurrentDisplayImpl: EGLContext is nullptr.
...
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: org.qtproject.jld_mes2024, PID: 28892
E AndroidRuntime: java.lang.NullPointerException: Attempt to write to field 'boolean org.qtproject.qt.android.QtEditText.m_optionsChanged' on a null object reference in method 'void org.qtproject.qt.android.QtInputDelegate.lambda$resetSoftwareKeyboard$0$org-qtproject-qt-android-QtInputDelegate()'
E AndroidRuntime: at org.qtproject.qt.android.QtInputDelegate.lambda$resetSoftwareKeyboard$0$org-qtproject-qt-android-QtInputDelegate(QtInputDelegate.java:167)
E AndroidRuntime: at org.qtproject.qt.android.QtInputDelegate$$ExternalSyntheticLambda4.run(Unknown Source:2)
E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:942)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:223)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:324)
E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8680)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1061)
...
I can only solve it by recompiling Qt6Android.jar,Repair process(Look at the two pictures)：

[aha_1980]

@vcplay: Bugreports need to go to https://bugreports.qt.io with a minimal reproducer example. Please also search if such an report already exists (and please leave a link to the report here so others can follow.)
This is a user forum and not monitored by the developers.

[vcplay]

ok,thanks.

[Axel Spoerl]

Before you file a bug report: Can you boil this down to a simple reproducer?
I am asking, because I can't help the feeling that the issue is caused by the application. The crash happens, when the input connection dies, before the delayed restart is executed. That shouldn't be the case under normal circumstances.

=> Is there a Qt version where this didn't happen?
Even if there is, a small change in event processing can uncover this issue.