Repository navigation
Autolinking not working on v3 #56
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I tested using a supported version of react native.
- I checked for possible duplicate issues, with possible answers.
Bug summary
The autolinking on Android is not working. Just installing the library and running the app will give the error:
TurboModuleRegistry.getEnforcing(...): 'QuickBase64' could not be found
I think this is because the android directory in this library does not have the build.gradle file, and that's why autolinking is not picking up the library.
Can you please check?
Thank you!
Library version
3.0.2
Environment info
System:
OS: macOS 26.6.2
CPU: (14) arm64 Apple M3 Max
Memory: 2.13 GB / 36.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.22.2
path: /Users/george/.nvm/versions/node/v22.22.2/bin/node
Yarn:
version: 4.13.0
path: /Users/george/.nvm/versions/node/v22.22.2/bin/yarn
npm:
version: 10.9.7
path: /Users/george/.nvm/versions/node/v22.22.2/bin/npm
Watchman:
version: 2026.05.18.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.15.2
path: /Users/george/.local/share/mise/installs/ruby/3.3.11/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.5
- iOS 26.5
- macOS 26.5
- tvOS 26.5
- visionOS 26.5
- watchOS 26.5
Android SDK: Not Found
IDEs:
Android Studio: 2026.1 AI-261.26222.65.2613.16025427
Xcode:
version: 26.6/17F113
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.13
path: /Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home/bin/javac
Ruby:
version: 3.3.11
path: /Users/george/.local/share/mise/installs/ruby/3.3.11/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.3
wanted: 0.86.3
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: trueSteps to reproduce
- Set up a new bare react native project
- Install this library
- Run the app
Reproducible example repository
no need for one
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Activity
huytdps13400 commentedon Aug 26, 2026
I tested this against a clean React Native 0.86.3 app using
@react-native-community/cli@20.1.0and the currently publishedreact-native-quick-base64@3.0.1. I could not reproduce the autolinking failure:react-native configreports the package asisPureCxxDependency: truewith both CMake paths andQuickBase64Impladd_subdirectory(...)entries and anautolinking_cxxModuleProviderbranch forQuickBase64Impl::kModuleNameapp:assembleDebugsucceeds for arm64-v8a, armeabi-v7a, x86, and x86_64, withlibappmodules.sopackaged for each ABIThe missing
android/build.gradleis intentional for a pure-C++ dependency. CLI 20.1 classifies a dependency as pure C++ only when the threecxxModule*fields are present and there is no manifest/build.gradle; adding one without a Java package would make dependency discovery return null.Also, npm currently has no
3.0.2; the latest published version is3.0.1. Could you share the output of:and the QuickBase64 lines from
android/app/build/generated/autolinking/src/main/jni/{Android-autolinking.cmake,autolinking.cpp}after a clean build? That should show whether this is a different artifact, stale autolinking output, or another project-level configuration issue.gmanolek2 commentedon Aug 27, 2026
Hi @huytdps13400
Thank you for your quick response! I found the issue, I didn't have
react-native-quick-base64listed in dependencies inpackage.json. I think that's why it was not picked up by autolinking. I am using the library@craftzdog/react-native-bufferwhich has a dependency on this library, and it got installed because i could see it innode_modulesdir, and I didn't know why it was not autolinked. I took a look again at the README of@craftzdog/react-native-bufferand it says to also install this library as a dependency, I think I missed that.After adding the dependency explicitly in
package.json, the issue was fixed.Thank you again, and sorry for the hassle!