LayerDrawable creates new instances of children using constant state even if not supported [37068452]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Oct 28, 2015 03:15AM

- Steps to reproduce the problem (including sample code if appropriate).

1. Create a custom Drawable implementation that doesn't override getConstantState().
2. Create a LayerDrawable instance, with an instance of the custom drawable as child.
3. Call mutate() on the LayerDrawable.

- What happened.

The LayerDrawable throws a NullPointerException while trying to create a new instance of the original Drawable from it's non-existent constant state.

java.lang.NullPointerException: Attempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable()' on a null object reference
at android.graphics.drawable.LayerDrawable$ChildDrawable.<init>(LayerDrawable.java:1723)
at android.graphics.drawable.LayerDrawable$LayerState.<init>(LayerDrawable.java:1792)
at android.graphics.drawable.LayerDrawable.createConstantState(LayerDrawable.java:152)
at android.graphics.drawable.LayerDrawable.mutate(LayerDrawable.java:1652)

- What you think the correct behavior should be.

The LayerDrawable should mutate it's children as well upon it's own mutation, instead of attempting (in an unsafe and unguaranteed way) to create new instances of the children that nonetheless share the same state (and thus are not actually mutated).

Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).

Nexus 6 Emulator (Intel Atom x86_64) - Google APIs - API Level 23

deleted

Restricted

0 B

Comments

am...@google.com <am...@google.com> #2Oct 28, 2015 04:17AM

Assigned to am...@google.com.

I'm having the same problem and unfortunately there's no trace of the error (I can't find it on logs at least).

My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.

am...@google.com <am...@google.com> #3Nov 2, 2015 01:22PM

Status: New

I also have this error. Any idea?

[Deleted User] <[Deleted User]> #4Nov 3, 2015 09:01AM

I'm seeing the same problem. I believe this is the only way to use the Blobstore with Google Cloud Storage, correct? I'd be happy to create a different storage account but it doesn't seem possible to use the Blobstore/GS integration...

am...@google.com <am...@google.com> #5Nov 3, 2015 09:35AM

Assigned to am...@google.com.

I too am having this problem with the application parrot-pairing, although the otherwise-identical app parrot-pairing-dev worked fine the first time.

al...@android.com <al...@android.com> #6Nov 3, 2015 08:22PM

It occurred to me that I have a separate Cloud Services project that I think was previously also named "parrot-pairing" but which I renamed to "parrot-pairing-db" when I discovered the names would clash. Could this renaming process have left some detritus around that poisoned the "parrot-pairing" name for cloud services projects?

[Deleted User] <[Deleted User]> #7Nov 4, 2015 10:07PM

Thank you for the report. There are some errors which are not resolved by simply retrying. In the case of parrot-pairing I have found the bug which we will fix in a future release. When the fix rolls out, the retry should succeed.

The error information is not visible to application developers as it's an error in the implementation. However, given a particular app id we on the App Engine team can investigate further.

This is not the only way to use Google Cloud Storage and App Engine, although it is one of the ways we intend to accomplish our goal of simplifying the configuration of your application. There is more information on how to configure this here:

https://developers.google.com/appengine/docs/python/googlestorage/

al...@android.com <al...@android.com> #8Nov 5, 2015 03:35PM

Could you look into my app? The ID is whamcitylights

It would save me a lot of time to be able to use the Blobstore API integration with GS. I plan to slowly migrate to GS completely but I really can't afford to make the full transition right now. Thus enabling this integration would be huge benefit. Thanks

al...@android.com <al...@android.com> #9Nov 5, 2015 03:36PM

Marked as fixed.

The issue with whamcitylights appears to be the same one--in fact I expect most cases are that same issue.

[Deleted User] <[Deleted User]> #10Nov 6, 2015 10:08AM

Thanks! When do you expect the fix to roll out? Days? Weeks? Months?

[Deleted User] <[Deleted User]> #12Jan 21, 2016 10:20PM

Hello. I'm getting this error as well for app id colorfulsoftware-earthbeats. it is a java app with blobs.

re...@gmail.com <re...@gmail.com> #13Aug 31, 2016 01:53PM

I'm trying to activate Google Cloud Datastore, because Google Cloud SQL is not free. I'd like to use it as a database for my Google App Engine Application, with App Engine PHP. Basically PHP/SQL -> PHP/Datastore. I don't even know if what I'm doing is how Google Cloud Datastore supposed to work, but it'd be cool to see my nuts and bolts do something! Many Thanks to the developers for even having option available.

al...@android.com <al...@android.com> #14Sep 6, 2016 05:02PM

Add my app grooves-me to the list of those having this problem. I upgraded to paid for the app click upgrade under the cloud integration and then several attempts at retry. I am willing to help dev if they need anything from me.

am...@google.com <am...@google.com> #15Oct 4, 2016 08:48AM

[Comment deleted]