Apple disables hot update

Original title: Apple disabling hot update may also not tolerate these "gray behavior"

Reprint Address: http://sd.china.com.cn/a/2017/keji_0313/892062.html

On the evening of March 8, an email from Apple exploded in a group of domestic app developers. The main content of this message is: Prohibit the use of Lua or JavaScript scripts in the app/game for hot update (mainly using rollout, Jspatch of the hot new technology framework). Mail out, the domestic programmer group depressed, and even rumors of the company will be about the use of Jspatch technology departments throughout the cut off.

E-mails from Apple to developers

"Hot Update", or dynamic code, allows developers to fix bugs and release features without releasing a new version, allowing developers to bypass Apple's audit mechanism, avoid lengthy audit waits, and the cost of multiple rejections. Originally, "Hot Update" was a friendly thing for developers, and Apple also explained the question of why it was banned-"the risk of being exploited by intermediaries (other than the developers themselves)", or by "man-in-the-middle attack."

But the "man-in-the-middle attack" is actually a euphemism for the developers of Apple. As you can see, disabling the hot update is due to the fact that the game maker drills holes and exploits the bad content of the hot update.

After the hot update is disabled, for the domestic game manufacturers, in addition to the big Bag game update may become difficult, also means that the industry's two gray behavior-the use of products that have been approved by Apple on the shelves of the product's hot update, 1 products civet for the Prince; 2) switch the payment Process collection account number, to bypass the Apple partition. These two industries have already defaulted for at least a year and will be limited.

Civet Cats for the Prince

The behavior of civet cats for the Prince, in the industry has been in public, small to less in line with the rules of promotional activities, large to the audit and the official version of the full inconsistency, all kinds of situations are not uncommon. This response to Apple's audit is similar to what many now do with the "White Lotus version" of the product-just the difference between the details of the audit and the terms.

Apple audit clauses, for sweepstakes, guessing and other promotional activities audit very strict, so some developers submit product audit version, will not reveal this kind of information, to be approved by the shelves, only use the Hot Update bypass audit, and then release a variety of irregularities; what's more, the original version that looks very normal, A variety of erotic, guided and paid pop-up windows are filled after the hot update.

Switching the payment process

If a civet cat is still in the Apple tolerable range, then switching the payment process is really the cake that touches the interest. The basic flow is as follows: Normal version through Apple audit-go online after the call script, switch payment account number-user pay when there is no difference, but the money is priority to enter the developer's own account. That would have been a 30% share of Apple, which flowed into the developer's pocket and became another source of profit. There are many unknown products, usually to buy advertising traffic support users new, high income but never seen into the best-selling list Top100, many have adopted this approach.

Hot update is intended for the convenience of developers, do not need to pass through the cumbersome review process, but also to keep the initial package size, user-friendly download. But when the loophole is exploited by unscrupulous developers in China, and even becomes a profitable model of semi-disclosure, it is not only the "grey zone", but the "real cross-border". Apple banned the hot update, the spread of large-package app, to see its determination to rectify the trend.

Since last year, the turmoil about AppStore has been constant. From the shell, no moral integrity brush list, abuse keyword optimization aso, to version, switch payment ... Apple's strike strength is more intense than once. The latest follow-up to disabling hot updates is that the two frameworks, the Jspatch and Rollout.io, are currently in the worst-hit areas, with almost 100% receiving warning messages; domestic and foreign affected companies such as Bugtags, push, gold, etc. have updated the SDK, or launched a temporary solution , and there are developers on the Internet that use react native passed the AppStore audit. At the same time, since Lua is a development script, its ability to invoke functions is deterministic and limited, so it is relatively safe.

Some developers have indicated that they passed the AppStore audit with react native.

Of course, technical issues are secondary, and we all want to see a healthy, fair-competition industry, and Apple wants to take the opportunity to continue creating a more secure and reliable platform environment for developers and players. As to how much impact this will have on the industry, we have to wait and observe the changes.

Sweep attention to the public number:

Apple disables hot update