utils.downloadPage() stopped working as it used to

App Building
42

Hi @Alexandra_Matthews,

Would you be able to send a JSON export of an app where this repros, as well as the exact parameters you passed in to utils.downloadPage()? I'm unable to reproduce this issue locally.

1 Like
43

@Gregory_Caplan @Van @daniyalafzal

Would you be able to send a JSON export of an app where this repros so we can see what might be causing the issue?

44

Thanks for your report @dchoi, Would you mind sharing a repro app?

45

Hey @MiguelOrtiz :wave:

Would you be able to share a repro app and description?

1 Like
46

Hi Brenna

So it doesn't seem to be a problem on Safari on mac, but on Chrome on Mac it doesn't work.

We also have found, that when using Safari, it fails to print anything contained within a container. This means we needed to move everything out of containers to get the contents of the container to print.

Here are the download Utils parameters:

utils.downloadPage(Centres.data.name['0'],{fullscreen: true,  componentsToExclude: ["button1", "select1", "select2"]

});

How can I send this JSON export to you securely?

Thanks

1 Like
47

You should be able to send the JSON export as an attachment to the message. To break this down, this seems like a browser-specific issue:

  • In Chrome, the fullScreen option doesn't work and cuts off some of the screen but containers show content.
  • In Safari, none of the screen is cut off but containers don't show content.

Is this understanding correct?

48

I'm experiencing this as a browser-specific issue. When I use Edge, I see the child components within the referenced container (or even if I just download the full page without inclusions or exclusions). On Chrome, these components don't show up regardless of the configuration of the util.downloadPage.

1 Like
49

Hey @brenna.chen , any updates from the team on this browser issue?

50

Thanks for flagging the browser issue with utils.downloadPage()! We've identified several possible factors contributing to the inconsistent behavior across browsers like Edge and Chrome. We're actively investigating, but due to the confusing nature of the bug, we don't have a clear timeline for a fix yet. We'll be sure to keep you updated as we make progress, and we appreciate your patience in the meantime!

4 Likes