For cute little white iOS programmers, iOS launch an APP to AppStore will more or less encounter some indescribable problems. Take me as an example. I used to work in an advertising company. However, Apple had a stricter review mechanism for advertising. Because inappropriate handling is faced with rejection over and over again. crying….. In 2015, the company needed to access an advertising integral wall. When discussing this in advance, my iOS colleagues and I both declared in advance that Apple had already banned this type of application. Once we found that it was likely to be taken down, the product manager embedded the integral wall into the project with a try attitude. Sure enough, on the third day of InReview, all user names in Apple’s developer center became CLOSED and the product was removed. What follows is the telephone communication communication with apple personnel, but is not to reply not to inform, is to seal your number under your program, how! Had to start standby procedures, re-open account shelves. In this case described above, how to avoid risks to the maximum extent, what needs to be mentioned here is to cooperate with background personnel to dynamically hide functions, the main flow chart is as follows:
Processing is the background before I do a interface returns a BOOL value, we need to provide the current need shelves before the version number and background database (online each app background has a data archive) compare, when the version number is greater than the background file returns False we take advantage of this background back NO hidden value function or module, Otherwise, TRUE indicates that the version has been approved, and the function modules hidden during the use of the user are displayed. However, this is just the most extreme way to avoid risk, and it doesn’t necessarily mean your APP is safe. Again, there is a risk of removal but it’s not a big risk. These are some of the most common ways to hide features in iOS apps during launch. 🙂 🙂