Need help with toolargetool?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

538 Stars 63 Forks MIT License 100 Commits 11 Opened issues


A tool to help you debug TransactionTooLargeExceptions on Android 7

Services available


Need anything else?

Contributors list

Now in Kotlin!


A tool for debugging

on Android.

"Most underrated solution." - Kedar Paranjape, Jun 7 '18 at 14:26


  1. Include
    as a dependency (you can remove it again once you've debugged your crash):
- Add `maven { url '' }` in your project's `build.gradle`:

  allprojects {
      repositories {
          maven { url '' }
  • Add implementation '[email protected]' in your module's build.gradle:

    dependencies {
        implementation '[email protected]'
        //implementation '[email protected]' // if you don't use AndroidX in your project

  1. Import The package

  2. import;

  3. Add code to start logging during app start, for example in your



  4. Monitor logcat output to see which components are writing substantial data to the transaction buffer and when:

    $ adb logcat -s TooLargeTool

Example logcat output (TODO: improve this example):

   D/TooLargeTool: MainActivity.onSaveInstanceState wrote: [email protected] contains 1 keys and measures 0.6 KB when serialized as a Parcel
                                                                           * android:viewHierarchyState = 0.6 KB

Release process

Note: these instructions will only work if you have the relevant Bintray credentials

  1. Open
  2. Increase all the version numbers.
  3. Make a commit and tag it with
    git tag -a v -m ""
  4. Run
    ./gradlew clean install && ./gradlew bintrayUpload

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.