Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

signingReport is not listed in the Gradle tool window

ErrorsigningReport is not listed under Tasks > android in the Gradle tool window

Short answer

Android Studio can skip building the Gradle task list during sync to speed it up, and then the Gradle panel shows no tasks, signingReport included. Clear the Experimental setting that skips it and sync again. If you only need the SHA-1 now, run ./gradlew signingReport from the project root.

  • Applies to Android Studio current stable, Android Gradle Plugin 8.x, Gradle 8.x and 9.x, Windows 11, macOS 26, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Run the task from the terminal. If it prints a report, your project is fine and only the IDE's task list is missing.

    # macOS, Linux, Windows PowerShell
    ./gradlew signingReport
    # Windows Command Prompt
    gradlew signingReport
  2. 2Match what you see, then jump to its fix

    1. 1Under the Gradle tool window, the Tasks node is empty or missing for every module, not just for signingReport.The IDE skips building the Gradle task list during syncFix
    2. 2Other tasks appear, but you opened the root project entry or a library module.You are looking under the wrong nodeFix

What does the error look like?

  • signingReport is not listed under Tasks > android in the Gradle tool window

Cause 1 of 2

The IDE skips building the Gradle task list during sync

1Check

Open the Experimental page of the settings. Android Studio 4.2 added a sync option that leaves the task list empty, and the Android docs say to clear checkboxes that limit the task list.

File > Settings > Experimental            (Windows, Linux)
Android Studio > Settings > Experimental  (macOS)

2Fix

Uncheck Do not build Gradle task list during Gradle sync, apply, then sync the project again.

Uncheck: Do not build Gradle task list during Gradle sync
File > Sync Project with Gradle Files

3Verify

Tasks > android now lists signingReport.

View > Tool Windows > Gradle > YourApp > Tasks > android > signingReport

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 2

You are looking under the wrong node

1Check

Android's signing guide puts the task under your app module, in Tasks, then android.

./gradlew :app:tasks --all | grep -i signingReport

2Fix

Expand the application module (named app in a default project) and open Tasks, then android. Run the task from there, or call it for that module in the terminal.

./gradlew :app:signingReport

3Verify

The report appears in the lower panel; the line starting with Store gives the debug keystore location.

./gradlew :app:signingReport

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Leave the Experimental task-list option off in projects where you often run Gradle tasks from the IDE.
  • Keep a note of ./gradlew :app:signingReport for CI or machines where the panel is not set up.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

adb tcpip 5555 fails because no device is found

adb: more than one device/emulator

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.