Skip to main content
gameduchy
gameduchy
Participant
March 31, 2018
Question

IOS is blocking AIR, rejected for months,due to AIR has API using IOPSCopyPowerSourcesInfo

  • March 31, 2018
  • 41 replies
  • 30556 views

Our mobile game uses FLash, and AIR 29 to make it work on IOS devices,

However, we can't upgrade our game since half year ago, and Apple review team finally told us the reason:

REJECTED：

Thanks for your resubmission.

Guideline 2.5.1 - Performance - Software Requirements

Your app uses or references the following non-public APIs:

_IOPSCopyPowerSourcesInfo, _IOPSCopyPowerSourcesList, _IOPSGetPowerSourceDescription

The use of non-public APIs is not permitted on the App Store because it can lead to a poor user experience should these APIs change.

Continuing to use or conceal non-public APIs in future submissions of this app may result in the termination of your Apple Developer account, as well as removal of all associated apps from the App Store.

Next Steps

If you are using third-party libraries, please update to the most recent version of those libraries. If you do not have access to the libraries' source, you may be able to search the compiled binary using the "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 tools can help you narrow down where the problematic code resides. You could also use the "nm" tool to verify if any third-party libraries are calling these APIs.

Resources

For information on the "nm" tool, please review the "nm tool" Xcode manual page.

If there are no alternatives for providing the functionality your app requires, you can file an enhancement request.

Then we found it's in AIR sdk, even 29.

Then we replied:

The earlier letter said our app has the following non-public APIs:

"_IOPSCopyPowerSourcesInfo", "_IOPSCopyPowerSourcesList" and "_IOPSGetPowerSourceDescription".

We checked the ipa file with the tools you suggested.

"nm" and "oTool" found none.

The tool "strings" only found "IOPSCopyPowerSourcesInfo", "IOPSCopyPowerSourcesList" and "IOPSGetPowerSourceDescription" (non-underlined) referenced.

After searched the non-underlined version from the apple develop center, we thought they are public APIs.

However, we never called them.

These were found in the popular SDK Adobe AIR, and were alone there for years.

We haven't got any alternatives beyond Adobe AIR.

    This topic has been closed for replies.

    41 replies

    Show previous replies
    N
    niestudio
    Participating Frequently
    April 19, 2018

    I re-submitted our app with Air29 build 122, but it was still rejected for the same reason.

    I cleaned the project and rebuilt again only to find those strings still there.

    Any advice for something I might have missed?

      O
      OMA2k
      Inspiring
      April 20, 2018

      My app was approved with AIR 29 Build 122 after having been rejected with a previous build of AIR 29.

      Could you please tell me how to get those strings from the compiled IPA?

      Amrita Gangwani
      Adobe Employee
      Amrita Gangwani
      Adobe Employee
      April 18, 2018

      Hi,

      AIR ADK version 29.0.0.122 has been released. The Apple store app rejection issue, Tracker is addressed with this build. You may download the build from Download Adobe AIR SDK

      Thanks!

      I
      ivanp2689695
      Known Participant
      April 20, 2018

      Wasn't fixed. Apps are still rejected.

      Probably reason is that Adobe is testing this version of the SDK on Windows only?

      P
      pauland
      Participating Frequently
      April 20, 2018

      I made a submission to Adobe using the Adobe beta SDK 29 from a Mac, with no problem.

      M
      marcanw
      Inspiring
      April 13, 2018

      My app has been approved by Apple.

      Thx Air Team :-)

        jprankard
        jprankard
        Participating Frequently
        April 13, 2018

        I also had an issue when testing Ad-Hoc (enterprise certificate). But I regarded it as something odd with my certificates/signing process (there are many issues with signing certificates).


        I did manage to get around it to test before submitting to the app store but re-signing my ad-hoc IPAs and then testing those.

        I generated the IPA from Adobe Animate, then resigned with the same certificate/key on mac with this tool 'IPA Sign':

        GitHub - RichardBronosky/ota-tools: A burgeoning collection of tools for Over-The-Air distribution of mobile application…

        Then I used i-Funbox to install the IPA to the device quickly without having to do uploading/download with enterprise plist:

        iFunbox | the File and App Management Tool for iPhone, iPad & iPod Touch.

        Is everyone having this certificate issue when generating AIR 29.0.0.112 ad-hoc?

        E
        Evan_Gilbert
        Participant
        April 13, 2018

        On AIR 29.0.0.112 Ad Hoc worked just fine for me.

        AIR 29.0.0.122 was where I had Ad Hoc issues.

          E
          Evan_Gilbert
          Participant
          April 13, 2018

          I'm also having trouble making an Ad Hoc build. I think I might have figured out what's going on however...

          It appears to relate to the new "beta-reports-active" Entitlement. This entitlement is only supposed to exist on the App Store profiles (based on my exploring of an App Store and Ad Hoc provisioning profile). I just made an Ad Hoc build with the new AIR 29 and my app.xml did not specify "beta-reports-active" in the Entitlements section. However, unzipping the resulting ipa and running 'codesign -d --entitlements :- "Payload/MyApp.app"' for some reason "beta-reports-active" has been added. This is causing an "The executable was signed with invalid entitlements" error when trying to load it onto a valid device. Also of note is that the previous AIR 29 does not do any of this nonsense with the "beta-reports-active" Entitlement.

          Hope this helps!

            SangHee
            SangHee
            Known Participant
            April 17, 2018

            My case is the same.

            I did not specify "beta-reports-active" in descriptor file (.xml).

            By the way ...

            when it was built with air 29.0.0.122,

            "beta-reports-active" was added automatically.

            But this was not added in air 28 or air 27.

            jprankard
            jprankard
            Participating Frequently
            April 12, 2018

            New AIR 29 app has now been accepted by Apple (mine had 2 ANE’s).

            Thanks for the quick turnaround @chris and adobe.

            Regarding the Assets.cab. Its better for us to have a format Apple generate/approve. That way we don’t have to wait for an adobe air update when Apple require a new icon size.

              Anki_AG_
              Adobe Employee
              Anki_AG_
              Adobe Employee
              April 13, 2018

              Hi Developers,

              App Store submission issue has been fixed. Please download the AIR SDK from Download Adobe AIR SDK. Kindly let us know in case you face any issues.

              Thanks,

              Ankit | Adobe AIR Engineering

              R
              robertoc23790038
              Participating Frequently
              April 13, 2018

              I can't install AdHoc apps generated with this version.....

              Thanks

                jprankard
                jprankard
                Participating Frequently
                April 11, 2018

                Built with beta version 29.0.0.122 on Adobe Animate CC. Submitted to apple for review.

                Will try to remember to post back here if it is all good, but if you hear nothing it's all gone well

                S
                shdfgfjty7
                Participant
                April 11, 2018

                Is there a way to overlay Flex and AIR SDK with provided 122 build? I use this instruction on Mac Overlay Adobe AIR SDK on Adobe Flex SDK | Adobe Flash Builder​​ with AIRSDK_Compiler.dmg downloaded from Shared Files - Acrobat.com , but get errors during compilation like Error: Unable to locate specified base class 'spark.components.Application' for component class 'Main'.

                Maybe I'm doing anything wrong?

                A
                Aymeric-
                Known Participant
                April 11, 2018

                Strangely, even if I knew there was an issue with AIR and iOS, I made a build with AIR 27 two days ago and it was approved yesterday. Someone had the same experience? Perhaps Apple changed something on their side?

                I'm on Mac OS High Sierra 10.13.4, with Xcode 9.3 and AIR SDK 27.

                The app uses Citrus Engine and many libs (Starling, Feathers, TweenMax...) and somes ANEs :

                M
                marcanw
                Inspiring
                April 11, 2018

                Apple review is a bit random.

                J
                joeboy_uk
                Inspiring
                April 10, 2018

                at least we have a fix coming. will look forward to that

                mcorbex
                mcorbex
                Participant
                April 10, 2018

                Hi Chris,

                Could you please give the url of the release channel for those like me who don't know it yet ?

                Best regards,

                Matt

                chris.campbell
                Community Manager
                chris.campbellCommunity Manager
                Community Manager
                April 10, 2018

                Hi all,

                Here are the updated versions of the AIR SDK that we believe fix the issue reported in this thread.  We're still in the process of testing and would appreciate feedback from the community.  If everything looks good, we hope to update the official download page with this build within the next few days.

                Windows AIR SDK 29.0.0.122

                Mac AIR SDK 29.0.0.122

                Thanks,

                Chris

                  Show more replies
                  Terms & ConditionsAccessibility statement
                  Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices