Not sure if you have solved this problem already, but just to add a little more information to this, we were seeing the same problem not only on gingerbread devices, but also on ice cream sandwich(4.0.3 and 4.0.4) devices.
Followed your advice, added android.aaptOptions.useAaptPngCruncher = true and that fixed our build for now. We noticed that this caused an error with a bunch of png files pulled into our apk from Appcompat (rev 19.0.1). Today, we rebuilt code that was working with gingerbread and ICS devices on Tuesday (noticed a dramatically increased apk size ~30% larger today), diffed the apk contents, saw that the png files from AppCompat were the only files that were different between the good and the bad apks. Then I ended up finding this post and your fix. Hope that helps. Thanks for the fix! On Thursday, March 20, 2014 8:20:23 PM UTC-4, Xavier Ducrohet wrote: > > our versioning scheme isn't great. 0.9.2 contains a new feature (the png > processor). > > So far we've mostly increase the minor version when there's a > compatibility change. If we updated it every time we added a feature, we'd > be at 0.30.* This will change when we reach 1.0. > > That said, yes using the + notation is just not a good idea in general. > > > On Thu, Mar 20, 2014 at 12:26 PM, Michael Barany > <[email protected]<javascript:> > > wrote: > >> I am also seeing this issue on GB. >> that flag does fix the issue. >> >> Any chance this will be fixed in 0.9.2 without the use of the flag? >> It's strange that a patch version causes this crash. Makes me want to >> remove all my patch pluses from dependencies. >> >> >> On Thursday, March 20, 2014 2:21:08 PM UTC-4, Xavier Ducrohet wrote: >> >>> the problem is that it's not a bad png. It's technically a valid png. >>> It's just triggering a strange bug in GB. >>> >>> >>> On Wed, Mar 19, 2014 at 11:57 PM, Christoffer Hirsimaa < >>> [email protected]> wrote: >>> >>>> The flag for android.aaptOptions.useAaptPngCruncher = true did work! >>>> >>>> So any ideas how to narrow down the bad png? >>>> >>>> >>>> On 19 March 2014 19:49, Xavier Ducrohet <[email protected]> wrote: >>>> >>>>> I've seen reports that aapt isn't outputing some error information >>>>> like it used to so this must be it. I need to troubleshoot this. >>>>> >>>>> >>>>> On Wed, Mar 19, 2014 at 11:19 AM, Daniel Lew <[email protected]>wrote: >>>>> >>>>>> Nevermind, I'm an idiot. >>>>>> >>>>>> I had, this morning, broken the build. There was a menu item whose >>>>>> string reference I changed. android:titleCondensed was correct, but >>>>>> android:title still pointed at a string that no longer existed. >>>>>> >>>>>> The error message could be made a little more clear but this was my >>>>>> fault. 0.9.1 builds fine. >>>>>> >>>>>> -Daniel >>>>>> >>>>>> >>>>>> On Wed, Mar 19, 2014 at 1:04 PM, Daniel Lew <[email protected]>wrote: >>>>>> >>>>>>> Actually, shoot. Now it's happening a few hours after reverting >>>>>>> even on 0.9.0. Everything was building fine before. I did just >>>>>>> upgrade to >>>>>>> Android SDK Tools 22.6.1. >>>>>>> >>>>>>> I honestly have no idea what's going on. I was building/running >>>>>>> fine an hour ago. :P >>>>>>> >>>>>>> -Daniel >>>>>>> >>>>>>> >>>>>>> On Wed, Mar 19, 2014 at 12:53 PM, Daniel Lew <[email protected]>wrote: >>>>>>> >>>>>>>> Oh, I thought it was related, my bad. >>>>>>>> >>>>>>>> Our builds have been working up through 0.9.0, so it's new to >>>>>>>> 0.9.1. I've just switched back to 0.9.0 for now. >>>>>>>> >>>>>>>> -Daniel >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Mar 19, 2014 at 11:21 AM, Xavier Ducrohet <[email protected] >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Did that happen before, using 0.9.0? >>>>>>>>> >>>>>>>>> This is in a different build step, so I'm not sure how it would be >>>>>>>>> related to the png processor. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Mar 19, 2014 at 9:08 AM, Daniel Lew <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> I'm also getting issues with the new 0.9.1 aapt, but setting >>>>>>>>>> that command doesn't seem to fix anything. Here's a gist of the >>>>>>>>>> error: >>>>>>>>>> https://gist.github.com/dlew/6cbe4a92d20ef49e7270 >>>>>>>>>> >>>>>>>>>> I tested 0.9.1 on a different project and it worked just fine, so >>>>>>>>>> it's something about this particular project it doesn't like. >>>>>>>>>> >>>>>>>>>> -Daniel >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wednesday, March 19, 2014 10:47:30 AM UTC-5, Xavier Ducrohet >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, I've seen another report that it's due to the new png >>>>>>>>>>> processor. >>>>>>>>>>> >>>>>>>>>>> For now you can disable it with >>>>>>>>>>> android.aaptOptions.useAaptPngCruncher >>>>>>>>>>> = true >>>>>>>>>>> >>>>>>>>>>> I would love though if you could figure out which png causes >>>>>>>>>>> this (and send it to me, off list if needed). >>>>>>>>>>> >>>>>>>>>>> We have a whole suite of png tests and none of them triggers >>>>>>>>>>> this. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Mar 19, 2014 at 8:24 AM, Christoffer Hirsimaa < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> While developing today I noticed I can't boot my application on >>>>>>>>>>>> Galaxy Pocket anymore. It shows the default theme of the activity >>>>>>>>>>>> (onCreate >>>>>>>>>>>> is called but never finishes when trying to log) and no crash >>>>>>>>>>>> dialog is >>>>>>>>>>>> shown afterwards. After an hour of head banging against the wall I >>>>>>>>>>>> found >>>>>>>>>>>> out that it is the 0.9.1 release that causes this. The only thing >>>>>>>>>>>> that >>>>>>>>>>>> appears in logcat is this: >>>>>>>>>>>> >>>>>>>>>>>> A/libc﹕ Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1) >>>>>>>>>>>> >>>>>>>>>>>> My application has native libs but they don't even have time to >>>>>>>>>>>> attempt to load them from what I can see in logcat. Changing back >>>>>>>>>>>> to 0.9.0 >>>>>>>>>>>> makes the application work again and this is independent of my own >>>>>>>>>>>> code. >>>>>>>>>>>> >>>>>>>>>>>> Something else I can check for? Is this enough for you to find >>>>>>>>>>>> the problem? >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>> Google Groups "adt-dev" group. >>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>>> it, send an email to [email protected]. >>>>>>>>>>>> >>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Xavier Ducrohet >>>>>>>>>>> Android SDK Tech Lead >>>>>>>>>>> Google Inc. >>>>>>>>>>> http://developer.android.com | http://tools.android.com >>>>>>>>>>> >>>>>>>>>>> Please do not send me questions directly. Thanks! >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>> Google Groups "adt-dev" group. >>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>>> send an email to [email protected]. >>>>>>>>>> >>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Xavier Ducrohet >>>>>>>>> Android SDK Tech Lead >>>>>>>>> Google Inc. >>>>>>>>> http://developer.android.com | http://tools.android.com >>>>>>>>> >>>>>>>>> Please do not send me questions directly. Thanks! >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>>> the Google Groups "adt-dev" group. >>>>>>>>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>>>>>>>> topic/adt-dev/2yaMkhp9wU8/unsubscribe. >>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>> to [email protected]. >>>>>>>>> >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "adt-dev" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Xavier Ducrohet >>>>> Android SDK Tech Lead >>>>> Google Inc. >>>>> http://developer.android.com | http://tools.android.com >>>>> >>>>> Please do not send me questions directly. Thanks! >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "adt-dev" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> *Christoffer* >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "adt-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Xavier Ducrohet >>> Android SDK Tech Lead >>> Google Inc. >>> http://developer.android.com | http://tools.android.com >>> >>> Please do not send me questions directly. Thanks! >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "adt-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. > http://developer.android.com | http://tools.android.com > > Please do not send me questions directly. Thanks! > -- *EMAIL CONFIDENTIALITY STATEMENT: This email, including any attachments hereto, may contain confidential and/or proprietary information of Videon Central, Inc., and/or may include information controlled for export purposes under the U.S. International Traffic in Arms Regulations (ITAR) and is intended for the recipient only. No export, sale, transfer, release or other disposition of this information is permitted without prior authorization. If you are not the intended recipient please 1) do not disclose, copy, distribute or use this message or its contents to any other person or entity. 2) advise the sender by return e-mail, and 3) delete all copies, including attachments, from your computer. Your cooperation is greatly appreciated.* -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
