and its not the actual number of classes I'm really focused on but a specific set that's causing the problem since the issue you linked brings up deeply nested interfaces.
No one really points a finger at this or that specifically in the issue and the blog post mentions joda time of which I haven't had any problems with for what i use in it (not much) after going through proguard. Do you have any ideas of what lib is causing the issue or do you have a complex app and would sooner point to that being the potential issue? I could really only think to brute force resolution of the cause. Remove dependency on anything you blanket keep class with in your proguard and see if the app installs, then if nothing just remove deps and comment relevant code until the app installs. Have your list of deps removed and add them back one by one to see if a single library is the cause or if it can be any combination of libraries added and removed making it not library specific. A tiring thing to do for sure but even after pin pointing a particular library I'd want to look at the proguard config to see if something could be adjusted there. On Tue, Jul 29, 2014 at 2:08 AM, Daniel Skinner <[email protected]> wrote: > that's interesting, i have an app I deploy to 2.3 that's rather large but > don't see this. From a cursory read of the issue I wonder how many classes > are being packed in your apk after proguard has run (should show during > build) and, mostly a wild guess, wonder if your proguard config does a > blanket keep of classes you dont actually need leading to the issue. > > > On Tue, Jul 29, 2014 at 2:00 AM, David Pérez < > [email protected]> wrote: > >> Am I the only one having this kind of problem? >> >> Am Freitag, 25. Juli 2014 14:19:36 UTC+2 schrieb David Pérez: >> >>> Hi all, >>> >>> When running my Scala app on a real Gingerbread device, I'm facing this >>> problem. >>> I'm using Scala 2.10.4. >>> Of course, I'm running ProGuard. >>> My APK has a size of 3.3 Mb, not so big. >>> >>> I've read this: http://birbit.com/how-to-solve-linearalloc-problem/, >>> but it is a little cumbersome to apply this solution. >>> I'm sure, I didn't use to have this problem before. >>> >>> Any tip, please? >>> >>> David. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "scala-on-android" 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. >> > > -- You received this message because you are subscribed to the Google Groups "scala-on-android" 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.
