PdfViewer GetFileAsync (always) returning NULL

1 Answer 19 Views

PDFViewer

David Cresswell asked on 29 Sep 2025, 05:32 PM | edited on 29 Sep 2025, 05:33 PM

Hi,

I'm getting on quite well with TelerikPdfViewer. But now I'd like to access a form filled PDF and save it.

I can see that the GetFileAsync function is meant to get me the current state of the file and have already noted that it...

"Returns null if no document is loaded."

However, the document definitely is loaded. I'm looking at and I can even see it's properties are loaded when I debug it. I've even tested with & without a Rebind(), just for good measure.

I can also access the originally loaded Data property but, inevitably, this doesn't contain the form changes

Am I missing something obvious?

Following my most recent and only other post, rendermode is definitely InteractiveServer

Thanks

David

David Cresswell

commented on 30 Sep 2025, 02:51 PM

Here is an example REPL in case it helps...

https://blazorrepl.telerik.com/QJEDRElo492eRPg145

1 Answer, 1 is accepted

answered on 01 Oct 2025, 11:03 AM

Hi David,

Frankly, at first I thought I was crazy too. Unfortunately, your observation is correct - the method does not work. I am truly sorry about the confusion and the missing feature.

The Blazor PDF Viewer depends on a home-grown JavaScript package, which in turn depends on PDF.js. My assumption is that something changed on the JavaScript side after we implemented the feature in the Blazor component and it broke the integration. The second puzzling bit is that you are the first one to report the problem.

I already logged a bug report on your behalf and awarded you Telerik points. I already notified the developers and I hope there is some minor oversight in the code that is easy to fix.

Regards,
Dimo
Progress Telerik

Your perspective matters! Join other professionals in the State of Designer-Developer Collaboration 2025: Workflows, Trends and AI survey to share how AI and new workflows are impacting collaboration, and be among the first to see the key findings.
Start the 2025 Survey

David Cresswell

commented on 01 Oct 2025, 03:17 PM

Dimo,

Thank you for the thorough feedback.

I take it a workaround with older versions of this and/or PDF.js is not an option?

The bug report is also welcome development. Although, given how many other Unplanned ones there are, where should I be setting my expectations in terms of timescale for a fix?

Regards

David

Dimo

commented on 02 Oct 2025, 07:04 AM

Hi David,

You are right that rolling back to an older version is not applicable in this case.

Given the nature of the bug, we will fix it with a higher priority rather then follow standard prioritization algorithms. We are already looking into it. So I would say that the next planned release in November may resolve the problem.

David Cresswell

commented on 02 Oct 2025, 07:20 AM | edited

Dimo,

Ok, thanks.

The November timescale may give me a problem with an increasingly urgent project requirement. I don't suppose there's any chance of a more incremental hot-fix, or even a more personalised workaround that might avoid me needing to source an alternative component?

Regards

David

Dimo

commented on 06 Oct 2025, 09:59 AM

Hi David,

It turns out the problem is not that straight-forward to fix. We can release a new product version sooner than November, but we will need at least a few more weeks to investigate and resolve the bug. I am afraid I cannot commit to a specific time frame at this point, which I realize puts you in a touch situation. Sorry about that.