6 Replies Latest reply on Jun 22, 2016 2:02 AM by App runner KG

    Adobe Air SDK 20 is not accepted by Apple

    App runner KG Level 1

      I downloaded the new Adobe Air SDK 20 and built my OSX App.

      First of all the file inside is different and there is no instruction how to sign the file in the right way. Finally I solved the signing problem, and I was able to send the App to the Mac OSX AppStore.

      But then Apple rejected the App, see below. I pay monthly fees for using Adobe products and there is absolutely no support and updates only causes headache.

      Please fix this bug or tell me how to codesign an application correctly with SDK 20.

      January 7, 2016 at 10:01 PM


      • 2.5 - Apps that use non-public APIs will be rejected



      The use of non-public APIs can lead to a poor user experience should these APIs change in the future, and is therefore not permitted. The following non-public APIs are included in your application:


      : OBJC_IVAR_$_NSView._bounds
      : OBJC_IVAR_$_NSWindow._frame


      If you have defined methods in your source code with the same names as the above-mentioned APIs, we suggest altering your method names so that they no longer collide with Apple's private APIs to avoid your application being flagged in future submissions.


      Additionally, one or more of the above-mentioned APIs may reside in a library included with your application. If you do not have access to the library's source, you may be able to search the compiled binary using "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.


      If you are unable to reproduce this issue, ensure you are testing the exact version of the app that you submitted for review, and that you're doing so in a minimally privileged environment. See Technical Q&A QA1778: How to reproduce bugs reported against Mac App Store submissions.


      For information on how to symbolicate and read a crash log, please see Technical Note TN2123 - CrashReporter.