Missing binary on Android with RN 0.76 & Expo SDK 52

[nzapponi]

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

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RJS-2921

[nzapponi]

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]

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

[nzapponi]

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]

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]

Ah awesome, thanks for the clarification.

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

[kbinder]

@alexphl Thank you this solved my issue.

[nzapponi]

Thanks so much!

[s-turcheniuk]

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

[kraenhansen]

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.

[Amurmurmur]

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.

fcking legend

[CodeWithBlaze]

hey guys, i have a bare react native app which is using realm. it is working fine in developement but when i release it for android
using gradlew assembleRelease and install it in the device, then i get this error "could not find realm binary". I am using react native 0.76.1. it will be great if someone could help me or provide me some guidance. Thank you

[AdamGerthel]

I have the same issue. Adding @react-native-community/cli solves it for debug builds but the issue persists in release builds.

Update: It was my EAS builds that weren't working. Fixed by adding to my eas profile (eas.json):

      "env": {
        "EXPO_USE_COMMUNITY_AUTOLINKING": "1"
      }

[ArindamRayMukherjee]

What worked for my bare react-native(0.76.5) app that only wishes to use expo-image(2.0.3) from expo(52.0.0) and wishes to link separately to realm(12.14.0) was the follows

in package.json

EXPO_USE_COMMUNITY_AUTOLINKING=1 react-native run-android

in ios/Podfile the following if conditional (this may or may not come with the instrumentation done by the tools prescribed by the expo docs for integrating with bare react-native, in my case it did arrive)

//other code

target 'ProjectName' do
  use_expo_modules!

  if ENV['EXPO_USE_COMMUNITY_AUTOLINKING'] == '1'
    config_command = ['node', '-e', "process.argv=['', '', 'config'];require('@react-native-community/cli').run()"];
  else
    config_command = [
      'node',
      '--no-warnings',
      '--eval',
      'require(require.resolve(\'expo-modules-autolinking\', { paths: [require.resolve(\'expo/package.json\')] }))(process.argv.slice(1))',
      'react-native-config',
      '--json',
      '--platform',
      'ios'
    ]
  end

  config = use_native_modules!(config_command)

//other code

and in android/settings.gradle the following conditional similar to iOS (this may or may not come with the instrumentation done by the tools prescribed by the expo docs for integrating with bare react-native, in my case it DID NOT arrive as opposed to the Podfile change)

extensions.configure(com.facebook.react.ReactSettingsExtension) { ex ->
  if (System.getenv('EXPO_USE_COMMUNITY_AUTOLINKING') == '1') {
    ex.autolinkLibrariesFromCommand()
  } else {
    def command = [
            'node',
            '--no-warnings',
            '--eval',
            'require(require.resolve(\'expo-modules-autolinking\', { paths: [require.resolve(\'expo/package.json\')] }))(process.argv.slice(1))',
            'react-native-config',
            '--json',
            '--platform',
            'android'
    ].toList()
    ex.autolinkLibrariesFromCommand(command)
  }
}

[kfchan-git]

still can't find the realm in android folder, works when i run it in debug mode; already added @react-native-community/cli into the package.json but still not working

[AdamGerthel]

still can't find the realm in android folder, works when i run it in debug mode; already added @react-native-community/cli into the package.json but still not working

Are you using Expo? If so, see #6933 (comment)

[kfchan-git]

still can't find the realm in android folder, works when i run it in debug mode; already added @react-native-community/cli into the package.json but still not working

Are you using Expo? If so, see #6933 (comment)

yes, but i dont have the eas.json file since i'm using android studio to build; or is there any other way to link it?

[AdamGerthel]

still can't find the realm in android folder, works when i run it in debug mode; already added @react-native-community/cli into the package.json but still not working

Are you using Expo? If so, see #6933 (comment)

yes, but i dont have the eas.json file since i'm using android studio to build; or is there any other way to link it?

I see... Hmm, if you're using Expo, I don't think you should be using Android Studio to build. You're at least not making it easy for yourself. You'll need a way to set EXPO_USE_COMMUNITY_AUTOLINKING=1.

You know, you don't need to use the cloud service EAS. You can use the --local flag to run eas locally.