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

Missing binary on Android with RN 0.76 & Expo SDK 52 #6933

Closed
nzapponi opened this issue Nov 15, 2024 · 10 comments
Closed

Missing binary on Android with RN 0.76 & Expo SDK 52 #6933

nzapponi opened this issue Nov 15, 2024 · 10 comments

Comments

@nzapponi
Copy link

How frequently does the bug occur?

Always

Description

Since upgrading to Expo SDK 52 & RN 0.76, any Android build fails with "Could not find binary" error.

All troubleshooting steps were taken, none helped.

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

  • Create an Expo project with SDK 52 (new arch not enabled)
  • Add Realm
  • Run

Version

12.14.0

What services are you using?

Local Database only

Are you using encryption?

Yes

Platform OS and version(s)

Android 14

Build environment

Tried both RN DevTools and Expo Dev Client

Cocoapods version

No response

Copy link

sync-by-unito bot commented Nov 15, 2024

➤ PM Bot commented:

Jira ticket: RJS-2921

@nzapponi
Copy link
Author

Added repro sample project. This is a clean expo project with just realm added.
To reproduce:

  • Clone project
  • Install deps
  • Run expo run:android

https://github.com/nzapponi/realm-bug-repro

@kbinder
Copy link

kbinder commented Nov 15, 2024

I am experiencing the same issue since updating to Expo 52 and React Native 0.76.1.

@nzapponi
Copy link
Author

I did some quick checking and after running expo prebuild, no realm files are found in the android folder. It looks like they're not being bundled at all

@alexphl
Copy link

alexphl commented Nov 15, 2024

This is happening because Expo SDK 52 has removed @react-native-community/cli autolinking.

Although it's a breaking change, it is only briefly mentioned in their blog post:

Reduced size of Expo CLI by removing the dependency on RNC CLI. Expo projects use expo-modules-autolinking to discover both Expo Modules and modules built with the React Native module API (such as Turbo Modules). You can opt in to @react-native-community/cli autolinking by setting the environment variable EXPO_USE_COMMUNITY_AUTOLINKING=1 and running pod install again.

The fix is to add @react-native-community/cli to your package.json and set the EXPO_USE_COMMUNITY_AUTOLINKING=1 env variable, followed by running prebuild.

@nzapponi
Copy link
Author

Ah awesome, thanks for the clarification.

I'll test this later today and close the ticket.

@kbinder
Copy link

kbinder commented Nov 15, 2024

@alexphl Thank you this solved my issue.

@nzapponi
Copy link
Author

Thanks so much!

@s-turcheniuk
Copy link

Thanks for the suggestion, but Is there a plan to make realm-js to work with expo-modules-autolinking?

@kraenhansen
Copy link
Member

kraenhansen commented Nov 20, 2024

Since the notice of deprecation, we don't plan to add any new features to the SDK. That being said, if this was provided as a PR from the community, we would love to review and likely merge it.

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

No branches or pull requests

5 participants