Closed stezu closed 1 year ago
Thanks for this PR. Can you also include the build output in your PR, as CI fails without. And if you want, can you also update your changelog entry to include the PR information, like the existing entries.
Thanks!
Thanks for this PR. Can you also include the build output in your PR, as CI fails without. And if you want, can you also update your changelog entry to include the PR information, like the existing entries.
Thanks!
@kbrandwijk I updated the changelog, but I'm not sure what you're looking for with the build output. The previous PRs to this repo don't appear to include build output in their descriptions so I don't have any examples to follow.
Thanks for this PR. Can you also include the build output in your PR, as CI fails without. And if you want, can you also update your changelog entry to include the PR information, like the existing entries. Thanks!
@kbrandwijk I updated the changelog, but I'm not sure what you're looking for with the build output. The previous PRs to this repo don't appear to include build output in their descriptions so I don't have any examples to follow.
If you run yarn build
in the project, it will update the files in the build folder. Those are included in the repo.
Thanks for this PR. Can you also include the build output in your PR, as CI fails without. And if you want, can you also update your changelog entry to include the PR information, like the existing entries. Thanks!
@kbrandwijk I updated the changelog, but I'm not sure what you're looking for with the build output. The previous PRs to this repo don't appear to include build output in their descriptions so I don't have any examples to follow.
If you run
yarn build
in the project, it will update the files in the build folder. Those are included in the repo.
@kbrandwijk Any update on this fix release?
Implemented in https://github.com/expo/sentry-expo/pull/290 due to lack of follow up here. Thank you for providing the fix though!
Checklist
Why
Fixes an issue present with Expo 46 (also documented in #279) where the
react.gradle
import is now:The previous regular expression was expecting a
/
character before thereact.gradle
string and was not matching this new import string.How
The regular expression was updated to support both the old import style and the new one.
Test Plan
The change was used to run
expo prebuild
locally on a project upgraded to expo 46 and thebuild.gradle
validated to ensure the sentry change was successfully applied.