Font changes from the current one to the previously used while typing
I'm working on a document in which I used Avenir font, but for the most I use Myriad Pro. When I click with the Type tool I see in the character box I'm with the default font (Myriad Pro) and start typing. Then noticed I'm now in Avenir font!
This bug is brand new with the latest update (29.1), I didn't add any issue of that type before.
I'm on Windows 11 PC Core i7-13700 32 Go of RAM
The team plans to push the fix from the Beta build into the main one in first week of January — hooray!
The current workaround in 29.1 is to disable Missing Glyph Protection option in Preferences > Type.
-
onenower commented
Will the punctuation squeezing issue also be resolved in the next version? Currently unable to use version 29.1, temporarily returning to the old version.
-
Henri Le Forestier commented
I have a revolutionary idea for that: why don't you test basic features before releasing?
-
To add to the status update — the fix that was pushed into Beta happened fast, and the team can update Betas often... but the schedule for the GA (Global Availability) releases is rather strict. Hope this incident changes something in the way how these are handled.
Thank you all so much for coming here at UserVoice and reporting this problem — and others. Never hesitate to come here or at forums and log bugs and ask for features or changes!
I wish for all of us less bugs and more meaningful changes in the coming year. -
Pratiksha Parad commented
i have set the primary character& paragraph style with qanelas regular. However, everytime i copy the text box and edit it, it either takes poppins or Qanelas thin. I have tried changing default fonts from myriad pro to qanelas regular as well. this is a bug.
-
Tyler Fonville commented
When I'm updating some copy, the font doesn't assume the current style, it reverts to the originally used font. The only way to fix this is by starting a new line somewhere else using the font I need.
-
iconwerk commented
I have the same issue. Adobe, please test every release candidate before you publish it. It’s a lot of work to find a work-around for every new bug that comes with your bugfix updates. :-)
-
Robert Blosser commented
Adobe is probably the only company that has successfully figured out how to get their beta testers (paying customers) to pay Adobe to beta test their failing products. These apps continue to degrade with bugs that make any professional user lose money and time using this broken product. This instance is only one of many bugs that is frustrating Adobe's core audience. On top of that their customers are spending additional time communicating obvious bugs to the Adobe team! I really hope Adobe snaps itself out of this too big to fail mentality. As a professional user of these apps for over 30 years I remember how these ground breaking tools used to work and benefit the industry. Go back to the mentality of when software was released on CD and thoroughly tested since it would cost the company dearly to produce garbage on that platform. These days it's too easy to release garbage and let your user base figure out your problems! You're better than this Adobe!
-
Matthew Brindle commented
@Ngân Trương Thanks! Appreciate it.
Wonder how on earth this version got out the door, isn't there basic user testing for versions on at least the key basic tools.
-
Raggedy Man commented
Same issue.. So frustrating. Change one letter and it reverts it back the previous one.
-
Ngân Trương commented
@Matthew Brindle
I think ver 28.7.3 is the most stable, I reverted back and everything's nice again -
BC_大森 commented
イラストレータCC 2025にしてから、
逆に面倒で非効率になった機能があります。フォントの設定について。
たとえば「AIのGPT」と打ち、UD-新ゴシックに設定します。
ここに文字の訂正をし、「AIのチャットGPT」と打ちなおすと、
打ち直して加えた「チャット」の文字だけデフォルトフォント(私の場合は小塚ゴシック)で
打たれ、わざわざフォントを設定しなければなりません。今までであれば一度設定したフォントの文字列は、テキストを変更してもそのまま
フォントの設定は活きたままでした。文字を打ち直すたびにフォントを設定するのは、
その手間が重なっていくと膨大な時間のロスです。なぜこんなふうなバージョンアップの進化をさせたのでしょうか?
-
Kirudub commented
Same issue.
Serious PITA to have to manually change the typeface on a single character when editing type! Been happening since the update.
For what it's worth, I already had "Missing Glyph protection" checked in prefs, and I still got the bug.
Luckily I haven't had to work on a wall of text yet, but it's just a matter of time.
AI: 29.1
OS: Mac Sonoma 14.7.2
System: Mac Studio M2 64GB RAM
Edit: D'oh, reading comprehension fail, I'll try UN-checking the Glyph protection box. SMH.
-
Matthew Brindle commented
What date is next stable release? And what version can I revert to where this does not happen? It's destroying timelines + workflow.
-
Cher P commented
This just started for me yesterday. The workaround resolved the issue, but I am anxious for a fix. I hope the fix is noted in the update so I can remember to turn the workaround off.
I am running:
AI: 29.1
Mac OS: Sonoma 14.7.2 (my company controls updates)
MBP: M2 Max 64GB RAM -
Adrian Jean commented
Same on:
AI: 29.1
Mac OS: Sequoia 15.1.1
MBP: M4 64GB RAMHappens on our M1 machines as well.
It's brutal. Another productivity killer. -
Susana Ante González commented
I have the same issue in AI 2025, 29.1. It's a nightmare…
-
Henri Le Forestier commented
Just to clarify, the workaround was found by Adobe, I was just upping it as I saw many of you blocked on the issue (and the workaround was hidden by many comments)
Happy it helped :) -
Jon commented
Confirming that Henri Le Forestier's workaround of — Preferences (Settings) > Type > Enable Missing Glyph Protection > uncheck the box — totally worked for me!
-
Pedro commented
I'm having an issue, when I switch a font the software glitches while texting more stuff, it mixes the new font selected and the previous one.
-
Marc commented
Bravo Catalyst Creative and Henri! Nice to see the Adobe user community come together and workaround Adobe's carelessness together.