Skip to content

Conflict with react-native-legal on Android #5236

@ajarl

Description

@ajarl

What React Native libraries do you use?

Expo (mobile only), RN New Architecture, React Navigation, Expo Router, Expo Web

Are you using sentry.io or on-premise?

sentry.io (SaS)

@sentry/react-native SDK Version

7.0.1

How does your development environment look like?

See sample project https://github.com/tiagocorreiaalmeida/ReactNativeLegalWithSentry

Sentry.init()

See sample project https://github.com/tiagocorreiaalmeida/ReactNativeLegalWithSentry

Steps to Reproduce

When using the package react-native-legal to show license attributions and the Sentry React Native SDK is included, no license attributions are shown for the Android app (works fine in iOS). It seems there is some conflict with the way resources are generated on the Android side related to something that Sentry's gradle plugin does (maybe). See the following thread for more details including a reproduction sample. According to the maintainer of react-native-legal it seems to be something on the Sentry side; maybe some gradle task is not being executed.

callstackincubator/react-native-legal#108

Direct link to repro project: https://github.com/tiagocorreiaalmeida/ReactNativeLegalWithSentry

Expected Result

Sentry shouldn't have any effect on the generation of resources by other libraries. The license attributions in react-native-legal should be shown in Android when the Sentry SDK is applied.

Actual Result

react-native-legal's expected json file with the license data is not generated on build on Android and hence there are no licenses to show. If Sentry is not included, licenses are in fact shown, so there is some conflict between these two.

Metadata

Metadata

Assignees

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions