signingReport is not listed in the Gradle tool window
signingReport is not listed under Tasks > android in the Gradle tool windowShort 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.
Fix it fast
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 signingReport2Match what you see, then jump to its fix
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 Files3Verify
Tasks > android now lists signingReport.
View > Tool Windows > Gradle > YourApp > Tasks > android > signingReportConfirmed by developer.android.com
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 signingReport2Fix
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:signingReport3Verify
The report appears in the lower panel; the line starting with Store gives the debug keystore location.
./gradlew :app:signingReportConfirmed by developer.android.com
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 cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile 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 fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fixMobile apps
The emulator says the GPU driver is unsupported and falls back to software
vulkan-1.dll cannot be found
The emulator picks a graphics mode when it starts.
4 causes, each with a fix