{ "id": "115262", "key": "TIMOB-14068", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "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": "15116", "description": "2013 Sprint 11 BB", "name": "2013 Sprint 11 BB", "archived": true, "released": true, "releaseDate": "2013-06-03" }, { "id": "15109", "description": "2013 Sprint 11", "name": "2013 Sprint 11", "archived": true, "released": true, "releaseDate": "2013-06-03" }, { "id": "15478", "description": "Release 3.1.1", "name": "Release 3.1.1", "archived": true, "released": true, "releaseDate": "2013-06-17" }, { "id": "14982", "description": "Release 3.2.0", "name": "Release 3.2.0", "archived": false, "released": true, "releaseDate": "2013-12-19" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2013-05-31T21:40:18.000+0000", "created": "2013-05-31T00:14:09.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "qe-3.1.1", "qe-closed-3.1.1", "qe-testadded" ], "versions": [ { "id": "15478", "description": "Release 3.1.1", "name": "Release 3.1.1", "archived": true, "released": true, "releaseDate": "2013-06-17" }, { "id": "14982", "description": "Release 3.2.0", "name": "Release 3.2.0", "archived": false, "released": true, "releaseDate": "2013-12-19" } ], "issuelinks": [ { "id": "29199", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "115254", "key": "TIMOB-14061", "fields": { "summary": "The field service app fails to build for BlackBerry as the BB folder in resources gets deleted automatically", "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": "Low", "id": "4" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } }, { "id": "29210", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "115296", "key": "ALOY-681", "fields": { "summary": "Use CLI \"project\" hook to update app/assets platform-specific resources", "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" } }, "priority": { "name": "Medium", "id": "3" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } }, { "id": "29209", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "115295", "key": "TIMOB-14071", "fields": { "summary": "CLI: Add hook(s) for the \"project\" command", "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": "Low", "id": "4" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } } ], "assignee": { "name": "joshroesslein", "key": "joshroesslein", "displayName": "Josh Roesslein", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2014-02-20T23:57:24.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": "10230", "name": "BlackBerry", "description": "BlackBerry Platform" } ], "description": "Description:\r\n1. Create a default alloy app from the default templates in appcelerator studio without BB as target\r\n2. After the app is created enable BB in the tiapp.xml & save it (Note the blackberry folder gets created in the resources folder)\r\n3. Build & run for BB device/simulator\r\n\r\nActual Result:\r\n1. The build fails as the blackberry folder in resources gets deleted automatically\r\n\r\nExpected Result:\r\n1. The alloy app builds fine & runs as expected on the device/simulator", "attachment": [], "flagged": false, "summary": "Fail to run BlackBerry if the platform is enabled after alloy project is created", "creator": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "environment": "Environment:\r\nAPPC Studio : 3.1.1.201305292130\r\nTi BB SDK : 3.1.1.v20130529114554\r\nMac OSX : 10.8.2\r\nalloy: 1.1.2\r\nCLI : 3.1.1-alpha", "comment": { "comments": [ { "id": "255065", "author": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Checked with alloy 1.1.3-alpha & I can reproduce the issue.", "updateAuthor": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T00:55:38.000+0000", "updated": "2013-05-31T00:55:38.000+0000" }, { "id": "255081", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I can take a look if this is on Alloy's end. There's little chance it would have been a regression though. This would undoubedtly have been present in alloy 1.1.2.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T01:32:15.000+0000", "updated": "2013-05-31T01:32:15.000+0000" }, { "id": "255089", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I was able to reproduce using Lokesh's instructions.\r\n\r\nI don't think the source of this issue is Alloy though. I followed a similar set of instructions to Lokesh's as such:\r\n\r\n# Create a default alloy app from the default templates in appcelerator studio without BB as target\r\n# After the app is created enable BB in the tiapp.xml & save it (Note the blackberry folder gets created in the resources folder)\r\n# Instead of \"build & run\" in studio, which can cloud the issue's origin, I specifically ran the Alloy compile by hand to see if it caused the deletion of the Blackberry Resources folder. I did this:\r\n\r\n{code}\r\nalloy compile --config platform=blackberry\r\n{code}\r\n\r\nThe result was that the app successfully compiled for Alloy and that both the \"app/assets/blackberry\" and \"Resources/blackberry\" folders' contents remained intact. This leads me to believe that the issue lies with either Studio or some characteristic of the Blackberry build process that only occurs when Blackberry support is added after project creation via studio.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T01:52:17.000+0000", "updated": "2013-05-31T01:53:53.000+0000" }, { "id": "255093", "author": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "body": "This looks to be a CLI issue. Here is what we see:\n\n# When an alloy project is created without BB, the app/assets/blackberry folder is empty. By contrast, the android, iphone, and mobileweb folders have images and icons even when their respective deploy targets are not selected during project creation.\n# After the alloy project with BB is created, when BB is enabled via tiapp.xml, the following command is run:\n\n{code}\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"--no-banner\" \"project\" \"--sdk\" \"3.1.1.v20130530171546\" \"--project-dir\" \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb\" \"deployment-targets\" \"blackberry,tizen,mobileweb,android,iphone,ipad\"\n{code}\n\nThe command will copy the assets to Resources/blackberry directory correctly, but app/assets/blackberry folder is still empty.\n\n# Then when project is run on BB simulator, it would fail on the packaging part. This happens from command line as well.\n# After we manually add the images to app/assets/blackberry directory, running on BB simulator would work.\n", "updateAuthor": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T02:16:15.000+0000", "updated": "2013-05-31T02:16:15.000+0000" }, { "id": "255095", "author": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "body": "More on the sequence of commands Studio runs, and I tried them in order from the command line:\n\n# First project creation:\n\n{code}\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"--no-banner\" \"create\" \"--platforms\" \"ios,android,mobileweb,tizen\" \"--type\" \"app\" \"--id\" \"testbb.test\" \"--sdk\" \"3.1.1.v20130530171546\" \"--workspace-dir\" \"/Users/mxia/Documents/Titanium_Studio_Workspace\" \"--name\" \"testbb\" \"--verbose\" \"--force\"\n{code}\n\nThe project is created, and there is no app folder, and that is expected.\n\n# Then we run \"alloy new\":\n\n{code}\n\"/usr/local/bin/alloy\" \"new\" \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb\" \"default\"\n{code}\n\nAfter running this from command line, app folder is created, along with individual platform as sub-directories. However, android, iphone, and mobileweb under assets have contents, while app/assets/blackberry has no content. And I think that's the problem.\n", "updateAuthor": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T02:23:52.000+0000", "updated": "2013-05-31T02:23:52.000+0000" }, { "id": "255097", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~mxia] alloy will attempt to grab the existing contents of the Resources folder for a particular platform and move it into that platforms' \"app/assets/PLATFORM_NAME\" folder when you do \"alloy new\". If there is no \"Resources/blackberry\" folder contents when you call \"alloy new\", then alloy has nothing to try and populate it with. The \"Resources/blackberry\" folder needs to be present and populated before calling \"alloy new\". Does that make sense?", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T02:33:51.000+0000", "updated": "2013-05-31T02:33:51.000+0000" }, { "id": "255108", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Is this really BB specific? Would the same thing happened if you added on new platform of any stripe to an existing project? If we add a new platform to a project, it seems we then also need to call some alloy command to move over the resources, no?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T04:41:50.000+0000", "updated": "2013-05-31T04:41:50.000+0000" }, { "id": "255109", "author": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Copied from my email:\n\nHigh level points:\n\n# It is reproducible from command line using the same set of commands Studio runs, so it is not an Appcelerator Studio specific issue;\n# The issue happens when BlackBerry is not included in the initial project creation but added later through tiapp.xml; it does not happen when BlackBerry is included in the initial project creation.\n\nMore detailed investigation:\n\n1. When user creates the project with selected platforms, the following command is run:\n\n{code}\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"--no-banner\" \"create\" \"--platforms\" \"ios,android,mobileweb,tizen\" \"--type\" \"app\" \"--id\" \"testbb.test\" \"--sdk\" \"3.1.1.v20130530171546\" \"--workspace-dir\" \"/Users/mxia/Documents/Titanium_Studio_Workspace\" \"--name\" \"testbb\" \"--verbose\" \"--force\"\n{code}\n\nAt the end of the run, Resources folder contains the following files and directories:\n\n-rw-r--r-- 1 mxia staff 1158 May 30 21:21 KS_nav_ui.png\n-rw-r--r-- 1 mxia staff 1074 May 30 21:21 KS_nav_views.png\ndrwxr-xr-x 5 mxia staff 170 May 30 21:21 android\n-rw-r--r-- 1 mxia staff 1164 May 30 21:21 app.js\ndrwxr-xr-x 8 mxia staff 272 May 30 21:21 iphone\ndrwxr-xr-x 5 mxia staff 170 May 30 21:21 mobileweb\ndrwxr-xr-x 3 mxia staff 102 May 30 21:21 tizen\n\nThere is no blackberry directory since BB isn't included; expected result.\n\n2. Then this command is run:\n\n{code}\n\"/usr/local/bin/alloy\" \"new\" \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb\" \"default\"\n{code}\n\nThis creates the app directory under project root. It has an \"assets\" folder, which in turn contains android, iphone, blackberry, and mobileweb. Only the blackberry one is empty. From Tony's latest comment in the ticket, this is expected as well since Resources/blackberry folder is not there.\n\n3. Now user enables BlackBerry in the tiapp.xml and saves, the following command is called:\n\n{code}\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"--no-banner\" \"project\" \"--sdk\" \"3.1.1.v20130530171546\" \"--project-dir\" \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb\" \"deployment-targets\" \"blackberry,tizen,mobileweb,android,iphone,iPad\"\n{code}\n\nIt copies the BB assets from the SDK to the Resources directory so Resources/blackberry/ folder contains content. The app/assets/blackberry folder remains empty.\n\n4. Finally Studio runs the build command:\n\n{code}\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"build\" \"--platform\" \"blackberry\" \"--sdk\" \"3.1.1.v20130530171546\" \"--log-level\" \"trace\" \"--target\" \"simulator\" \"--ndk\" \"/Applications/bbndk\" \"--ip-address\" \"192.168.163.135\"\n{code}\n\nAnd here are the outputs at the end:\n\n[Command] :source /Applications/bbndk/bbndk-env.sh && blackberry-deploy -installApp -launchApp -device 192.168.163.135 -package \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb/build/blackberry/x86/o-g/testbb.bar\" \nError: Command failed: Warning: Using default icon: /Applications/bbndk/host_10_1_0_132/darwin/x86/usr/samples/icons/blackberry-tablet-default-icon.png\nError: Attribute image: file cannot be found in the list of packaged files: assets/splash-600x1024.png \n\nWarning: Using default icon: /Applications/bbndk/host_10_1_0_132/darwin/x86/usr/samples/icons/blackberry-tablet-default-icon.png\nError: Attribute image: file cannot be found in the list of packaged files: assets/splash-600x1024.png \n\n\nError: Command failed: Error: File does not exist or not a file or cannot read: /Users/mxia/Documents/Titanium_Studio_Workspace/testbb/build/blackberry/x86/o-g/testbb.bar \n\nError: File does not exist or not a file or cannot read: /Users/mxia/Documents/Titanium_Studio_Workspace/testbb/build/blackberry/x86/o-g/testbb.bar \n\n\nIf we check the Resources/blackberry/ folder now, it becomes empty again. My suspicion is that the build script copies from assets folder instead of respecting the existing content in Resources, thus wiping it out since assets folder is empty.\n\nThe solution to me seems to be that we should call \"alloy new\" again after step 3 to copy the content from Resources to assets again; however, I tried that from command line and it failed because app folder already exists. Then the next suggestion is for the build script to respect the existing content in Resources if they don't exist in the corresponding assets folder. Either way, we would need help from the platform team since Studio doesn't call \"alloy new\" directly or interfere with the build command.\n", "updateAuthor": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T05:02:20.000+0000", "updated": "2013-05-31T05:02:20.000+0000" }, { "id": "255110", "author": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I also checked to see if it's a BB specific issue by calling the project create command with only android specified. In that case, \"alloy new\" will still generate content under app/assets/iphone and app/assets/mobileweb even though only Resources/android exists, so the process works. For tizen, the app/assets/tizen folder doesn't exist either, but it doesn't appear to affect the build command, as it succeeds anyway.\r\n", "updateAuthor": { "name": "mxia", "key": "mxia", "displayName": "Michael Xia", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T05:03:03.000+0000", "updated": "2013-05-31T05:07:46.000+0000" }, { "id": "255152", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "So I can make a change to Alloy to add the SDK's Resources for BB like I have for iphone, android, and mobileweb, *BUT* this only helps when \"alloy new\" is called, which should not be called every time a new platform is added to a project. This would, as its name states, create a new Alloy project from scratch, using the given template. So if this was an existing project with work in it, it would get blown away. So \"alloy new\" should not be part of Studio's workflow every time someone adds a platform to an existing project, only on initial project creation. So, while this is an important note, I don't think it solves this issue.\r\n\r\nWe have a couple options, let me know what you guys think, or of you think there's a possible solution I'm missing. [~ingo] I know you generally like having the \"fast\" and \"right\" way to evaluate, so...\r\n\r\nh3. fastest way\r\n\r\nWhenever Studio adds BB as a new platform to a project, it adds the \"blackberry\" folder to both \"Resources\" and \"app/assets\". \r\n\r\n*pros:* quick, and requires a change to only one project (Studio)\r\n*cons:* Doesn't account for the CLI\r\n\r\nh3. longer, better way\r\n\r\nAlloy implements a new command for adding new platforms relying on assets contained in alloy itself. So instead of Studio calling \"alloy new\", which is dangerous after initial project creation, Studio would call \"alloy platform add blackberry\", or something like that, which would then populate the \"app/assets/blackberry\" folder.\r\n\r\n*pros:* could be done in studio or CLI\r\n*cons:* now requires change to both Alloy and Studio\r\n\r\nh3. even longer, even better way\r\n\r\nThe CLI exposes a hook for the completion of this very long command (I believe \"project\" is the command name):\r\n\r\n{code}\r\n\"/usr/local/bin/titanium\" \"--no-colors\" \"--no-prompt\" \"--no-banner\" \"project\" \"--sdk\" \"3.1.1.v20130530171546\" \"--project-dir\" \"/Users/mxia/Documents/Titanium_Studio_Workspace/testbb\" \"deployment-targets\" \"blackberry,tizen,mobileweb,android,iphone,iPad\"\r\n{code}\r\n\r\nAlloy modifies its current hook to read this input, and make sure \"app/assets\" folders are supplied for any platform specified if the \"project\" command is adding \"deployment-targets\". \r\n\r\n*pros:* Studio and CLI are covered and there's no manual alloy step for anyone anymore\r\n*cons:* not a quick fix", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T12:18:08.000+0000", "updated": "2013-05-31T12:34:17.000+0000" }, { "id": "255155", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~tlukasavage] Can you give an estimate on how long the three options would take from your perspective?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T12:47:40.000+0000", "updated": "2013-05-31T12:47:40.000+0000" }, { "id": "255184", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~ingo]\n\noption 1: no time from my perspective (all work is in studio's court here)\noption 2: a couple hours (plus Studio's estimate of time)\noption 3: to be comfortable with its stability, about a day since changing the hook potentially impacts every Alloy app (lots of testing). But I couldn't even start it before this hook was added to the CLI, and obviously whatever version of the CLI supports it would be necessary.\n\nThere is however a 4th option which would likely be faster than all the other and would put the work on the BB platform, which makes sense since it is the new kid on the block in this scenario. Can't BB just handle the scenario where it doesn't have the appropriate files in its \"Resources/blackberry\" folder? Again, like option #1, not ideal, but quick and covers this situation.\n\nTo be clear, option #3 is the way to go long term. It just introduces a lot more variables and potential for regression at this late point in the game than does option #1 or #4. ", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T17:13:45.000+0000", "updated": "2013-05-31T17:13:45.000+0000" }, { "id": "255195", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "To be clear on option #4, the BB build process should copy the necessary assets to both \"Resources/blackberry\" and \"app/assets/blackberry\". With the assets in both folders, it ensures that the app is back in sync and that further files can be added to the \"app/assets/blackberry\" folder going forward in the app's development.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T17:41:28.000+0000", "updated": "2013-05-31T17:41:28.000+0000" }, { "id": "255244", "author": { "name": "joshroesslein", "key": "joshroesslein", "displayName": "Josh Roesslein", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Russ and myself sat down and came up with a solution in BlackBerry CLI.\nA pull request [#65|https://github.com/appcelerator/titanium_mobile_blackberry/pull/65] is up for review now.\nThis makes the CLI more gracefully handle a missing BlackBerry resources folder by falling back to the SDK templates directory.", "updateAuthor": { "name": "joshroesslein", "key": "joshroesslein", "displayName": "Josh Roesslein", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T20:02:38.000+0000", "updated": "2013-05-31T20:02:38.000+0000" }, { "id": "255264", "author": { "name": "joshroesslein", "key": "joshroesslein", "displayName": "Josh Roesslein", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Pedro discovered another problem if the project's Resources/blackberry contains a file (ex: .npmignore).\nI tweaked the way we fall back to using the default resources in the SDK if they are missing in the project.\nPull request is ready and Pedro will be reviewing and testing it shortly.", "updateAuthor": { "name": "joshroesslein", "key": "joshroesslein", "displayName": "Josh Roesslein", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-05-31T21:20:51.000+0000", "updated": "2013-05-31T21:20:51.000+0000" }, { "id": "255598", "author": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Verified the fix in both titanium studio & appcelerator studio & now able to successfully run alloy apps in which BB target has been added after the app has been created.\r\n\r\nEnvironment:\r\nTi Studio : 3.1.1.201305312303\r\nAppcel Studio : 3.1.1.201306031002\r\nTi BB SDK : 3.1.1.v20130531163723\r\nMac OSX : 10.8.2\r\nAlloy : 1.1.3-cr\r\nCLI - 3.1.1-cr\r\nZ10 BB simulator : 10.0.10.822\r\nZ10 device running 10.0.10.88\r\n", "updateAuthor": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2013-06-03T21:06:05.000+0000", "updated": "2013-06-03T21:06:05.000+0000" } ], "maxResults": 16, "total": 16, "startAt": 0 } } }