Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-16901] iOS: Custom Archive location not working

GitHub Issuen/a
TypeImprovement
PriorityHigh
StatusOpen
ResolutionUnresolved
Affected Version/sRelease 3.2.1
Fix Version/sn/a
ComponentsCLI
Labelscb-tooling, supportTeam
ReporterMarco Cota
AssigneeChris Barber
Created2014-04-30T19:18:26.000+0000
Updated2018-05-06T23:51:23.000+0000

Description

Issue

When setting a custom location for the archive files in Xcode and building from Studio the file is saved in the default location /Users/username/Library/Developer/Xcode/Archives instead of the new directory making the archive file unavailable for the organizer.

Steps to repro

Open Xcode Preferences Modify Archive directory in Locations to /Users/username/documents/archive In Studio package an app for iTunes Store Expected Results: The .xcarchive file will be created in the custom directory /Users/username/documents/archive and will be available in the Xcode Organizer for Validation and Upload Actual Results: The .xcarchive file is created in the default directory /Users/username/Library/Developer/Xcode/Archives and is not available for the Xcode Organizer to be validated.

Comments

  1. Ingo Muschenetz 2014-04-30

    Is this related to an existing ticket?
  2. Praveen Innamuri 2014-04-30

    I don't recollect there is an existing ticket for this issue. Also, I think this issue should be handled through CLI.
  3. Hans Knöchel 2016-10-03

    This is caused by [this hardcoded line](https://github.com/appcelerator/titanium_mobile/blob/master/iphone/cli/hooks/package.js#L40). -I'm wondering what Studio does with the custom path.- The custom path is set [here](https://github.com/appcelerator/titanium_mobile/blob/master/iphone/cli/hooks/package.js#L192) and could be used above as well.
  4. Chris Barber 2016-10-03

    I've already labeled this issue as cb-tooling and it will be addressed in the next build system.
  5. Hans Knöchel 2016-10-03

    Ohh, that's what it's for. Alright then! The change is a one-liner, but that's also fine!

JSON Source