- Guideline 2.3.1 – Efficiency
- Guideline 2.5.2 – Efficiency – Software program Necessities
Your app, extension, or linked framework seems to comprise code designed explicitly with the potential to alter your app’s conduct or performance after App Evaluate approval, which isn’t in compliance with App Retailer Evaluate Guideline 2.5.2 and part 3.3.2 of the Apple Developer Program License Settlement.
This code, mixed with a distant useful resource, can facilitate important adjustments to your app’s conduct in comparison with when it was initially reviewed for the App Retailer. When you might not be utilizing this performance at the moment, it has the potential to load personal frameworks, personal strategies, and allow future function adjustments. This contains any code which passes arbitrary parameters to dynamic strategies corresponding to dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and working distant scripts in an effort to change app conduct and/or name SPI, based mostly on the contents of the downloaded script. Even when the distant useful resource isn’t deliberately malicious, it may simply be hijacked through a Man In The Center (MiTM) assault, which might pose a severe safety vulnerability to customers of your app.
Does anybody know how one can clear up this drawback ?
I believe the issue is brought on by engine utilizing scorching replace regardless that I don’t use it
What’s the model of the engine you’re utilizing?