Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for [email protected] #4913

Merged
merged 119 commits into from
Oct 30, 2023
Merged

Support for [email protected] #4913

merged 119 commits into from
Oct 30, 2023

Conversation

@piaskowyk piaskowyk changed the title Fix compatibility with [email protected] on Android Fix compatibility with [email protected] Aug 11, 2023
@tomekzaw
Copy link
Member

@efstathiosntonas Thanks for the reminder! Looks like this PR already contains these changes:

Zrzut ekranu 2023-10-30 o 10 06 46

Copy link
Member

@tomekzaw tomekzaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@piaskowyk piaskowyk marked this pull request as ready for review October 30, 2023 10:00
@piaskowyk piaskowyk enabled auto-merge October 30, 2023 10:00
@piaskowyk piaskowyk added this pull request to the merge queue Oct 30, 2023
Merged via the queue into main with commit fe587cf Oct 30, 2023
19 checks passed
@piaskowyk piaskowyk deleted the @piaskowyk/rn73-nightly-android branch October 30, 2023 10:02
@lafest
Copy link

lafest commented Nov 2, 2023

@piaskowyk Hi, can you check this comment? #4913 (comment)

@piaskowyk
Copy link
Member Author

Hey, could you tell me how I can reproduce this error?

@lafest
Copy link

lafest commented Nov 3, 2023

@piaskowyk
I used xcode 14.3, [email protected], CLANG_CXX_LANGUAGE_STANDARD = "gnu++14" when I met the error. Is there any other information I can provide that will help solve this problem?

gabrieldonadel added a commit to expo/expo that referenced this pull request Nov 10, 2023
)

# Why

In order to have the react-native 73 upgrade PR ready by the end of the
week we will need to temporarily bump
react-native-reanimated to a nightly version, given that
software-mansion/react-native-reanimated#4913
has not been officially released yet.
 

# How

`et uvm -m react-native-reanimated -c
f06ee065904ebeac3fa72d4bda32ba3360bf49e7 -s
3.6.0-nightly-20231031-c56d44fd9`

# Test Plan

Run locally expo go unversined and bare-expo

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
@mikehardy
Copy link
Contributor

Would be nice to see this released, react-native 0.73 is on rc4 now and should go out soon
You all probably coordinate with releases like I do though, so you might be holding the release on purpose
Either way - was about to propose the exact same buildConfig true PR to build.gradle but saw this was already in :-)

Cheers

@daviddamilola
Copy link

Hello, thanks for you work. Pending the time this is released, what are the steps if i want to use react-native-reanimated from the main branch.

i tried to add it by doing this in package.json

"react-native-reanimated": "https://github.com/software-mansion/react-native-reanimated.git#main",

which works when building locally, but when doing a release build it breaks with this error

▸ Linking mobile

❌  ld: symbol(s) not found for architecture arm64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

@altaywtf
Copy link

altaywtf commented Nov 15, 2023

@daviddamilola
Copy link

Thanks @altaywtf , will try it out.

@UNIDY2002
Copy link
Contributor

when doing a release build it breaks with this error

+1

Using the nightly does not seem to solve the problem.

See: https://github.com/thu-info-community/thu-info-app/actions/runs/6891922352/job/18748125712#step:11:2696

Not sure whether anything is wrong on my side.

@daviddamilola
Copy link

Thanks @altaywtf , will try it out.

Hello, i can confirm the error remains for v0.73.0-rc.4 but works for v0.73.0-rc.1

@UNIDY2002
Copy link
Contributor

... when doing a release build it breaks with this error

▸ Linking mobile

❌  ld: symbol(s) not found for architecture arm64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

It seems that this issue is fixed by bf7df79. I've tried on the latest nightly and the build error no longer shows up.

onizam95 pushed a commit to onizam95/expo-av-drm that referenced this pull request Jan 15, 2024
…o#25161)

# Why

In order to have the react-native 73 upgrade PR ready by the end of the
week we will need to temporarily bump
react-native-reanimated to a nightly version, given that
software-mansion/react-native-reanimated#4913
has not been officially released yet.
 

# How

`et uvm -m react-native-reanimated -c
f06ee065904ebeac3fa72d4bda32ba3360bf49e7 -s
3.6.0-nightly-20231031-c56d44fd9`

# Test Plan

Run locally expo go unversined and bare-expo

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
@mohan-sprinklr
Copy link

I met below error in RN0.73-rc.2. is there any change with handling hermes? if I comment out enableDebuggging and disableDebugging, build successfully completed.

Undefined symbols for architecture x86_64:
  "facebook::hermes::inspector_modern::chrome::enableDebugging(std::__1::unique_ptr<facebook::hermes::inspector_modern::RuntimeAdapter, std::__1::default_delete<facebook::hermes::inspector_modern::RuntimeAdapter>>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&)", referenced from:
      reanimated::ReanimatedHermesRuntime::ReanimatedHermesRuntime(std::__1::unique_ptr<facebook::hermes::HermesRuntime, std::__1::default_delete<facebook::hermes::HermesRuntime>>, std::__1::shared_ptr<facebook::react::MessageQueueThread> const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>) in libRNReanimated.a(ReanimatedHermesRuntime.o)
  "facebook::hermes::inspector_modern::chrome::disableDebugging(int)", referenced from:
      reanimated::ReanimatedHermesRuntime::~ReanimatedHermesRuntime() in libRNReanimated.a(ReanimatedHermesRuntime.o)
ld: symbol(s) not found for architecture x86_64

Did you find the solution for this?
i am trying to upgrade react-native version from 0.72.6 to 0.73.6 and I have updated the version of react-native-reanimated to its latest version in which I am getting same issue.

@UNIDY2002
Copy link
Contributor

@mohan-sprinklr IMHO, this should have been fixed in the latest release of react-native-reanimated. Would you mind confirm whether clearing build cache, re-running pod install and re-building the APP helps?

@mohan-sprinklr
Copy link

@mohan-sprinklr IMHO, this should have been fixed in the latest release of react-native-reanimated. Would you mind confirm whether clearing build cache, re-running pod install and re-building the APP helps?

I am still getting the issue in react-native-reanimated latest version i.e 3.8.0
For now I have added a quickfix to manually disable HERMES_DEBUGGER in node_moduels/react-native-reanimated/RNReanimated.podspec file
image

I cleared pod cache --> deleted Pods folder --> reinstalled pods --> cleared build folder inside xcode --> manually deleted xcode cache inside /Users//Library/Developer/Xcode
Nothing worked for me.

@ydvnishant001
Copy link

I think commenting the enableDebugging and disableDebugging option in "node_modules>react-native-reanimated>Common>cpp>ReanimatedRuntime>ReanimatedHermesRuntime.cpp" is better. SInce React Native has deprecated Remote JavaScript Debugging.

I can no longer see the option in Android dev-menu to remote debug. And the above methods are shown in dev-menu for ios earlier but now are deprecated but still being used by reanimated(I assume). So commenting them makes the build run successfully.

also @mohan-sprinklr , disabling hermes in debug did not fix the issue for me.

If anyone wants to use remote debugging they can follow this official guide - https://reactnative.dev/docs/next/other-debugging-methods. Which works on both ios and android.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.