On Feb 21, 8:42 am, "Mark Murphy" <mmur...@commonsware.com> wrote:
> 1. Why are you "still not able to use an ant script to automate the
> build&sign process"?
>
> 2. If you aren't able to do #1, how do you know it "triggers the bug and
> gives you a corrupted apk"?

OK, to clarify: If the ant script is used to sign the apk, it might
produce a corrupted apk, i.e. throwing ClassCastException or
NullPointerException at some point.  This seems not happening all the
time though.  However, if I export an unsigned apk using Eclipse and
sign it manually on the exactly same source code, everything is fine.
So we had to give up using the ant script.

The only "fancy" thing we do in the build script is to copy an xml
that has the release Google Maps api key into res/values.  But I think
this should have no impact since the copy happens before compilation
and the R.java will be regenerated by the build script:


===================================
        <target name="copy-release-files">
                <copy file="${build.resources}/api-keys-release.xml" tofile="$
{resource-dir}/values/api-keys.xml" overwrite="true"/>
        </target>

    <target name="release" depends="copy-release-files, dex, package-
res">
===================================

=======================================
Buildfile: build.xml

copy-release-files:
     [copy] Copying 1 file to /workspaces/android-ws/theProject/res/
values

dirs:
     [echo] Creating output directories if needed...
    [mkdir] Created dir: /workspaces/android-ws/theProject/bin-build
    [mkdir] Created dir: /workspaces/android-ws/theProject/bin-build/
classes

resource-src:
     [echo] Generating R.java / Manifest.java from the resources...
     [exec]     (skipping hidden file 'res/drawable/.DS_Store')
  ...
=======================================

I'm not saying this is the same issue as the copy protection.  Just
they look very related.

> 3. Do you have a reproducible scenario you can publish with code? Or does
> the phenomenon only occur with this one app?

We have not put any effort to reproduce the problem in other code base
since we can still export and sign the apk manually without any
problems.  We will submit the code if we find a way to reproduce it.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to