-
Notifications
You must be signed in to change notification settings - Fork 685
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
Version 2.2.2 uri load bug #1513
Comments
Thanks for the report - I'll take a look (or someone else feel free to submit a fix). As a work-around looks like removing the |
Yes, but in version 2.2.2, the File path is created like this |
@JYLEE1988 Where are you getting this file URI from? There's already a regression test for |
@colinrtwhite |
I encountered this problem and ended up downgrading the version to 2.2.1. Here's the URI: |
A previous change to fix #1344 to handle # characters in literal no-scheme paths broke file:// scheme URI parsing by including the entire literal URI in the file path, which breaks encoded paths (like those with spaces) and URIs with non-path data (such as query parameters). This partially reverts the prior fix, so that # is not supported in file:// URIs, requiring the user to either use a no-scheme URI or encode the path, as # is reserved in URIs for fragment declarations. Fixes: #1513 Test: FileUriMapperTest#ignoresAfterPathCorrectly Test: FileUriMapperTest#decodesEncodedPath
Describe the bug
uri starting with
file:///
is not loaded.A change occurred in the file creation method in version
2.2.2
, which is expected to be related to this.#1466
In version
2.2.1
, the uri image loads well.To Reproduce
Try to load a uri starting with
file:///
.For example
file:///storage/emulated/0/android/data/{package-name}/cache/images/temp.jpg
Version
2.2.2
The text was updated successfully, but these errors were encountered: