Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1098769
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T00:37:47+00:00 2026-05-17T00:37:47+00:00

I configured my android project to use ant. When building using the keyword release

  • 0

I configured my android project to use ant. When building using the keyword release it fails with this message:

java.lang.NullPointerException
at com.android.ant.ApkBuilderTask.execute(ApkBuilderTask.java:239)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

It fails on build.xml line 249 which is included here:

<macrodef name="package-helper">
    <attribute name="sign.package" />
    <element name="extra-jars" optional="yes" />
    <sequential>
        <apkbuilder
             outfolder="${out.absolute.dir}"
             basename="${ant.project.name}"
             signed="@{sign.package}"
             debug="${manifest.debuggable}"
             verbose="${verbose}">  **LINE 249 IS HERE**
           <file path="${intermediate.dex.file}" />
           <sourcefolder path="${source.absolute.dir}" />
           <sourcefolder refid="android.libraries.src" />
           <jarfolder path="${external.libs.absolute.dir}" />
           <jarfolder refid="android.libraries.libs" />
           <nativefolder path="${native.libs.absolute.dir}" />
           <nativefolder refid="android.libraries.libs" />
           <extra-jars/>
        </apkbuilder>
    </sequential>
</macrodef>

That is called from line 401 which contains these lines:

<target name="-package-release" depends="-dex, -package-resources">
    <package-helper sign.package="false" />
</target>

It looks like there is some problem with ApkBuilderTask.java but I don’t know how/where to get the source of ApkBuilderTask.java. Has anyone run into this problem and found a solution? I’m using android SDK tools revision 7 if that helps.

Note: Running “ant debug” or “ant release” all comes out to the same result.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T00:37:48+00:00Added an answer on May 17, 2026 at 12:37 am

    This is a change introduced in the r7 tools. You need to update the <apkbuilder> task in your build.xml, in the ways that saturnine points out above.

    Given that this error only happens when you customize your build.xml, I think you need to go back and redo the customizations. If you look for $ANDROID_SDK/tools/ant/ant_rules_r3.xml and paste them into your build.xml (replacing the definitions that you pasted in last time), it should fix your problems.

    You may be able to get away without customizations, as the new version of the rules are far more customizable, and include -pre-compile and -post-compile hooks.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.