{ "id": "149467", "key": "TIMOB-19178", "fields": { "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "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": [ { "id": "14826", "description": "Release 5.1.0-remaining iOS9 features, Android M features", "name": "Release 5.1.0", "archived": false, "released": true, "releaseDate": "2015-11-20" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2015-09-14T22:44:37.000+0000", "created": "2015-07-06T20:47:37.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "qe-4.1.0" ], "versions": [ { "id": "16723", "description": "Windows Platform Support, ListView updates, Vector overlays in maps", "name": "Release 4.1.0", "archived": false, "released": true, "releaseDate": "2015-07-08" } ], "issuelinks": [ { "id": "48773", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "150653", "key": "TISTUD-7682", "fields": { "summary": "Update Windows SDK Preference Page to use Windows Publisher ID", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "subtask": false } } } } ], "assignee": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "updated": "2015-09-25T16:51:50.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "12642", "name": "Windows", "description": "Windows authoring support" } ], "description": "h5.Description\r\n\r\nCurrently the Windows platform is using the id tag within the tiapp.xml in order to populate the Package/Identity/Name of the app. The Package/Identity/Name is given to the user by Microsoft when the app is created on the Windows developer dashboard, an example is 55769Appcelerator.pkgTest, the section before period is the same for every app created with the same account and the section after the period is the name of the app.\r\n\r\nIn order to pass the Windows certification test the designated app id must be present, however when building for Android the Windows app id is not a valid id as it begins with a number.\r\n\r\nThere should be a tag within the section of the tiapp.xml that is used to populate the Package/Identity/Name section for the app, allowing the same app to be published across multiple platforms with the same tiapp.xml\r\n\r\nh5.Steps to reproduce\r\n\r\n1. Package an app for Windows phone without setting the id property to the id given from Microsoft\r\n2. Upload the app to the dashboard on dev.windows.com\r\n3. Change the id to match the property and repeat 1-2\r\n4. Attempt to package for Android\r\n\r\nh5.Actual result\r\n\r\n2. When validating the package the validation will fail\r\n3. The validation will pass\r\n4. The packaging will fail\r\n\r\nh5.Expected result\r\n\r\nA developer should not have to change the tiapp.xml values between packaging for different platforms", "attachment": [], "flagged": false, "summary": "Windows: Add tiapp property for windows app ID", "creator": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "subtasks": [], "reporter": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "environment": "Windows 8.1\r\nAppc CLI (NPM): 4.1.0-1\r\nAppc CLI (Registry): 4.1.0-5\r\nTi SDK: 4.1.0.v20150706111546", "closedSprints": [ { "id": 482, "state": "closed", "name": "2015 Sprint 17 Windows", "startDate": "2015-08-15T04:01:00.000Z", "endDate": "2015-08-29T03:59:00.000Z", "completeDate": "2015-08-28T13:51:24.221Z", "originBoardId": 144 }, { "id": 492, "state": "closed", "name": "2015 Sprint 19 Windows", "startDate": "2015-09-13T04:01:57.811Z", "endDate": "2015-09-26T03:59:00.000Z", "completeDate": "2015-09-25T17:02:02.836Z", "originBoardId": 144 } ], "comment": { "comments": [ { "id": "358175", "author": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "body": "So I think even if we could use some sort of prefix to work around the use of leading digits in the app id, we have an issue of existing Android apps (and likely iOS) apps that the developers then add Windows support for - and the Windows Store assigns some new appid. According to this, the external appid must remain constant _forever_ or the app will be treated as new and lose ratings/counts/etc: http://tools.android.com/tech-docs/new-build-system/applicationid-vs-packagename\r\n\r\nIt seems like even if we could magically find some way to get one appid to \"work\" on all platforms there's the issue of needing to specify different values for different platforms for existing apps - and also the issue of users picking an appid to use at the beginning of the process for Android/iOS and getting one assigned by the store for Windows.", "updateAuthor": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "created": "2015-07-22T21:16:03.000+0000", "updated": "2015-07-22T21:16:03.000+0000" }, { "id": "358356", "author": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "body": "cc [~pinnamuri] - If we go forward with an overriding tiapp id per-platform underneath the platform tag, this will impact Studio in some way - either the schema used to validate tiapp.xml, and/or if we want some Ui to surface platform-specific values.", "updateAuthor": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "created": "2015-07-27T15:39:02.000+0000", "updated": "2015-07-27T15:39:02.000+0000" }, { "id": "362765", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "Reopening ticket:\r\n\r\nWindows 8.1\r\nAppc CLI Core: 5.0.0-50\r\nAppc CLI NPM: 4.2.0-1\r\nTitanium SDK : 5.0.0.v20150909153915\r\nNokia Lumia 930 8.1\r\n\r\nWhen adding the app ID using the below, I still get the original app ID specified in the tiapp.xml\r\n\r\n{code}\r\n\r\n com.test\r\n\r\n{code}", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2015-09-10T18:16:37.000+0000", "updated": "2015-09-10T18:16:37.000+0000" }, { "id": "363847", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "My suggestion is we now defer this to 5.0.1.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2015-09-14T22:28:47.000+0000", "updated": "2015-09-14T22:28:47.000+0000" }, { "id": "363851", "author": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "body": "I intentionally am only using the windows specific app id for Windows store submission, not for analytics or Ti.App.id or anything else. My thought was that we want to still use the cross-platform Tiatnium appid for this app in our own APIs and analytics data - and that this value is specifically meant to only allow you to specify the correct Windows Store-assigned id for Windows Store submission.", "updateAuthor": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "created": "2015-09-14T22:37:56.000+0000", "updated": "2015-09-14T22:37:56.000+0000" }, { "id": "364078", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "Verified using:\r\n\r\nWindows 8.1\r\nAppc CLI Core: 5.0.0-55\r\nAppc CLI NPM: 4.2.0-8\r\nTitanium SDK : 5.0.0.v20150915230722\r\nLumia 930 (8.1)\r\n\r\nWhen using the below the ID specified will be used for the PACKAGE_GUID for a Windows project and pass the analysis on upload to dev.windows.com. As expected when querying the appID using Ti.App.id the original ID specified is returned.\r\n\r\n{code}\r\n\r\n 64475EwanHarris.pkgTest2\r\n\r\n{code}\r\n\r\nClosing ticket", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2015-09-16T13:57:51.000+0000", "updated": "2015-09-16T13:57:51.000+0000" } ], "maxResults": 10, "total": 10, "startAt": 0 } } }