segmentio / analytics-react-native

The hassle-free way to add analytics to your React-Native app.
https://segment.com/docs/sources/mobile/react-native/
MIT License
354 stars 181 forks source link

Please add support for React Native 0.73 and Expo SDK 50 #915

Closed anojht closed 4 months ago

anojht commented 5 months ago

Please add support for React Native 0.73 and Expo SDK 50 which now defaults to Java 17 for the build environment.

Currently builds are failing due to Java version being pinned at 11:

image
leemhenson commented 5 months ago

Yeah, not working for me on Expo 50 either. This is what I see from expo prebuild:

expo prebuild --clean

Warning! Your git working tree is dirty.
It's recommended to commit all your changes before proceeding, so you can revert the changes made by this command if necessary.

✔ Would you like to proceed? … yes

✔ Cleared android, ios code
✔ Created native directories
✔ Updated package.json | no changes
✔ Finished prebuild
⚠️  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Unable to find a specification for `sovran-react-native` depended upon by `segment-analytics-react-native`

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Something changed somewhere and now, after completing rebuilding my node_modules and package-lock.json, I can expo prebuild successfully with Expo 50 and have been able to submit events to Segment.

catodapice commented 5 months ago

any news on this? I've RN 0.73 and still failing on Android & iOS

naleon commented 4 months ago

guys, do you have any due date for this update?

Jeecabs commented 4 months ago

In case it's helpful for anyone, I managed to resolve the Android build issues. Here's what worked for me:

I cleared the node_modules and package-lock.json, then reinstalled everything. After doing so, the builds started passing in EAS. Here are the versions of the relevant packages I used in my package.json:

{
    "react-native": "0.73.2",
    "expo": "~50.0.6",
    "expo-random": "~13.6.0",
    "@segment/analytics-react-native": "^2.18.0",
    "@segment/sovran-react-native": "^1.1.0"
}
anojht commented 4 months ago

I can confirm clearing the lock file and the node_modules directory then doing an install does indeed fix the builds on EAS.

Leaving the issue open for the maintainers to review any changes needed to properly support the new SDK.

oscb commented 4 months ago

0.73 shouldn't require any update on the library, as per this note on RN repo by default RN should handle the namespace part.

While it now supports Java v17 by default, supporting v11 should just be compatible with new java versions.

I know from experience that Gradle cache is problematic after a major upgrade (either on RN or on our library) so yes, the fix should be to do a clean build. Delete grade cache, delete build. Not sure if NPM needs to be cleaned but might be required for Expo.

Doing some work to align to the new namespace change but I confirmed the lib already works without changes in the E2E 0.73 example we have in the repo.

oscb commented 4 months ago

:tada: This issue has been resolved in version 1.1.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 2.19.0 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 1.3.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 1.1.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 0.6.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 1.1.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 0.4.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 0.7.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

oscb commented 4 months ago

:tada: This issue has been resolved in version 1.2.0 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

klam-wavefin commented 4 months ago

iOS XCode build is still failing for me after using the latest "@segment/sovran-react-native": "1.1.1",, wondering if anyone else sees the same thing. I am in the middle of upgrading RN to 0.73.4

image