Skip to content
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

fix: an issue that crashes when cancel is not present #852

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

ajakka
Copy link
Contributor

@ajakka ajakka commented Jul 15, 2024

I have a use case where the user swipes multiple pdf files, and when the pdf is still loading and user swipes it, the cancel function get fired before its initialized. I fixed it by checking if the cancel function exists before calling it.

@ajakka
Copy link
Contributor Author

ajakka commented Jul 31, 2024

@wonday could you please merge this asap, it's a simple change yet it crashes apps in production, I have to manually change it in node_modules every time a yarn install is invoked.

@wise-danya
Copy link

@ajakka you can use patch-package to apply your fix locally after every yarn install without waiting for the PR to be merged.

@ajakka
Copy link
Contributor Author

ajakka commented Sep 22, 2024

@wise-danya Thank you, I was actually so close to deciding to make a new library :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants