Operating System: macOS Monterey v12.1
Illustrator version: 26.1

Steps:
1. Open .ai file or .svg file in Illustrator that uses a gradient
2. Export as SVG with the following settings (see attached screenshot):
- Styling: Presentation attributes
- Font: SVG
- Images: Preserve
- Object IDs: Unique
- Decimal 2
- Minify: yes
- Responsive: yes

Expected Result:
- The SVG elements use the "fill", "stroke", etc attributes directly
- No <style> tag
- No inline style attributes in the SVG elements
- Object IDs are random strings (uuid)
- SVG shouldn't have the <?xml starting tag

Actual Result:
- Object IDs are not random, it' using "a, b, c, d, ..." as the IDs - similar pattern to what Object IDs = Minimal would look like
- There is no styling applied at all
- When opening the file in Chrome, the styling is lost and most elements appear black

This is an issue because it conflicts with other elements on the web page that the SVG will be displayed on

Description:
When I run Export for Screens via ExtendScript, it slows down and looks frozen. The rainbow cursor will appear.

It actually works, and will finish if I wait long enough. It seems to take about 10 times longer than running it manually from the GUI.

This is especially noticeable when exporting JPEGs. If the image to be exported is large to some extent, it will hardly progress after the progress bar reaches about 99%. CPU usage will be around 100%.
Example: When exporting 8 1700x1000px artboards at 300ppi, it takes 157.636 seconds (the weight of each JPEG is 2.9MB).

If I manually export the same conditions from the GUI, it will finish immediately.
Example: When exporting 8 1700x1000px artboards at 300ppi, it takes about 2 seconds (the weight of each JPEG is 1.7MB).

PNG24 is slower than manual, but it doesn't affect as much as JPEG. The CPU usage was around 160%.
Example: When exporting 8 1700x1000px artboards at 300ppi, it takes 39.376 seconds.

It happens under the following conditions.
• At least Illustrator 2020-2022 (24.3.0-26.0.2)
• At least 2 environments of macOS Monterey 12.0.1 (Apple Silicon) / Big Sur 11.6 (Apple Silicon)
• At least two models of MacBook Air (Apple Silicon, 16GB memory) / iMac (Apple Silicon, memory unknown)
• Run via ExtendScript Document.exportForScreens
• Option JPG 100,300ppi (artboard size is 1700x1000px)
• Include transparency in artboard

It doesn't happen under the following conditions, or the delay is not so noticeable.
• When executed manually from the GUI
• When the option is set to JPG 100, 72ppi
• When the option is set to PNG24, 300ppi
• When removing the transparency from the artboard

The following items do not seem to have much effect.
• Whether to start Illustrator with Rosetta. Rosetta makes it even slower

Expected behavior:
When I run Export for Screens via ExtendScript, it works as fast as I do via the GUI.

Document:
Attachment
• sample.ai (ai file used for export)
• exportForScreens.txt (script to execute. Please change the extension to jsx)

Movie
https://youtu.be/JNYN2ajyVKY

=== Japanese from here on ===

ExtendScript経由のスクリーン用に書き出しが遅く，固まる

説明：
ExtendScript経由で［スクリーン用に書き出し］を実行すると動作が遅くなり，レインボーカーソルが出て固まったように見えます。実際は動いていて長い時間待てば終わるものの，GUIから手動で実行するのと比べると10倍ほど時間がかかるようです。

JPEGを書き出すときに顕著です。書き出す画像がある程度大きいと，プログレスバーが99%くらいになった後ほとんど進みません。CPU使用率は100%前後になります。
例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は157.636秒（できたJPEGの重さは1点につき2.9MB）

同じ条件の書き出しをGUIから手動で実行すると，すぐに終わります。
例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は2秒くらい（できたJPEGの重さは1点につき1.7MB）

PNG24は手動よりは遅いですが，JPEG程大きく影響しません。CPU使用率は160%前後でした。
例：1700x1000pxのアートボード8枚を300ppiで書き出すとき，かかる時間は39.376秒

次の条件で起こります。
• 少なくともIllustrator 2020〜2022(24.3.0〜26.0.2)
• 少なくともmacOS Monterey 12.0.1(Apple Silicon) / Big Sur 11.6(Apple Silicon)の2環境
• 少なくともMacBook Air(Apple Silicon, 16GBメモリ) / iMac(Apple Silicon, メモリ不明)の2機種
• ExtendScriptのDocument.exportForScreens経由で実行
• オプションJPG 100，300ppi(アートボードサイズは1700x1000px)
• アートボードに透明効果を含む

次の条件では起こらないか，遅延がさほど気になりません。
• GUIから手動で実行したとき
• オプションをJPG 100，72ppiにしたとき
• オプションをPNG24，300ppiにしたとき
• アートボードから透明効果を削除したとき

次の項目はあまり影響しないようです。
• IllustratorをRosettaで起動するかどうか。Rosettaにしたらさらに遅くなる

期待する動作：
ExtendScript経由で［スクリーン用に書き出し］を実行したとき，GUI経由で行うのと同じくらい速く動きます。

資料：
添付ファイル
• sample.ai（書き出しに使うaiファイル）
• exportForScreens.txt（実行するスクリプト。拡張子をjsxに変更してください）

動画
https://youtu.be/JNYN2ajyVKY

1. Rename the .txt file to .aia
2. Load this file as a set into Actions panel
3. Open the .ai document (make sure that linked .tif file is loaded)
4. Export the file using Save For Web command. Set size to 200% and save the result as 1.jpg
5. Run the 'Test' action form the loaded set. Save the image as 2.jpg

Compare both files. 2.jpg is looking more red than 1.jpg
No profiles attached to JPGs.

1. Run the action again
2. While the S4W dialog is open, go to Optimize menu (hamburger button in top right corner) and disable 'Convert to sRGB' option

The generated result gets less red (toggle it back and forth to see the difference).

1. Cancel the dialog and run S4W command directly again
2. Toggle the same option again

No difference happen with the red tint, the image stays the same.

It feels like some double conversion happens.
Yes, S4W is legacy, but this is how you called it. It is widely used still. This needs to be fixed.

Hi,

I have recently stumbled upon a random issue with exporting SVGs from Illustrator (Desktop). I am recycling some previously used assets that I know work fine and are fully compatible with Articulate Rise (the eLearning tool I import the SVGs to).

For some reason, within the last week or so, something has changed. Now when I try to import my SVGs to Articulate, I get an error saying the file type is invalid. Having investigated this with the Articulate support team, we discovered that during the export process, Illustrator is adding a random invalid character (this one (`)).

See attached images for reference.

I can edit the styling using SVG viewer, but it's slowing down our output immensely and I'm not sure what has changed? I know for a fact these images work fine in the current courses they sit in.

Note: If I ungroup the assets on the banner image, and export them as SVGs, they all import fine and don't have the angled apostrophe. If I group them together, however, the apostrophe appears! The obvious solution would be to ungroup and collect as a single asset, which I've tested and unfortunately, this still presents the same issue. I've also tested grouping newly created assets together there are no issues.

Hopefully, someone out there can help out with this!

Thanks in advance,
Steph

I updated to Adobe Illustrator V26.0.3 today. And now AIT file opens as AIT file.

It should open as a new AI file when opening from AIT file since it is a template.

FYI, I am using MacBook Pro M1 2020, and MacOS Motley V.12.1.

Doen anyone getting the same problem?

---Additional Comment---

After testing, I found out that this is happening when I open an AIT file from my One Drive folder.

When I copied AIT file on my desktop, then it opened as a new AI file as it was used be.

For more details, I am using One Drive App (V.22.002.0103.0004) which I recently updated on Jan-26-2022.