-
Notifications
You must be signed in to change notification settings - Fork 17
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
RoxyFileman dies on interpreting an invalid image #89
Labels
Comments
hassanelsherbiny
added a commit
that referenced
this issue
Mar 10, 2024
hassanelsherbiny
added a commit
that referenced
this issue
Mar 10, 2024
…erpreting-an-invalid-image-#89 RoxyFileman dies on interpreting an invalid image #89
hassanelsherbiny
added a commit
that referenced
this issue
May 3, 2024
hassanelsherbiny
added a commit
that referenced
this issue
May 3, 2024
…erpreting-an-invalid-image-#89 RoxyFileman dies on interpreting an invalid image #89
hassanelsherbiny
added a commit
that referenced
this issue
May 3, 2024
hassanelsherbiny
added a commit
that referenced
this issue
May 3, 2024
…erpreting-an-invalid-image-#89 RoxyFileman dies on interpreting an invalid image #89
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
version: 4.60.5
Steps to reproduce the problem:
RoxyFileman will stop working when this happens, as the call on RoxyFilemanFileProvider.cs#396 returns null and the next line throws an exception.
Expected behavior:
or
or
The text was updated successfully, but these errors were encountered: