Just curious, how did this influence your application? Do you access
network layer from UI thread?
Anyway, I think this is a bug, there is nothing changed in documentation.
And StrictMode example in documentation still uses App's onCreate(). So
there are no signs of this being an intentional change so far.
On Monday, July 16, 2012 9:43:59 PM UTC+3, b0b wrote:
>
>
> Thank you for your in-depth analysis.
>
> I've ended up with this, call in the Application derived class onCreate():
>
> private void setLaxStrictMode() {
>
> if(Build.VERSION.SDK_INT < Build.VERSION_CODES.GINGERBREAD) return
> ;
>
> if(Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN) {
> StrictMode.setThreadPolicy(ThreadPolicy.LAX);
> log.info("StrictMode: LAX");
> } else {
>
> new Handler().postAtFrontOfQueue(new Runnable() {
> @Override
> public void run() {
> StrictMode.setThreadPolicy(ThreadPolicy.LAX);
> log.info("StrictMode (JB): LAX");
> }
> });
> }
> }
>
>
> Now the real question is if the change in handleBindApplication() was
> intended, or if it is a real bug.
>
> In any case it broke my app on JB, and got me a few expeditive 1-star
> comments on Google Play
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
