-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libpng warning when compiling with gradle #16
Comments
What version of the build tools are you using? We haven't seen the issue, but similar problems have been reported with |
From my app's buildToolsVersion "21.1.2" |
What OS and Java version are you using? Would you be willing to share a stacktrace? If possible, I'd be curious to see if compilation using build tools circa version 19 works. In the meantime, we'll see if we can reproduce the issue. |
Using Yosemite 10.10.1 (14B25), my JDK is The app builds - I'm just getting a ton of log barf in the process. |
This is just an issue with the version of libpng aapt uses (https://code.google.com/p/android/issues/detail?id=77704).
Future updates of the build tools should fix this, for now it's just noise. |
@designatednerd did this answer your issue? |
@lkorth Yes, but I'd recommend leaving this open until the noise goes away so that anyone else encountering this issue is able to see what the problem is. |
https://groups.google.com/forum/#!msg/adt-dev/rjTQ_STR3OE/-UcNQRISTKsJ has a solution for this. Just need to clean up the metadata on the PNGs. |
Stripped assets coming soon to a release near you! |
Thanks! On Wed, Apr 29, 2015 at 10:03 AM Luke Korth notifications@github.com
|
👍 |
Just to note, there will still be some warnings generated because of the card form. I have made the commit to strip the metadata in the card form, however it won't take effect until the next version of the card form is released and Drop-in is updated. |
Every time I build using Gradle on Android Studio, I get warnings of this type for pretty much every drawable resource in your library:
Is there some kind of setting I should be looking at to ignore this on my end? Or is this something you guys can fix on your end?
The text was updated successfully, but these errors were encountered: