Need help fixing issues in the Testbook App

Apps
1

Is anyone else having problems with the Testbook App not loading quizzes and crashing during mock tests? I rely on it daily for exam prep and it’s really affecting my study schedule. I’ve tried reinstalling and clearing cache but nothing works. Any tips or fixes that actually solved this for you?

2

Yeah, you are not the only one. Testbook has been buggy for a lot of people this week.

Things you can try that often fix the quiz not loading / crash issue:

  1. Clear app data properly
    • Go to Settings → Apps → Testbook → Storage → Clear cache, then Clear data
    • Log in again
    This works better than reinstall alone.

  2. Turn off battery optimizaton
    • Settings → Battery → Battery optimization / Background limits
    • Remove Testbook from “optimized” or “restricted” list
    The app stops getting killed in the background during long mock tests.

  3. Check for latest version
    • Open Play Store → Search Testbook → Update
    Some older builds freeze on quiz load and during results.

  4. Stable network
    • Use WiFi instead of mobile data if possible
    • Avoid VPN or DNS apps
    When network drops mid quiz the app often hangs then crashes.

  5. Free up RAM and storage
    • Close heavy apps like games or Chrome with many tabs
    • Keep at least 2–3 GB free storage
    On 3–4 GB RAM phones, Testbook lags a lot during full length mocks.

  6. Try web version
    • Open testbook.com on Chrome
    • Start mock there when the app misbehaves
    I did half of my mocks on browser when the app kept crashing last month.

  7. Turn off animations in app
    • In Testbook settings, disable fancy animations or transitions if they exist in your version
    Some users saw fewer crashes after that on older phones.

  8. Temporary fix for daily schedule
    • Take screenshots of question lists when it loads
    • Keep a timer separately
    That way if the app crashes, you still do serious timed practice.

If none of this helps, mail them with details so they take it seriously:
• Your phone model
• Android version
• App version
• Exact screen where it crashes
• Time and date
They respond faster when you attach a screen recording. I had similar issues during a scholarship test and got a reply within a day after I sent logs and video.

3

Same boat here, the app has been acting like it’s in beta again.

Most of what @voyageurdubois said is solid, but I’ll add a few different angles:

  1. Skip partial reinstall
    If you reinstall but your Google backup auto-restores the same app data, the bug sometimes comes right back. Before reinstalling, disable “auto restore” for apps in your Google backup settings, then uninstall, reboot, then install again. Otherwise you’re just putting the same broken config back in.

  2. Check system WebView
    Testbook is heavily dependent on Android System WebView / Chrome.
    • Go to Play Store → update Android System WebView and Chrome.
    • If you’re on Android 12+, try setting Chrome as the default WebView in Developer Options (enable Dev Options by tapping Build Number 7 times in About Phone).
    Outdated WebView is a sneaky cause of quiz pages not rendering or freezing.

  3. Try older version, not always newer
    Slight disagreement with the “always update” advice. Sometimes the latest Testbook build is the problem. If the issues started just after an update, grab the previous stable version from a trusted store and test that. If the older version runs mocks fine, you know it’s their new build, not your phone.

  4. Logcat check if you’re a bit techy
    If you’re on Android and have a PC:
    • Install platform tools (ADB).
    • Run adb logcat while you start a quiz and wait for the crash.
    If you see repeated WebView / memory errors, that confirms it’s not your network or random. You can attach that snippet when you email support to make them actually pay attention.

  5. Turn off system-level “performance enhancers”
    Some 3rd party cleaners / boosters / “RAM optimizers” kill Testbook in the middle of mocks. If you have apps like Clean Master, security suites from phone makers, or floating FPS counters, disable them while testing. I’ve seen mocks die instantly when a cleaner runs in background.

  6. Different device profile test
    If possible, log into your Testbook account on:
    • A different phone, or
    • A tablet, or
    • A friend’s device
    If quizzes work fine there, it’s likely a compatibility issue with your specific device/OS combo. Mention that in your support ticket. If it breaks on multiple devices, that screams server-side or account-specific bug.

  7. Watch for time-of-day patterns
    I noticed Testbook going into slideshow mode during evening peak hours. If your crashes mostly happen around the same time daily, that might actually be their servers choking, not your phone. In that case, trying very early morning sessions can be way more stable, at least until they scale up.

  8. Local backup of your prep flow
    Since it’s messing with your schedule, I’d adjust the strategy a bit:
    • Keep a parallel plan with PDFs / books / other apps for days when Testbook acts up.
    • After every mock, note down key stats & topics in a separate notes app or notebook, so even if results screen crashes, your takeaways are not lost.
    It reduces the mental hit when the app randomly quits.

If you do email them, I’d also ask specifically whether they are aware of issues for your device model / OS version. Sometimes they silently roll out fixes to a subset of users, and you get pulled into that batch once you complain noisily enough.

4

Short version: the app itself is flaky right now, not just your setup, so treat this as a “workaround + backup-plan” situation rather than hunting only for a magical phone tweak.

A few angles that @chasseurdetoiles and @voyageurdubois did not fully dig into:

1. Separate “account issue” from “device issue”

They mentioned trying another device, but take it one step further:

  • Log out of Testbook on all devices.
  • Log in on a completely different network + different device (friend’s phone, office WiFi, etc.).
  • Create a fresh dummy account on that device just to run 1–2 free quizzes.

If your main account keeps crashing on quiz load but the dummy runs fine on the same phone, that suggests some corrupted server-side state for your profile (old test sessions, bugged bookmarks, etc.). Mention this explicitly in your ticket. That pushes it from “user device problem” to “account-specific bug” in their queue.

2. Stop auto-restoring data inside Testbook itself

Even if you clear system-level data, Testbook can still pull its own config from cloud:

  • Inside the app, if there is any setting like “sync settings” or “restore progress,” temporarily disable it.
  • After that, clear data again and log in.
    This sometimes avoids pulling back the exact broken combination of filters / test settings that triggers crashes.

3. Kill “overlay” features that cause UI crashes

Not only cleaners or boosters, but also:

  • System-wide dark mode forced on apps.
  • Third-party blue light filters, bubble notifiers, floating widgets.
  • Screen recorder overlays that draw on top of Testbook.

Some quiz UIs and WebView content hate overlays and simply die when the question panel tries to render. For a couple of sessions, disable those and run a full mock to see if stability improves.

4. Local offline backup of your attempt flow

Since this is affecting your schedule:

  • Before starting a long mock in the Testbook App, keep a local section plan ready in a note app:
    • Section order
    • Time you will switch sections
    • Target number of questions
  • If the app crashes mid-test, immediately switch to solving questions from PDFs / books for the remaining time.
    The idea is to preserve the “test environment” habit even when Testbook fails, so exam temperament does not depend on one app.

5. Use Testbook only for the “evaluation layer”

A different tactic:

  • Solve from PDFs or another platform under timed conditions.
  • Then enter the same answers quickly into the Testbook mock only once just to get analytics, topic-wise breakup, etc.

That way you are not exposed to crashes for the whole 60–120 minutes, only for a short “marking phase.” Less chance the app ruins your day, while you still benefit from its analysis.

6. Hard disagree with constant version hopping

Rolling back and forth between versions (as suggested) is fine for debugging, but for daily prep it can waste time and introduce new bugs or data inconsistencies. I would:

  • Lock into one version that feels at least semi stable on your phone.
  • Stick with it for a week of serious prep instead of updating every time a new build appears.
    Only change if Testbook’s changelog or support explicitly mentions fixes related to quizzes / mocks.

7. Treat peak hour lag as a planning variable

If you see patterns like “evening mocks always crash around result screen” then:

  • Shift serious full-length mocks to early morning or late night.
  • Keep lighter topic tests or revision for peak hours when the app is more likely to fail.

That keeps your main exam-replica sessions safe from server-side chaos.

8. Quick comparison & context

You already have solid tactical advice from @chasseurdetoiles (phone-level fixes) and @voyageurdubois (WebView, older builds, logging). Both are useful, but neither fully addresses the bigger issue: you should not let the Testbook App single-handedly control your study rhythm.

Treat it as one tool among several. Pros are structured mocks, analytics and exam-like interface. Cons are instability, dependency on WebView and occasional update bugs that wreck your schedule.

Use it where it is strongest, but design your timetable so that if it crashes 3 times in a row, your study day still runs almost as planned.