TroubleshootingLast updated

    TTLock App Crashing on iPhone or Android? How to Fix It

    A TTLock-compatible app that crashes or freezes on iPhone or Android is usually fighting one of a handful of platform issues: an outdated OS, a missing permission, a corrupted cache, low storage, or battery-saver settings that kill background Bluetooth. Updating the OS, clearing the app's cache and reinstalling — your locks and credentials stay safe in the cloud account — resolves the vast majority of cases.

    Why this happens

    Smart lock apps run a persistent Bluetooth connection alongside normal UI code, which makes them more sensitive to OS quirks and background restrictions than a typical app. Crashes and freezes usually trace back to one of these:

    • An outdated OS version. Both iOS and Android change Bluetooth and permission APIs between releases; an app built against a newer API can misbehave on an old OS version, and vice versa.
    • Missing or revoked permissions. If Bluetooth, Location (Android) or Notifications permissions were denied or later revoked in system settings, the app can crash when it tries to use a feature it assumes it has access to.
    • A corrupted local cache. Cached lock data, images or session tokens can become inconsistent after a failed sync or interrupted update, causing the app to freeze on launch.
    • Low device storage. Both platforms behave unpredictably — slow launches, failed writes, crashes — when free storage runs critically low.
    • Background Bluetooth restricted by battery-saver mode. Aggressive battery optimisation (common on Android manufacturers' custom skins, and iOS Low Power Mode) can suspend the app's Bluetooth scanning mid-task, which some app versions handle poorly.
    • A pending app or OS update. Running an old app build against a current OS, or the reverse, is one of the most common freeze triggers after either side pushes an update.

    How to fix it

    1. Update the app to the latest version. Check the App Store or Google Play for a pending update before troubleshooting further.
    2. Update the phone's OS. Install any pending iOS or Android system update; many crash reports trace back to a mismatch between an old OS and a current app build.
    3. Re-check every requested permission. On iOS, go to Settings > Privacy & Security and confirm Bluetooth and Notifications are allowed. On Android, check App info > Permissions for Location, Nearby devices and Notifications.
    4. Clear the app's cache (Android) or offload and reinstall (iOS). On Android, use App info > Storage > Clear cache first, before clearing data. On iOS, long-press the app and choose Offload App, which keeps its documents but resets its runtime state.
    5. Free up storage. Delete unused apps, photos or downloads if the device is near capacity, then relaunch.
    6. Reinstall the app. Your locks, users, passcodes and access history are tied to your cloud account, not to local app data, so signing back in after a reinstall restores everything — it does not remove anything from the locks themselves.

    Battery-saver and background Bluetooth

    Many Android manufacturers ship additional battery-management layers on top of stock Android that aggressively freeze background apps to save power. If the app crashes or drops its Bluetooth connection specifically after sitting in the background, check the manufacturer's battery settings (often called something like "battery optimisation" or "app hibernation") and exclude the app from those restrictions. On iOS, disable Low Power Mode while actively using the app, since it throttles Bluetooth scanning.

    Smart Lukko is an independent third-party app for TTLock-compatible smart locks and is not affiliated with TTLock or Sciener; the OS-level battery and permission behaviour described here applies to any Bluetooth-based lock app on the same phone.

    If that didn't work

    • Restart the phone. A full restart clears stuck background processes and a stale Bluetooth stack that a simple app relaunch won't touch.
    • Check if it happens on a specific screen. Crashes tied to one screen (adding a lock, viewing access logs) point to a specific data issue rather than a general OS problem — note exactly when it happens if you contact support.
    • Try another phone, if available. This isolates whether the crash is device-specific (settings, OS version, hardware) or affects the account's data everywhere.
    • Confirm you're signed into the correct account after reinstalling.Locks belong to the account, not the device, so a reinstall only restores your locks once you sign back in with the same email.

    Frequently asked questions

    Will reinstalling the app delete my locks or passcodes?

    No. Locks, shared users, passcodes and access logs are stored against your cloud account, not on the phone. Reinstalling and signing back in with the same account restores everything.

    Why does the app only crash when it's in the background?

    Aggressive battery-saver settings on some Android phones freeze background apps to save power, which can interrupt an active Bluetooth connection and trigger a crash. Excluding the app from battery optimisation usually fixes this.

    Does Low Power Mode on iPhone cause crashes?

    It can contribute, since Low Power Mode throttles background Bluetooth scanning. Try disabling it while actively using the app if crashes happen mainly when the screen is off or the app is backgrounded.

    The app freezes on launch before I can even sign in. What should I try first?

    Clear the app's cache (Android) or offload and reinstall it (iOS), and make sure the phone has enough free storage. A corrupted local cache or near-full storage are the most common causes of a freeze at launch.

    Is it safe to clear the app's storage and data, not just cache?

    Yes, since your lock data lives in the cloud account. Clearing data signs you out locally, so you'll need to sign back in afterwards, but nothing is lost from your account or from the locks themselves.

    Keep reading