React Native: fix linker error when plugin-react-native-span-access is not installed#787
Merged
hamudi-ahmed merged 1 commit intonextfrom Feb 17, 2026
Merged
Conversation
Browser bundle sizeNPM build
CDN build
Code coverageCoverage values did not change👌. Total:
Generated against 8802f00 on 17 February 2026 at 10:51:18 UTC |
…registry pattern for ios
607e0ee to
8802f00
Compare
lemnik
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
The
BugsnagReactNativeAppStartPluginimplementation is provided by the optionalplugin-react-native-span-accessmodule, but we still had a direct reference to the plugin in the main React Native SDK, causing linker errors when the optional module is not installed (as reported in #785)This PR fixes the issue by removing the plugin reference and implementing a
BugsnagPerformanceAppStartProviderandBugsnagPerformanceAppStartRegistrysimilar to the Android implementation.Design
The
BugsnagReactNativeAppStartPluginnow registers itself with theBugsnagPerformanceAppStartRegistryduring the install phase, and the main SDK now looks for a registeredBugsnagPerformanceAppStartProviderinstead of calling the plugin instance directly.Testing
Existing app start tests covered by CI, plus some additional manual testing to ensure that projects still build and run successfully when the optional module is not installed.