Bank of America App 'Session Interruption' Error: Step-by-Step Fixes for iOS & Android

By David Sterling, Senior Financial Systems & Cybersecurity Analyst (CISA) Published: September 2026 | Technical Verification: Mobile Banking Security & Client API

You launch the Bank of America mobile app, authenticate with Face ID or your fingerprint, and immediately encounter a crash prompt reading: "Session Interruption" (frequently rendered in code logs as session_interruption_label or SESSION_TIMED_OUT_ABRUPTLY). The app closes, freezes on a dark navy screen, or reloads the credential screen in an endless loop.

This error is not an indicator of an account lockout or financial penalty. Rather, it represents a state desynchronization between your smartphone's secure hardware enclave and Bank of America's API gateway. Here is the technical breakdown of why this glitch occurs and how to completely resolve it.

Basic Troubleshooting First Aid: Quick Resolution Matrix

Technical Analysis: What Triggers 'Session Interruption'?

The Bank of America mobile app uses a hybrid native/embedded WebKit architecture secured by mutual Transport Layer Security (mTLS) and OAuth 2.0 bearer tokens. Under normal operating conditions, when you open the app, your device exchanges a cryptographically signed hardware key stored in your phone's Secure Enclave (Apple) or Titan M/Trusty TEE (Android) for an ephemeral session token.

A "Session Interruption" occurs when one of four failures breaks this cryptographic chain:

1. Biometric Enclave Token Corruption: When iOS or Android receives a system update, security certificates stored inside the OS Keychain can lose synchronization with third-party apps. If the Bank of America app attempts to validate a cached biometric token that the operating system has invalidated, the security handshake terminates abruptly, throwing a session interruption error.
2. Network Handshake Interruption (Wi-Fi to Cellular Handoff): If your phone switches between a home Wi-Fi network and a cellular 5G tower while the app is performing initial data synchronization, your external IP address changes mid-stream. Bank of America's banking APIs immediately sever connections when an active TLS socket changes IP addresses without re-negotiation.
3. WebKit Storage Bloat & Stale Cookies: The app utilizes an internal Safari WebKit (iOS) or Android System WebView container to render specific views, including bill payments and document centers. If these embedded browser caches accumulate corrupted cookies or exceed local memory quotas, the rendering engine crashes, producing an abrupt session interruption.

Step-by-Step Fixes for iPhone (iOS)

Work through these steps in sequence. Do not simply delete and reinstall the app without following the cache-clearing instructions, as iOS iCloud backups can restore the exact same corrupted configuration files.

1. Execute an iOS App Offload (Retains Login Profile, Clears Binaries)

An app offload removes the executable code while purging corrupted temporary cache files:

1. Open Settings on your iPhone.
2. Navigate to General > iPhone Storage.
3. Scroll down and tap Bank of America.
4. Tap Offload App and confirm.
5. Wait 15 seconds, then tap Reinstall App.
6. Launch the app and attempt to log in manually with your password.

2. Reset Biometrics for Bank of America

If offloading does not resolve the crash:

1. Open the Bank of America app. If it allows you to reach the sign-in screen, tap Sign In with Password instead of allowing Face ID to scan.
2. Once logged in, tap the Menu icon (bottom right).
3. Tap the Gear icon (Settings) > Security.
4. Toggle Face ID / Touch ID to OFF.
5. Log out of the app completely.
6. Force close the app (swipe up from the bottom of your screen and flick the app card away).
7. Relaunch the app, sign in with your credentials, and toggle Face ID back ON to generate a brand-new cryptographic token in your iPhone's Secure Enclave.

3. Clear Safari System Cookies

Because the app relies on WebKit:

1. Go to Settings > Safari.
2. Tap Advanced (at the bottom) > Website Data.
3. Search for bankofamerica and tap Delete.

Step-by-Step Fixes for Android Devices

On Android, session interruptions are almost universally tied to corrupted application data or stale WebView components.

1. Wipe App Cache and Data Partition

1. Open your phone's Settings.
2. Go to Apps (or Apps & notifications) > See all apps.
3. Locate and select Bank of America.
4. Tap Storage & cache.
5. Tap Clear Cache, then tap Clear Storage (Clear Data). (Note: This resets the app to factory conditions. You will be prompted to re-enter your User ID and complete SafePass SMS verification upon relaunch.)

2. Update Android System WebView & Google Chrome

The Bank of America app requires modern rendering frameworks to execute session authorization:

1. Open the Google Play Store.
2. Tap your profile icon > Manage apps & device > Updates available.
3. Ensure Android System WebView and Google Chrome are updated to the latest available releases.

Verification and Testing

After executing the fixes above:

1. Ensure your phone is connected to a reliable, single-source network (switch off Wi-Fi and use cellular data if your router has aggressive firewall rules).
2. Launch the Bank of America app.
3. Manually enter your Online ID and passcode.
4. If prompted, complete the one-time SafePass SMS code.
5. Once inside your dashboard, navigate to Accounts > Statements & Documents. If this screen renders cleanly without dropping the connection, your local session tokens are fully restored.

If the app continues to throw session interruptions despite a full clean install, check Downdetector or the Bank of America support feed. During scheduled core ledger maintenance (typically Sundays between 1:00 AM and 5:00 AM ET), the mobile API gateway is intentionally taken offline while the main website remains partially functional.