It turned out behavior is the same on 3 windows environments (haven't check on other OS yet) so I suspect this is not the issue with environment, but rather something wrong with device itself. While I understand that 'unknown' is not a good sign, I'm okay with seeing it if it doesn't prevent debugging / apk uploading. The issue is that QtCreator seems to be more strict than android studio and just leaves me no choice.
> ср, 22 мая 2019 г. в 02:27, Christian Gagneraud <chg...@gmail.com>: > > > > On Wed, 22 May 2019 at 10:16, Alexander Ivash <elder...@gmail.com> wrote: > > > > > > I've got a weird issue: QtCreator disallows to upload apk or debug it > > > due to 'ABI is incompatible error'. It definitely used to work in the > > > past (yes, my device is really armeabi-v7a and armeabi-v7a is really > > > what I select in QtCreator) and stopped working after updating android > > > sdk or after rooting device / messing with fastboot drivers, not > > > sure... What is interesting, Android Studio has no issues with > > > uploading / debugging (even though it shows device as 'unknown'). So > > > the question is: how to cheat QtCreator and bypass its 'ABI check' and > > > thus regain ability to upload/debug? > > > > Maybe the question is how to fix your broken setup. > > > > It sounds like you're device is now reporting the wrong information > > for QtC's ABI check. > > And Android Studio reporting your device as 'unknown' is not a good sign > > either. > > > > My 2 cents, > > Chris _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
