GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Expo config plugin is a no-op but is documented as needed for native crash reporting · Issue #206 · exceptionless/Exceptionless.JavaScript

Expo config plugin is a no-op but is documented as needed for native crash reporting #206

New issue
Copy link
New issue
Copy link
Open
#212
Open
Expo config plugin is a no-op but is documented as needed for native crash reporting#206
#212
Copy link
Labels
bug

Description

@ejsmith
ejsmith
opened on Oct 28, 2026
Issue body actions

The Expo config plugin shipped in @exceptionless/react-native 3.2.1 (@exceptionless/react-native/expo-plugin) returns the Expo config unchanged. The README and the agent skill tell users to add it for development and standalone builds, and to check it's present when native crashes don't show up, but adding or removing it has no effect on the generated native project.

Where

  • packages/react-native/expo-plugin/withExceptionless.cjs#L3: const withExceptionless = (config) => config;
  • packages/react-native/README.md#L41-L49: "Add the config plugin to app.json when using development or standalone builds"
  • .agents/skills/exceptionless-javascript/references/client-react-native.md#L107: "verify ... that the config plugin is present before rebuilding the native app"

What happens

npx expo prebuild produces the same ios/ project with or without the plugin in app.json. The native crash reporter is linked by autolinking from exceptionless-react-native.podspec, not by the plugin. Users who follow the troubleshooting advice will be checking for a plugin that doesn't change anything.

Expected

Either the plugin applies the native configuration the SDK needs, or the docs say it's optional (kept for forward compatibility) and point troubleshooting at what actually matters: a development or standalone build, a rebuilt native app, and autolinking of the pod.

Steps to reproduce

  1. In an Expo app with @exceptionless/react-native 3.2.1, run npx expo prebuild --clean with "plugins": ["@exceptionless/react-native/expo-plugin"] in app.json, and save the ios/ folder.
  2. Remove the plugin entry and run npx expo prebuild --clean again.
  3. Diff the two ios/ folders: there is no difference.

Suggested fix

If no native changes are needed, keep the plugin as a harmless placeholder but update the README and skill to say it's optional and remove it from the troubleshooting steps. If native configuration is actually needed, implement it in the plugin with the appropriate @expo/config-plugins mods and add a test that checks the modified config.

Activity

  1. ejsmith
    added
    bug
    on Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.