search

expo / sentry-expo

MIT License
202 stars 83 forks source link

sentry-expo 7.0.1 causes fastlane error during production build #359

Closed pkayfire closed 7 months ago

pkayfire commented 1 year ago

Summary

Seeing a fastlane error when trying to build an Expo project with sentry-expo 7.0.1. Downgrading back 6.2.1 resolves the error.

image

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?

iOS

SDK Version (managed workflow only)

7.0.1

Environment

expo-env-info 1.0.5 environment info: System: OS: macOS 13.0.1 Shell: 5.8.1 - /bin/zsh Binaries: Node: 18.16.0 - /usr/local/bin/node Yarn: 1.22.15 - ~/.yarn/bin/yarn npm: 8.1.2 - /usr/local/bin/npm Managers: CocoaPods: 1.8.4 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4 Android SDK: API Levels: 28, 29 Build Tools: 28.0.3, 29.0.3 System Images: android-29 | Google Play Intel x86 Atom IDEs: Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild npmPackages: expo: ^48.0.16 => 48.0.19 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.71.8 => 0.71.8 react-native-web: ~0.18.9 => 0.18.12 npmGlobalPackages: eas-cli: 3.14.0 expo-cli: 6.3.8 Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

Build expo project for production with sentry-expo 7.0.1

sebastiancrossa commented 12 months ago

running into the same issue!

winstromming commented 10 months ago

@pkayfire @sebastiancrossa I was able to resolve this (or a similar?) issue (on 7.0.0) by removing the postPublish hook for uploading sourcemaps.

krystofwoldrich commented 10 months ago

@pkayfire Can you share the whole build log, hopefully from there we will be able to identify what's happening.

github-actions[bot] commented 8 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 7 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.