Document custom proxies blocking traffic to sentry.io

[mslalith]

Gradle Version

8.6

AGP Version

8.2.2

Code Minifier/Optimizer

Proguard

Version

4.3.0

Sentry SDK Version

7.3.0

Steps to Reproduce

I've integrated Sentry to my project (https://github.com/mslalith/focus_launcher/pull/383). I'm able to see crash reports in devDebug builds but not in devRelease builds

Expected Result

Crashes should properly report in release builds

Actual Result

Crashes are not being reported in release builds

[romtsn]

hi, could you enable debug logs and check the logcat output - it should show you what exactly is happening.

        <meta-data android:name="io.sentry.debug" android:value="true" />

[mslalith]

Nothing is shown when I tried enabling debug mode from SentryPluginExtension. Lemme check with manifest override

[mslalith]

Looks to me that sentry files are also obfuscated.

BTW, debug logs are not being shown when enabling from SentryPluginExtension but working if added from manifest.

[romtsn]

BTW, debug logs are not being shown when enabling from SentryPluginExtension but working if added from manifest.

Yea, that's because debug in SentryPluginExtension is for the gradle plugin, and to have the sdk debug logs enabled you have to go through manifest.

---

Few questions to the issue:

• Are you using self-hosted Sentry or sentry.io?
• Do you set a proper DSN for your release builds?
• Are you behind a proxy on your device/emulator?

[mslalith]

Are you using self-hosted Sentry or sentry.io?

Not self-hosted

Do you set a proper DSN for your release builds?

DSN is proper. I can see it in debug logs

Are you behind a proxy on your device/emulator?

No. I tested on real device as well

I can see crash reports with debug build but not with release

[mslalith]

@romtsn Somehow today I could see crash reports from emulator (release build) but still no luck when tested on real device

[romtsn]

@romtsn Somehow today I could see crash reports from emulator (release build) but still no luck when tested on real device

just to make sure, do you restart the app after it crashes? we upload crash reports on restart (to not block the process from termination for too long) and whenever internet connectivity changes

[mslalith]

just to make sure, do you restart the app after it crashes? we upload crash reports on restart (to not block the process from termination for too long) and whenever internet connectivity changes

Yes I did

[mslalith]

@romtsn Found the issue. When DuckDuckGo's App Tracking Protection is enabled, reports are not being sent. For now I disabled this for my launcher. But I feel this should be properly handled (if it is possible)

[romtsn]

@romtsn Found the issue. When DuckDuckGo's App Tracking Protection is enabled, reports are not being sent. For now I disabled this for my launcher. But I feel this should be properly handled (if it is possible)

glad you figured it out. I don't think we can handle this, but it definitely deserves to be mentioned on the docs/troubleshooting. I will address that, thanks for the update!

[kahest]

Troubleshooting entry similar to e.g. https://docs.sentry.io/platforms/javascript/troubleshooting/#dealing-with-ad-blockers would make sense