Text disappears when typing in text box

[Elaine5E3A]

I'm getting this issue where when I make any changes to text within a text box, like typing within it, cutting/pasteing, editing, etc. the text disappears. Sometimes it'll come back if I click out of the text box. Sometimes it comes back if I switch between normal and preview mode.

It doesn't happen every time, but often enough to be incredibly annoying.

I'm running:

• Mac OS 11.4
• Macbook Air M1 2020
• InDesign 16.2.1

[ubergreg]

Hi Ashutosh,

1. macOS 11.6, ID 16.4

2. 2020 Mac Mini M1

3. Both when GPU Performance is enabled and disabled

4. The problem persists

4. Every single file that I work on is affected in exactly the same way

5. Unable to locate it for the moment (apologies)

I have an Intel MBP from late 2013 running the latest version of InDesign, and the problem simply doesn't exist on that machine.

[Joel Berggren]

I can't beleive you read these threads and didn't ask for the one spec all the M1 systems have in common, which is 8GB of ram. If you want to replicate the problem simply get any M1 Mac with 8GB of ram running any version of OSX, and any version of M1 InDesign and start using the text tool for 5 minutes. You'll be able to observe this bug at your leisure.

[Scully20]

Thank you!  I read these posts and see the commonality among us all.  How Adobe can't see what we are experiencing is so frustrating.... as if we don't know what we are doing in the program.  It's like someone shutting off the lights in a room and we have to constantly turn them on again to see what we are working on!  ENOUGH ALREADY!!  I'm ready to go back to good old QuarkXPress.  LOL

[virfortisdei]

I have the 8GB M1 Mac Mini and the 16GB version and it's exactly the same on both

[stevem78227445]

I'm running 16GB and still getting it????

[BrizzoAB]

1. Mac OS 10.14.6 and Indesign 16.4
2. Mac Book Pro 15” Retina Late 2013
3. I had a similar problem but with images that didn’t display correctly when I added a shadow or tilted the image or changed the shape to a circle. The images disappeared in the preview mode. Or the frame around the image disappeared when I tilted it. The problem was gone when I turned off the GPU Performance.
4.  (My issue was not with the text.)
5.  I'm not sure wich file to attach...

[jackdesign2000]

Hi Ashutosh,

1. MacOS Monterey 12.0.1 + InDesign 2022 (17.0)

2. MacBook Air (M1, 2020) 

3. Happens in both viewing screens

4. Resetting prefs doesn't work. 

4b. Happens will all of my InDesign files

5. Not sure what you are looking for in preference files, a screen shot of each section? I've never altered these preferences.

I'm not seeing any new revolations for this issue, so I'm replying. Overall my laptop is only a few months old, I didn't have any issue the first month, but now it's every project I work on in InDesign. I just went from BigSur to Monteray, both OS systems had the same issue. As you can see I'm working on the the latest version of InDesign too. It's always up to date. Any help would be appreciated. It's very disruptive to mine and everyone elses work flow.

Thank you!

[jeffhalmos]

Until the InDesign team learns how to work fully with M1, or remove legacy code or whatever is clogging it up, the only way to get past this issue is to turn off and back on the GPU Performance checkbox whenever the issue crops up. I have to do it a few times a day on an M1 mini with 16GB RAM.

The issue is over half a year old regarding M1 Macs, but it goes back to at least 2017 (https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/20408851-indesign-perfo...). So.

[jackdesign2000]

Yep, that's what I do all day long, toggle. So yes, it's a quick fix at least, but still frustrating none-the-less. Thanks for the response. I just wanted to make sure I didn't miss the "fix" yet! 

[jeffhalmos]

IF ONLY!

[roberteblesse]

Ashutosh— Your absence on this thread for the past two months is disgusting. Are you still investigating this issue? How about a progress report. Adobe's lack of response to this issue incomprehensible and reeks of disregard for all us who have been loyal to Adobe over the years. Get with it!

[SteveP56]

I completely agree, Robert. It’s nothing less than a disgrace. Years of support for Adobe from loyal customers and this is their response - or lack of one. Adobe will pay a price on time for this. Meanwhile, Adobe: respond and deal with this chaos. Get a grip on Indesign / M1 chip problem.

Sent from my iPhone

[Dave Creamer of IDEAS]

Disgusting is inappropriate--frustrating would be more apropos. And there was no need to call out Ashutosh directly.

Ashutosh's job description is Senior Technical Support Consultant, who I suspect feeds information to the programmer team(s). These teams generally don't give progress reports (there could be legal implications here)--they just release new updates after testing. 

Get mad at Adobe and/or Apple corporations, but don't make it personal against a single person. 

[roberteblesse]

Cream-Training—I apologize if my use of the word disgusting gave the impression I was criticizing Ashutosh personally. That certainly wasn't my intent and I'm sure he's a fine person and an excellent support consultant. Not to debate semantics, however, he represents Adobe, who so far, has failed to deal with this serious issue. I'm sure this failure has disgusted many people, like myself. To give Ashutosh credit, he's the only Adobe representative who has responded to the issue in the last two months. No one is blaming him, but a multitude of people are mad and frustrated with Adobe over the issue, which unfortunately, that hasn't elicited a response from them in over two months, much less a solution. Adobe's silence portends a disregard for its customers, so even an update that they are still working on the problem would be encouraging.

[marilynn90461272]

1. OS 11.5.2, InDesign 16.2.1

2. MacBook Air M1 2020

3. No idea status of GPU Performance, and I don't care to poke around to do the analysis that Adobe should do.

4. No interest in resetting any preferences. See comment above.

InDesign worked fine until InDesign upgrade, and I have loved it for years. Now text disappears. Now I have to click forever on layers, links, etc., to get a response. The app is generally sluggish. If we were not forced to upgrade, we would not have these problems. I am unbelievably annoyed. 

[Fearless_artist5E5A]

How is your investigation going?

[MandyNauticalia]

Thank you for your suggestions and comments, as of yet this is still not resolved ☹
I’ve tried turning “GPU performance” OFF
And changing “User interface scaling" in Preferences to the smallest

[guido5F9D]

OSX 11.5.1

MacBook Pro 13” M1 2020

Happens with both GPU enabled and disabled.

Resetting TextEdit preferences didn’t work.

Sample of the file doesn’t matter - it happens on all files, all across - either new or old.

Preference files: the link is a bit confusing - I have a lot of cache files in the InDesign caché folder, so I can't help with that.

[Marc5CCB]

What a complete joke this is!!! Adobe are very happy to keep taking people's money every month but when it comes to fixing their glitchy software, you could not give a damn. This problem is massive. Its been around for long enough that the Adobe developers can figure it out and fix it. It is a HUGE problem and is causing your users no end of trouble. What kind of morons are running the show here?

[BobLevine]

Easy does it there! What will you have to say if it turns out to be an Apple bug causing this?

Not saying it is, but we haven't eliminated that from the mix just yet.

[Joel Berggren]

Adobe has already aknowledged in this thread that it is their issue. It's bizarre the amount of misinformation and just plain impossible theories "Adobe Community Professionals" are posting here. I have to assume that title has something to do with using the products, but having zero idea how they are acually programmed.

[jeffhalmos]

Id is the only app that's having this issue. Not just all apps, but other Adobe apps.

[Marc5CCB]

Don't give me that "easy does it" nonsense please. This is very clearly an Adobe issue, as they've previously acknowledged. It's completely unacceptable for them to continue taking money for software that is clearly not up to the task. They treat their customers with contempt so they should expect a fair amount of vitriol in return. They've had PLENTY of time to fix this very major problem. 

[Crystian Cruz]

The fact Adobe assigned two "correct answers" ia actually offensive, after months without solution and lack of feedback. What is the point of having community support if the support we get is this one?

[MadMcGun]

This issue appeared to have been solved in 16.4 but in now back into 17 and 17.1

Please do the same fix you did for 16.4 on the 17 please