Support React Native 0.79#2410
Conversation
48772b8 to
06fc1cc
Compare
| - "0.74" | ||
| - "0.76" | ||
| - "0.77" | ||
| - "0.78" |
There was a problem hiding this comment.
should we drop 0.72 from the matrix yet? I can't remember what the decision was on the support matrix, but 0.76 is now unsupported by react native.
There was a problem hiding this comment.
I don't think we can drop 0.72 - our test matrix policy is the latest 3 versions, plus even versions back to 0.72
| "paths": [ | ||
| "test/react-native-cli", | ||
| "packages/react-native-cli" | ||
| ] |
| @@ -0,0 +1,51 @@ | |||
| import Bugsnag | |||
There was a problem hiding this comment.
just to confirm, this is the only change between these versions?
There was a problem hiding this comment.
There's also the Bugsnag.start call on line 18.
The reason we need new before/after fixture files is because the whole AppDelegate.swift template has changed in 0.79 with the introduction of RCTReactNativeFactory
|
Hi @yousif-bugsnag , I do not want to open a new issue, so I ask here.
|
|
Hi @irekrog,
There is no v8.3.2 of This PR did add tests for React Native 0.79 though, and we haven't seen any build issues on Android. It looks like the gradle task isn't able to resolve the codegen script for some reason. Do you see the same error if you invoke the codegen task manually before building? ./gradlew generateCodegenArtifactsFromSchemaIf you're still having problems please feel free to write in to support@bugsnag.com with some more details, and ideally some steps to reproduce, and we can try to investigate further. Thanks! |
|
Ok, got it. Yes, after calling Thanks! |
|
Ok, when I manually added the package: then it works fine, I think there is a problem with monorepo/pnpm (which I use) |
Goal
Add support for React Native 0.79
Changeset
Testing
Covered by CI