应用暂停时Crashlytics频繁发起网络请求的原因及耗电影响咨询

Let’s walk through what’s going on here and answer your questions clearly:

1. Common Reasons for Background Requests in Crashlytics v1.4.1.19 #

• Pending Crash/Error Reports: If your app hit crashes, ANRs, or non-fatal errors before moving to the paused state, this older SDK version might be retrying to send those reports in the background. Unlike newer releases, v1.4.1.19 doesn’t handle pending uploads efficiently—it often triggers retries even when the app isn’t active.
• Session Metadata Sync: Crashlytics tracks user sessions, and when your app enters the background, the SDK may attempt to finalize and send session data (like duration, app state, or user interactions) to its servers. This behavior was more prevalent in older builds that didn’t optimize when background syncs should happen.
• Legacy Health Checks: Some early Crashlytics versions included periodic background checks to confirm the SDK was working correctly. While this is rare in modern versions, your specific release might still include this logic, leading to unexpected requests.

2. Battery Impact of These Background Requests #

Absolutely—these requests can impact battery life, especially if they’re frequent:

• Each network request wakes up the device’s cellular/Wi-Fi radio, which is one of the biggest battery drainers. If the SDK is sending multiple POST requests to /spi/v2/events while the app is paused, it keeps the radio active longer than necessary.
• If uploads fail, older SDKs like v1.4.1.19 may not use exponential backoff (slowing down retries over time). This means repeated, frequent attempts that waste extra battery.

3. Steps to Fix This #

• Upgrade to the Latest Crashlytics SDK: Your version is quite outdated. Google (now managing Crashlytics as part of Firebase) has heavily optimized background behavior in newer releases—including smarter upload scheduling, improved retry logic, and reduced background activity. Upgrading will almost certainly cut down on these unwanted requests.
• Audit App Errors: Check your Crashlytics dashboard for spikes in crashes or non-fatal errors. Fixing those underlying issues will reduce the number of pending reports the SDK is trying to send in the background.
• Review Background Permissions: Make sure your app isn’t granting unnecessary background permissions that let the SDK run unrestricted. While Crashlytics uses standard background processing, double-checking permissions can help limit unnecessary activity.

内容的提问来源于stack exchange，提问作者Pradeep Reddy