App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

It is reported that the United States recently responded to the call of the Apple Corp, in order to achieve a harmonious community civilization, the full development of various undertakings, pay close attention to the construction of spiritual civilization. The formation of organizational leadership, regular guidance, accurate benchmarking, timely inspection, summary and improve the five mechanisms to ensure the establishment of standardized, scientific, standardized. – front line reports from old drivers

The main cause of the incident is in the App Review Guide Line of this 2.5.2 Store:

2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area nor may, they download, install or, execute code, including other iOS, watchOS, macOS, or tvOS apps.

This is updated after 16 years of WWDC. This rule is also very easy to understand, all executed code should be included in the App, can not download the code to the local implementation. OC or JS or other forms of code, can be considered to violate this rule. But Apple has not been strict law enforcement, until today began to send a warning to a large number of similar suspects, or have been rejected.

Of course, this is nothing to blame, this execution depends on the mood, after all, Dad never need to reason. From time to time will be like a father.

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?
fatherly love

According to feedback to see, there are two main criteria for judging the current apple.
is a specific API scan, such as:

Dlopen (), dlsym (), respondsToSelector:, performSelector:, (method_exchangeImplementations)

But this is not a complete ban on the use of these API, but there is a rule to check whether these API parameters are likely to be introduced externally.
, for example, this is no problem:

If ([self.delegate respondsToSelector: @selector (myDelegateMethod)) {[self.delegate performSelector: @selector (myDelegateMethod)]}

So writing may be hit back:

NSString *remotelyLoadedString =. (download from your backend) [self performSelector: NSSelectorFromString (remotelyLoadedString)];

In addition, we will check the specific class names, such as everyone knows JSPatch and Rollout, found that APP with such a potential threat to the library may be back. But this approach seems to be able to pass through confusion.

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

Do not understand why I mentioned JSPatch would like to send a facial expression, the impression of a certain period of time in the past have been prompted by the shelf, and then relax. Inner OS: “the emperor! I was wronged!.”

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?
crape myrtle, save me quickly

Judgment of the future

Apple is 100 percent reluctant to bypass the audit code was issued. Whether it is to repair the bug, or a small function, how can the high cold capitalist enterprises let you rub, if you go in. In fact, the special situation of our country, if anything really illegal on the apple was also unable to live, do not want to go offline App Store.

One foot in mind, it is always a vulnerability of program execution. Yes, it is possible to play the game and the official, but you want to send the code under this thing is not really affect the operation of the App to do? If the price increase? For example, was found a direct closure of your Apple ID, or not to do?

Smart people have been working on how to improve the stability of the road APP. Forget about HotPatch.

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

RN& Weex can continue a life

From the feedback of the parties, this round of apple is responsible for the release of the code, rather than for the use of JS code to write business logic. If you think this is a problem, it will be some of the core API JSCore changed to private API. Just in the air, the framework based on this technology is very easy to provide the ability to send the code to perform logic, so pushed to the light.
I have asked the person in charge of Weex before, he made it clear that Weex is not in order to solve the problem of hot update. Just happen to have this ability.
apple in the new JavaScriptCore framework introduced in iOS 7, is that the implementation of APP in JS was beneficial to the entire iOS ecosystem, otherwise why make an unnecessary move. So now just to solve the problem of abuse after the introduction of this framework. So I think this round of remediation, the framework of the JS2Native can certainly be back.

Swift?

Some people say that there is no apple in the next big game for Swift. In order to confirm the matter a good friend consulted the father of Swift CL:

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

dad said:
very tight lipped

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?

Building a harmonious society

Come, let us stand together: I volunteered to work with the United States to build a harmonious App Store ecology.

App Store pay close attention to the construction of spiritual civilization, JSPatch is going to die?