Reporting a bug in the “Print Pro Plugin for Bubble”
When I print in the desktop version, it prints correctly, but when I print from the mobile, it appears incorrect. I’ll show it in the video below:
https://www.youtube.com/shorts/sh5QLTut23w
Is there anything that can be done?
Hello @arturdiboa ,
I am sorry to hear that you have had difficulties with our plugin. We have passed this information to the development team, they will check it and we will get back to you as soon as possible.
Additionally, can you please also tell us the version of the Bubble you are currently using? This information will help us understand better what went wrong with our plugin, inside your app.
Thank you once more, and we’re looking forward to hearing from you soon.
Wish you a great day.
I am using the latest version of Bubble, and in the video linked below, I demonstrate the bug occurring on the Zerocode plugin’s own demonstration page.
Hello, @arturdiboa,
Thank you for sharing additional information.
I have updated the task to investigate this issue.
As soon as I get updated information from the development team, I will get back to you.
Thank you for your understanding and cooperation.
Cheers!
Hello @arturdiboa,
Thank you for your patience.
I’ve looked into the problem and it appears that the core of the issue is related to an incompatibility between the jQuery print function and Android’s browser environment.
As of December 31, 2020, Google Cloud Print is no longer supported, and this seems to have affected our feature that prints a PDF from the website. While this function works correctly on iOS and computer platforms, on Android devices it behaves differently. Instead of printing the designated PDF, it triggers the printing of the entire web page. This issue is likely due to the way Android devices process and execute JavaScript and jQuery commands.
A potential workaround for this problem could be to connect your phone directly to the printer using a USB cable. This might bypass the issue with the Android browser environment.
I apologize for the inconvenience this issue has caused and regret that I couldn’t offer a more immediate solution to resolve this problem directly within the plugin’s current functionality.
If you have any additional questions, please feel free to ask.
Cheers!