A bit of a dishabused reaction concerning Qt Android and iOS platforms
-
I have been proposing for a few years an Android application based on Qt 5.15x.
I am, however, more and more disappointed by the difficulties I encounter.
I update my application after having properly tested it on physical devices and on the simulator. However, I often find myself faced with behaviors on the users' machines that I can't reproduce. Crashes or freezes, the indications given by google console are often themselves enigmatic, indicating backtrace with only one or two lines and not referring to the program code itself.
I try to update the Qt library by compiling it myself but I only see a multiplication of issues since I went from 5.15.2 to 5.15.5
The current issues seem to concern QAccessibility and the A11y support.Also, I'm not sure what to do anymore. I'm certainly going to remove my app from the Play as I find myself unable to offer an app that works on all machines.
Is there a way to improve things? How to explain these different behaviors on each device (is it due to the Android overlay?)
How can I improve my debugging practices?I must add that the linux, windows and macos versions work perfectly. The real problem concerns the ios and Android versions (especially Android).
Thanks !
Francky
-
I have been proposing for a few years an Android application based on Qt 5.15x.
I am, however, more and more disappointed by the difficulties I encounter.
I update my application after having properly tested it on physical devices and on the simulator. However, I often find myself faced with behaviors on the users' machines that I can't reproduce. Crashes or freezes, the indications given by google console are often themselves enigmatic, indicating backtrace with only one or two lines and not referring to the program code itself.
I try to update the Qt library by compiling it myself but I only see a multiplication of issues since I went from 5.15.2 to 5.15.5
The current issues seem to concern QAccessibility and the A11y support.Also, I'm not sure what to do anymore. I'm certainly going to remove my app from the Play as I find myself unable to offer an app that works on all machines.
Is there a way to improve things? How to explain these different behaviors on each device (is it due to the Android overlay?)
How can I improve my debugging practices?I must add that the linux, windows and macos versions work perfectly. The real problem concerns the ios and Android versions (especially Android).
Thanks !
Francky
@Francky033 said in A bit of a dishabused reaction concerning Qt Android and iOS platforms:
I often find myself faced with behaviors on the users' machines that I can't reproduce.
Do you know which Android version those machines are running?
Android features are an ever-moving target; newer Android versions often break functionality in apps that ran perfectly in older Android versions.
I only see a multiplication of issues since I went from 5.15.2 to 5.15.5
If you are using Qt 5.15.5, that means you have a commercial Qt license. Contact Qt Support (https://account.qt.io/s/support ) and ask them to help you investigate.
-
Android 12 seems overrepresented yes.
No, in fact, I currently use the open source version of Qt 5.15.5 that I compile myself...
-
Android 12 seems overrepresented yes.
No, in fact, I currently use the open source version of Qt 5.15.5 that I compile myself...
@Francky033 said in A bit of a dishabused reaction concerning Qt Android and iOS platforms:
No, in fact, I currently use the open source version of Qt 5.15.5 that I compile myself...
Ah that's right... that was open-sourced 2 weeks ago.
Android 12 seems overrepresented yes.
Android 12 was released 4 months after Qt 5.15.5, so that probably explains a lot.
Furthermore, Android 12 has changed a lot compared to Android 11: https://bugreports.qt.io/browse/QTBUG-99542
I must add that the linux, windows and macos versions work perfectly. The real problem concerns the ios and Android versions (especially Android).
The desktop platforms don't break backward compatibility as frequently as the mobile platforms.
iOS causes fewer headaches than Android because Apple maintains strict control over the hardware and OS. Android runs on a huge variety of hardware and is very customizable so there are a lot more pathways for things to break.
-
One thing that can help in a range of cases: Request your permissions (by string) at runtime, rather than relying on the Manifest. This way, you don't need to wait for Qt to implement support for a new permission.
See here for example code: https://code.qt.io/cgit/qt/qtandroidextras.git/tree/examples/androidextras/musiclist/main.cpp?h=5.15
-
I have been proposing for a few years an Android application based on Qt 5.15x.
I am, however, more and more disappointed by the difficulties I encounter.
I update my application after having properly tested it on physical devices and on the simulator. However, I often find myself faced with behaviors on the users' machines that I can't reproduce. Crashes or freezes, the indications given by google console are often themselves enigmatic, indicating backtrace with only one or two lines and not referring to the program code itself.
I try to update the Qt library by compiling it myself but I only see a multiplication of issues since I went from 5.15.2 to 5.15.5
The current issues seem to concern QAccessibility and the A11y support.Also, I'm not sure what to do anymore. I'm certainly going to remove my app from the Play as I find myself unable to offer an app that works on all machines.
Is there a way to improve things? How to explain these different behaviors on each device (is it due to the Android overlay?)
How can I improve my debugging practices?I must add that the linux, windows and macos versions work perfectly. The real problem concerns the ios and Android versions (especially Android).
Thanks !
Francky
@Francky033 said in A bit of a dishabused reaction concerning Qt Android and iOS platforms:
The current issues seem to concern QAccessibility
take a look here: https://bugreports.qt.io/browse/QTBUG-95764
