Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24475] Android: Cannot Package app for Play Store after updating to Titanium SDK 6.0.2.GA

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionNot Our Bug
Resolution Date2017-03-12T16:15:19.000+0000
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelsn/a
ReporterJames Childs
AssigneeShak Hossain
Created2017-03-10T18:56:33.000+0000
Updated2017-03-29T20:54:57.000+0000

Description

Steps to Reproduce

I was running Titanium SDK 6.0.1.GA. I decided to install the update 6.0.2.GA before packaging for the Android Store. After the update and testing the app with the new SDK version, I decided to package the app. After getting prompted for the necessary properteis such as directory and keystore properteis, and presented with an error saying Android SDK 4.4.2 was not found (See android_build_error1 attachment). I hit OK and the packaging stops. I have Android SDK 4.4.2 installed and it shows as installed when I go to the Install SDK page from preferences (see android_installed_sdk attachement)

Actual Result

An error saying Android SDK 4.4.2 was not found is thrown, and teh packaging stops

Expected Result

The app would be package for dsitribution properly without any errors.

Attachments

FileDateSize
.log2017-03-10T18:56:40.000+00005751979
android_build_error1.tiff2017-03-10T18:56:50.000+000082914
android_installled_sdk.tiff2017-03-10T18:56:49.000+0000160300
diagnostic1607098197835906901.log2017-03-10T18:56:47.000+0000255790

Comments

  1. James Childs 2017-03-11

    Hello, I was able to get around this issue and successfully package the app for the Google Play store. To resolve the issue I uninstall and reinstalled Android API 4.4.2. After reading that a similar issue existed with Android Studio and that it might cache related, I decided to uninstall and reinstall the API.
  2. Hans Knöchel 2017-03-12

    Thanks for the info! Will resolve then.
  3. Lee Morris 2017-03-29

    Closing ticket as it has been established that the issue is not our bug.

JSON Source