doyke / wwwjdic

Automatically exported from code.google.com/p/wwwjdic
0 stars 0 forks source link

Will only return results when connected to wifi, not mobile data #81

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Turn wifi off on your device. (I'm using a Nexus 4.)
2. Search normally
3. No results!
4. Re-enable wifi
5. Search again
6. Now there are results!

What is the expected output? What do you see instead?

Expected output: some results!
Actual output: no results! (Until I connect to some wifi.)

What version of the product are you using? On what operating system?

Using version 2.3.8.1. OS: Android 5.0 Lollipop, though I experienced the same 
issue on Android 4 as well. Nexus 4.

If possible, provide a stack trace (logcat).

Sorry, no stack trace. Would one be helpful in this case? If you give me 
instructions, I'd be happy to (attempt to) provide one...

As I can only test on HTC Magic and Nexus One, I can't reproduce device
specific issues.  Without a stack trace, there is usually nothing I can do.
So do attach logcat output. That or, send me a phone :)

Please provide any additional information below.

Note that it's not a connectivity issue. When I get no results in the app, I 
navigate to the wwwjdic site (or jisho.org) to search and those work fine. All 
other apps work fine with wifi disconnected, including my web browser.

(And if it was a connectivity issue, I'd expect the app to throw some kind of 
error rather than just returning "no results". Really threw me for a loop there 
for a while!)

Thanks for any help. And again, let me know if I can help debug in any way. 
Your app is awesome otherwise!

Original issue reported on code.google.com by not.disc...@gmail.com on 25 Nov 2014 at 9:21

GoogleCodeExporter commented 8 years ago
Oh, one additional note: it's not a matter of a particular mirror being down -- 
I can switch mirrors and get the same results, until connecting to wifi.

Original comment by not.disc...@gmail.com on 25 Nov 2014 at 9:23

GoogleCodeExporter commented 8 years ago
Your carrier is probably trying too hard to cache HTTP responses. The app sends 
no-cache headers, but they are probably ignored. What carrier are you using? 

Try opening this URL in a browser (while on mobile data) to see if returns a 
response: 

http://www.csse.monash.edu.au/~jwb/cgi-bin/wwwjdic.cgi?1MDJ%C0%E8%C0%B8

Original comment by nikolay....@gmail.com on 26 Nov 2014 at 2:48

GoogleCodeExporter commented 8 years ago
It did indeed return a response... attaching screenshot. All seems normal there.

My carrier is AT&T, by the way.

Original comment by not.disc...@gmail.com on 26 Nov 2014 at 5:10

Attachments:

GoogleCodeExporter commented 8 years ago
Sorry, the URL should have been

http://www.csse.monash.edu.au/~jwb/cgi-bin/wwwjdic.cgi?1ZDJ%C0%E8%C0%B8

In any case, it might handle browser access differently, so it's best to debug 
this via the app, which I can't do directly. I could give you test app to run, 
but that would probably take some time.

Original comment by nikolay....@gmail.com on 28 Nov 2014 at 5:04

GoogleCodeExporter commented 8 years ago
Successful result again with that new URL. I'd post a screenshot, but it more 
or less looks like a text version of the above, as I'm sure you know :P

Original comment by not.disc...@gmail.com on 1 Dec 2014 at 10:56

GoogleCodeExporter commented 8 years ago
I've actually gotten a new phone since then, a 2014 Moto X, and find I have the 
same result. So at least that narrows it down somewhat to a non-phone related 
issue :P

Original comment by not.disc...@gmail.com on 2 Jan 2015 at 6:07