Note that there are some explanatory texts on larger screens.

plurals
  1. PODifference between ICS and Gingerbread?
    text
    copied!<p>I have an app on Google Play with 20k+ downloads with 4,6+ rating, and since loads of devices got their ICS upgrades in the last few months, some(not that many) weird errors started to show up. Theese are not force closes, since I covered all possible NullPointers, etc, but for example wrong/not working networking stuffs.</p> <p>First of all, here is the networking part of my app:</p> <pre><code> HttpClient hc = new DefaultHttpClient(); //init the HttpClient hc.getParams().setParameter("http.protocol.content-charset", "UTF-8"); //set the encoding to UTF-8 HttpParams hp = hc.getParams(); //get HttpParams HttpConnectionParams.setConnectionTimeout(hp, TIMEOUT); //set the timeout HttpConnectionParams.setSoTimeout(hp, TIMEOUT); //set the timeout HttpProtocolParams.setUserAgent(hp, ActMain.userAgent); //set the user agent HttpResponse resp = hc.execute(new HttpGet(item.buildQuery())); //execute the query Stat.result=EntityUtils.toString(resp.getEntity(), HTTP.UTF_8); //save the result </code></pre> <p>This is working flawlessly on Gingerbread devices. Not a single(as far as I'm aware of) error report arrived from Gingerbread devices. But, some reports arrived from ICS devices, like, the result of the query is empty, the app will say that there is no such a result for the given options. Again, since there is no actual force close or any real report, I'm not sure if the code I gave causes the error, I'm not sure if the source of the problem is the Gingerbread vs ICS thingie, it is just a wild guess, but the only common thing I could discover from the reports was ICS.</p> <p>My real question is something like this: can ICS cause the error described above? It shouldn't I think, since I use standard apache http thingies, but who knows, worth a shot. </p> <p>Thanks for any feedback!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload