Highlighted

AIR 29+ can not debug app on iOS. App is never installed on the device

Engaged ,
May 23, 2018

Copy link to clipboard

Copied

When I try to debug iOS app with Flash Builder 4.7 and with AIR 29 or 30 Beta the app is not installed on the device. Compilation is completed and I get the message that I need to open the app but app is never installed on devices. I tried manually to install app by going to bin-debug folder and trying to install ipa from there but it says that app ipa is corrupted or not compatible with iOS 11.

Is anyone able to debug app on iOS with AIR 29 or AIR 30 Beta?

This is now solved and is working properly with latest AIR SDK 31.

TOPICS
Development

Views

4.7K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

AIR 29+ can not debug app on iOS. App is never installed on the device

Engaged ,
May 23, 2018

Copy link to clipboard

Copied

When I try to debug iOS app with Flash Builder 4.7 and with AIR 29 or 30 Beta the app is not installed on the device. Compilation is completed and I get the message that I need to open the app but app is never installed on devices. I tried manually to install app by going to bin-debug folder and trying to install ipa from there but it says that app ipa is corrupted or not compatible with iOS 11.

Is anyone able to debug app on iOS with AIR 29 or AIR 30 Beta?

This is now solved and is working properly with latest AIR SDK 31.

TOPICS
Development

Views

4.7K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
May 23, 2018 1
Adobe Employee ,
May 23, 2018

Copy link to clipboard

Copied

Hi,

Thank You for reporting the issue. Please log a bug on Tracker for the same.

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2018 0
Community Beginner ,
May 25, 2018

Copy link to clipboard

Copied

Created the ticket - Tracker

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 2
Engaged ,
May 25, 2018

Copy link to clipboard

Copied

Denis, thanks for creating the ticket.

The issue is still present with latest AIR SDK Beta 30.0.0.103.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0
Adobe Community Professional ,
May 25, 2018

Copy link to clipboard

Copied

I can debug with AIR 29 or 30, but did have a combination where the app didn't install. For me it was because I was using an Enterprise Ad Hoc certificate. I changed to a non-Enterprise developer profile, and then debugging worked well.

If you're trying Enterprise too, I think the difficulty may be that you have to go into Settings, General, Profiles & Device Management, to give the installed app permission to run. So, Flash Builder trying to do that automatically is likely to fail.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0
Engaged ,
May 25, 2018

Copy link to clipboard

Copied

Hi Colin,

I did not use Enterprise, just a regular development certificate. On which system are you?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0
Adobe Community Professional ,
May 25, 2018

Copy link to clipboard

Copied

Some future version of macOS. Also, I use Animate, but that still shares ADT in common with FB. Any failure to install the app from FB is likely to happen with the same conditions from Animate, and it certainly was failing for me.

Something else that may have failed for me was doing a debug build with a non-Enterprise AD Hoc certificate. I either found that had the same problem, or I skipped trying that, can't remember.

Are you using Development or Distribution certificates and profiles?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0
Engaged ,
May 25, 2018

Copy link to clipboard

Copied

I am using Development certificate and Development provision profile. I also tried using Distribution certificate and Development provision profile but that does not work either.

I can not use Distribution provision for debugging because when debugging flash is always automatically adding .debug to the app id like com.adobe.ShapesInMotion.debug.

I am on latest Windows 10 and Flash Builder 4.7

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0
New Here ,
May 25, 2018

Copy link to clipboard

Copied

The issue is still present with latest AIR SDK 30beta & 29.0.0.122.

OS: Windows7

IDE: FlashBuilder 4.7 (64bit)

TestingDevice:

iPhone5(iOS8.4.1)

iPhoneSE(iOS10.3)

iPhone6 plus(iOS11.3.1)

iPhone7(iOS11.3)

iPhoneX (iOS11.3.1)

iPadAir2(iOS11.3.1)

iPadMini4(iOS11.3.1)

[AIR 28.0.0.127]

debug cert + debug profile = OK

adhoc&dist cert + adhoc profile = OK

[AIR 29.0.0.112]

debug cert + debug profile = OK

adhoc&dist + adhoc profile = OK

[AIR 29.0.0.122] (AppStore Rejection HiddenAPI FIX)

debug cert + debug profile = Fail

adhoc&dist + adhoc profile = Fail

[AIR 30.0.0.93 Beta]

debug cert + debug profile = Fail

adhoc&dist + adhoc profile = Fail

[AIR 30.0.0.103 Beta]

debug cert + debug profile = Fail

adhoc&dist + adhoc profile = Fail

This is obviously a ploblem of SDK. not certificate.....

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 3
Adobe Community Professional ,
May 25, 2018

Copy link to clipboard

Copied

I'm sure that it's the SDK that has introduced the problem, and the bug report will help solve that. But I am able to do debug testing with AIR 30.0..0.103.

I just confirmed that I could, and I also tested with Distribution Ad Hoc. Developer certification and profile definitely worked, and Distribution Ad Hoc definitely failed to install the app. Console showed:

dataStdErr:

Installation Error: ApplicationVerificationFailed.

I also tried distribution and with target as ipa-debug. Still failed to install.

So, for me at least, only developer certificate and profile works with AIR 30.

BTW, if I use AIR 26, distribution ad hoc works, and I can debug ok.

I'll add a note to the bug report, so that they don't get sidetracked too much blaming FB or IntelliJ.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 4
New Here ,
Jun 19, 2018

Copy link to clipboard

Copied

Hi Colin, do you mind explaining how you managed to debug the device plugged on your machine running FB? Just to be clear, I need to put breakpoints on FB and run the app on the device, did you manage to accomplish that?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 19, 2018 2
Adobe Community Professional ,
Jun 19, 2018

Copy link to clipboard

Copied

I was giving suggestions about things that stopped AIR from installing at all, not Flash Builder specific. Under High Sierra my Flash Builder crashes when trying to configure things, so I can't easily test to see how far I get.

I see in the bug tracker that the latest AIR that has been tested is the 30.0.0.103 beta. Are the issues still true with the release 30.0.0.107? Could be worth adding a note to the bug report, at least for the fact that Amrita will get notified that there's still a problem.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 19, 2018 0
Engaged ,
Jun 19, 2018

Copy link to clipboard

Copied

Since May 20 I haven´t been able to install iOS apps on my iPad with Distribution Certificate and Profile using AIR SDK 30.0.0.107 and Animate.

same error always:

Installation Error: ApplicationVerificationFailed.

I can publish using AIR SDK 30.0.0.107 with Developer Certificate and Profile but that won´t go up the App Store.

I had been reporting the issue here:

Request for an update on the steps required to successfully build an iOS app with Adobe Animate CC

The team's response was, "Currently, we have SDK 26 in Animate. No changes have been made to Adobe Animate. To use the latest SDK, include the AIR_30_assert.car file that is created by xcode in the "AIR for iOS settings" of the AIR iOS doc under "included files" section."

But that doesn´t fix the problem.

- I reinstalled everything: Mac os High Sierra - Adobe Animate - Apple Certs & Profiles - Xcode - iPad -

That did not solve the problem either...

I wonder what anyone else using Animate is doing to upload apps to the App Store.

I hope we can get soon a solution.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 19, 2018 2
Adobe Employee ,
Jun 19, 2018

Copy link to clipboard

Copied

Hi,

To debug the application you may use a developer certificate and a developer provisioning profile on both Flash Builder as well as Animate CC.

It is known that you cannot install the ipa-app-store type application packaged with distribution certificate and distribution provisioning. But the app should upload fine on App store.

For beta testing of the application, you may use distribution certificate and Ad hoc provisioning with target type as ipa-ad-hoc. It should successfully install on your test devices.

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 19, 2018 0
Engaged ,
Jun 20, 2018

Copy link to clipboard

Copied

Hi Amrita,

I use Adobe Animate because without knowing code I can build my apps. Honestly I have never needed to debug my apps so I don´t know really how to do it. What I did was to use a Developer Certificate and Profile, on the AIR FOR IOS SETTINGS > DEPLOYMENT > DEVICE DEBUGGING IN INTERPRETER MODE and on the "Debug" menu I selected Debug Movie > On Device via USB. Then I tried to upload the resulting .ipa with Application Loader but I got this message:

ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.musycom.PianoSheetReadingPRO [Payload/Piano Sheet Reading PRO.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."

Can you orient me on how to debug the app in order to upload it to the App Store?

Best Regards!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 20, 2018 0
Engaged ,
Jun 20, 2018

Copy link to clipboard

Copied

Amrita,

I can not debug application with any certificate on FB using air 30. App is still never installed on the device. I am using FB 4.7 and latest windows 10

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 20, 2018 0
Adobe Employee ,
Jun 20, 2018

Copy link to clipboard

Copied

Hi,

To upload the application on App Store you will have to package the application using Distribution Certificate and Distribution provisioning.

For debugging purpose you may use Developer provisioning and Developer certificate.

Here is the gist of it all:

Upload to App Store: Distribution Certificate + Distribution provisioning

Beta Testing the App: Distribution Certificate + Adhoc Provisioning

Debugging the App: Development Certificate + Development Provisioning

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 20, 2018 0
New Here ,
Jun 20, 2018

Copy link to clipboard

Copied

adobe seems to have not noticed that this problem is on Air SDK...

I have not changed anything.

Only the SDK version(AIR 29.0.0.122 and later) is the cause of the problem...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 20, 2018 3
Engaged ,
Jun 21, 2018

Copy link to clipboard

Copied

I´m using SDK 30.0.0.107 but I can´t build the app with Distribution Cert & Prof.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 21, 2018 0
Adobe Community Professional ,
Jun 21, 2018

Copy link to clipboard

Copied

If you only build the app by doing a Test Movie/On Device via USB, then you wouldn't be able to make an IPA that is App Store and Distribution settings. But, you can select the right certificate and profile, and build for App Store, then use the File menu to select Publish. That should give you an IPA that you can upload to Apple.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 21, 2018 1
Engaged ,
Jun 21, 2018

Copy link to clipboard

Copied

Hi Colin,

Thanks for your always appreciated advice.

I already selected the right Distribution certificate and the App Store profile, then built for App Store, then used the File menu to select Publish. That gave me an .ipa as you say. But when I tried to upload it to App Store I got this:

ERROR ITMS-90179: "Invalid Code Signing. The executable 'Payload/Piano Sheet Reading PRO.app/Piano Sheet Reading PRO' must be signed with the certificate that is contained in the provisioning profile."


Best Regards

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 21, 2018 0
Adobe Community Professional ,
Jun 21, 2018

Copy link to clipboard

Copied

That would happen if you have made a provisioning profile and then renewed your developer subscription, created a new P12 file, but don't go back and edit the profile. The profile has to be based on your current valid certificate, the same one that gave you the P12.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 21, 2018 2
Engaged ,
Jul 05, 2018

Copy link to clipboard

Copied

Hi Amrita Gangwani​,

Debugging is still not working with AIR 30.0.0.107 on iOS even if I use Development Certificate + Development Provisioning Profile.

I am using Windows 10, Flash Builder 4.7, iPhone X with iOS 11.4 and AIR SDK 30.0.0.107 and debugging does not work on iOS.

Application is built ok but is never installed on the device. It also does not work with AIR 28.0.0.125 and AIR 27.0.0.132.

I think this stopped working for iOS 11.

Regards,

Caslav

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 05, 2018 0
Adobe Employee ,
Jul 05, 2018

Copy link to clipboard

Copied

Hi Caslav,

I would suggest you to try installing the application after uninstalling any previous version of the app from the device. Have you tried installing the application on any other iOS version? What is your observation for the same?

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 05, 2018 0
Engaged ,
Jul 06, 2018

Copy link to clipboard

Copied

Hi Amrita,

Yes I always do that, but the result is the same. Application is never installed on the device. And whether I choose fast or standard compile option does not matter either.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 06, 2018 0
Community Beginner ,
Jul 12, 2018

Copy link to clipboard

Copied

chaky, I still able to debug with AIR27 (iOS 10, 11)
But AIR30 is still doesn't allow me to do it.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 12, 2018 0
Engaged ,
Jul 12, 2018

Copy link to clipboard

Copied

Hi Denis,

I don't know why I can't. What is your env. Do you use Windows or Mac OS, do you use Flash Builder?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 12, 2018 0
Contributor ,
Jul 12, 2018

Copy link to clipboard

Copied

I'm also continuing to have this same problem. I've checked my dev certificate, my provisioning profile, my app ID, etc, and I still get either ApplicationVerificationFailed or the APIInternalError every time I try to debug on my iPhone via USB. I'm on the Mac and use IntelliJ IDEA for development.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 12, 2018 0
Adobe Employee ,
Jul 12, 2018

Copy link to clipboard

Copied

Hi,

In that case, please refer Troubleshooting common Adobe AIR installation errors with iOS applications.​ Also, ensure that your Device's UDID is included in the provisioning profile.

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 12, 2018 0
Community Beginner ,
Jul 13, 2018

Copy link to clipboard

Copied

chaky, Win8 x64 + IntelliJ IDEA

Distribution certificate and provisioning profile (adhoc)
Check your certificate/profile dates, try to debug w/o anes.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 13, 2018 0
Contributor ,
Jul 16, 2018

Copy link to clipboard

Copied

Thanks Amrita and Denis for your feedback. I'm sorry to report that I'm still getting error messages even though I've tried the things that you suggested.

Here are some details...

I'm doing my testing with a minimal app that does almost nothing. I'd be glad to provide this code if it would be helpful.

I'm randomly getting either an APIInternalError or an ApplicationVerificationError.

This doesn't happen with AIR 28, but does happen with AIR 30.

Amrita wrote:

> In that case, please refer Troubleshooting common Adobe AIR (http://blogs.adobe.com/flashplayer/2015/08/troubleshooting-air-installation-errors-ios-applications....) installation errors with iOS applications.

This page suggest four possible causes for this problem:

1. "Wildcard characters used in application id". I'm not using wildcard characters in my ID.

2. Problems related to an <Entitlements> tag in my app XML. I have no such tag in my app XML.

3. "Wrong certificate used for packaging". This one is a bit vague. I've gone over the steps for creating my certificate and provisioning profile and am fairly sure that I'm doing this correctly. The fact that I can debug using AIR 28 suggests that I am.

4. "device UUID is not listed in the provisioning profile". I've double-checked to make sure that I have the correct device ID in my provisioning profile.

Denis wrote:

> Distribution certificate and provisioning profile (adhoc)

If I understand this correctly you're saying that I should use a distribution cert and an adhoc provisioning profile.

I've tried this, and also tried using a development cert and profile. Both work with AIR 28; neither works with AIR 30.

> Check your certificate/profile dates

I've created both my certs and my profiles from scratch.

> try to debug w/o anes.

I'm doing my testing with a "minimal app" which I've created, which does very little and uses no ANEs.

It looks as though this is definitely a problem with AIR 30.

For now I'll do my debugging with AIR 28, then publish with AIR 30, but this does need to be fixed.

Amrita - have you or your colleagues at Adobe successfully debugged on iOS via USB with AIR 30? If so, is it consistently problem-free, intermittent problems, consistent failure, or what?

Thanks,

Douglas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 16, 2018 2
Explorer ,
Jul 16, 2018

Copy link to clipboard

Copied

I too am having this issue. Please note that I am an Adobe Certified Expert (ACE) for Flex 4.6 (before Adobe discontinued the ACE program), and I have been developing Flash/Flex/AIR apps since Flex 3.0. I have created quite a few commercial AIR apps and this problem only manifests in AIR 30 (and 29 I might add, but that was due to beta-reports-active entitlement that is no longer being written to the embedded.mobileprovision file).

Here is the iOS Console output showing what appears to be a malformed entry:

Jul 16 14:26:35 Eriks-iPhone-6 installd(libmis.dylib)[3043] <Notice>: entitlement '<private>' has value not permitted by provisioning profile '<private>'

Jul 16 14:26:35 Eriks-iPhone-6 installd(MobileSystemServices)[3043] <Notice>: 0x16ef3f000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 147: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.FOc3EW/extracted/Payload/keiretsuforum.app : 0xe8008016 (The executable was signed with invalid entitlements.)

Thank you for your kind consideration and there's really no need to send me links to pages that teach how to develop or troubleshoot AIR apps. This appears to be a problem introduced in AIR 30.

We haven't had a fully functioning AIR release since version 27 due to the public APIs problem, followed by the beta-reports-active entitlement problem, now followed by this new problem. Sure appreciate if you could take this seriously.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 16, 2018 2
Community Beginner ,
Jul 24, 2018

Copy link to clipboard

Copied

Hi,

I guess I face the same problem, I am not able to debug on a connected device with developer certificate and profile:

Installation Error: ApplicationVerificationFailed.

or

Installation Error: APIInternalError.

My app update is uploaded for beta testing to Apple, but rejected („no further action after launch screen“) and I can not debug. But I can reproduce the problem by installing the beta version with testflight.

With iOS simulator the bug does not happen, app works fine…

Douglas, the workaround with a fallback to air 28 does not work for me, the following error occurs:

ld: library not found for -lgcc_s.1

So I took a look at the iOS debug console (Xcode) but I do not understand the logs…

Maybe someone can help with a guide on how to use the iOS debug log messages in Xcode to debug air applications?

Or is the best option for an unexperienced person to wait for adobe to bring the debug option to work again?

Any help is appreciated!

Best Regards,

Martin.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 24, 2018 2
Contributor ,
Jul 24, 2018

Copy link to clipboard

Copied

Hi Martin,

> the workaround with a fallback to air 28 does not work for me, the following error occurs:

> ld: library not found for -lgcc_s.1

> Maybe someone can help with a guide on how to use the iOS debug log messages in Xcode to debug air applications?

I'm sorry, but I don't have experience with either of these ... if it was my project I'd start by googling the error ... but I wouldn't count on getting anything useful ...

Perhaps someone else could help?

> Or is the best option for an unexperienced person to wait for adobe to bring the debug option to work again?

Good question. It seems that this is a big enough problem that the AIR team would be working on it, but it's not clear whether that's the case. The bug's (https://tracker.adobe.com/#/view/AIR-4198657) status is "To Test". Does anyone know what this means? Does it mean "test to confirm that there's a bug" or "test to confirm that we have a fix"?

If you haven't done so already please vote and comment on the bug.

My general experience with AIR is that the team eventually deals with major problems like this, but it can take weeks or months. On the one hand, AIR is wonderful, with many advantages over writing native code. On the other hand, it's pretty clear that the AIR team has a lot on their plate compared to the resources they have available, and problems like this keep rearing their heads, and it can take a while for them to get fixed. And, as you know, these slow fixes can create serious problems for AIR developers.

Douglas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 24, 2018 0
Community Beginner ,
Jul 25, 2018

Copy link to clipboard

Copied

Hi Douglas,

thanks for your help and the link to the bugs report page - I voted for it.

Looking forward that this will be fixed or some workaround will be found.

Best Regards,

Martin.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 25, 2018 0