-
-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS heavy pdf rendering issue #1926
Comments
This is due to the large size of the pdf. This issue is not going to be fixed in next 15 days as it is end of the year and most of the community will be away from there cubicles. Adobe is free to use and easy to plug and play. `import React, { useEffect } from "react"; const clientId = process.env.REACT_APP_ADOBE_CLIENT_ID; const previewConfig = { const PdfViewerIos: React.FC<{ const loadDoc = () => { return ;}; export default PdfViewerIos; |
Thank you so much for the detailed explanation and background information. I really appreciate it! By any chance, will this issue be fixed after 15 days? We’re not in a huge rush and can wait a little longer. Ideally, we’d prefer to continue using this library if possible. |
what we need is a lazy load feature for the pdf on scroll as that is the only way to reduce the burst of RAM usage(crossing 384mb +) but that will also need the meta data to be maintained to allow the search feature since this feature is bit time taking to implement and there is also a possiblity that iOS fixes this on there end and release the fixes in iOS 18.2 or 18.3. Difficult to assume this issue to be fixed soon in this library as this will need a very significant development. |
Before you start - checklist
Description
iOS PDF Rendering Issue with Large Files
We're experiencing PDF rendering issues specifically on iOS devices. The browser becomes unresponsive when trying to render certain PDF files.
Steps to reproduce
With iOS phone.
Expected behavior
I hope large pdf file would open in ios also.
Actual behavior
browser is broken with large pdf file.
Additional information
No response
Environment
The text was updated successfully, but these errors were encountered: