Re:Apple starts rejecting apps with “hot code push” features
by prabodhprakash on Wednesday March 08, 2017 @05:44AM
(#13819389)
"You write regular Objective-C methods that are callable from JavaScript," - the objC function that I am calling from JS can be capable of calling a private API received by it in an argument - that breaks the entire claim of reactNative not supporting calls to private API. React Native must also go down.
[ Parent
| on HN ]
Re:Apple starts rejecting apps with “hot code push” features
by jameside on Wednesday March 08, 2017 @12:25PM
(#13821720)
If you deliberately write code that calls private APIs that are exposed to JS in your React Native app, I expect only your specific app to receive this warning. The same would be true in an app that doesn't use React Native at all, as we've seen with apps using Rollout.
The warning is not about React Native, it's about exposing uncontrolled access to native APIs including private ones and React Native doesn't do that.
Re:Apple starts rejecting apps with “hot code push” features
by wruza on Wednesday March 08, 2017 @07:21AM
(#13819736)
See the difference between a regular human who in theory can take a knife and violently rob or kill someone, and human-like robot that can be easily programmed to do the same. Who has to be isolated?
It is all about intents. If app allows that, it is banned for that behavior, not for having React in his kitchen. But if you have armed drone there, then police has a question.