Eric Bailey
d4b23d3ab4
* Clean up env files * Use new env in Sentry setup file * Use new env in Bitdrift setup file * Use new env in chat proxy header * Prefix Bitdrift key with EXPO_PUBLIC * Deprecate SENTRY_RELEASE since we use package.json now * Use existing EXPO_PUBLIC_BUNDLE_IDENTIFIER short commit has as Sentry dist value * Fix missing bundle identifier for Render deploys * Deprecate SENTRY_DIST in favor of EXPO_PUBLIC_BUNDLE_IDENTIFIER * Prefix SENTRY_DSN with EXPO_PUBLIC to match others * Remove debugging field * Replace NODE_ENV in places where its safe * Self review * Properly patch Sentry package * Echo variables to .env in Dockerfile instead of passing to shell script * Make sure EXPO_PUBLIC_ENV is set for web container builds * Update IS_TESTFLIGHT to include testflight-android * Slice bundle hash to match other platforms, needed for render.com deployments * [APP-1331] Migrate `app-info` to new env (#8703) * Move env files into directory with platform specific files * Migrate usages of app-info to new env * Fix bad import * Update BUNDLE_DATE format comment * Trim RENDER_GIT_COMMIT to first 7 to match --short sha * Clarify build process env vars and ensure they are explicitly passed in * Revert Sentry patch as a result of prev commit * Update webpack Sentry dist value based on prev commits * Add PACKAGE_VERSION and replace in statsig to fix conflict * Fix render substitution syntax * Remove invalid syntax * Remove unnecessary testflight check * Just use long commit hash * Slice full hash for display in app * Fix missing space in ios workflow * Pass in sentry CLI env vars, align matching values * Align on RELEASE_VERSION * Add new env setup to missed OTA spot * Update webpack to use same SENTRY_RELEASE var * Just fallback to package version for Render deploys * Remove TF check for BUNDLE_DATE * Set EXPO_PUBLIC_ENV for bundle update * Consistent naming "Env" * Add comment * Use RELEASE_VERSION instead of package.json * Update PR comment CI
33 lines
971 B
TypeScript
33 lines
971 B
TypeScript
import {init} from '@sentry/react-native'
|
|
|
|
import * as env from '#/env'
|
|
|
|
init({
|
|
enabled: !env.IS_DEV && !!env.SENTRY_DSN,
|
|
autoSessionTracking: false,
|
|
dsn: env.SENTRY_DSN,
|
|
debug: false, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
|
|
environment: env.ENV,
|
|
dist: env.BUNDLE_IDENTIFIER,
|
|
release: env.RELEASE_VERSION,
|
|
ignoreErrors: [
|
|
/*
|
|
* Unknown internals errors
|
|
*/
|
|
`t is not defined`,
|
|
`Can't find variable: t`,
|
|
/*
|
|
* Un-useful errors
|
|
*/
|
|
`Network request failed`,
|
|
],
|
|
/**
|
|
* Does not affect traces of error events or other logs, just disables
|
|
* automatically attaching stack traces to events. This helps us group events
|
|
* and prevents explosions of separate issues.
|
|
*
|
|
* @see https://docs.sentry.io/platforms/react-native/configuration/options/#attach-stacktrace
|
|
*/
|
|
attachStacktrace: false,
|
|
})
|