SixLabors load error

PDF not generating through bot.
Could not load type 'SixLabors.ImageSharp.Formats.Jpeg.JpegEncodingColor' ... SixLabors.ImageSharp, Version=4.0.0.0

Has this been reported and looked at by the support team or do I need to do something to fix? Our company quoting app is not generating quotes.

I had the same issue, but it resolved after refreshing AppSheet several times.

The error is appearing on editor when click “Save and verify data”, not with just “Save”

Experiencing the same issue here. Anyone know if this has been resolved yet?

I started noticing this error with our apps last night.
‘SixLabors.ImageSharp.Formats.Jpeg.JpegEncodingColor’ from assembly 'SixLabors.ImageSharp, Version=4.0.0.

I ran into this issue after updating the app. I cleared the browser cache for the appsheet site and it seems to be working now

Please engage Support to have this AppSheet-internal error addressed.

Attn @Jose_Arteaga

We are experiencing the exact same issue as of 13 October 2026.

Our AppSheet automation bots, which generate and save PDF inspection reports to Google Drive, were functioning normally until yesterday.

Today, numerous executions have failed with the identical SixLabors.ImageSharp.Formats.Jpeg.JpegEncodingColor error.

Previously generated reports remain accessible, but newly generated PDFs are not being created. Consequently, our email automations also fail because the attachments cannot be found.

This is affecting our inspection and certification operations. Could the AppSheet team please confirm whether this is a known issue and provide an estimated resolution time?

Same issue here, since Oct 12, 2026 around 11:48 AM PDT.

Every “Create a new file” (PDF) step in our app fails at run time with:

Template Type: 'Body' could not be read due to Could not load type 'SixLabors.ImageSharp.Formats.Jpeg.JpegEncodingColor' from assembly 'SixLabors.ImageSharp, Version=4.0.0.0, Culture=neutral, PublicKeyToken=d998eea7b14cab13'.

What we checked:

  • It affects all 5 PDF bots in the app (different templates), including a bot created today.
  • A template with no images at all fails with the same error, so it is not caused by template content.
  • On Oct 12 the editor also flagged PDF bots as invalid and the app version became “not runnable”. Today editor validation passes again, but PDF generation still fails at run time (latest failure: Oct 13, 2:54 PM UTC).
  • Data source: Dropbox. These bots worked fine until Oct 12.

Looks like a server-side ImageSharp version mismatch in the PDF renderer. @Jose_Arteaga, could the team please take a look? Our production documents (reception tickets, production logs, bills of lading) depend on these bots. Thank you!

Thanks for reporting this. I have already escalated this issue with support and engineering. I will be publishing updates on this post:

Please refer to the latest update here: