Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Packaging error with no further info

Like so many others, I'm getting an error when attempting to package my app (in my case, for Android). I get just "Packaging Error" as the message with no further details. I'm sure I'm entering the password correctly. I've confirmed the alias using:

keytool -list -v -keystore MYKEYSTORE

Is there a log some place or some way to find out further what's causing this?

Titanium Developer 1.2.1 with SDK 1.4.1 (09/16/10 19:46 f634bc) on Windows. The app compiles and runs fine in the emulator and on my Droid.

— asked September 21st 2010 by Tim Poulsen
  • android
  • packaging
  • windows
0 Comments

5 Answers

  • Could I just sign the myapp-unsigned.apk file using jarsigner? See http://developer.android.com/guide/publishing/app-signing.html

    — answered September 22nd 2010 by Tim Poulsen
    permalink
    3 Comments

    • Yes, that's what we're trying to do automatically. You might try running Titanium Developer in debug mode. Launch it from the command line with –debug the trace in the console window may show more about what the error is.

      — commented September 22nd 2010 by Don Thorp

    • Here's what the debug mode says (password removed):

      [15:39:05:500] [Titanium.Process.Win32Process] [Debug] Launching: python.exe "C:
\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\nb14
1c\android\builder.py" distribute \"Door2Door\" "\"C:\Documents and Settings\Tim
 Poulsen\My Documents\android-sdk-windows\"" \"C:\titanium\Door2Door\" \"com.sky
panther.door2door\" "\"C:\Program Files\Java\jdk1.6.0_19\bin\door2doorkey.keysto
re\"" \"my_password\" \"d2d\" \"C:\tmp\" \"4\"
[15:39:05:546] [Titanium.Network.HTTPClient] [Debug] Changing readyState from 0
to 1 for url:https://api.appcelerator.net/p/v1/app-track
[15:39:05:562] [Titanium.Proxy] [Debug] Looking up proxy information for: https:
//api.appcelerator.net/p/v1/app-track
[15:39:05:562] [Titanium.Proxy] [Debug] Checking whether https://api.appcelerato
r.net/p/v1/app-track should be bypassed.
[15:39:05:578] [Titanium.Proxy] [Debug] No bypass
[15:39:05:578] [Titanium.Proxy] [Debug] Using direct connection.
[15:39:08:656] [Titanium.Network.HTTPClient] [Debug] Changing readyState from 1
to 2 for url:https://api.appcelerator.net/p/v1/app-track
[15:39:08:671] [Titanium.Network.HTTPClient] [Debug] Changing readyState from 2
to 3 for url:https://api.appcelerator.net/p/v1/app-track
[15:39:08:671] [Titanium.Network.HTTPClient] [Debug] Changing readyState from 3
to 4 for url:https://api.appcelerator.net/p/v1/app-track

      It output that and then gave me the same failure error message. I have no proxy server involved, just a direct connection to my router/cable modem. I haven't tried manually signing with jarsigner. But I'll try that next and report.

      Thanks!

      — commented September 22nd 2010 by Tim Poulsen

    • jarsigner and zipalign worked without any problems. … now, the worry sets in…do I go live with this manually created version or do the problems indicate something's wrong with my app?

      — commented September 22nd 2010 by Tim Poulsen

  • That usually occurs when one piece of information is incorrect, most commonly the alias. Please see the HowTo: Package for the Android Market

    — answered September 21st 2010 by Don Thorp
    permalink
    2 Comments

    • Thanks Don. But, I've checked with the keytool utility, so I know I'm using the right alias. And, I wouldn't be able to use keytool without the password so I know I have that right (besides, I have it saved in my KeePass database). I use the Browse buttons for the location and keystore location fields, so I know they're right too.

      If I close Developer, kill the adb.exe process, then restart the whole packaging procedure, it almost looks like the packaging might work. The error doesn't pop up…but, nothing happens either. After an hour and a half, no files were generated. Task Manager shows zero CPU usage by Developer though a slightly increasing memory usage over time (8K increase every 30 sec. or so); adb.exe also shows no CPU usage.

      — commented September 21st 2010 by Tim Poulsen

    • adb isn't used during signing. What is the expiration date on your key?

      — commented September 22nd 2010 by Don Thorp

  • Thanks Don. But, I've checked with the keytool utility, so I know I'm using the right alias. And, I wouldn't be able to use keytool without the password so I know I have that right (besides, I have it saved in my KeePass database). I use the Browse buttons for the location and keystore location fields, so I know they're right too.

    If I close Developer, kill the adb.exe process, then restart the whole packaging procedure, it almost looks like the packaging might work. The error doesn't pop up…but, nothing happens either. After an hour and a half, no files were generated. Task Manager shows zero CPU usage by Developer though a slightly increasing memory usage over time (8K increase every 30 sec. or so); adb.exe also shows no CPU usage.

    — answered September 21st 2010 by Tim Poulsen
    permalink
    0 Comments

  • Here's an excerpt of my key, good till 2038.

    Alias name: d2d
Creation date: Sep 10, 2010
Entry type: PrivateKeyEntry
Certificate chain length: 1
...
Valid from: Fri Sep 10 17:35:03 EDT 2010 until: Tue Jan 26 16:35:03 EST 2038
Certificate fingerprints:
    — answered September 22nd 2010 by Tim Poulsen
    permalink
    0 Comments

  • I tried upgrading to the newest nightly SDK build - no change

    I updated my Android SDK (new ver. 7 tools available) - no change

    I updated my Java SDK - no change

    I completely powered off & pulled the laptop's battery, then restarted. Then, I deleted everything in my project's build directory. With nothing but Developer & the emulator running, the build for distribution process actually worked!

    But now, even though the app runs in the emulator, it won't run on my droid. It worked just fine before. I've tried recompiling a few times, even with older SDKs, same result.

    — answered September 22nd 2010 by Tim Poulsen
    permalink
    2 Comments

    • Use the DDMS tool to see why it's not installing on the Droid. It's in the ADK/tools folder. You can monitor the log statements.

      — commented September 23rd 2010 by Don Thorp

    • Oh, it installs. But it just freezes. It's the GPS/geolocation code. As soon as I try to use the GPS data the app freezes. I've tried reverting to earlier nightly builds and release versions of the SDK but every one I've tried does the same thing. It used to work.

      — commented September 23rd 2010 by Tim Poulsen
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.