Problem with Custom Component and ADOBE PDF embed API

App Building
,
1

Hi,

I am very new to custom components but I have followed this to embed the adobe PDF API:

When uploading a PDF file, It seems to work as the PDF is shown in the custom component. The problem is it is only shown for about 1 seconds and then the entire thing greys out and I can only see a scroller in the custom component.

So it seems the pdf is correctly loaded into the custom component, but then for some reason dissapears again. I do not get any errors, and it seems it is still registering the pdf just not showing it, given the scroller is still there. The scroller dissapears if I force an error.

Any help would be greatly appreciated :blush:

2

Just to give some more context. I did not make any changes to the app provided by @Kabirdas

The code for Model:
{
"pdf_base64": {{uploaded_pdf.value}},
"pdf_name": {{pdf_uploader.files[0]?.name || "url"}},
"client_id": {{textInput2.value}}
}

And I do have a API key from Adobe.

It also seems that the buttons in the app "Rotate" and "Download" will rotate the pdf, and then afterwards I can download the rotated PDF. I just cannot see it in the component.

3

https://community.retool.com/t/using-browsers-built-in-pdf-viewer/20010/4 -- Please check the solution in this post if having issues with the Adobe PDF API

5

Thanks,

But I have already read this post and it does not appear to address the issue I’m having. As mentioned the API, app and component seems to work fine, but for some reason it disappears again after load.

6

Meant to suggest the work around the post recommended. Not able to reproduce this issue - will take it back to the team for further feature development.

7

Alright, I’ll see if I can find a work around that works for me :blush: thanks!

8

Hi @rikkesborup I am seeing the same issue when using allowed domains other than retool-edge.com :thinking: For example, using www.retool-edge.com, retool.com, etc, as the allowed domain for my adobe api key all have the reload issue.

Are you seeing cors errors like this in the browser console? Failed to load resource: the server responded with a status of 401 (Unauthorized)?

Are you using the upload from local option?

Hope you already found a workaround :crossed_fingers: