Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
Qt Creator 6.0.0
-
None
-
c1512dce87 (qt-creator/qt-creator/7.0) c1512dce87 (qt-creator/qt-creator/master) c1512dce87 (qt-creator/tqtc-qt-creator/7.0) c1512dce87 (qt-creator/tqtc-qt-creator/master) c1512dce87 (qt-creator/tqtc-qt-creator/qds-3.1), e6875aa01 (master)
-
2023wk20FOQtforAndroid
Description
The deployment might fail sometimes if the kit's ABIs list is not known:
The kit supports "", but the device uses "arm64-v8a, armeabi-v7a, armeabi".
This probably underlines a deeper issue because the kit's ABIs list should be valid if the kit is valid. However, it might be reasonable to go forward with the deployment if this case is hit and fail later to install if the ABIs don't match.
Attachments
| For Gerrit Dashboard: QTCREATORBUG-27103 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 397513,3 | Android: don't stop deployment if the kit's ABIs list is empty | 7.0 | qt-creator/qt-creator | Status: MERGED | +2 | 0 |
| 400478,2 | Android: don't fail if device abi list is empty | 7.0 | qt-creator/qt-creator | Status: MERGED | +2 | 0 |
| 478510,2 | Android: don't stop deployment if kit's abis list is empty | master | qt-creator/qt-creator | Status: MERGED | +2 | 0 |