Why Is My Strava App Crashing During Long Runs?

You lace up your shoes, start your Strava recording, and head out for a long run. Everything feels great for the first few miles. Then, somewhere around mile 8 or 10, you glance at your phone and discover the app has crashed. Your data is gone. Your pace splits have vanished. That perfectly tracked route is now a blank screen. This is one of the most frustrating experiences for any runner who depends on Strava to log their training.

You are not alone in this struggle. Thousands of runners report the same problem across Reddit, the Strava Community Hub, and running forums every single month. The Strava app crashes during long runs for a variety of reasons, from aggressive battery optimization settings to GPS conflicts and memory overload. The good news is that almost every one of these causes has a clear, practical fix.

This post will walk you through 14 proven solutions to stop your Strava app from crashing during long runs. Each fix is easy to follow and does not require any technical expertise. By the end of this guide, your Strava app should stay alive and recording for every mile of your longest runs.

In a Nutshell

• Battery optimization is the number one culprit. Most Android phones aggressively kill background apps to save battery. Samsung, Xiaomi, Huawei, and OnePlus devices are especially notorious for shutting down Strava mid run. You must exempt Strava from battery optimization in your phone settings to keep it running.
• Low Power Mode on iPhones will crash Strava. Apple’s Low Power Mode restricts background activity and GPS usage. This directly causes Strava to lose its GPS signal or shut down entirely during long runs. Always disable Low Power Mode before you start recording.
• Location permissions must be set to “Always Allow.” If Strava only has permission to access your location “while using the app,” the moment your screen locks, the app loses GPS access. This can cause freezes, data loss, and outright crashes.
• Clearing the app cache fixes many crash issues. Strava stores temporary data that can become corrupted over time. A simple cache clear from your phone settings often resolves repeated crashing without losing any of your saved activities.
• An outdated app or operating system creates conflicts. Running an old version of Strava on a new operating system, or a new version of Strava on an old operating system, produces compatibility errors that lead to crashes.
• Phone overheating during long runs triggers emergency shutdowns. Extended GPS tracking generates heat. When your phone gets too hot, the operating system will force close demanding apps like Strava to protect the hardware.

Understanding Why Strava Crashes During Long Runs

Strava crashes during long runs because extended recording sessions place heavy demands on your phone. The app must maintain a continuous GPS lock, process real time data, and keep running in the background while your screen is off. Each of these tasks consumes battery, memory, and processing power.

Short runs rarely trigger crashes because the phone can handle 20 or 30 minutes of GPS tracking without strain. Long runs of 60 minutes or more push the phone’s resources to their limits. The operating system starts making decisions about which apps deserve to keep running. Unfortunately, Strava often loses that competition to system processes.

Android devices are particularly aggressive about this. Manufacturers like Samsung, Xiaomi, OnePlus, and Huawei add their own battery management layers on top of Android’s built in restrictions. These layers automatically close apps that have been running in the background for too long. The phone treats Strava the same way it treats a social media app you forgot to close.

iPhones handle background apps differently but still cause problems. iOS limits the resources available to background apps, and features like Low Power Mode cut those resources even further. The result is the same: Strava stops recording, freezes, or crashes entirely during your run.

Understanding these root causes is essential because each one requires a different fix. A runner dealing with battery optimization problems needs a different solution than someone whose app cache is corrupted. The sections below address each specific cause with clear, step by step instructions.

Disable Battery Optimization for Strava on Android

Battery optimization is the single most common reason Strava crashes during long runs on Android phones. Every Android manufacturer includes aggressive power management features that kill background apps. Strava records your run in the background, which makes it a prime target for these battery savers.

The fix requires you to exempt Strava from battery optimization. The exact steps vary by phone brand. On Samsung devices, go to Settings, then Apps, tap the three dot menu in the upper right corner, select Special Access, choose Optimize Battery Usage, find Strava in the All Apps list, and toggle it off. On OnePlus devices, go to Settings, then Battery, then Battery Optimization, switch to the All Apps list at the top, find Strava, and select Don’t Optimize.

For Xiaomi phones running MIUI, go to Settings, then Additional Settings, then Battery and Performance, then Manage Apps Battery Usage, and set Strava to no restrictions. Huawei users need to add Strava to the Protected Apps list and also disable battery optimization under Settings, Apps, Advanced, Ignore Optimizations.

After making this change, restart your phone and test Strava on your next run. This single fix resolves the crashing issue for the majority of Android users.

Turn Off Low Power Mode on iPhone Before Running

Low Power Mode on iPhone reduces background activity to extend battery life. It dims the screen, limits email fetching, and restricts GPS access for background apps. This directly conflicts with what Strava needs to record your run accurately.

Many runners enable Low Power Mode before a long run because they worry about battery life. This seems logical but creates the exact opposite of the intended result. Strava needs full GPS access and unrestricted background processing to record your run. Low Power Mode takes both of those away.

To disable Low Power Mode, go to Settings, then Battery, and toggle off Low Power Mode. You can also swipe into Control Center and tap the battery icon if it appears yellow. Make sure the icon returns to its normal color before starting your Strava recording.

If battery life is a concern during long runs, there are better ways to conserve power. Turn on Airplane Mode after starting your Strava recording. This disables cellular data and Wi Fi, which are the biggest battery drains on your phone. GPS works independently from cellular service, so Strava will continue to track your location accurately.

You can also reduce screen brightness to its minimum setting and disable notifications from other apps. These adjustments save far more battery than Low Power Mode without interfering with Strava’s ability to record your run.

Set Location Permissions to Always Allow

Strava requires constant access to your phone’s GPS to track your run. If your location permissions are set to “Only While Using the App”, Strava loses GPS access the moment your screen turns off or another app moves to the foreground. This causes data gaps, frozen recordings, and crashes.

On iPhone, go to Settings, then Privacy and Security, then Location Services, find Strava, and select Always. Also make sure the Precise Location toggle is turned on. Without precise location, Strava uses approximate positioning that produces inaccurate distance readings and can cause the app to behave unpredictably.

On Android, go to Settings, then Apps, then Strava, then Permissions, then Location, and select Allow All the Time. Some Android versions phrase this differently, but the option you need grants Strava background location access. Also check that your phone’s overall location mode is set to High Accuracy, which uses GPS, Wi Fi, and mobile networks together for the best positioning.

A Reddit user recently resolved their Strava crashing issue by discovering that their phone had silently revoked Strava’s storage permission after an operating system update. Permissions can change without your knowledge after updates. Make it a habit to verify Strava’s permissions after every major phone update.

This is a quick fix that takes less than a minute but prevents a huge percentage of crash and data loss problems during long runs.

Clear Strava’s Cache and App Data

Strava stores temporary files on your phone to speed up loading times and store offline data. Over time, this cache can grow large and become corrupted. Corrupted cache files are a known cause of Strava crashes, especially when the app tries to process large amounts of GPS data during long activities.

On Android, go to Settings, then Apps, then Strava, then Storage, and tap Clear Cache. This removes temporary files without deleting your account data or login information. If clearing the cache does not resolve the issue, you can also tap Clear Data, but this will log you out and reset all local settings.

On iPhone, there is no direct cache clearing option. The equivalent action is to delete the Strava app and reinstall it from the App Store. Before doing this, make sure your activities are synced to your Strava account online. All your data lives on Strava’s servers, so reinstalling the app will not erase your activity history.

The Strava Community Hub lists cache corruption as a known issue that affects users who have been running the app for extended periods without reinstalling. Several users reported that their app crashed every time they tried to open an activity, and clearing the cache resolved it immediately.

Make clearing Strava’s cache a regular maintenance task. Doing it once a month keeps the app running smoothly and prevents the buildup of corrupted temporary files that cause crashes during demanding long runs.

Update Strava and Your Phone’s Operating System

Running an outdated version of Strava on a newer operating system, or vice versa, creates compatibility conflicts. These conflicts produce unpredictable behavior including crashes, GPS failures, and sync errors. Keeping both the app and your operating system current is one of the simplest preventive measures.

Open the App Store on iPhone or Google Play Store on Android and check for Strava updates. Enable automatic updates if you have not already. Strava releases frequent updates that include bug fixes and performance improvements. A crash you experience today may have already been fixed in the latest version.

Operating system updates matter just as much. Apple and Google regularly release patches that change how apps interact with GPS, battery management, and background processes. An iOS or Android update can break Strava’s functionality overnight if the app has not been updated to match the new system requirements.

However, be cautious with major operating system updates. Early adoption of a new iOS or Android version sometimes introduces new bugs. Check the Strava Community Hub or Reddit after a major OS update to see if other users report issues. If problems are widespread, you may want to wait a few days for Strava to release a compatibility patch.

Also verify that your phone model is still supported by Strava. Older devices running outdated operating systems may lose official Strava support, which means new app versions may crash or fail to install entirely.

Prevent Your Phone from Overheating

Phones generate significant heat during long GPS tracking sessions. The processor works continuously to maintain a satellite lock, record data points, and run background processes. On hot days or during runs lasting more than an hour, your phone can overheat and trigger an emergency shutdown of demanding apps.

The operating system protects the hardware by force closing apps that contribute to excessive heat. Strava, with its constant GPS usage, is almost always one of the first apps to be shut down. You may notice your phone feeling warm before the crash occurs.

To prevent overheating, remove your phone from any thick case during long runs. Cases trap heat and prevent natural cooling. If you carry your phone in an armband or running belt, choose one made from breathable mesh material rather than neoprene or heavy fabric.

Avoid direct sunlight on your phone. Keep it in a pocket, running vest, or shaded pouch rather than an exposed armband. Even a few degrees of temperature reduction can prevent the operating system from triggering a thermal shutdown.

Close all unnecessary apps before starting your run. Every open app adds a small amount of heat and processing load. Swipe away social media apps, email, and browsers. The fewer apps competing for resources, the cooler your phone will stay during a long Strava recording session.

If overheating is a persistent problem, consider recording your runs with a GPS watch and syncing the data to Strava afterward. This removes the phone from the equation entirely.

Free Up Phone Memory and Storage

Your phone needs available RAM (active memory) and storage space to run Strava smoothly. When your phone runs low on either, the operating system aggressively closes background apps to free up resources. Strava, running silently in the background during your run, becomes an easy target.

Check your phone’s available storage by going to Settings, then General, then iPhone Storage on iOS or Settings, then Storage on Android. If you have less than 2 GB of free space, your phone is more likely to experience app crashes during memory intensive tasks like GPS tracking.

Delete unused apps, old photos, and downloaded files to create breathing room. Move photos and videos to cloud storage. Clear downloads you no longer need. Every bit of freed storage helps your phone manage its resources more efficiently during long runs.

RAM management matters even more than storage for preventing mid run crashes. Before starting your Strava recording, close all other open apps manually. On iPhone, swipe up from the bottom and flick away each app. On Android, tap the recent apps button and clear all.

Phones with 4 GB of RAM or more handle Strava’s demands much better than budget devices with 2 or 3 GB. If you run long distances regularly and use Strava as your primary tracker, your phone’s hardware capabilities matter. This does not mean you need the newest flagship, but a phone with sufficient RAM makes a real difference.

Enable Background App Refresh for Strava

Background App Refresh allows apps to update their content and maintain active processes while they are not on your screen. If this feature is disabled for Strava, the app cannot maintain its GPS lock or record data when the screen is off.

On iPhone, go to Settings, then General, then Background App Refresh. Make sure the master toggle at the top is enabled. Then scroll down to Strava and ensure its individual toggle is also turned on. Some users disable Background App Refresh globally to save battery, which silently kills Strava’s recording ability.

On Android, the equivalent setting is found under Settings, then Apps, then Strava, then Battery. Select Unrestricted or Allow Background Activity, depending on your phone’s wording. This tells the operating system to let Strava run freely in the background without restrictions.

A common scenario involves runners who recently switched phones or performed a factory reset. Fresh installations of Strava may not have Background App Refresh enabled by default. The app works perfectly when the screen is on, so the runner assumes everything is fine. The crash occurs only during the long run when the screen has been off for an extended period.

Test this by starting a short recording, locking your phone, and placing it in your pocket for 15 minutes. Check the recording afterward. If there are gaps or the app has stopped, Background App Refresh is likely the culprit.

Use Airplane Mode to Save Battery and Reduce Conflicts

Airplane Mode is an underrated tool for runners who track long runs with their phone. It disables cellular data, Wi Fi, and Bluetooth while leaving GPS fully functional. This dramatically reduces battery consumption and eliminates network related conflicts that can cause Strava to crash.

Many Strava crashes occur because the phone is simultaneously trying to maintain a cellular connection, search for Wi Fi networks, and run GPS tracking. Each of these tasks fights for the same radio hardware and processing power. Removing cellular and Wi Fi from the equation lets your phone dedicate its full resources to GPS tracking.

To use this method, open Strava first and start your activity recording. Then enable Airplane Mode from your phone’s quick settings panel. The GPS recording will continue without interruption. Your phone will use significantly less battery because it is no longer communicating with cell towers and Wi Fi routers.

This approach has an additional benefit. Your phone will not receive notifications, calls, or messages during your run. For many runners, this is a welcome side effect that eliminates distractions. If you need to receive emergency calls, you can re enable cellular briefly and then switch Airplane Mode back on.

Reddit users in the Strava community frequently recommend this method as their primary solution for long run crashes. Several runners report that Airplane Mode extended their recording time from crashing at 90 minutes to running smoothly for four hours or more.

Reinstall Strava as a Last Resort

If you have tried every other fix and Strava still crashes during long runs, a complete reinstall often resolves deep rooted issues. Reinstalling removes corrupted files, broken preferences, and leftover data that a simple cache clear cannot reach.

Before uninstalling, confirm that all your activities are synced to your Strava account. Open a web browser, go to strava.com, and log in. Check that your recent activities appear there. Your activity data is stored on Strava’s servers, not on your phone. Reinstalling the app will not delete your history, segments, or social connections.

On iPhone, press and hold the Strava icon and tap Remove App, then Delete App. On Android, go to Settings, then Apps, then Strava, and tap Uninstall. After removal, restart your phone before reinstalling. This clears any remaining temporary files from memory.

Download Strava fresh from the App Store or Google Play Store. Log in to your account and immediately configure your permissions. Set location to Always Allow, enable Background App Refresh, and exempt Strava from battery optimization. Do not skip these steps, because the reinstalled app will have default permission settings that may not match what Strava needs for long run recording.

Test the fresh installation on a medium distance run before trusting it for your long run. Record a 45 minute to 60 minute session and verify that the GPS track is accurate, the app stays active, and no crashes occur. This gives you confidence before your next big training effort.

Consider Using a GPS Watch Instead of Your Phone

If your phone consistently fails during long runs despite every software fix, the most reliable solution is to record your runs with a dedicated GPS watch and sync the data to Strava afterward. GPS watches are built specifically for extended athletic tracking and do not suffer from the same background process limitations as phones.

Watches from Garmin, COROS, Polar, Apple Watch, and other brands all sync directly with Strava. You record the activity on your watch, finish your run, and the data appears in your Strava feed automatically. The GPS accuracy is typically better than phone GPS, and battery life on most running watches exceeds 10 hours in GPS mode.

This approach eliminates every phone related crash issue discussed in this guide. You no longer need to worry about battery optimization, background app refresh, overheating, or memory management. Your phone stays in your pocket or at home, and your watch handles the tracking.

Many serious runners consider a GPS watch an essential piece of equipment rather than an optional accessory. The reliability and accuracy improvements justify the investment for anyone who runs long distances regularly. You still get all the social features, segment tracking, and training analysis that make Strava valuable, but the data source becomes far more dependable.

If you already own a smartwatch, check whether it has a native Strava app or can sync through a connected fitness platform. You may already have a solution on your wrist that you have not explored.

Check for Known Strava Bugs and Server Issues

Sometimes the crash is not your fault at all. Strava occasionally releases updates that contain bugs affecting specific devices or operating system versions. These bugs can cause crashes that no amount of settings adjustment will fix until Strava releases a patch.

Before spending hours troubleshooting your phone, check the Strava Community Hub at communityhub.strava.com. Strava’s support team labels confirmed problems as “Known Issues” and provides status updates. If your crash matches a known issue, you can rest assured that a fix is in development.

Reddit’s r/Strava community is another valuable resource. Other runners often report new bugs within hours of an update. A quick search for “crash” or “not recording” will show you whether other users are experiencing the same problem. If many people report the same issue after the same update, the problem is on Strava’s side.

You can also check Strava’s server status. Occasional server outages prevent the app from syncing or functioning properly. While server issues rarely cause the app to crash outright during recording, they can cause errors when saving or uploading your activity that may look like a crash.

If a known bug is causing your crashes, the best temporary fix is to roll back to a previous version of Strava on Android (by sideloading an older APK) or to wait for the next update on iPhone. Strava typically patches critical bugs within a few days of discovery.

Reset Your Phone’s GPS and Network Settings

Corrupted GPS data or misconfigured network settings can cause persistent Strava crashes that survive app reinstalls. Resetting these settings gives your phone a fresh start without erasing your personal data or apps.

On Android, install the free app called GPS Status and Toolbox from the Google Play Store. Open the app, go to the menu, select Manage A GPS State, and tap Reset. This clears the cached satellite data that your phone uses for quick GPS locks. Stale or corrupted A GPS data forces the phone to work harder to find satellites, which increases processing load and battery drain during long runs.

On iPhone, go to Settings, then General, then Transfer or Reset iPhone, then Reset, and select Reset Location and Privacy. This reverts all location settings to factory defaults. You will need to grant location permissions again to all your apps, including Strava. Also consider resetting network settings from the same menu, which clears Wi Fi passwords and cellular configurations that might interfere with GPS performance.

After resetting, take your phone outside with a clear view of the sky. Open Strava and let it acquire a GPS lock before you start moving. Wait until the GPS indicator shows a strong signal. This initial lock establishes a solid connection with satellites and reduces the chance of signal loss during your run.

Performing a GPS reset once every few months is good maintenance practice for any runner who relies on phone based GPS tracking.

Create a Pre Run Checklist to Prevent Future Crashes

The best way to prevent Strava crashes is to follow a consistent routine before every long run. A simple pre run checklist takes 60 seconds and eliminates the most common causes of mid run crashes.

Start by charging your phone to at least 80% before heading out. A phone that starts at 40% battery is far more likely to trigger aggressive power saving measures during a long run. Fully charged phones give the operating system less reason to kill background apps.

Next, close all apps except Strava. Open your recent apps view and swipe away everything. This frees up RAM and reduces heat generation. Then verify that Low Power Mode is off on iPhone or that battery saver is disabled on Android.

Open Strava and start your recording before locking the screen. Wait a few seconds to confirm that the GPS lock is strong and the recording has begun. This ensures Strava is the active foreground app when your phone’s screen turns off, which gives it priority over other background processes.

Finally, enable Airplane Mode after starting the recording if you do not need to receive calls during your run. This single step dramatically improves battery life and reduces the chance of resource conflicts.

Write this checklist in your phone’s notes app or tape it to your mirror. Following it before every long run will save you from the frustration of lost data and crashed recordings. Prevention is always easier than troubleshooting.

Frequently Asked Questions

Why does Strava only crash on long runs and not short ones?

Short runs place minimal demands on your phone’s battery, memory, and GPS. The operating system does not feel pressured to close background apps during a 20 minute run. Long runs of 60 minutes or more push these resources to their limits. Battery optimization features activate, the phone heats up, and the operating system begins closing apps it considers nonessential. Strava, running in the background while your screen is off, becomes a target. The longer your run, the more opportunities the phone has to trigger a shutdown.

Will I lose my run data if Strava crashes mid activity?

It depends on when the crash occurs and your phone’s operating system. Strava attempts to save GPS data periodically during recording. In many cases, partial data from before the crash is recoverable. Check your Strava feed after the crash. You may find a truncated activity with data up to the point of the crash. However, data recorded after the crash point is permanently lost. Using a GPS watch as a backup ensures you never lose an entire run.

Does Strava use more battery than other running apps?

Strava’s battery usage is comparable to other GPS tracking apps like Nike Run Club, MapMyRun, and Runkeeper. All GPS based running apps drain battery at similar rates because GPS tracking is the primary power consumer. The differences come from additional features like live segments and beacon sharing, which use extra data. Disabling these features during long runs reduces Strava’s battery footprint slightly.

Can I use Strava on an older phone for long runs?

You can, but older phones are more likely to crash during long sessions. Phones with less than 3 GB of RAM and older processors struggle to maintain GPS tracking for extended periods. Older batteries also degrade faster under heavy GPS use. If you run long distances regularly with an older phone, keep the phone as cool as possible, close all other apps, and use Airplane Mode to reduce the processing load.

How do I report a Strava crash to the developers?

Visit the Strava Community Hub at communityhub.strava.com and search for your issue first. If it already exists, add your experience to the thread. If it is a new problem, create a post with your phone model, operating system version, Strava app version, and a description of what happened. You can also contact Strava support directly through the app under Settings, then Help, then Contact Us. Include as much detail as possible to help the development team identify and fix the bug.

Should I use a phone case or armband during long runs with Strava?

Use a lightweight, breathable case or armband. Thick, insulated cases trap heat and increase the chance of thermal shutdowns during long GPS tracking sessions. Mesh armbands and thin running belts allow better airflow around the phone. Avoid placing your phone in direct sunlight. A phone that stays cool runs Strava more reliably for longer periods.