This below trick can work for ads, offerwalls, graphics… you name it:
The strategy is based on creating a connection in your code to a file somewhere online that you can change at will. Essentially the app code reads this file on the internet instead of being stuck inside itself. That way, you can update the file whenever you want to turn features on and off, and you don’t need to create some type of elaborate back-end system. It’s a very cool strategy and useful even if you’re not trying to trick Apple or for any other shady intentions. As mentioned, the only downside is that the user must have an internet connection for these changes to take place; otherwise the code will be stuck doing whatever it is you specify if there isn’t an internet connection.
Because I used the first tactic, I don’t have code to share with you for this pro version, but it shouldn’t be too difficult to write up.
Besides, I know Warnings and Crashes are for a developer to fix, if he/she chooses to fix. In this case I have a good code review practice to have the code generate minimal possible warnings. I was able to resolve many warnings as possible. However, at times, it is possible that XCode generates some stray warnings. I am also capable to fix those. I am so much familiar with comprehensive list of reasons( Apple Appstore Review Guidelines documents) that can lead to your app's rejection in the review process.