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
DevMenu is null in NativeModules #2678
Comments
@markrickert it looks like you added this custom command, can you take a look? |
@wisammechano It looks like this functionality was removed in recent versions of react-native. We'll have to pull this example out as there's not really an easy way to programmatically show the dev menu on the device, unfortunately. Thanks for bringing this to our attention! |
@markrickert we could sub in for the expo one? https://docs.expo.dev/versions/latest/sdk/dev-client/#devclientopenmenu |
From what I can tell, this just won't work in Expo Go. If you build via CNG the native module is available. You can also toggle the Expo menu when
|
Describe the bug
This was my first time exploring Ignite and React Native, and while fiddling around, this custom command was failing because DevMenu was null. I tried searching for the DevMenu module, but I couldn't find any document about it besides the DevSettings module.
Ignite version
9.6.3
Additional info
System
platform darwin
arch arm64
cpu 8 cores Apple M1 Pro
directory N /Users//Projects/n/N
JavaScript (and globally-installed packages)
node 22.0.0 /opt/homebrew/bin/node
npm 10.6.0 /opt/homebrew/bin/npm
npm 10.6.0
yarn 1.22.19 /usr/local/bin/yarn
create-react-app 5.0.1
create-react-library 3.1.1
pnpm 9.0.6 /usr/local/bin/pnpm
bun - not installed
expo 50.0.17 managed
Ignite
ignite-cli 9.6.3 /Users//.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /Users//.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java - not installed
android home - undefined
iOS
xcode 15.3
cocoapods 1.15.2 /Users//.rvm/gems/ruby-3.3.1/bin/pod
Tools
git git version 2.39.3 (Apple Git-146) /usr/bin/git
The text was updated successfully, but these errors were encountered: