AppStore rejects due to code obfuscation and selector switch: nothing has been done in the application

Question

My iOS app has gone through several releases. I added another function (playing audio files using facebook audio360 tbe format), and the application was rejected with the wording:

From Apple 2. 3 Performance: An Accurate Metadata Guide 2.3.1 - Performance

We found that your application contains hidden features. In particular, it would be appropriate to remove all obfuscation and the code selector using this application before resubmitting for viewing.

The following presentation of this application may require a longer viewing time.

Next steps

• Review the Performance section of the App Store Review Guide.
• Make sure your application is compatible with all sections of the App Store Review Guide and the Apple Developer Program Terms of Use.
• Once your application is fully compatible, resubmit your application for viewing.

Submitting applications designed to mislead or harm customers or avoid the verification process may result in the termination of your Apple Developer Software Account. Check out the Apple Developer Program Terms of Service to learn more about our termination policies.

If you think your app is compatible with the App Store review of the Guide, you can file an appeal. Alternatively, you can provide additional information about your application by directly responding to this message.

I am not doing “code obfuscation and selector manipulation”, filed an appeal, which was also rejected, pointing to the same recommendation.

I use objective-c with some quick ones, Xcode 9, Product -> Archive -> Submit to App Store ... Is this some kind of obfuscation that I can turn off?

Answer 1

Perhaps your sound reproduction function uses a third-party structure that uses code obfuscation?

In any case, you can use the / usr / bin / nm tool to output the characters inside your raw executable and see how any of them looks “distorted” in any way.

Answer 2

Here's how I solved this problem: I added another function to my application and sent it again. This time Apple has accepted it. So I have no idea why this was not accepted the first time.

Answer 3

This is most likely a third-party library that does this.

I used Hopper to get to know the library.

First, unzip the ipa and get the application file.

Secondly, drag it to Hopper and start scanning.

Thirdly, the search for mutilated selectors.