{ "id": "174152", "key": "TIMOB-27411", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2019-09-19T21:41:49.000+0000", "priority": { "name": "None", "id": "6" }, "labels": [ "cb-tooling", "griffin-app" ], "versions": [], "issuelinks": [], "assignee": null, "updated": "2019-12-12T14:51:55.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [], "description": "Would be great to be able to have access to the iOS and Android properties that are defined in the tiapp.xml file. For some things like \"team-id\", a developer needs to define it again as either at different tiapp.xml property, config.json, or somewhere else in order to be able to use it when doing things like Keychain access.", "attachment": [], "flagged": false, "summary": "Allow access to iOS/Android properties from tiapp.xml", "creator": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "environment": null, "comment": { "comments": [ { "id": "451753", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "I'm not following. The Titanium build as well as Titanium CLI plugins have access to {{builder.tiapp.ios\\['team-id'\\]}}. There are no properties that are used that aren't explicitly defined.\r\n\r\nAre you talking about Alloy and it's old tiapp.xml parser?\r\n\r\nCan you describe in more detail your use case?", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2019-10-02T05:15:50.000+0000", "updated": "2019-10-02T05:15:50.000+0000" }, { "id": "451764", "author": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "body": "I was talking about from within the app code itself. Right now, in order to use the team-id, we need to store it in both properties and team-id elements in tiapp.xml.", "updateAuthor": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "created": "2019-10-02T15:09:49.000+0000", "updated": "2019-10-02T15:09:49.000+0000" }, { "id": "451767", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Oh, ok, then I have that use case covered. All of those properties like team-id and use-app-thinning should never have been their own tag, rather properties. I would have guessed that team-id would be only of interested during build. Interesting.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2019-10-02T15:30:13.000+0000", "updated": "2019-10-02T15:30:13.000+0000" }, { "id": "451768", "author": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "body": "Thanks! We have to have access to the team-id for stuff like keychain access", "updateAuthor": { "name": "bhouse", "key": "bhouse", "displayName": "Brenton House", "active": true, "timeZone": "America/Chicago" }, "created": "2019-10-02T15:33:42.000+0000", "updated": "2019-10-02T15:33:42.000+0000" } ], "maxResults": 4, "total": 4, "startAt": 0 } } }