[docs] Getting error reporting with source maps with Expo updates

[kennethlynne]

Summary

After seeing this commit: expo/eas-cli@7ebb547
The part about source maps under known issues https://docs.expo.dev/eas-update/known-issues/ (saying eas update will not create or send source maps to Sentry.) and this documentation about using sentry https://docs.expo.dev/guides/using-sentry/
and check out the link to the example project in the bugsnag documentation in the bottom https://docs.expo.dev/guides/using-bugsnag/ (404 - not found).

I am super confused how to get source maps working with bugsnag and Expo updates. What is correct and is there a bugsnag example repo (at all?) with this working already, then the link needs to be updated in the bugsnag docs, or removed if not?

Link to the related docs page

https://docs.expo.dev/eas-update/known-issues/

Anything else?

No response

[kennethlynne]

I have noticed that npx expo export --dump-sourcemap will generate source maps now, but it is not automatically sent to bugsnag.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.