-
-
Notifications
You must be signed in to change notification settings - Fork 353
Description
OS:
- Windows
- MacOS
- Linux
Platform:
- iOS
- Android
SDK:
-
@sentry/react-native
-
react-native-sentry
SDK version: 1.2.1
react-native
version: 0.61.5
Are you using Expo?
- Yes
- No
Are you using sentry.io or on-premise?
- sentry.io (SaaS)
- on-premise
Configuration:
Sentry.init({
dsn: SENTRY_DSN,
environment: ENV,
})
I have the following issue:
I recently upgraded to 1.2.1 of this plugin, and suddenly started to get ApplicationNotResponding errors. According to the java documentation here https://docs.sentry.io/clients/java/integrations/#android, it looks like it's an optional setting that you have to turn on (and that it waits 5 seconds before sending the error).
I have not turned it on, and it seems to complain after 4 seconds.
I realise I don't have the latest version of sentry, and will look at getting that updated soon, but I just wanted to confirm if that was a known issue, and perhaps has been fixed.
If not, can you please confirm why it seems to be enabled by default, since the java docs at least seems to suggest it's an opt in option.
I am using this in my sentry.properties, defaults.url=https://sentry.io/, but assuming that should be as the documentation mentioned.
An example title of the error is ApplicationNotResponding: Application Not Responding for at least 4000 ms.
Update:
I decided to use the ANR error by setting the timeout to 15seconds, which is getting ignored, I'm still getting alerts after 4 seconds. I'm going to assume then that explicitly disabling is going to also have no effect.
The biggest problem of all. My quota of events is going to run out in three days, which means sentry becomes useless to me.