RN 0.34 and 0.35 Support

[richardhuaaa]

• react-native-code-push version: 1.14.6-beta
• react-native version: 0.34.0

We have just verified RN 0.33.0 is supported in the latest version of CodePush. RN 0.34.0 is not supported yet, so this issue tracks verifying RN 0.34 support, including any required fixes. If you have tested this and run into specific issues, please post them here!

[stewart42]

Hi, please see #540 might be related to 0.34 ?

[richardhuaaa]

@stewart42 - I am fairly sure that your issue is related to a breaking change in RN 0.34, so I'm moving your issue here:

• react-native-code-push version: 1.14.6-beta
• react-native version: 0.34
• iOS/Android version: Android 7.0
• Does this reproduce on a simulator, or only on a physical device? physical device (Nexus 5x)
• Repro steps and/or stack trace:

const codePushOptions = {
    checkFrequency: codePush.CheckFrequency.ON_APP_RESUME,
    installMode: codePush.InstallMode.ON_NEXT_RESUME,
    mandatoryInstallMode: codePush.InstallMode.IMMEDIATE,
};

• upload a new bundle to code-push servers
• pause the activity
• resume the activity
• codepush downloads new bundle
• pause the activity
• resume the activity and then below happens
  1. The exception java.lang.NoSuchMethodException: createFileLoader [class android.content.Context, class java.lang.String] occurs at L116
  2. then an exception java.lang.NoSuchFieldException: No field mJSBundleFile in class Lcom/facebook/react/XReactInstanceManagerImpl; (declaration of 'com.facebook.react.XReactInstanceManagerImpl' appears in /data/app/com.xxxxxxxx.android.debug-1/base.apk) is raised at L122
  3. the outer catch then triggers loadBundleLegacy() which attempts to recreate the activity
  4. once the activity is recreated the onHostResume event fires L434 and loadBundle is called looping back to the first excpetion above

We are imbedding this in an existing app that does have multiDexEnabled set to true, not sure if this is relevant?

Any ideas what I am doing wrong?

[richardhuaaa]

We will address this early next week, but if a fix is needed immediately, you could downgrade to RN 0.33.0. Thanks to @geof90 for identifying the cause:

This is (yet another) breaking API change to JsBundleLoader.createFileLoader in RN 0.33 (it no longer requires a Context to be passed to it). See the related commit: facebook/react-native@0c2fdf4#diff-e110fa648a5e434c9533e8e35b5b1f6dR50

We need to change this line https://github.com/Microsoft/react-native-code-push/blob/master/android/app/src/main/java/com/microsoft/codepush/react/CodePushNativeModule.java#L116 in our code.

[stewart42]

I can confirm that changing L116 and L117 to:

Method createFileLoaderMethod = jsBundleLoaderClass.getDeclaredMethod("createFileLoader", String.class);
Object latestJSBundleLoader = createFileLoaderMethod.invoke(jsBundleLoaderClass, latestJSBundleFile);

did resolve the issue for RN 0.34. I am not sure how to best structure the code to handle the various versions of react-native. One suggestion could be to tie the versions react-native-code-push to react-native, in the same way that react-native does with react?

[jerson]

@stewart42 it work for me :) 👍

[richardhuaaa]

@stewart42 - sorry I didn't reply! We generally try to support older versions of RN for as long as possible, as not everybody updates to the latest version, and we still want them to be able to receive the latest CodePush features and fixes. I've put our PR #557 which maintains backward compatibility - thanks so much for helping to validate the fix!