same here, do not know why, but sometimes all is gray and I need to quit Indesign to make it work again

Samsung 32” 4K via DisplayPort. MacBook Poro 16” M2, clambhelled. Latest developer beta of Sequoia, it it’s been happening with official releases. Because the Samsung is 4K I’m using the 3008 pixel setting for a better interface size. It’s a ratio that doesn’t slow down the OS.

I would boot ID, work on a project that might take a few hours and a variety of other apps and everything would be fine. But leaving the app open but not active for hours including various amounts of the Mac sleeping would without fail cause ID to show a blank screen even though there is still a file open. I can blindly select things but nothing shows, and i can see the art if i select CPU View, but it all goes blank the second i select GPU again. Only recourse is to quit and reboot the app.

There are many people on the ID Forum mentioning the very same issue, one was an IT guy who says all of their ID designers have the issue. It’s a thing.

For the last 3 or 4 updates (current is 19.5.0.85), in MacOS running the latest versions, ID presents with a blank screen when the app is open but not active for a period of time. This is absolutely a continuing lack of ability of Adobe to work with Apple silicon, namely the video RAM, since the solution is to switch to CPU view, which is a no. Otherwise the app has to be quit and rebooted. Every single time that this happens, which is every single time it's left unattended. Everyone I know that uses ID has this problem.

Also: disabling GPU preview brings the pages back.

I just recorded a video to show it. I was previously using a external monitor, and after unplugging, Indesign wouldn't display any document pages in the working area.

I had two very different documents open, one was long with many pages filled with text and heavy images, one containing only a few pages with normal images. Both behaved the same.

I noticed that the document's pages desapear after I change the display I'm working on.

I started working in a 13" macbook pro and later plugged a dell monitor. When I pushed the app to the bigger display, Indesign stoped showing the pages in the main working area. I closed the doc and opened it again, and it would display the pages normally in the dell monitor.

The same happens the other way around if I start working on the dell monitor and later change to the laptop.

Version of Adobe InDesign, InCopy or InDesign Server: Indesign 17.2
Steps to reproduce the issues: Start a document in one display and then try to go on using it in another display.
Expected result: Change displays, adjust the window size and go on working normally.
Actual result: Indesign hides all document pages in the main working area. They are still visible in the pages window.
Test file, screenshot, video or GIF capturing the issue (optional): attached.

After waking up the computer, it happens almost every time on my Apple Studio Display connected to my Mac mini M1.

Same problem. After sleep (sometimes) documents on external monitors are greyed out. Switching from GPU to CPU helps, but still greyed out if switching back. Using v19.0.1 on a MacBook Pro M1, Ventura 13.5.1

Hi,
Do you have any progress on this issue?
Thanks.

I face almost the same bug on InDesign v19 on Sonoma after changing the display profile of an Apple Studio Display while running InDesign, the inner part of the document window becomes gray or pink or green and nothing else appears, the document is no longer visible.

This same issue, I believe, has been reported in the past. Since I upgraded to 19.0 version, this bug appears most times. I have uninstalled and then reinstalled Indesign, and still happens.

Best Regards
David

Correction. This happens when the computer wakes up from sleep and maximizes the window.

Note: When the computer is turned on, everything looks fine and everything described above happens when the InDesign is maximized.

Just closing and reopening the document will help. Nothing else. It's annoying when the document is not saved and therefore needs to be saved before closing, but you don't know what you are actually saving. It then accumulates versions unnecessarily.