Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

M3 MacBook Pro shows black screen after exiting apps on 27.0 (Golden Gate)

I recently upgraded my M3 MacBook Pro to 27.0 (Golden Gate). I have noticed one bug that has consistently appeared since that time. Whenever I exit an app, or even a game in Steam, I then see a black screen. No wallpaper. I need to move my cursor to the bottom of the screen to bring up the Dock. When I click on Finder, the expected display then appears. It's not a major problem, but it is annoying! Is there some setting in 27.0 that would correct this problem, or do I look elsewhere?


Thanks for your help!

2 replies

There have been many issues reported with exiting Full Screen apps, Mission Control and Spaces on macOS 27 Golden Gate, especially regarding the way Full Screen apps and app switching are handled. Some have been resolved by identifying and removing incompatible 3rd party extensions, others are bona fide bugs. 

 

See if the problem is present when you boot in safe mode. That process performs some system cleanup and clears caches, and also disables 3rd party extensions that may cause problems.

 

Start up your Mac in safe mode - Apple Support

 

If that does not correct the issue, test in a new user account. A newly-created user account will have all settings at default, and if the issue does not occur in that new account then it provides guidance on what may need to be changed to correct the issue.

 

Add a user or group on Mac - Apple Support

 

Once the testing is complete, the new account can easily be deleted.

 

Delete a user or group on Mac – Apple Support

 

Those steps will help to isolate the problem.

 

It might help to download and run EtreCheck, written by a long-time forum member. The free version is fine. Post the full report using the Additional Text button. No personal information is revealed. 



If the issue persists in safe mode and a new user account, that suggests that it's a bug that Apple needs to address. Bugs can be reported to Apple here:

Feedback - macOS - Apple

 

Reporting issues like this to Apple is the only way to get them fixed. They do prioritize bugs based on frequency of reports, so the more people who report it, the faster it will be addressed.

The 27.0.1 update fixed this problem for me!