iOS 13 and AIR SDK finds but does not connect to the device

myflashlab commented 4 years ago

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:

connect your iPhone to your Mac then run:

adt -devices -platform ios

it correctly finds the device:

List of attached devices:
Handle  DeviceClass DeviceUUID                  DeviceName
4    iPhone      xxxxxxxxxxxxxx      Hadi Tavakoli’s iPhone

Then I tried to install an .ipa file:

adt -installApp -platform ios -device 4 -package "Main.ipa"

but I see the error Error connecting to your device! which is exactly the same error I saw on the intelliJ IDEA.

I hope this is an easy fix as iOS 13 is already out there :)

tuarua commented 4 years ago

Raised same here. https://github.com/Gamua/Adobe-Runtime-Support/issues/86

divlaine commented 4 years ago

have the same problems but with flash develop. With ios 12 it works with ios13 not

ajwfrost commented 4 years ago

Hi all

We're aware of this one, and are looking into it, hope to have a fix pushed out before too long. I believe it's possible to download the apps via an old version of iTunes, or via Xcode, as a temporary workaround..

thanks

d-angelovski commented 4 years ago

Flash builder has also issues with this.

There is also this: https://tracker.adobe.com/#/view/AIR-4198872

divlaine commented 4 years ago

https://tracker.adobe.com/#/view/AIR-4198872

duxpel commented 4 years ago

Hi @ajwfrost We continue with this error, are we missing something?

Release Notes (Version 33.0.2.281) ... 3.1.2 Build Tools The iIPA tool has been updated so that it can connect to and deploy applications onto devices running iOS/iPadOS version 13 (Gamua-112). ...

-package and -devices work perfectly as previously. Instead -install command returns the same error Error connecting to your device! . We have tested with adt.bat and with iIPA.exe of your last release (33.0.2.281) but we can't install the application on the device.

Tested from a Win10 64bits system. iPhone 6S (iOS 13.1.2)

Thanks in advance! issue_112

ajwfrost commented 4 years ago

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!

duxpel commented 4 years ago

@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... Once the -install command is executed, jump to the next command line in less than two seconds without getting an error/success message. I have checked but the app is not installed on the device. Moreover, the behavior is the same when the value of the _PATH_TOIPA parameter is incorrect and non-existent. I attach a capture of the command line. Thanks again for your help! :)

issue_112_v2

lamselli commented 4 years ago

Hi ! Doesn't seem to work for me either on Mac. When you try to install, it directly ends with no return and the app is not installed on the device...

tuarua commented 4 years ago

seeing the same as @lamselli on macOS (using Catalina 10.15) eg

./adt -installApp -platform ios -device 1 -package /bin-release/device/Example.ipa

ajwfrost commented 4 years ago

Hmm... this is a little strange, we'll take a deeper look, will update you soon

ajwfrost commented 4 years ago

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 adobe.support@harman.com and I'll get to you tomorrow; Windows folk would be a little easier..

thanks

duxpel commented 4 years ago

Sure! I just sent you an email.

ajwfrost commented 4 years ago

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!

xs2bas commented 4 years ago

Using SDK 30.0.2.288, still facing this problem, while the release notes states:

The iIPA tool has been updated so that it can connect to and deploy applications onto devices running iOS/iPadOS version 13 (Gamua-112). Currently there is a restriction in uninstalling applications from iOS13 which we will investigate.

Does not work when I publish and deploy from Animate, nor when I try to install from the command line.

This is the error I receive from Animate:

iPad Air : The device has encountered an unexpected error. installOrUninstall_new(inspectie v2.5.6.ipa)

... and this is the one from command line:

Installation Error: could not transfer the application to the device.

Something strange that I came across is that when publishing the app in 33.0.2.288, the file size of the ipa dropped to 8.357 kB ... but when publishing with lower versions, the size is around 15,000 kB ...

Which certificate type should I use when publishing from Animate to the iPad? I have tried both (newly created) developer and distribution profiles ...

ajwfrost commented 4 years ago

Okay this is getting weird .. @xs2bas are you able to send us the IPA file so that we can check this and see what's happening? If it's 9MB you can probably just email it to adobe.support@harman.com but if that doesn't work, email us anyway and we can send you a link for a place to upload it..

Thanks

lamselli commented 4 years ago

From my side, it seems to work. (adt -installApp -platform ios -device 1 -package Main.ipa installed the ipa correctly)

myflashlab commented 4 years ago

Well, I confirm that V33.0.2-288 works perfectly on installing .ipa on iOS 13+ devices. Tested with:

Terminal as the first post --> OK
ANELAB app installer window --> OK
intelliJ and connecting to debugger --> OK

MacOS: 10.14.6 xcode: 11.0

@ajwfrost on Monday, I may try to test on other macOS versions also if necessary?

Kudos to the Harman Team... Continuing on someone else's work is always a big pain and you are doing a great job. keep it up :)

HeyDonny commented 4 years ago

Thank you, I can confirm app install on 33.0.2.288 also works with Windows 7 / ADT.

xs2bas commented 4 years ago

Okay this is getting weird .. @xs2bas are you able to send us the IPA file so that we can check this and see what's happening? If it's 9MB you can probably just email it to adobe.support@harman.com but if that doesn't work, email us anyway and we can send you a link for a place to upload it..

Thanks

@ajwfrost I just sent you an email! (both files I sent you are published using Animate)

ajwfrost commented 4 years ago

@xs2bas thanks for this; the ipa built with the .288 SDK appears to just contain 64-bit code whereas the one from the .246 build looks like it also contains 32-bit machine code.. We might need to get to the bottom of what's different in the calls from Animate to the ADT program here, there shouldn't be any changes within this or within the other iOS-related files between these two builds but that's also worth checking.

Are you able to install either of these two IPA files onto an iOS13 device using the .288 version of the iIPA tool? or do they both give the error? If you're using Animate .. we will need to double-check exactly how this makes the calls as it might be doing something different from the command-line tools.

htmiel commented 4 years ago

Using Animate on Windows 10 64bit, with AIR 33.0.2.288:

publishing to iPhone 6 (iOS 12) installs the app correctly
publishing to iPad Air 2 (iPadOS / iOS 13) I get the message "IPA file has been installed on the connected iOS device successfully" but the app does not actually install on the device. I can successfully install the IPA only using iTunes.

xs2bas commented 4 years ago

@ajwfrost I have the same problem using command line: size differences and not able to install to iOS13-device. This is the command I use to build, and the warning I get:

"C:\Program Files\Adobe\Adobe Animate CC 2018\SDK\33.0.2.288\bin\adt" -package -target ipa-ad-hoc -storetype pkcs12 -keystore "E:\Projecten\Omniboxx\omniboxx_dist_16okt.p12" -storepass xxxxxxx -provisioning-profile "E:\Projecten\Omniboxx\InspectieApp\certificates\comwennetinspectieomniboxx_dist_16okt.mobileprovision" inspectie.ipa inspectie-app.xml inspectie.swf -extdir "bin" appicons textures Assets.car Default-Landscape@2x~ipad.png Default-Landscape~ipad.png Default-Landscape-414w-736h@3x~iphone.png

Warning: Using default implementation for native extension 'com.distriqt.square.picasso' Warning: Resource de.lproj has been skipped because of mismatch with supported languages information in application descriptor. Warning: Resource en.lproj has been skipped because of mismatch with supported languages information in application descriptor. Warning: Resource es.lproj has been skipped because of mismatch with supported languages information in application descriptor. Warning: Resource fr.lproj has been skipped because of mismatch with supported languages information in application descriptor.

xs2bas commented 4 years ago

Build and install from Animate, SDK 33.0.2.288: iPhone : The device has encountered an unexpected error. installOrUninstall_new(inspectie 33.0.2.246.ipa) Installation Error: could not transfer the application to the device.
Build and install from command line, SDK 33.0.2.288 Uninstallation Error: cannot uninstall from iOS13. installOrUninstall_new(inspectie.ipa) Installation Error: PreflightingApplication.
Build and install from Animate, SDK 33.0.2.246 and below: iPhone : The device has encountered an unexpected error. Error connecting to your device!
Command line using SDK 33.0.2.246 and below: Error connecting to your device!

ajwfrost commented 4 years ago

Thanks for all that! We'll take a look.

One thing I wondered: are you able to build it using 33.0.2.246, so that you have the larger file size, and then use the command line with 33.0.2.288 to install it?

xs2bas commented 4 years ago

Build with 33.0.2.246 and installing using 33.0.2.288:

Uninstallation Error: cannot uninstall from iOS13. installOrUninstall_new(inspectie.ipa) Installation Error: VerifyingApplication.

xs2bas commented 4 years ago

Some more info from iOSLogInfo ... looks like entitlement-issues, but I used old and newly created certificates/profiles:

Oct 22 14:36:43 iPhone mobile_installation_proxy(MobileInstallation)[278] : (null):5:1:1:1:Beginning installation for file:///private/var/mobile/Media/PublicStaging/inspectie.ipa/ with options { AllowInstallLocalProvisioned = 1; PackageType = Developer; } Oct 22 14:36:43 iPhone mobile_installation_proxy(CoreServices)[278] : setting operationType to LSOperationTypeInstallApplication from options Oct 22 14:36:43 iPhone mobile_installation_proxy(CoreServices)[278] : created clientInstaller for type InstallApplication Oct 22 14:36:43 iPhone mobile_installation_proxy(CoreServices)[278] : Application proxy for has no bundle identifier Oct 22 14:36:43 iPhone lsd(MobileInstallation)[81] : (null):5:1:1:1:Kicking off ininstall: file:///private/var/mobile/Media/PublicStaging/inspectie.ipa/ type 4 with options { AllowInstallLocalProvisioned = 1; PackageType = Developer; } Oct 22 14:36:43 iPhone lsd(CoreServices)[81] : install choke: after enqueueing operation, got role 0 Oct 22 14:36:43 iPhone lsd(CoreServices)[81] : not writing preliminary journal for install operation with no known bundle ID. Oct 22 14:36:43 iPhone lsd(MobileInstallation)[81] : (null):5:1:1:1:Proceeding with install: file:///private/var/mobile/Media/PublicStaging/inspectie.ipa/ type 4 with options { AllowInstallLocalProvisioned = 1; PackageType = Developer; } Oct 22 14:36:43 iPhone installd(MobileSystemServices)[45] : 0x16bcab000 -[MIClientConnection _doInstallationForURL:withOptions:completion:]: Install of "/private/var/mobile/Media/PublicStaging/inspectie.ipa" type Developer (LSInstallType = (null)) requested by lsd (pid 81) Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Received termination request from [daemon:45] on application with context <RBSTerminateContext: 0x1490171f0; code: 0xDEAD6502; explanation: FBSApplicationTerminationAssertion; reportType: 0; maxRole: 0; maxTerminationResistance: 3> attrs = { <RBSPreventLaunchLimitation: 0x147dd9fd0>; } Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Acquiring assertion targeting application from originator [daemon:45] with description <RBSAssertionDescriptor; FBSApplicationTerminationAssertion; ID: 26-45-2644; target: application> attributes = { <RBSPreventLaunchLimitation: 0x147dd9fd0>; } Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Assertion 26-45-2644 (target:application) will be created as active Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Finished acquiring assertion 26-45-2644 (target:application) Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Executing termination request for: application Oct 22 14:36:43 iPhone SpringBoard(SpringBoard)[54] : termination assertion efficacy for com.wennet.inspectie.omniboxx (app not found) changed to 3 Oct 22 14:36:43 iPhone containermanagerd[62] : command=, client=, error= Oct 22 14:36:43 iPhone installd(MobileSystemServices)[45] : 0x16bcab000 -[MIInstaller performInstallationWithError:]: Installing Oct 22 14:36:43 iPhone installd(MobileInstallation)[45] : com.wennet.inspectie.omniboxx:7:5:1:1:Start : Install (New) Oct 22 14:36:43 iPhone misagent(libMobileGestalt.dylib)[107] : taking platform fast path for key: re6Zb+zwFKJNlkQTUeT+/w Oct 22 14:36:43 iPhone profiled[221] : Provisioning profiles changed Oct 22 14:36:43 iPhone profiled[221] : Updating MIS trust... Oct 22 14:36:43 iPhone trustd[121] : cert[0]: SubjectCommonName =(leaf)[]> 0 Oct 22 14:36:43 iPhone trustd[121] : cert[0]: LeafMarkerOid =(leaf)[force]> 0 Oct 22 14:36:43 iPhone trustd[121] : OCSPResponse: single response has extension(s). Oct 22 14:36:43 iPhone trustd[121] : cert[0]: IssuerCommonName =(path)[]> 0 Oct 22 14:36:43 iPhone installd(Security)[45] : Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] Oct 22 14:36:43 iPhone trustd[121] : cert[0]: SubjectCommonName =(leaf)[]> 0 Oct 22 14:36:43 iPhone trustd[121] : cert[0]: LeafMarkerOid =(leaf)[force]> 0 Oct 22 14:36:43 iPhone trustd[121] : OCSPResponse: single response has extension(s). Oct 22 14:36:43 iPhone trustd[121] : cert[0]: IssuerCommonName =(path)[]> 0 Oct 22 14:36:43 iPhone installd(Security)[45] : Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] Oct 22 14:36:43 iPhone trustd[121] : cert[0]: SubjectCommonName =(leaf)[]> 0 Oct 22 14:36:43 iPhone trustd[121] : cert[0]: LeafMarkerOid =(leaf)[force]> 0 Oct 22 14:36:43 iPhone trustd[121] : OCSPResponse: single response has extension(s). Oct 22 14:36:43 iPhone trustd[121] : cert[0]: IssuerCommonName =(path)[]> 0 Oct 22 14:36:43 iPhone installd(Security)[45] : Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] Oct 22 14:36:43 iPhone trustd[121] : OCSPResponse: single response has extension(s). Oct 22 14:36:43 iPhone installd(libMobileGestalt.dylib)[45] : elided platform fast path for key: re6Zb+zwFKJNlkQTUeT+/w Oct 22 14:36:43 iPhone profiled[221] : Scheduling check for expired profiles between Wed Oct 23 03:00:00 2019 and Wed Oct 23 05:00:00 2019. Oct 22 14:36:43 iPhone UserEventAgent(com.apple.BackgroundTaskAgentPlugin)[24] : userEventCallback: Remove Event - token = 2030 Oct 22 14:36:43 iPhone UserEventAgent(com.apple.BackgroundTaskAgentPlugin)[24] : userEventCallback: Add Event - token = 2062, jobRequest = Oct 22 14:36:43 iPhone installd(libmis.dylib)[45] : entitlement '' has value not permitted by provisioning profile '' Oct 22 14:36:43 iPhone installd(MobileSystemServices)[45] : 0x16bcab000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 183: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.i1duNv/extracted/Payload/Inspectie App.app : 0xe8008016 (The executable was signed with invalid entitlements.) Oct 22 14:36:43 iPhone installd(MobileSystemServices)[45] : 0x16bcab000 -[MIInstaller performInstallationWithError:]: Verification stage failed Oct 22 14:36:43 iPhone runningboardd(RunningBoard)[26] : Invalidating assertion 26-45-2644 (target:application) from originator 45 Oct 22 14:36:43 iPhone SpringBoard(SpringBoard)[54] : termination assertion efficacy for com.wennet.inspectie.omniboxx (app not found) changed to 0 Oct 22 14:36:43 iPhone installd(MobileInstallation)[45] : com.wennet.inspectie.omniboxx:7:5:2:0:Fail (End) : Install (New) Oct 22 14:36:43 iPhone lsd(MobileInstallation)[81] : (null):5:1:2:0:MobileInstallation returned nil for file:///private/var/mobile/Media/PublicStaging/inspectie.ipa/ Oct 22 14:36:43 iPhone lsd(CoreServices)[81] : not writing final journal for install operation with no known bundle ID. Oct 22 14:36:43 iPhone lsd(CoreServices)[81] : install choke: after attempting to perform one operation, got role 2 Oct 22 14:36:43 iPhone mobile_installation_proxy(MobileInstallation)[278] : (null):5:1:2:0:_LSInstallationManager install:withError finished Oct 22 14:36:43 iPhone mobile_installation_proxy(MobileSystemServices)[278] : 0x16b253000 handle_install: Installation failed: Error Domain=MIInstallerErrorDomain Code=13 "Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.i1duNv/extracted/Payload/Inspectie App.app : 0xe8008016 (The executable was signed with invalid entitlements.)" UserInfo={LibMISErrorNumber=-402620394, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=183, FunctionName=+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:], NSLocalizedDescription=Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.i1duNv/extracted/Payload/Inspectie App.app : 0xe8008016 (The executable was signed with invalid entitlements.)} Oct 22 14:36:43 iPhone notification_proxy(MobileSystemServices)[279] : 0x16d0b7000 -[MNPLockdownConnection receiveMessage]: lockdown_receive_message error! Oct 22 14:36:43 iPhone mobile_installation_proxy(MobileSystemServices)[278] : 0x16b1c7000 handle_connection: Could not receive request from host. Oct 22 14:36:43 iPhone UserEventAgent(PersistentConnection)[24] : Invalidating simple timer <PCSimpleTimer: 0x10620c8a0>

myflashlab commented 4 years ago

Although AIR SDK V33.0.2-288 allowed me to build and debug on iOS 13 but it seems like the generated .ipa file cannot be uploaded to app store... I see this error when uploading the .ipa:

Your binary, ‘*******’, has a 64-bit architecture slice, so you must include the \“arm64\” value for the UIRequiredDeviceCapabilities key in your Xcode project. Learn more...”

Hopelessly, I added UIRequiredDeviceCapabilities key/value to the manifest file but again the same error.

That would be nice to figure this out too...

ajwfrost commented 4 years ago

Okay thanks for that; we'll check here.. I just reviewed the changes that were made in ADT for the 64-bit compilation problem (i.e. for building using Catalina) which may be behind some of these updates i.e. where the binary has got smaller and probably the above issue with the 64-bit architecture slice..

dseeker commented 4 years ago

Was using Animate with 32.0.0.116 to iOS 12 and was working ok. Updated to iOS 13 and was unable to test on device. Download and used 33.0.2.288, but receiving another error

ajwfrost commented 4 years ago

Thanks - so we have some IPA files that can't be transferred to the device and some that can; and we have IPAs that can be transferred to the device but not uploaded to the App Store.. Working on getting these issues resolved, but facing a few challenges due to the undocumented mechanisms that are in use here..!

zanorg commented 4 years ago

Same here : ITMS-90502: Invalid Bundle - Your binary, 'XXXXXX', has a 64-bit architecture slice, so you must include the "arm64" value for the UIRequiredDeviceCapabilities key in your Xcode project.

Compiled with Animate / AIR 33.0.2.288 on windows 7 64bits I did not try to put it on iPad for now though..

awaza001 commented 4 years ago

Me too. same. ERROR ITMS-90502: "Invalid Bundle. Your binary, 'xxx.yyy.zzz', has a 64-bit architecture slice, so you must include the "arm64" value for the UIRequiredDeviceCapabilities key in your Xcode project.

AnimateCC2020,adobe Air33.0.228 macOS10.15.1

Warning in Transporter. I cannot store delivery.

awaza001 commented 4 years ago

Solved. I was downgraded. Then I was able to register the store without problems.

MacOS15.14,AdobeAir32,AnimateCC2020

1030damian commented 4 years ago

awaza001, where did you get that?

rogerclarkmelbourne commented 4 years ago

Me too...

I get the same error on multiple installations, on OSX all using AIR 33.0.2.288

I was running Animate 2019, but just installed the update to 2020 today, but it didnt fix the problem.

I have an older machine that still had Animate 2018 on it, but where I'm using the latest AIR33 and that didn't work either.

I've tried using the old Application Loader and the new Transporter App, and that didn't make any difference.

iccoolb commented 4 years ago

I got the same error message as dseeker: Installation Error: could not not transfer the application to the device.

I tried it on different workstation and different mobile devices but always received the same error.

Setup of one of the workstations is: -Windows 10 1803 (Build 17134.765) 64-Bit -Adobe Animate 20.0 -AIR 33.0.2 -AIR 32.0.0 -iTunes 12.10.2.3 -Bonjour 3.1.0.1 -Apple Mobile Device Support 13.0.0.38 -Apple Application Support (64-bit) 8.1 -Apple Application Support (32-bit) 8.1

iPhone: iPhone XR Softwareversion 13.2

iPad: Saddly I haven't the device at hand but it's a 2017 Pro modell with latest updates (as today is 13th of November 2019) installed.

Would be nice to get this issue fixed, I'm strugglin quite a while now.

Many thanks for your support.

Kind regards

awaza001 commented 4 years ago

AIR SDK 33.0.2.315 released. https://airsdk.harman.com/download

I don't want to get along with Catalina...

rogerclarkmelbourne commented 4 years ago

I just downloaded and tested, but publishing on OSX I got "Unknown error"

I'll try on my newer OSX box and see if that has the same problem.

BTW. How do I get more information other than "Unknown error" which is not very useful...

Edit. I get the same error on Animate 2020 (very latest download) and also 2019 on another machine.

When I switch back to the previous version from Harman, it publishes and does not give "Unknown error" - but the App store rejects it :-(

iccoolb commented 4 years ago

AIR SDK 33.0.2.315 Release Notes: The SDK is not yet updated to support iOS, macOS or Windows platforms, so should only be used for Android applications. It supports 32-bit and 64-bit platforms (ARMv7, ARMv8, x86, x86_64), and will create a separate APK for each of the different architectures.

rogerclarkmelbourne commented 4 years ago

@iccoolb

OK :-(

topomonkey commented 4 years ago

Okay, so just to be clear: is there NO WAY to publish an app with air to ios 13 at the moment? Adobe didn't update air32 to work with ios 13 and Harman doesn't support ios (yet) at all?

That's just too bizarre... Or am I missing something?

htmiel commented 4 years ago

@topomonkey At least on Windows, you can use the last version of iTunes which had the "apps" tab, meaning iTunes64Setup 12.6.5.3

I use this to publish to iOS 13 devices.

ajwfrost commented 4 years ago

Yes, currently you need to use the AIR tools to create your IPA file, but Apple’s tools to transfer this to the device.

topomonkey commented 4 years ago

@htmiel thanks, so you are using air33 to publish to ios13? Or air32?

htmiel commented 4 years ago

I use AIR 33.0.2.288. I have not yet tried the latest release from a few days ago.

ajwfrost commented 4 years ago

The latest release fixes #142 for iOS but doesn't change the attempts it's making to transfer the files to the device. This does work for some people but not others ..! But we're also finding that e.g. on a new Windows 10 computer if you download iTunes from the Windows Store, the DLLs for interacting with Apple devices are kept private.. so we are having to look at even more of a workaround that doesn't even use their private APIs.. (I am getting the impression that Apple want to be the only ones to be able to interact with their devices..)

So in terms of publishing, you can create the IPA file still with AIR, but you can't install it onto a device: for this part, you need to take the IPA and use iTunes or XCode (or another utility..?)

rogerclarkmelbourne commented 4 years ago

AIR 33.0.2.315 on Mac does not even generate an IPA.

And IPA's created by 288 get rejected by the App Store

@ajwfrost & @htmiel Are you saying that if you manually create an IPA on windows using 288 or 315 it can then be uploaded to the App store ?

I've noticed on Adobe's forum, someone reported the App store problem, but then updated their post to say it had started to work.

My guess would be that some parts of the AIR API are missing something now required by Apple, so it would depend on what you App uses, whether the App store reject it.

Unfortunately my app uses all sorts of stuff including StageWebView and StageText and also has multiple ANE's :-(

awaza001 commented 4 years ago

rogerclarkmelbourne Catalina is bad.If you downgrade macOS to ver10.14 and use air32, you can register in the AppStore

rogerclarkmelbourne commented 4 years ago

@awaza001 From what I can remember, there was a problem using AIR 32 which required me to update to AIR 33 288, but I can't remember what it was.

However it was likely to be the same sort of issue that we are now contending with i.e Apple change something to block Adobe AIR apps, because they don't really want people developing apps using anything else except XCode

airsdk / Adobe-Runtime-Support

iOS 13 and AIR SDK finds but does not connect to the device #112