React native: No Bugsnag API Key set, js engine: hermes
See original GitHub issueHi, Since upgrading bugsnag to latest version, can’t make it work on adroid. Crashes on opening, however it does send a crash report to my bugsnag account. Bugsnag error: “No Bugsnag API Key set, js engine: hermes”. It works no problem with ios. Api key is set inside AndroidManifest.xml. I’ve tried inside App.js with and without apiKey:
import Bugsnag from '@bugsnag/react-native';
Bugsnag.start({
apiKey: '90d03f98aa81640e********',
});
“react-native”: “0.63.2” “@bugsnag/react-native”: “^7.3.1”
using with hermes.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Configuration options - React Native - Bugsnag docs
You can find your API key in Project Settings from your Bugsnag dashboard. If not set, it will be loaded from your AndroidManifest.xml...
Read more >No native client found. Is Bugsnag React Native installed in ...
I have updated my AndroidManifest.xml, MainApplication.java, Info.plist, build.gradle to include the api-key and bugsnag-react-native was ...
Read more >Using Hermes - React Native
Hermes is an open-source JavaScript engine optimized for React Native. For many apps, using Hermes will result in improved start-up time, ...
Read more >Bugsnag API key not being found in Info.plist #31 - GitHub
When running send_build_to_bugsnag in fastlane, I get the following error: A Bugsnag API key is required to release a build. Set BugsnagAPIKey ...
Read more >@bugsnag/plugin-react-native-hermes - npm
@bugsnag/plugin-react-native-hermes. Adds support for the Hermes JS engine. License. This package is free software released under the MIT ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This has now been fixed and released in v7.3.4
@tobiasbu - thanks for the info. Yes, we can confirm the bug can affect projects whether or not they use Hermes. We’re working on the fix.