#jspdf -autotable not accessible after closing or publishing app

1 messages · Page 1 of 1 (latest)

pearl hearth
#

I installed jspdf-autotable https://cdnjs.cloudflare.com/ajax/libs/jspdf-autotable/3.5.28/jspdf.plugin.autotable.min.js. The library installs and works fine until i deploy my app or close it and reopen it

tidal leafBOT
#

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Team Appsmith

queen prawn
#

<@&725604214666952714> I had this same issue last week. I had jsPDF working, then added the autotable plugin and it worked at first. Not sure what triggered it to stop working, but it could have been deployment.
cc @dense jasper

dense jasper
#

@pearl hearth are you facing issues on the view mode after a deploy?

tidal leafBOT
#

Please help us with the following information for faster debugging.

Which version of Appsmith are you on?
Provide screenshots/screen recordings of the original error/code snippet.
Add details about your use case and provide steps to reproduce the issue, if
possible.

#

Please help us with the following information for faster debugging.

Which version of Appsmith are you on?
Provide screenshots/screen recordings of the original error/code snippet.
Add details about your use case and provide steps to reproduce the issue, if
possible.

pearl hearth
#

I noticed when the plugin is installed it says it can be accessed through "default" then after closing it changed to "_createTable"

tidal leafBOT
#

Could you send us some screenshots or a loom.com screen recording to showing the
issue?

queen prawn
#

this is what the plugin looks like after it has stopped working. I can't remember if it showed as a different entry name at first, while the plugin was still working.

Screen_Shot_2023-02-09_at_9.03.21_AM.png
pearl hearth
#

yes, after initial install and without closing it shows available as default

pearl hearth
queen prawn
#

@pearl hearth that app looks amazing! Great work on this. It's an excellent example of what we can do now with external libraries!

And thank you for the screen recording. This clearly shows the library reference changing from 'default' to '__createTable' which is when the plugin stops working. I ran into the same issue but have not had time to troubleshoot further. Thank you for doing the hard work and sharing your findings.

@dense jasper check out this video.

dense jasper
#

we should hopefully have some updates on Monday. I'll keep you posted. Have a great weekend 🙂

#

btw, your app is really well built! love how you're harnessing the power of custom JS libs for PDF generation ❤️

pearl hearth
#

I would be glad too. I will have to test my vpn ( havent worked remotely in awhile) to my work network to show you, I would not be at work during those hours. I will schedule as soon as i can. Thank you

queen prawn
dense jasper
oblique scarab
#

sorry to revive an old support, How do we fix it? I have the same problem. it changes from default to __createtable

queen prawn
#

cc @dense jasper

dense jasper
#

@oblique scarab which library are you facing this issue on?

oblique scarab
#

nvm I resolved it

#

so instead of using doc.autotable()
I used

const table = __createTable(doc, {/*table options*/})
//and to draw it
__drawTable(doc, table)