Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
iOS 13 and AIR SDK finds but does not connect to the device #112
It seems like if your device is updated to iOS 13, the AIR SDK can't connect to the device. So intelliJ can't install the .ipa on the connected device.
I tested xcode 11 and it does find the device and install apps on it like before.
I also tested via commandline:
it correctly finds the device:
Then I tried to install an .ipa file:
but I see the error
I hope this is an easy fix as iOS 13 is already out there :)
Release Notes (Version 126.96.36.1991)
-package and -devices work perfectly as previously. Instead -install command returns the same error
Tested from a Win10 64bits system.
Okay thanks - looks like something has gone wrong in our source code control process, as the binary that was checked in turns out to have been built from the old source code.. not quite sure how that happened, sorry! The "iIPA" binary on the Mac releases seems to be correctly built from the updated source code..
So, to get the updated exe for Windows in the short term, we've just uploaded this as a standalone file that you can download from https://airsdk.harman.com/assets/iIPA.zip
The zip is 49817 bytes, md5sum 4b37db10927afa3cf8ec2e901868e166; the executable within this is 99328 bytes, md5sum de65819acb7c8c4a5b52182e52504b36.
We'll make sure this gets added in properly to the next SDK release!
@ajwfrost Thank you very much for your quick response!
I just tried the iIPA.exe you sent compressed in a zip file but it didn't work well for me...
Okay so it looks like there were still some deeper API changes within iOS13 which require some updates.. we have got past the first hurdle but there appears to be a final step which isn't working for us yet.
Is anyone willing to share an IPA with us, and for us to send them debug/instrumented versions of this executable file, so that we can try to eliminate the problems being something specific to our set-up? We sometimes find our development machines are a little unusually configured so it would be useful to have a second opinion; we've actually found that this is also failing for us using a third party utility (iMazing) so there may be something else wrong here..
Anyway, if you're able to help then please email to firstname.lastname@example.org and I'll get to you tomorrow; Windows folk would be a little easier..
With thanks to @duxpel , we have a way of doing this now. We need to get this properly updated as it's a very different mechanism to what Adobe had previously been doing here, and then we'll push out updates for Windows/MacOS versions.
Thanks for your patience!