News for hackers. Stuff that matters.
Re:Apple starts rejecting apps with “hot code push” features by jameside on Wednesday March 08, 2017 @12:50PM (#13821963)
Apple has been fine with WebViews in apps since the beginning of the App Store, including WebViews that make calls to native code, like in the Quip app. WKWebView even has APIs for native and web code to communicate. It's OK for a WebView to call out to your native code that saves data to disk, registers for push notifications, plays a sound, and so on.

React Native is very much like a WebView except it calls out to one more native API (UIKit) for views and animations instead of using HTML.

What neither WebViews nor React Native do is expose the ability to dynamically call any native method at runtime. You write regular Objective-C methods that are statically analyzed by Xcode and Apple and it's no easier to call unauthorized, private APIs.

With Expo all of the native modules are safe to use and don't expose arbitrary access to native APIs. Apps made with Expo are set up to be good citizens in the React Native and Apple ecosystems.

Re:Apple starts rejecting apps with “hot code push” features by iOSGuy on Wednesday March 08, 2017 @01:40PM (#13822480)
Well, let's be clear here. I use React Native, and it would take me about 30m to write a bridged React Native method that could execute ObjC code dynamically, including accessing all the private APIs you could want.
Re:Apple starts rejecting apps with “hot code push” features by jameside on Wednesday March 08, 2017 @02:27PM (#13822905)
Yeah. Objective-C is definitely really flexible. From my reading of the warning, the important thing is not to execute Objective-C dynamically or access private APIs regardless of whether you're using React Native, Cordova, a WebView, or even a bare iOS app.
Re:Apple starts rejecting apps with “hot code push” features by t1amat on Wednesday March 08, 2017 @02:07PM (#13822697)