Android Studio Mac Bounces But Does Not Open | Fix Fast

You click the icon. It hops in the Dock a few times. Then nothing. No window, no error, just silence. When android studio mac bounces but does not open, it hits problems, then quits before the UI shows.

The good news is that this pattern is often repairable without wiping your projects. Most of the time you’re dealing with one of three things: a damaged cache, a bad setting carried over from another version, or a macOS rule blocking the app from launching.

What The Bounce-Then-Quit Pattern Means

On macOS, the bouncing icon is the launch sequence. If it stops and the app never appears, Android Studio likely crashed during early startup. That can happen before it can show a dialog, which is why it feels like “nothing happened.”

Startup crashes tend to land in a few buckets. Some are about files on disk, like a cache entry that can’t be read. Some are about the bundled Java runtime not matching what a plugin expects. Others are about macOS blocking a component the app wants to load.

Start With Two No-Risk Checks

• Wait 30 seconds — On the first run after an update, macOS can verify the app and it can feel frozen even when it is working.
• Try one fresh launch — Quit it from the Dock if it’s still bouncing, then open it again so you can tell a one-off stall from a repeat crash.

Confirm It Fully Quit

• Open Activity Monitor — Search for “Android Studio”, “java”, or “studio”. If a process is stuck, the app may be hung, not closed.
• Force quit stuck processes — Select the process and quit it, then retry the launch so you start from a clean slate.

What You See	Likely Cause	First Move
Dock icon bounces, then vanishes	Crash during early startup	Reset caches and settings folders
Dock icon keeps bouncing for minutes	Hang during indexing or a blocked prompt	Check Activity Monitor, then try logs
Android Studio shows once, then never again	Corrupt config after update	Start with a clean config directory

Android Studio Mac Bounces But Does Not Open

If you’ve hit this loop more than once, skip the guesswork and do a clean reset of the folders Android Studio rebuilds on launch. Your projects live somewhere else, so deleting caches and settings does not delete your code. It does reset UI choices, installed plugins, and some IDE preferences.

Before you delete anything, close Android Studio and stop any lingering java or studio processes in Activity Monitor. That prevents half-written files and speeds up the next start.

Reset The Cache Folders

• Open Finder’s Go To Folder — Press Shift + Command + G so you can jump straight to a path.
• Delete the caches directory — Go to ~/Library/Caches/Google/AndroidStudio* and move the matching folder to Trash.
• Delete the logs directory — Go to ~/Library/Logs/Google/AndroidStudio* and move the matching folder to Trash.

Reset The Settings Directory

This is the folder that most often blocks startup after a version change. It holds settings, plugins, and state. Android Studio will recreate it when it starts again.

• Open Finder’s Go To Folder — Press Shift + Command + G again.
• Remove the settings folder — Go to ~/Library/Application Support/Google/AndroidStudio* and move the versioned folder to Trash.
• Keep a backup if you want — Rename the folder with “-old” instead of deleting it, so you can copy back pieces later.

Launch Once With No Projects

• Open Android Studio — Let it build fresh folders and show the startup screen.
• Skip opening a big project — Create a tiny test project first so you can confirm the IDE itself is stable.
• Add plugins slowly — If a plugin caused the crash, adding them back one by one makes the culprit obvious.

If the app opens after this reset, you’re done. If it still bounces then quits, the next step is to check for a version conflict or a Java runtime issue.

Android Studio On Mac Bounces Then Quits After Updates

One common trap is installing a newer build, then installing an older build, then trying to open the older one. The older app may read a newer cache format and fail during startup. This is most visible when you try a Canary build, decide you don’t like it, then go back to Stable.

Pick One Channel And Clean The Rest

• Decide which build you want — Keep one stable app bundle in /Applications, not a pile of duplicates.
• Remove leftovers from older builds — Delete versioned AndroidStudio folders in Caches, Logs, and the settings directory.
• Reopen the chosen build — Let it recreate its folders cleanly before you open any large project.

Use A Launcher That Keeps Versions Separate

If you test different channels often, JetBrains Toolbox can install builds side by side while keeping your IDE folders cleaner. That reduces cross-version collisions and makes it easier to uninstall a build without leaving debris behind.

Fixes That Target Java And Gradle Startup

Android Studio ships with a bundled Java runtime, so you don’t need a separate Java install for the IDE to run. Still, local Java settings can clash with what the IDE expects, mainly when you’ve set custom JVM options or you’ve changed Gradle’s JDK location in a prior install.

Remove Custom JVM Options That Break Launch

• Search for vmoptions files — In Finder, search your home Library for studio.vmoptions and idea.vmoptions.
• Rename the custom file — Add “-old” to the filename so Android Studio falls back to defaults.
• Retry the launch — If it opens, add options back one at a time later.

Test A Clean Gradle JDK Choice

If Android Studio opens but crashes when you open a project, Gradle can be the trigger. A mismatched JDK path can kill the sync phase and take the IDE down with it on some setups.

• Open a tiny new project — Use an empty template so sync is simple.
• Set Gradle JDK to the embedded runtime — In Settings, pick the embedded JDK that ships with Android Studio.
• Restart the IDE — A full restart ensures the new JDK choice is used.

Check For GPU Rendering Crashes

On some Macs, UI rendering can crash the IDE on launch. If you suspect that, a JVM flag can disable Metal rendering. This is not a first pick, but it can rescue older hardware.

-Dsun.java2d.metal=false

• Add the flag carefully — Put it in your custom vmoptions file only after you’ve tried a clean reset.
• Remove it later — Once the IDE is stable, test without it so you don’t keep a workaround you no longer need.

MacOS Security And Permission Fixes

macOS can block apps that were downloaded, moved, or unpacked in a way Gatekeeper doesn’t like. When that happens, you may see the icon bounce then quit, or you may get a one-time warning that you clicked past and forgot.

Clear Quarantine Flags On The App Bundle

• Move Android Studio to Applications — Don’t run it from Downloads or a mounted disk image.
• Run a quarantine clear command — In Terminal, run the command below on the app bundle path.

xattr -dr com.apple.quarantine "/Applications/Android Studio.app"

Grant File Access If A Prompt Was Missed

• Open Privacy & Security — In System Settings, check for a blocked app notice and allow it.
• Allow access to needed folders — If you use projects outside your home folder, grant Android Studio access when macOS asks.
• Retry the launch — A restart after granting access can help the permission take effect.

Check Disk Space And File Ownership

• Free a few gigabytes — Low disk space can break startup writes and cause early exits.
• Fix folder permissions — If the Google directories under your Library have odd ownership, rename them and let the IDE rebuild them.

Clean Reinstall Without Losing Your Work

If you still can’t get a window, treat this like a clean install. Remove the app, delete the folders it rebuilds, then install fresh. This avoids dragging a broken config into the new copy.

Remove The App And All Rebuildable Folders

• Delete the app bundle — Remove Android Studio from /Applications.
• Delete caches and logs — Remove the AndroidStudio folders in Caches and Logs under your home Library.
• Delete the settings folder — Remove the versioned AndroidStudio folder in ~/Library/Application Support/Google/.

Install Fresh From The Official Download

• Download the current stable build — Grab it from the Android Developers site so you get the right package for your Mac.
• Install with a simple drag — Copy the app into /Applications, then launch it once before adding plugins.
• Let the first run finish — The first launch can take time while it sets up the Android SDK and indexes.

When It Still Won’t Open

If the Dock bounce persists after a clean reinstall, pull the log and read the last lines. The log usually names the failing component, which tells you what to fix next.

• Open the log folder — Go to ~/Library/Logs/Google/AndroidStudio*/idea.log and open idea.log in a text editor.
• Scan for the first error — Look for lines tagged ERROR near the end, then note the library or plugin name mentioned.
• Try one change at a time — Fix the named item, relaunch, then recheck the log so you don’t chase multiple problems at once.

If you’re still stuck, you can run Android Studio from Terminal so the crash output is visible. Open the app bundle, go into Contents/MacOS, then run the launcher binary from there. This can show missing libraries, blocked components, or a Java crash that never surfaced on screen.

Disk space and permissions can trigger silent exits too. Make sure you have a few gigabytes free on your startup disk, then restart your Mac. Next, try launching Android Studio from a fresh macOS user account. If it opens there, the issue sits in your user files. You can also boot into macOS Safe Mode once, log in, then reboot normally. That clears some cached launch services entries. If you use JetBrains Toolbox, remove and reinstall from there.

One last check is to confirm your macOS and Android Studio builds match your hardware. Apple silicon Macs want the current Apple silicon build. Intel Macs want the Intel build. A mismatch can lead to weird launch behavior, especially if you moved the app between machines.

If you found yourself searching for “android studio mac bounces but does not open” again after fixing it once, save time by keeping only one installed channel, updating in place, and doing a quick cache reset when you switch builds. That habit prevents most repeat launch failures.