expo / sentry-expo

MIT License
202 stars 83 forks source link

Conflict with expo/config-plugins versions using sentry/expo 6.2.0 and expo SDK 48 #375

Closed SanaviaNicolas closed 4 months ago

SanaviaNicolas commented 9 months ago

Summary

I follow the guide to install sentry into my project but when i run npm expo-doctor to check if it's all ok I have the following error:

Expected package @expo/config-plugins@~6.0.0 Found invalid: @expo/config-plugins@7.2.5 (for more info, run: npm why @expo/config-plugins) Advice: Upgrade dependencies that are using the invalid package versions.

One or more checks failed, indicating possible issues with the project.

The dependencies tree can be found on the following image:

Screenshot 2023-10-23 alle 16 11 00

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android, iOS

SDK Version (managed workflow only)

48

Environment

Reproducible demo or steps to reproduce from a blank project

none

github-actions[bot] commented 7 months ago

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.

ivanmartinvalle commented 7 months ago

Commenting for activity. Running into the same issue.

ivanmartinvalle commented 7 months ago

I upgraded to Expo 49 and problem stops.

krystofwoldrich commented 6 months ago

Hello everyone, @sentry/react-native now supports Expo out of the box!

The new package doesn't depend on expo-updates package, so it won't conflict with the version you are using in your project.

Update to https://github.com/getsentry/sentry-react-native/releases/tag/5.16.0 or newer to get all the new features.

Migration guides available:

github-actions[bot] commented 4 months ago

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[bot] commented 4 months ago

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.