AppStore rejection

[nikola....@leadit.rs]

Hello,

Recently, our app was rejected from the AppStore with following message:

We discovered that your app contains obfuscated code, selector mangling, or features meant to subvert the App Review process by changing this app's concept after approval to the App Store.

The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.

Next Steps

- Review the Performance section of the App Store Review Guidelines.
- Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program. 
- Once your app is fully compliant, resubmit your app for review.

Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the Terms & Conditions of the Apple Developer Program to learn more about our policies regarding termination.

If you believe your app is compliant with the App Store Review Guidelines, you may submit an appeal. Alternatively, you may provide additional details about your app by replying directly to this message.

Libraries we use in our codenameOne project are - BouncyCastleSDK, CN1-Helper, Codename One Data Access Library, Codename One Google Native Maps Support, COdename One JSON Library, codenameone-connectivity, Device.

We published another app to the App store, and the only difference are maps, since we didn't have them before.

Is there anything in these libraries that was changed and could cause some problems with the app store?

Thank you

If you are experiencing an issue please mention the full platform your issue applies to:
IDE: NetBeans/Eclipse/IDEA
Desktop OS
Simulator
Device

[Shai Almog]

Hi,

that's very odd. I've never seen this type of rejection before. Can you provide details about the cn1libs or native libraries that you use within the app?

[shannah]

There are quite a few references to this type of rejection.  E.g. 

From 2017:

https://forums.developer.apple.com/thread/88716

https://stackoverflow.com/questions/46568675/appstore-rejected-because-of-code-obfuscation-and-selector-mangling-none-is-don

https://github.com/Microsoft/code-push/issues/616

https://github.com/Estimote/iOS-Fleet-Management-SDK/issues/267

From this month:

https://stackoverflow.com/questions/55783050/apple-rejected-the-binary-2-3-1-performance-after-upgrading-to-react-native

But none of those really shed light.

The only useful bit of advice I gleaned from there was

you can use the /usr/bin/nm tool for outputting the symbols within your raw executable and see if any of those look "mangled" in any way.

I expect that that will give you a *lot* of output.

The best course of action is to reply to them and ask for more clarification.  

Steve 

[nikola....@leadit.rs]

Hi all,

I'll just reply here, we sent message to Apple support, since we needed some clarification about which part is giving us trouble, and after a while they responded with a generic answer, and continued with the review of the app as if nothing happened. The app was approved a few minutes after their response, so unfortunately, there was no real answer on what was the problem. It seems that a lot of apps built with something that isn't pure Objective C/Swift code were getting this error in the last month or two, so maybe Apple started changing something, or they made some errors themselves.

Thank you for your answers.