[Bug] Reactive pdf export stuck to the first download

[ronki2304]

Is there an existing issue for this?

• Yes, I have searched the existing issues and none of them match my problem.

Product Variant

Self-Hosted

Current Behavior

hello,

I face weird issue when I update a resume, those updates are not in the pdf generated

Expected Behavior

No response

Steps To Reproduce

• create a resume and do some stuff
• export to pdf
• update some content
• export to pdf

What browsers are you seeing the problem on?

No response

What template are you using?

None

Anything else?

I use the simple docker compose
I tried to restart chrome container only not work
I tried to restart the full stack, not work
only a full container flush work, I suppose it is some temporary files that stuck the generation

[roshanabdullah]

I have checked the code @ronki2304 the data object is coming empty from the server side, when we click on the pdf download it redirects us giving error on the server side 404 not found

which is actually correct because the data object is coming empty

config : {transitional: {…}, adapter: Array(3), transformRequest: Array(1), transformResponse: Array(1), timeout: 0, …} data : {} headers : AxiosHeaders {access-control-allow-origin: '*', content-length: '2', content-type: 'application/json; charset=utf-8', date: 'Thu, 13 Jun 2024 19:17:36 GMT', etag: 'W/"2-vyGp6PvFo4RvsFtPoIWeCReyIC8"', …} request : XMLHttpRequest {onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: true, upload: XMLHttpRequestUpload, …} status : 200 statusText : "OK",

so the data:{} object is empty, Please @AmruthPillai could you please provide any solution to this?

[ronki2304]

I see but why the first export works?

[roshanabdullah]

I see but why the first export works?

because the data object is being returned at the export url

[AmruthPillai]

Please pin the browserless/chrome version to v2.13.0. The issue was not related to Reactive Resume.

[ronki2304]

hello the error remains even browserless/chrome version to v2.13.0.

Please reopen the issue