Just updated to ID 2020 15.1 and found a bug which makes the program unusable forcing me to immediately downgrade.
When I open on of my ID documents created in previous version of ID, all of my defined text variables as well as page numbers are corrupted and replaced by the "ss" text. Changing the style has no effect. I can create page number based on the 'Basic Paragraph' style but when i choose any other previously created style, the number changes to 'ss'.
Even the variable field preview shows 'ss' text instead of variable name.
The same document opens in ID 2020 15.0.3 without any problems.

To place a graphicItem with text wrap, it is not an object-based indent like 2020, but a text frame-based indent before 2019.

1 Version
16.0.1(macOS10.14/10.15.6)

2 Steps to reproduce the issues
1. Make TextFrame. To places graphicItem above the textFrame and set text wrap.
2. The indent set in the textFrame does not take effect for the object for which wrap text is set like before 2019.

3 Expected result
Indent set in the textFrame does take effect for the object for which wrap text is set like 2020.
Please refer below Community article.
https://community.adobe.com/t5/indesignフォーラム/indesign2020ではできていた回り込み時のインデント設定の維持が2021ではなくなっている/m-p/11677071

4 Actual result
The indent set in the textFrame does not take effect for the object for which text wrap is set like before 2019.

Problem Description:
Querying navigation points inside a movie trigger errors from InDesign 16.

Steps to Reproduce:
1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

var btn = app.activeDocument.buttons[0];
var beh = btn.behaviors[0];
var mov = beh.movieItem;
var navPts = mov.navigationPoints;
try{

alert(navPts.length); /*doesn't exist*/

}catch(err) { alert([err,err.line])}

try{

alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */

}catch(err) { alert([err,err.line])}

alert(navPts.everyItem().getElements().length); /incorrectly says zero, when there are 2 navigation points/

Actual Result:
Each produces two separate errors.

Expected Result::
Both should be valid queries.

Any Workarounds:

No. Expected functionality is simply missing.

movie.navigationPoints.everyItem().getElements().length at least doesn't produce an error, but it also doesn't include navigation points.

This feature was added back to InDesign, but the scripting of it was neglected. I've filed a bug in prerelease as well. Posting here so others are aware.

WHAT THE FONT!?!

Our publishing company recently ran the InDesign update (to 15.0.2) and have discovered some major font issues. I have narrowed it down to InDesign 15.0.2, macOS Catalina 10.15.3, and Suitcase Fusion 21.0.0. I actually don't think Suitcase has too much to do with this, because the problem occurred after the InDesign update, but it's our font management software so I'm including it. Basically it appears system fonts have become problematic with InDesign. Packaged files are suddenly showing up with lots of the dreaded pink. I have tested about everything I can. I even created some very simple type only files that are having system font issues as well. Sometimes the document will open ok and the fonts will appear fine. Then when I go to export, the system fonts turn pink. Sometimes the file can't open the fonts at all and they start out and remain highlighted pink. Other times it will open but them shut off a few seconds later. It's only happening with system fonts. I have included screen shots for reference. I hope this issue can be fixed asap because it's font chaos over here! Thank you.

When exporting a PDF with the Japanese version of InDesign for Mac, the Osaka font is used for the characters in the page information. If there are voiced or semi-voiced sound marks of Japanese characters in the file name, an error will be displayed and the characters will be garbled because Osaka does not support those characters.

1. Name the indd file "だじづでど.indd".


2. Export the PDF.


3. An error is displayed and the file name of the page information is garbled.

Osaka is no longer a very old font on the Mac. Don't use Osaka now.

Use a font that supports semi-voiced sound marks to prevent errors. Illustrator already uses KozGoPr6N-Regular to prevent errors.

Japanese:
PDFのページ情報にOsakaフォントを使わないでください

日本語版のMac版InDesignでPDFを書き出すと、ページ情報の文字にOsakaフォントが使われます。ファイル名に日本語の文字の濁音や半濁点があると、Osakaがそれらの文字に非対応なので、エラーが表示され、文字化けします。

1. inddのファイル名を「だじづでど.indd」にします。


2. PDFを書き出します。


3. エラーが表示され、ページ情報のファイル名が文字化けします。

MacではもはやOsakaはとても古いフォントです。今はOsakaを使わないでください。

半濁点に対応したフォントにして、エラーを防いでください。IllustratorはKozGoPr6N-Regularを使ってすでにエラーを防いでいます。

Version : Adobe InDesign 2021(ver.16.0.1 ja_JP)
OS : macOS10.15.6

1.Steps to reproduce the issues

1. Open Find/Change Window.

2. Select "文字種変換" and click "Specify attributes to Find" and Select Style button.

3. The selected Style does not shown in "Find Format" area and we can't apply it. However, click the button, we can see selected Style we selected previouse step.

4. The Change Format in "文字種変換" also unavailable.

2.Expected result
The selected style is displayed correctly in Find Style area and is correctly apply.
Also, the replacement style is set correctly in Change Style and replaced as well like InDesign 2021.

1. Actual result
   We can't set Find Format and Change Format options in "文字種変換" in Find/Change window.
   Test file, screenshot, video or GIF capturing the issue (optional)

Japanese.
1.問題を再現する手順

 1.検索と置換ウィンドウを開きます。

 2.「文字種変換」を選択し、「検索形式」をクリックして、「検索する属性を指定」ボタンをクリックします。

 3.選択したスタイルが検索形式のエリアに表示されず、適用できません。ただし、再度「検索する属性を指定」ボタンをクリックすると、前の手順で選択したスタイルが表示されます。

 4.「置換形式」のスタイルも利用できません。

2.期待される結果
InDesign2021と同様に、選択したスタイルが「検索形式」エリアに正しく表示され、検索対象として正しく機能する。また、「置換形式」も同様に設定できて正しく置換が行える。

3.実際の結果
「検索と置換」ウィンドウの「文字種変換」で「フォーマットの検索」および「フォーマットの変更」オプションを設定することはできません。

Please refer below,
https://community.adobe.com/t5/indesignフォーラム/文字種変換で検索形式の指定ができません/m-p/11695809

Today I have updated to InDesign 15.1 and when I try to export to PDF the application immediately crash.

This happen even I change the type of export (small dimension, print, etc.).

I'm using windows 10 pro ver. 1909 build 18363.836, and Indesign 15.1 x64.

The system start to work but the application crash at 16% of the export.

The problem seems connected with something on the file, because I try to export another project and it work perfectly.

The file was all "green" in the preliminary checks panel.

And I notice that the system crash also using other function, example scrolling the pages list or the links list.

There is something wrong in the new version 15.1 that stops the compiling. Unfortunately no errors appear, only application crash.

Coming back to version 15.0.3 have solved the problem and the file was perfectly exported in PDF.