Crashes or freezes can happen for different reasons, but our developers are working hard to improve the game with updates.

Try these steps, even if you’ve already done some of them, as they can help improve how the game and device run:

  1. Close all running apps: Swipe away all the apps in your multitasking bar. How to do this.

  2. Restart your device:

    • Hold the Sleep/Wake button until the red slider appears.
    • Drag the slider to turn off your device.
    • After it’s off, hold the Sleep/Wake button again until you see the Apple logo.
  3. Update the game:

    • Open the App Store.
    • Tap the blue account icon in the top right corner.
    • Scroll down and check if Lumber Inc is in the list of available updates. If it is, tap "Update." If it’s not listed, your game is up-to-date.
  4. Check free space:

    • Go to Settings > General > About > Available.
    • You should have at least 20% free space for the game to run smoothly. If your storage is almost full, it may cause issues.
  5. Check your internet connection: Make sure your internet is working and that you have a stable signal (especially if using Wi-Fi).

  6.  Check if there is conflict of apps  
    • Temporarily disable the VPN or any optimization apps. Launch the game without these background apps to see if the issue is resolved.

  7. Low Power Mode: Turn off Low Power Mode in Settings > Battery as it can reduce device performance during gameplay.

  8. Overheating: Let your phone cool down or lower the screen brightness.
  9. System settings: Turn off background app updates in Settings > General > Background App Refresh.

  10. GPS issues: Turn off location services for the game in Settings > Privacy > Location Services.

  11. Bluetooth: Turn off Bluetooth to avoid network interference.

  12. Notifications: Temporarily disable notifications from other apps.

  13. iOS bugs: Ensure your iOS is up-to-date.

If the problem continues, send us a screenshot and details of what’s happening:

  • What actions cause the crash or freeze?
  • When did you first notice the issue (after an update, etc.)?