do you see that in your manifest?
Hello. Thanks for reply.
If you mean if I see the keys in myApp.xml descriptor the answer is no.
If you mean if I see the keys in info.plist after building the .ipa the answer is yes.
Air compiler adds UIRequiredDeviceCapabilities key during the building process.
i see that too in the plist, but haven't had an app rejected because of it. i've submitted 6 apps this month with 5 pending review and 1 accepted for sale in the app store.
they were all published with air 184.108.40.206 and i suspect they all contain that key and values. i inspected the one app's plist that was accepted on the store and it definitely contains those key/values.
if it were a problem, i would change the plist manually and rezip and rename to an ipa and resubmit. but i really think you should use the latest air sdk to rebuild your app and retry submitting: Archived Adobe AIR SDK versions
I finally found a solution for this issue and want to share it here in order to help all developers facing the same problem.
I downloaded an App for Mac called AirSign (https://www.airsignapp.com/), wich allows to edit and re-sign .ipa assuming that you own proper certificate and provisioning profile.
Using this App i was able to remove the unwanted Required Functions (opengles-2 and armv7) and then export to Xcode Archive.
Then I opened the archive with XCode and packaged the new .ipa from there.
Finally I uploaded the ipa from Application Loader.
Note that AirSign can repack the ipa but for some reasons I don't know it is not accepted when uploading with the Application Loader.
I really hope this can help and I guess why Adobe is not interested in this problem.
To answer Kglad about app not rejected:
The problem is not present for new apps. Apple do accepts UIRequiredDeviceCapabilities key, that is very important to prevent those devices which haven't some capabilites to install an app and then cannot run it.
The matter is when upgrading an old app, wich doesn't have the UIRequiredDeviceCapabilities key in info.plist.
In this case Apple will reject any upgrade having that key because, for the same reason explained before, the new app (wich requires specific capabilities) may not run on some devices that have the old app (wich did not require any specific capability).
Hope this can clarify.