ansaurus

Question

Why is WebView unable to open some local URLs (Android)?

Answer 1

+1 A:

Try getting rid of the % in the filename. Or, escape it as %25.

CommonsWare 2009-11-10 00:37:09

Well sure, but shouldn't `URLEncoder.encode()` have handled that? Isn't that it's whole reason for existing? Anyhow, I tried it and it tries to open it now, but it's just dumping it out as text instead of rendering the image.

fiXedd 2009-11-10 00:50:08

Your <img> tag in your update does not have a properly-encoded relative URL, as you have not escaped your % sign as %25. As to why URLEncoder.encode() is not doing that, I have no idea, but AFAIK you cannot have a bare % in a URL. Moreover, since this is an asset, baked in your APK, why are you fussing with troublesome filenames in the first place? Just rename the file to something simple. If *that* fails, confirm you have a valid JPEG image.

CommonsWare 2009-11-10 01:34:54

Basically I'm building a port of an iPhone app that will allow my client to dump files into the assets directory, change a couple settings, then recompile to create a "whole new app". I can't predict what characters the filenames will contain and this is specifically from the test set that he provided me. Believe you me, if I could just rename the files I would.

fiXedd 2009-11-10 01:48:55

Oh, also, I noticed the bad name in the `<img>` and corrected it... still didn't work. The image opens fine everywhere else (Firefox, Eye of GNOME, GIMP), but just for good measure I opened it in GIMP, changed it a little, then resaved. Still no luck.

fiXedd 2009-11-10 01:50:39

Just for fun I went ahead and removed the `%` from the filename and it made no difference... still won't load as an image.

fiXedd 2009-11-10 01:53:30

Do other JPEGs work in your assets, and it is just this one failing? Or are JPEGs overall failing?

CommonsWare 2009-11-10 03:02:24

I just tried it with JPEGs, PNGs, and GIFs and I get the same results on them all.

fiXedd 2009-11-10 06:03:46

Okay, this has diverged into a different topic all together. I think I'm going to open a new question.

fiXedd 2009-11-10 08:07:23

Answer 2

A:

I would guess that WebView only understands text related content types so it faithfully treating your JPG as base64 encoding, decodes and displays resulted gobble-goop as text. I don't really know if it's possible to set content type for WebView but as workaround you can try to throw img tag inside html tag and load resultet page. Also you probably can only use WebView#loadDataWithBaseUrl

DroidIn.net 2009-11-10 04:48:44

Turns out it works fine with images... kinda. See my answer if you care.

fiXedd 2009-11-10 09:52:20

Answer 3

+3 A:

Okay, after spending way too long on this, I've figured out what's going on. Basically, if images stored in the assets/ directory contain a space (e.g., " ") in their file name, they won't render as images.

myWebView.loadUrl("file:///android_asset/testimage.jpg");

works fine. However,

myWebView.loadUrl("file:///android_asset/test+image.jpg");

just throws a not found error and

myWebView.loadUrl("file:///android_asset/test image.jpg");
// and
myWebView.loadUrl("file:///android_asset/test%20image.jpg");

show it improperly displayed (as text... see screenshot in question).

This unexpected behaviour is present on (at least) 1.5, 1.6, and 2.0 and I filed a bug report.

fiXedd 2009-11-10 09:51:41

Thanks for clearing this

DroidIn.net 2009-11-11 02:03:17

ansaurus

tags:

views:

answers:

Why is WebView unable to open some local URLs (Android)?

related questions