“as is” I would say it does not support it completely yet
but then your best bet is to use the Harman AIRSDK and report issues to them
a quick search for “iOS 13” bring some issues
you will see @ajwfrost answer most of them
so my guess is that Harman is working on supporting iOS 13
also in the release notes you can see
iPhoneOS SDK Version: 13.2
iPhoneSimulator SDK Version: 13.2
so yeah they do use the iOS 13 SDK
but you can also read
10 iOS support
For deployment of AIR apps on iOS devices, the AIR Developer Tool will use the provided tools to extract the ActionScript Byte Code from the SWF files, and compile this into machine code that is then linked with the AIR runtime and embedded into the IPA file. The process of ahead-of-time compilation depends upon a utility that has to run with the same processor address size as the target architecture: hence to generate a 32-bit output file, it needs to run a 32-bit compilation process. This causes a problem on MacOS Catalina where 32-bit binaries will not run.
For this reason, it is not possible to create a universal binary (embedding both 32-bit and 64-bit ARM code) using MacOS Catalina (10.15) or later. The tools will only run the 64-bit version and the IPA files will be limited such that they only install onto 64-bit devices. To summarise the process/requirements:
Using MacOS versions up to and including 10.14, an IPA will be created that contains a universal binary with both 32-bit and 64-bit code in it. This can be installed onto older iOS devices that do not support 64-bit, as well as newer devices.
Using MacOS 10.15 upwards, with the restriction where we cannot run 32-bit executables, the IPA file will only contain the 64-bit code. These IPA files can only be installed onto 64-bit devices; there is an updated device requirements setting that is added automatically into the Info.plist file in this case.
Using Windows, developers can continue to support 32-bit and 64-bit generation as before.
so be careful about that too
As always I will advise to actually do the tests instead of guessing around etc.
just test it with code, either it works and you’re good to go, if not you got somewhere where you can report issues
spending too much time “I wonder if …” is a waste a of time imho