Error while deploying Chrome dependencies
The Google Chromium HTML renderer is an essential part of IronPDF's "Html To PDF" rendering process.
If IronPDF is unable to deploy Chrome Dependencies automatically, they may need to be added to a project manually via NuGet.
Multiple dependencies can be added:
On Windows, it is a good idea to ensure the target operating system has Visual C++ Runtimes installed.
Many modern applications cannot run without this essential operating system component.
We also have compatibility guides for Linux and Docker
- Ensure the correct Docker file is used
- Use the IronPdf.Linux NuGet package, instead of IronPdf
- Check that the Dotnet runtime is set to the correct setting - x64 or arm64
What to do if that does not solve it?
If that does not fix the issue, we are here to assist. Compatibility is a high priority to our engineering team.
Please send an email bug report to firstname.lastname@example.org. All compatibility issues will be seriously reviewed by a senior engineer.
Be sure to let us know about the operating system / platform being deployed to, especially if it is a cloud platform like AWS or Azure.
How to Enable Native Logging in IronPDF
Attaching Log Files to a bug report more than doubles the probability that we can isolate the issue and solve it rapidly.
Place this at the top of your code, prior to running any IronPDF methods (all versions after 2021.3.1).
IronPdf.Logging.Logger.EnableDebugging = true; IronPdf.Logging.Logger.LogFilePath = "Default.log"; //May be set to a directory name or full file IronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All;
Log files created by IronPDF are found in the /bin directory of your project where your DLLs are deployed:
- default.log (Deployment process)
- cef.log (Rendering)
- IronSoftwareCefSubprocess.log. (Rendering & Threading)
- IronSoftwareEngine.log (Useful for debugging exceptions beginning with "Error generating PDF from..." )