NimbusErrorException$RequestError: Network error: "fetch error: java.net.SocketTimeoutException"

[jonalmeida]

https://sentry.prod.mozaws.net/operations/firefox-nightly/issues/11722256/?referrer=github_plugin

NimbusErrorException$RequestError: Error sending request: [no-sentry] Network error: Java error: "fetch error: java.net.SocketTimeoutException"
    at org.mozilla.experiments.nimbus.internal.NimbusError.intoException(nimbus.kt:14)
    at org.mozilla.experiments.nimbus.internal.NimbusClient.fetchExperiments(nimbus.kt:13)
    at org.mozilla.experiments.nimbus.Nimbus$fetchExperimentsOnThisThread$1.invoke(Nimbus.kt:1)
    at org.mozilla.experiments.nimbus.Nimbus.withCatchAll(Nimbus.kt:1)
    at org.mozilla.experiments.nimbus.Nimbus.fetchExperimentsOnThisThread$nimbus_release(Nimbus.kt:1)
...
(6 additional frame(s) were not displayed)

[INFO] Error sending request: [no-sentry] Network error: Java error: "fetch error: java.net.SocketTimeoutException"

┆Issue is synchronized with this Jira Task

[jonalmeida]

These three issues (#20267, #20268, #20269) all spiked on June 23rd in Sentry together because that was when we started to use the crash reporter in Nimbus. I don't believe they are new issues, but it is still something we need to address as clients are failing to register for an experiments.

[jonalmeida]

SocketTimeout doesn't seem like something we can do anything about (although the number of affected users seems unusually high), but do we need to report this? For AutoPushFeature, we filter out the non-fatal exceptions that the native layers throw - this might be an option here.

cc: @jhugman @travis79

[jonalmeida]

Spoke offline to James, we can filter out this error since it's not useful.