We are using the ‘Aspose.Slides.NET6.CrossPlatform’ package and trying to convert PPT slides into the pdf then we are getting - ‘The type initializer for ‘\u0005\u0015\u0019\u0005’ threw an exception’ this issue. Locally it’s working but whenever we deploying our code to linux server then this issue is coming.
Info
.Net version - .Net core 8.0
Server - Linux
Alpine version - 3.19
GLIBC version - Installed 2.23 version on alpine server
Sample Program code
[HttpPost()]
public async Task<IActionResult> UploadPPTFile(IFormFile file)
{
Presentation presentation = new Presentation(file.OpenReadStream());
presentation.Save("PDF-result.pdf", SaveFormat.Pdf);
return new ObjectResult($"PDF converted successfully.")
{
StatusCode = 201
};
}
Jenkinsfile
FROM icr.io/ic-devops/ic-dotnet-aspnet:8.0.3-alpine3.19
WORKDIR /app
EXPOSE 8080
RUN apk add --no-cache harfbuzz-dev
RUN apk add krb5-libs libgcc libintl libssl3 libstdc++ zlib
RUN apk --no-cache add libgdiplus
RUN apk update && apk add fontconfig
RUN apk add --no-cache icu-libs
ENV DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=false
ENV ASPNETCORE_URLS=http://*:8080;http://*:8081
RUN addgroup -g 2000 -S appuser && adduser -u 1000 -S appuser -G appuser -h /app
RUN chown appuser:appuser /app /tmp
USER appuser:appuser
ARG CSPROJ_PATH
COPY --chown=appuser:appuser PPT.Api .
ENTRYPOINT ["dotnet", "PPT.Api.dll"]
@sfulari,
Thank you for your patience. Unfortunately, the image icr.io/ic-devops/ic-dotnet-aspnet:8.0.3-alpine3.19 is hosted in a private registry. Could you please share a standalone sample project to reproduce the error?
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SLIDESNET-44736
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Any update on this Ticket? 21 Days is gone and we are still waiting on this ticket. We already purchased Aspose Total license and this delay of time affecting our timeline.
@sfulari,
We are sorry that you have to encounter this problem. The issue is still open. Unfortunately, I don’t have any additional information yet. We apologize for any inconvenience caused.
@sfulari,
Unfortunately, I don’t have information about ETA for the issue. I understand how frustrating it must be to wait without clear updates, and I’m here to help as much as I can in the meantime.