- SDK Version: 37.0.0
- Platforms(Android/iOS/web/all): iOS standalone app (but also sometimes on the Android standalone app).
Sentry crash reporting is configured on our standalone iOS and Android apps. Since a while ago, there started to appear a strange error that gets caught by two of our API calls (they get fired immediately after the app is open or comes from inactive to active state).
I managed to log the error
caught (as additional data in Sentry), and it appears to be rather strange and I assume it originates NOT from our API request calls, but probably from something Expo does below the hood:
{
column: 7285,
line: 131,
message: Network request failed,
name: TypeError,
sourceURL: https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js,
stack:
https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:131:7285
dispatchEvent@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:147:5676
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:142:6510
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:142:3250
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:65:1280
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:41:3685
https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:41:841
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:41:2939
value@https://d1wp6m56sqw74a.cloudfront.net/%40our-user%2Four-app%2F1.13.7%2F7548e094dceeab12974f77e52ea0c6d0-37.0.0-ios.js:41:813
value@[native code]
}
Any ideas where this is coming from, which causes it and how I can resolve it?
Interestingly, it seems like when this happens - probably it executes our API calls again. But I’m not 100% sure about the reason why this happens either.