-
Notifications
You must be signed in to change notification settings - Fork 325
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
Null safety #95
Comments
This plugin is not active for a 2 years. You can use clones of this repository ... as https://pub.dev/packages/pdf_viewer_jk/versions/2.0.0-nullsafety.1 |
yonatann
pushed a commit
to yonatann/flutter_plugin_pdf_viewer
that referenced
this issue
Jan 16, 2022
* update dependencies * apply strict linter - conflict * Workaround for NPE, ignore IDE project files. * Bump version, upgrade dependencies. * Ignored files cleanup. * More deleted files. * Delete flutter_plugin_pdf_viewer.iml * More Eclipse artifacts cleanup. * Update Gradle dependencies. * Upgrade old Flutter embedding. * Upgrade Flutter embedding. * Better error logging, maybe properly time cache deletion. * Make sure file is closed when done. * Make sure file is closed when done, better this time. * Use initFileURLWithPath to create a valid file path The NSURL init method initFileURLWithPath will ensure that the file:/// prefix is in place as well as making sure that any whitespace characters within the original path string are encoded correctly when creating the url. * Release implicitly retained CGPDFDocument and release retained CGPDFPage * Update pubspec.yaml * Update pubspec.yaml * Pn 53 (CrossPT#94) * I removed the line from 42 to 63 for deleting unused saved cache files. It makes memory problem when you try to open the PDF after several times. * remove .idea folder Co-authored-by: Eko Prasetyo <[email protected]> * more fixes and updates * updates * fixes for state problems * upgrade ersion number * update * bug fixes Co-authored-by: Ahmed Masoud <[email protected]> Co-authored-by: Ahmed Masoud <[email protected]> Co-authored-by: Enver ALTIN <[email protected]> Co-authored-by: Robert Hillary <[email protected]> Co-authored-by: Eko Prasetyo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are there plans to make the package compatible with null safety (here is the migration guide)?
The text was updated successfully, but these errors were encountered: