0.62.x RC Discussion

[kelset]

EDIT by @alloy:

The current version is v0.62.0-rc.5 and appears to be the golden one ✨

TODOs:

• Include these last fixes without doing another RC:
  • facebook/react-native@db12255
  • facebook/react-native@85a4b0f
  • facebook/react-native@5ca1d8f
• Need a blog post. @rickhanlonii is tasked with this.
• Update website content for v0.62 Create 0.62 versioned documentation facebook/react-native-website#1782
• Fix categorisation of changelog items
• Should we fold many related changelog items (e.g. re Flipper) into a single item? And who is the point person for this type of work?
• Make sure the Flipper team is able to support a release right now due to COVID-19

[SaeedZhiany]

@kelset

For completeness sake, these PRs have been mentioned:

facebook/react-native#21801 and facebook/react-native#27463 are not PR, they are issues.

have we PRs to fixing them?

[khat33b]

This issue needs to be fixed in 0.62 (facebook/react-native#27661). NativeModules object is coming null from 0.61.0 onwards and it should be fixed in 0.62. We have been unable to upgrade from 0.60.6 becuase of this issue.

[kelset]

@SaeedZhiany thanks, corrected the wording.

have we PRs to fixing them?

Not sure, you should find (if any) linked in the issues themselves. If not, you could try to submit one yourself 🤗

@khat33b the issue you linked is quite incomplete, I've commented there. It doesn't seem to be an actionable commit or PR about that.

[sofiageo]

I'm not sure if it's a known issue but with both rc versions my application won't run at all. Errors are similar to:

Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)', reason: 'Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication), stack:

I've found similar issues in the past from react-native upgrades but I didn't find any specific ways to fix it. Reverting just react dependency to 16.9.0 and react-native dependency to 0.61.5 - lets my application run normal again.

[kelset]

@sofiageo I would suggest not upgrading yet as we are still in the RC phase and things will likely change quite a bit still before 0.62.0.

That said, you can check via the upgrade-helper that you have taken all the necessary steps.

[jfrolich]

It doesn't look to be working with React-Native-Navigation (I get a blank screen after the upgrade). Didn't do more research yet, but it might be good to mention. Anyone else tried this with RNN?

[kelset]

@jfrolich I would recommend that you open an issue in the react-native-nav rep with a repro, and post the link here. So people can have the conversation over there while keeping a reference here.

---

Just a quick update, the roadmap for 0.62.0 is mostly bound to Flipper support - and since I forgot to mention it in the previous post I'll add it here now: facebook/react-native#27565

So it seems that there is still some work to do before it's going to be ready. Any help I'm sure it would be super appreciated.

[johnckendall]

This issue still exists: facebook/react-native#27860

[alexisbronchart]

Is facebook/react-native#26733 already included in 0.62 ? I can't manage to find it back in the history.

[mjmasn]

@alexisbronchart looks like the fix is present in both release candidates: facebook/react-native@3b3c95b