as for signing an already signed apk, you can just run jarsigner again manually
On Wed, Jan 1, 2014 at 12:47 PM, Perry Nguyen <[email protected]> wrote: > huh? > > clean > android:package-release > > that works fine > or rm classes.dex > > > On Wed, Jan 1, 2014 at 12:30 PM, Daniel Skinner <[email protected]> wrote: > >> well the issue occurs regardless of switching. I originally was just >> using gen-idea and intellij and first runs would bomb while subsequent runs >> would succeed with only `android:set-debug`. Even if i rm the target/, >> project/target/, and project/project folders and `android:set-release` from >> a clean starting position, i can't get a proper release build. >> >> Right now im more interested in a workaround but I can't get an unsigned >> copy of the debug build to sign myself since there's no >> `android:sign-debug` task, though the actual log message almost suggests >> the produced *-unaligned.apk is unsigned, I'd assume its signed with my >> local debug key. >> >> >> On Wed, Jan 1, 2014 at 2:06 PM, Perry Nguyen <[email protected]> wrote: >> >>> indeed, I suppose the dex file might need to be removed for a release >>> build (when switching back and forth) >>> >>> >>> On Wed, Jan 1, 2014 at 10:52 AM, Daniel Skinner <[email protected]> wrote: >>> >>>> I'm guessing this is related here >>>> >>>> https://github.com/pfn/android-sdk-plugin/blob/master/src/tasks.scala#L947 >>>> >>>> >>>> On Wednesday, January 1, 2014 12:35:40 PM UTC-6, pfn wrote: >>>> >>>>> same rules are applied regardless of build type >>>>> >>>>> >>>>> On Wed, Jan 1, 2014 at 10:23 AM, Daniel Skinner <[email protected]>wrote: >>>>> >>>>>> I'm using the pfn/android-sdk-plugin and I don't think this is any >>>>>> fault of the plugin but i have an app that depends on >>>>>> https://code.google.com/p/aacdecoder-android/ which i already have >>>>>> compiled into a jar and dropped into libs. >>>>>> >>>>>> Debug builds work just fine but release builds cause the native lib >>>>>> to seg fault and having previously carried this over from a non-proguard >>>>>> project, I was thinking there are differing options set by the plugin >>>>>> based >>>>>> on build type (debug/release). >>>>>> >>>>>> I only noticed this single file in the repo for configuring proguard: >>>>>> https://github.com/pfn/android-sdk-plugin/blob/ >>>>>> master/resources/android-proguard.config >>>>>> >>>>>> but might i be on the right track here? Or does the plugin apply the >>>>>> same rules regardless of build type? Digging into the source now >>>>>> >>>>>> -- >>>>>> 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/groups/opt_out. >>>>>> >>>>> >>>>> -- >>>> 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/groups/opt_out. >>>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "scala-on-android" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/scala-on-android/y_O8oSwDDTo/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> 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/groups/opt_out. >> > > -- 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/groups/opt_out.
