udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It's possible for an iOS or WatchOS Simulator to be deleted, but the device directory to remain. The current ioslib only detects simulators by walking the filesystem. This leads to an inconsistent state.    Instead, we should just eat the cost of subprocessing simctl. I think we're still going to have to read each device's plist file to get additional info."
Answer: 1814943.0

User story: "Investigate why certain tests fail on Windows Desktop, recently we have needed to disable a number of tests that have prevented the Jenkins builds from passing. We should investigate into why this is happening and try to re-enable the test cases that previously failed."
Answer: 72424.0

User story: - Team id is now required in the tiapp.xml when building an app with a watch extension and Xcode 8.  - Added build configuration settings for swift files in watch apps  Namely set the "SWIFT_VERSION" to "2.2", if it's not already set... all new Watch extension projects will have this set to "3.0"  - Removed old watchos2 template in favor of existing watchos2-objc template.  - Set default min iOS SDK version to 8.0 if not explicitly set in the tiapp.xml and compiling using Xcode 8.  - Removed old maintainers from package.jsons.
Answer: 491.0

User story: "Currently we are manipulating VS project file (.vcxproj) manually to update {{DefaultLanguage}} configuration at  [generate.js|https://github.com/<USER>titanium_mobile_windows/blob/master/cli/commands/_build/generate.js#L110], but we could let CMake to generate it by setting [VS_GLOBAL_variable|https://cmake.org/cmake/help/v3.0/prop_tgt/VS_GLOBAL_variable.html]."
Answer: 4844.0

User story: "Async HTTPClient (TIMOB-23678) introduces crash at NMocha test on Windows 10 Desktop. We disabled it temporary because it works well on mobile devices. We want to revisit it to find out why it crashes on desktop."
Answer: 30260.0

User story: "The {{build/docs.js}} script needs amending to take into account the {{WindowsOnly}} folder when generating the parity report and {{api.jsca}} file used for documentation."
Answer: 3718.0

User story: "With Titanium SDK 5.4.0 and 6.0.0 being different with respect to modules (especially Android), we need a better way to maintain the Hyperloop modules.    Creating a branch 1_2_X in Hyperloop Repo. This is for TiSDK 5.4.0+    Master branch in Hyperloop Repo will effectively be 2_0_X until it's needed to be branched. This is for TiSDK 6.0.0+"
Answer: 1321.0

User story: "Implement {{Titanium.Network.Socket}} methods and properties.    http://docs.<USER>com/platform/latest/#!/api/Titanium.Network.Socket"
Answer: 428355.0

User story: When running Fortify code analysis against the SDK the usage of "password" in comments where detected in the following files.    Reachability.m  TiUIAlertDialogProxy.m    It is recommended these comments be removed as some tools would identity them as providing information disclosure.
Answer: 1092.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: h6.Reproduce  1. If you have following method in custom SDK.  {code:title=TestLib.h}  #import <Foundation/Foundation.h>    @interface TestLib : NSObject     // Takes pointer to NSInteger as third argument to store result  +(void)addNumber: (NSInteger)num1 with:(NSInteger)num2 result:(NSInteger*)result;    @end  {code}  2. And call it in a app like following  {code}  var result = 0;         TestLib.addNumberWithResult(1, 2, result); // throws [NSInvocation setArgument:atIndex:]: NULL address argument error                   // TestLib expects a pointer to NSInteger as third argument      alert('Result: ' + result);  {code}    3.Then you will get error like following which seems hyperloop do not recognise the pointer to NSIntege or NSUInteger.  {code}  -[NSInvocation setArgument:atIndex:]: NULL address argument   [ERROR] : Script Error {   [ERROR] : column = 26;   [ERROR] : description = "-[NSInvocation setArgument:atIndex:]: NULL address argument";   [ERROR] : line = 98;   [ERROR] : message = "-[NSInvocation setArgument:atIndex:]: NULL address argument";   [ERROR] : name = NSInvalidArgumentException;   {code}    h6.Note  Note sure is this expected. If yes, please change this to a feature request ticket since customer try to use a RSA SDK, but can't do it because of the above issue.
Answer: 1251227.0

User story: "GCM [https://developers.google.com/cloud-messaging/faq] is going to be eventually deprecated for FCM [https://firebase.google.com/docs/cloud-messaging/]    We should be prepared for this and look and identify what different projects/parts we need to update."
Answer: 908619.0

User story: "Customer get the following problem, One specific device (belong to a their client) get incompatible problem when try to download app from google store. (attached screen)    But I can't find any reason why, they did no use any <user-feature> tage.     Please help to address this, or and idea will be help. (attached tiapp.xml file and Androidmanifest.XML file in case)    Device Info  Model: Vodacom Smart Kicka  Location:  South Africa  Android version: Android 4.4 Kitkat"
Answer: 1275466.0

User story: "The build page says the Windows Download includes Android and Mobile Web. It of course also includes Windows Phone, but it doesn't tell. It should be added."
Answer: 6413.0

User story: "Our current Module CI scripts assume building against an older SDK version with an older module API version for Android (something like 5.2.1.GA). We need to be able to build against master/6.0.0 builds of the SDK against the updated V8 APIs."
Answer: 191572.0

User story: "ti.urbanairship: https://github.com/<USER>modules/ti.urbanairship    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 37374.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "ti.touchid: https://github.com/<USER>modules/ti.touchid    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 14442.0

User story: "ti.paypal: https://github.com/<USER>modules/ti.paypal    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 194736.0

User story: "ti.omniture: https://github.com/<USER>modules/ti.omniture    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 28444.0

User story: "ti.moddevguide: https://github.com/<USER>modules/ti.moddevguide    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 39873.0

User story: "ti.map: https://github.com/<USER>modules/ti.map    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 14438.0

User story: "ti.ldap: https://github.com/<USER>modules/ti.ldap    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 28448.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "ti.imagefactory: https://github.com/<USER>modules/ti.imagefactory    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 20290.0

User story: "ti.geofence: https://github.com/<USER>modules/ti.geofence    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 15462.0

User story: "ti.facebook: https://github.com/<USER>modules/ti.facebook    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 14449.0

User story: "ti.crypto: https://github.com/<USER>modules/ti.crypto    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 16648.0

User story: "ti.compression: https://github.com/<USER>modules/ti.compression    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 20290.0

User story: "ti.cloudpush.mqtt: https://github.com/<USER>modules/ti.cloudpush.mqtt    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 35641.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "ti.admob: https://github.com/<USER>modules/ti.admob    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 20294.0

User story: "cloudpush: https://github.com/<USER>modules/cloudpush    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 14453.0

User story: "<USER>syncserver.client: https://github.com/<USER>modules/<USER>syncserver.client    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 492473.0

User story: "<USER>https: https://github.com/<USER>modules/<USER>https    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 28346.0

User story: "<USER>encrypteddatabase: https://github.com/<USER>modules/<USER>encrypteddatabase    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 18117.0

User story: "<USER>apm: https://github.com/<USER>modules/<USER>apm    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 28839.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "<USER>aca: https://github.com/<USER>modules/<USER>aca    Generally this requires some minor changes to each module:  - bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  - bump the module's apiversion to 3 (for Android)  - bump the minsdk to 6.0.0 (for Android)  At a higher level, we'll need to update our CI build scripts for modules to use the master branch SDK to build against, and Android NDK r11c."
Answer: 28840.0

User story: "h6.Reproduce:  1. Create a default mobile project  2. add following code to app.js  {code}  var win = Ti.UI.createWindow({   backgroundColor:'white'  });    var webview = Titanium.UI.createWebView({url:'voyasso.html',ignoreSslError :true});    win.add(webview);    win.open();  {code}  3. add the following html page to project (Moved into comment as it contain sensitive info)  4. Run the project on iOS device or simulator    h6.Actual Result:  (Check statement as it might contain sensitive info)    h6.Expected Result:  Since the APT is false in default, the url should load up."
Answer: 32015.0

User story: "h5.Description    The current bundled CMake does not support the next version of Visual Studio.    *The latest version of CMake does not support this yet also, see* https://gitlab.kitware.com/cmake/cmake/issues/16143     Once the above is updated then [this|https://github.com/<USER>titanium_mobile_windows/blob/master/cli/commands/_build/initialize.js#L58] will need to be updated also  "
Answer: 389785.0

User story: "For the release 6.0.0, we want to follow the way to use the previous version that is available before the most recent version. In this case, there will be Xcode 8 available for the Ti-SDK release 6.0.0 so we increase the minimum Xcode version from 7.0 to 7.3."
Answer: 14412.0

User story: "Now that we have a common tests suite that passes on iOS and Android, we need to set up a Pull Request builder for titanium_mobile jobs so that we can run our unit test suite as part of every PR."
Answer: 23496.0

User story: "iOS 10 allows the user to remove certain system-apps. In order to ensure that the developers do not forget that, we should leave an iOS 10 note in the docs so they know about that behavior when implementing the {{Ti.UI.EmailDialog}}."
Answer: 1631.0

User story: "iOS 10 finally exposed SiriKit, the public framework to interact with Siri. It allows the developer to send requests to Siri in order to fetch information from the following services:    - Audio or video calling  - Messaging  - Payments  - Searching photos  - Workouts  - Ride booking    Docs: https://developer.apple.com/library/prerelease/content/documentation/Intents/Conceptual/SiriIntegrationGuide/index.html    We should expose it as {{ti.siri}} with Hyperloop to access the {{Intents}} and {{IntentsUI}} framework. The big problem to solve here is, that Siri needs to be implemented inside a new target, which currently is only supported by creating a native target manually."
Answer: 245322.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "iOS 10 is in the house! In order to start extending the current core as well as ensuring the builds run stable, we need to expose the new iOS 10 utilities and resolve some warnings that come from it."
Answer: 15851.0

User story: Scenario:    Build an app for android (with ti build or appc run) to device. Switch git branches or take other actions that result in having tiapp.xml set a lower app version number. Try to build again, and you get the following failure:    {code}  [INFO]  Installing app on device: SM-G900V  [ERROR] Failed to install apk on "7d4c9760"  [ERROR] Error: INSTALL_FAILED_VERSION_DOWNGRADE  {code}    Instead of forcing developers to update the tiapp (which adds complexity to git workflows, like when you're reviewing a co-worker's PR), the build/run command should either automatically include the {{-d}} (allow downgrade) on the {{adb install}} command it execs, or it should have its own flag to enable that adb option.
Answer: 76669.0

User story: "This ticket include the changes being made to remove all deprecated API's across iOS and Android. On iOS, we have 106 API's that are marked to be removed by 6.0.0 (even API's from 1.8.0 and earlier), so it's time. On Android, we have 70 API's that are annotated with {{@Deprecated}}, without a remove-version. [~<USER> should decide which of them can be removed in 6.0.0."
Answer: 68015.0

User story: Right now if the red error controller is displayed we block opening other modal dialogs or new windows/views. This causes an issue with our unit tests because it means one failed test can fail any of the UI tests. The code is written in a way that we won't show the error controller if the deploy type is set to "production", but "production" is set as invalid value for a simulator or device launch.    Even if we could set deploy type to "production", that doesn't seem like the right fix for this (we still want other flags set for development like not minifying or encrypting the JS).
Answer: 11247.0

User story: "In attempting to set up an automated test suite for Android, I'm running into an issue whereby I cannot reliably spit the test results as JSON due to a number of issues. If I try to gather them all together and spit out on huge JSOn object, I run into TIMOB-23438 where it gets truncated around 4036 characters.    If I try to spit out JSON results after every test, I get intermittent truncated output, thereby breaking the JSON parsing.    When I do a manual {{adb logcat}} it always shows the full JSON output in the logs, however, the titanium CLI is truncating it for some reason."
Answer: 99892.0

User story: This is a parity issue. When running our mocha suite, we have a number of assertions inside JS callback functions. When an assertion fails on other platforms like iOS/Android, we show a "red screen of death" (on Android, it's more like an "ugly red dialog of death"). On Windows, we don't appear to do the same and the assertion error sort of gets squashed. We end up instead getting timeouts on the tests.
Answer: 63521.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Our Windows 10 unit tests sometimes crash out on Ti.Contacts.getAllPeople, causing the builds to be unstable."
Answer: 1052969.0

User story: "When I build a Windows app from Studio it works fine, but when I build the same app via CLI it fails with:    {code}  [ERROR] Failed to encrypt JavaScript files  [ERROR] Program launch failed. Unable to locate Java VM. Please set JAVA_HOME environment variable.  {code}    Which originates from:  https://github.com/<USER>titanium_prep/blob/247eaecf56160dce4273a8fd64977b83da671f06/android/launcher/main.jdk16.c#L139    Of course I could set {{JAVA_HOME}} but if Studio manages to find Java (and apparently pass it on to the CLI) then why can't the CLI?    IMHO the CLI should be able to do anything Studio can. Even better: Studio should not do anything the CLI so that Studio is as light as it can be and relies on CLI."
Answer: 1976626.0

User story: "These debug messages should not have the version hard coded in them.    https://github.com/<USER>titanium_mobile/blob/master/iphone/Classes/TiUIEmailDialogProxy.m#L60    https://github.com/<USER>titanium_mobile/blob/master/iphone/Classes/TiUIEmailDialogProxy.m#L87    https://github.com/<USER>titanium_mobile/blob/master/iphone/Classes/TiUIEmailDialogProxy.m#L89"
Answer: 86438.0

User story: "Merge this branch with master: https://github.com/<USER>titanium_mobile/tree/v8-update  Testing steps: Run scons with NDKr11c."
Answer: 79045.0

User story: The current version of the Boost library we use is out of date. We should update our setup NodeJS script to use the latest stable to avoid all the "Unknown compiler version" warnings during the build. This may require creating our own specialized subset of the library in a zipfile on S3, since the typical library has so many files it becomes a huge performance issue on initial setup (one-time).
Answer: 3175.0

User story: "In one of the my <USER>Project there is one functionality like,    We are showing a remote webpage in webview and in that webpage there is Photo Upload Browse button.    By clicking on that button Option dialog comes that ask to choose photo from Camera or Photo Gallery and we can select the photo.    That functionality is works fine in iOS but in android Titanium SDK has not support to choose and upload a photo from remote web page which is loaded on webview.    Earlier we are using a modified Titanium SDK. Can you please modified latest Titanium SDK(5.2.X Onwards) that support this feature.    Modified SDK (https://www.dropbox.com/s/j2csab3dhy6w3u2/4.1.0.GA_For_Correction_Camera_Web_upload.zip?dl=0) which allow to select photo from gallery or camera and this working fine in iOS and Android so the same change I need for latest version of Titanium SDK (5.2.X Onwards)    If you know, what changes we have to do in Titanium SDK to support this feature so can you suggest me in which file of Titanium SDK we need to do changes and what changes we have to write Titanium SDK files ?."
Answer: 3706.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There's no documentation about how to create native module on Windows. Related: [How to call a method added to the windows native module of Appelerator Platform|http://stackoverflow.com/questions/36213930/how-to-call-a-method-added-to-the-windows-native-module-of-appelerator-platform]  "
Answer: 13927.0

User story: "This ticket should summarize, what's necessary to make Hyperloop available without the usage of Titanium Mobile. Currently, we are hooking Hyperloop into the Ti build-<USER> allowing it to act independently therefore needs:  - Own CLI  - Creation of the AppDelegate  - Handling of assets    Just like ALOY-1488, it's a huge task, but it's here for discussion."
Answer: 772212.0

User story: "Windows SDK uses a mocha test suite for unit testing it's APIs, currently living at https://github.com/<USER>titanium_mobile_windows/tree/master/Examples/NMocha/src/Assets    iOS/Android use a suite living at https://github.com/<USER>titanium_mobile/tree/master/ti_mocha_tests    We should combine our test suites into a common repository so that any new tests we add will be performed across all the OSes and we can easily pick up parity issues. It would involve updating our build scripts to grab the test suite from it's new location, and would likely involve more explicit attention to party issues or OS specific tests. (Meaning we'll need to know if a test case isn't intended to work on a particular platform and would have to code it into the test to skip it)"
Answer: 116715.0

User story: "The files just lives in the wrong place on the filesystem compared to it's header and namespace."
Answer: 31937.0

User story: "The dev-macro {{#ifdef TARGET_IPHONE_SIMULATOR}} is also compiled to device and production, that's incorrect."
Answer: 199473.0

User story: "The build flags introduced by TIMOB-17446 to enable ALOY-858 are hack-ish and should be removed.    Instead, Alloy should handle i18n and platform folders like it does with Resources, as requested by ALOY-1365.    Once ALOY-1365 has been resolved and no longer requires the build flags, they should be removed."
Answer: 18741.0

User story: "Some UI components has inconsistent layout behaviors when auto-layout property is toggled on/off.  Components include:  TiMediaVideoPlayer  TiUIActivityIndicator  TiUIButton  TiUIButtonBar  TiUICanvasView  TiUIImageView  TiUILabel  TiUIListView  TiUIMaskedImage  TiUINavBarButton  TiUIPicker  TiUIProgressBar  TiUIScrollView  TiUIScrollableView  TiUISearchBar  TiUISlider  TiUISwitch  TiUITabGroup  TiUITableView  TiUITextField  TiUITextWidget  TiUIWebView  TiUIiOSAdView  TiUIiOSCoverFlowView  TiUIiOSLivePhotoView  TiUIiOSToolbar  TiUIiPadSplitWindow  "
Answer: 7195.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Enabling background task requires "badge icon" when building for Windows Store. It is required to package the app even when badge is not actually used.    {code}  04:26:48   C:\Users\<USER>.titanium\vsbuild\mocha\store.x86\Package.appxmanifest(45,8):   error APPX1675: App manifest declares background task of type timer, control channel,   push notification, or location without enabling lock screen notifications.   [C:\Users\<USER>.titanium\vsbuild\mocha\store.x86\Mocha.vcxproj]  {code}    FYI: Enabling background task (tiapp.xml)  {code:xml}  <windows>    <manifest>      <Extensions>          <Extension Category="windows.backgroundTasks" EntryPoint="TitaniumWindows_Ti.BackgroundServiceTask">            <BackgroundTasks>              <Task Type="timer" />            </BackgroundTasks>          </Extension>      </Extensions>    </manifest>  </windows>  {code}
Answer: 595.0

User story: "The releases on GitHub are marked as pre-release since 5.0.2.GA, which makes 5.0.1.GA still marked as latest release:    https://github.com/<USER>titanium_mobile/releases"
Answer: 38546.0

User story: "Github recently published a new feature to create issue- and PR-templates for community contributions.     In our case, we would be able to inform the user about the coding guidelines for extending the SDK, the CLA link, the necessary docs etc. For issues, we could mention to create a JIRA ticket first, attach build logs and provide the environment.    The required files ({{PULL_REQUEST_TEMPLATE}} and {{ISSUE_TEMPLATE}}) are placed inside a .github directory.     More information: https://github.com/blog/2111-issue-and-pull-request-templates"
Answer: 241587.0

User story: "To support Hyperloop modules, developers need to access common Ti-utilities like we already do with {{TiApp}}. Common used classes:  - TiUtils  - WebColor  - WebFont    Problem to discuss is also: What do we do for existing modules that want to be migrated to Hyperloop? They often rely on existing proxies (although not recommended)."
Answer: 242761.0

User story: The master branch has been 6.0.0 all along. Now that the roadmap has changed, we have to change the version to 5.4.0, and the docs for already merged tickets that were marked 6.0.0 to "since: 5.4.0"  
Answer: 23048.0

User story: One of customer want to know some info about following id in CLSUserDefaults.plist file.    {quote}  I found on the device/mobile an file named "CLSUserDefaults.plist" and inside it an information about "vendor_id"     My questions are:     1 - Is that information (vendor_id) receiving or is be sending to the any webserver??? <USER>or Crittercism???     2 - What's the meaning of this information???     3 - This information stays on the device/mobile???  {quote}
Answer: 1481608.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This issue occurs in several cases when we want to use a proxy (like TiBlob and TiUILivePhoto) and running on main-thread. The usual warning is {{\[WARN\] Creating \[object TiBlob\] in a different context than the calling function.}}. Example:  {code:javascript}  Ti.Media.openPhotoGallery({      mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO],      success: function(e) {        Ti.API.warn(e.mediaType);        Ti.API.warn(e.media);      }    });    var win = Ti.UI.createWindow({backgroundColor: "#fff"});  win.open();  {code}    It is caused because we create a blob using {{TiBlob *media = \[\[\[TiBlob alloc\] initWithImage:resultImage\]\];}} instead of using the page context:  {code}  TiBlob *media = [[[TiBlob alloc\] _initWithPageContext:[self pageContext]] autorelease];  [media setImage:resultImage];  {code}    This issue effects TIMOB-19666 and possibly many other proxies that have not been tested, yet. We need to make sure that the proxies are created properly and write unit tests to ensure their integrity.
Answer: 248480.0

User story: "As organizations are more frequently creating more than one application for their users (both internal and external), eliminating the need for logging into each application provides a much better overall experience to the end user.    Titanium should be updated to make it easy to implement cross app (same device) SSO using the secured storage options for each platform. This would provide an abstracted singular API, and enforce best practice around storing credentials on the device.     This feature would not perform the authentication to the system of record, but simply provide the mechanism for storing and retrieving the user session securely on the device for access from multiple apps.    *Use Cases*  {code}  As an app developer, I want to enable authentication between multiple applications on the same device, eliminating the need for users to sign in multiple times.  {code}    The above use case is from the developer perspective, providing the shared library as part of APS Native SDK, enables a consistent controlled experience for single sign-on, but does not implement the authentication itself.    And from the end user perspective:    {code}  As a user, i want to be able to login to one application and have my session persisted across multiple apps belonging to and developed by a single organization  {code}"
Answer: 698693.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I'm not sure if this is a doc issue or a problem with the scripts we use to generate the parity report.    In any case, looking at http://builds.<USER>com/mobile/master/mobilesdk-6.0.0.v20160203193439-parity.html I'm seeing some APIs listed as unsupported though they really are:    - Global  - Modules.Cloud* (?)  - Titanium.BlobStream  - Titanium.BufferStream  - Titanium.Filesystem.FileStream  - Titanium.Map  - Titanium.Map.Annotation  - Titanium.Map.View  - Titanium.Module  - Titanium.Proxy  - Titanium.UI.AttributedString  - Titanium.UI.ListItem  - Titanium.UI.ListSection  - Titanium.UI.Picker  - Titanium.XML.CDATASection  - Titanium.XML.Comment  - Titanium.XML.DocumentFragment  - Titanium.XML.EntityReference  - Titanium.XML.Text"
Answer: 261208.0

User story: "Travis CI has been doing well for build and unit testing on the titanium_mobile repo. However, several issues occur when using newer versions of Xcode > 6.4, including performance and other fails. To be able to have a more configurable environment, it'll be better to build a <USER>machine instead that can vet every PR ready to be merged into the repo."
Answer: 262014.0

User story: "Kota made great strides in eliminating a large source of memory hogging going on: storing all constant property values in fields of the enclosing type. We'd not only store them for the class definition but also for every instance! Now that we store them in an unordered_map and generate them on-demand they're only cached once per class. But it'd be a good improvement to move to something like an LRU cache to evict older constants out of the in-memory cache if we ever need to free some memory.   It'd be good to have more details on just how much memory these are taking up and what the speed/perf overhead of always generating them on-demand would be (or if that'd even be feasible whether the constants would be considered equal when regenerated)."
Answer: 2318217.0

User story: "MSBuild seems to lock resources after builds; preventing subsequent builds from completing.    This can be resolved by disabling node reuse:  http://stackoverflow.com/questions/3919892/msbuild-exe-staying-open-locking-files    This could also fix the previous problems of building in parallel?"
Answer: 443.0

User story: "We have an android example of bluring a view, we should add the iOS equivalent, too."
Answer: 26.0

User story: We currently run our unit test suite only on Windows Phone emulator (for both 8.1 and 10.0). We should also run the suite against a Windows Store/desktop app (target of "ws-local").
Answer: 47797.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: According to [Application Verifier|https://msdn.microsoft.com/en-us/library/windows/hardware/ff538115%28v=vs.85%29.aspx] for Windows Phone, bad memory allocation due to heap corruption and "out of memory" error has been observed. This may be a root cause of crash at application startup (TIMOB-20197). I'm observing that one of "out of memory" error occurs at {{Titanium::ApplicationBuilder}} constructor. Because we are instantiating every Titanium object in there, we may have a chance to reduce memory consumption by delaying instantiation of them. We might be able to instantiate them on demand.     
Answer: 19498.0

User story: "We added support for adding a {{HyperloopViewProxy}} to the Titanium view hierarchy, but not for removing them again. We should do a similar check like [here|https://github.com/<USER>titanium_mobile/blob/master/iphone/Classes/TiViewProxy.m#L191] to get the {{TiViewProxy}} correctly.    The thrown error: {{Invalid type passed to function. expected: TiViewProxy, was: HyperloopClass -\[TiViewProxy remove:\] (TiViewProxy.m:266)}}"
Answer: 140825.0

User story: "As part of the major release 6.0.0, we should set the minimum Xcode version from 6.4 to 7.2 and remove the {{IS_XCODE_6}} macros to cleanup the code base."
Answer: 293570.0

User story: "Investigate crash analysis library for Windows Store/Phone, equivalent for Crittercism, KSCrash and so on.    per TIMOB-20150    {quote}  To sum things up, the sdk team has decided to use these 2 libraries KSCrash and ACRA for iOS and Android respectively. The next step is to determine in detail the protocol for these libs with the crash-server endpoint. So PEM team please take a look at above comments and proposal, and we can determine how to move forward in replacing the crittercism client lib.    Things to note and consider:  1. do we need to achieve cross-platform parity in the data posted at client? or let the crash-server <USER>each platform's unique crash report and insert accordingly to the database?  2. additional information to append to the data, such as app guid or key.  3. windows platform will be considered at a later phase, with priority placed on iOS and Android.  4. Possibility to fork these 2 repos if in depth modifications are required.  {quote}  "
Answer: 31516.0

User story: "We should probably just remove all deprecated methods and properties pre 5.0.0"
Answer: 255913.0

User story: "Currently JavaScriptCore uses [Thread Local Storage|https://msdn.microsoft.com/en-us/library/windows/desktop/ms686801%28v=vs.85%29.aspx] functions to handle threading. It has been supported even on Windows Phone as well as Windows Store app, but as of Windows 10 it is not supported and it won't pass the Windows App Certification.  "
Answer: 2435.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Ti SDK 5.1 introduced permission checks on the camera module to prevent showCamera from being called when a user has denied permission but there are other possible scenarios besides permissions. The TiCameraActivity is missing a try catch block around Camera.open().    See Android documentation: http://developer.android.com/reference/android/hardware/Camera.html#open(int)  "
Answer: 2083.0

User story: "We have been disabling {{SAFESEH}} linker option just to supress compiler warning message for simulator according to [HAL/CMakeLists.txt#L195|https://github.com/<USER>HAL/blob/master/CMakeLists.txt#L195].     Since SAFESEH option is only available on x86 build, it has been a no problem before because it only affects on the simulator. But in the Windows 10 world, we could have x86 app for the Store App, and disabling SAFESEH won't pass the Windows App Certification for x86. We should enable it again even on x86 build.  "
Answer: 1007.0

User story: Since Windows Phone requires explicit permission to enable some API, we'll need to document about how to enable additional capabilities in *tiapp.xml*.    h5. i.e. how to enable user account information (TIMOB-20173)  {code:xml}  <windows>    <Capabilities>      <uap:Capability Name="userAccountInformation" />    </Capabilities>  <windows>  {code}    h5 i.e. how to allow background audio (TIMOB-20035)  {code:xml}  <windows>    <manifest>      <Extensions>        <Extension Category="windows.backgroundTasks" EntryPoint="TitaniumWindows_Media.AudioBackground">          <BackgroundTasks>            <Task Type="audio" />          </BackgroundTasks>        </Extension>      </Extensions>    </manifest>  </windows>  {code}  
Answer: 73510.0

User story: "We should probably just remove all deprecated methods and properties pre 5.0.0"
Answer: 20942.0

User story: "On Windows 8.1 Phone we use a Pivot: https://msdn.microsoft.com/library/windows/apps/windows.ui.xaml.controls.pivot.aspx  On Windows 8.1 Store(desktop) we use a ListView. Just by how the macros fall, we use the same in Windows 10 Desktop and Mobile now.    In the source we note we may want to use a SplitView on Windows 10: http://igrali.com/2015/04/12/getting-started-with-splitview-control-in-universal-apps/ and https://msdn.microsoft.com/library/windows/apps/windows.ui.xaml.controls.splitview.aspx    I think we have the choice of all three on Windows 10, so we may want to see which is the best fit."
Answer: 21288.0

User story: "Right now we have a single PR builder for Windows SDK and it runs the 8.1 build and unit tests. We should have it build for both Windows 8.1 and 10 and run those unit tests.    Some possible solutions:  - Generate a second PR builder copy of the first that runs 10 and unit test  - Make the existing PR builder more like our master build where it farms out to special 8.1 and 10.0 build jobs as a steps. Not sure if these jobs would get the code from the PR branches/refs on fetch without some changes, though."
Answer: 1482.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Our generate_project.js script for generating VS solutions from our Examples assumes usage if Windows 8.1 We have arguments to target Windows 10/MSBuild 14.0, but it doesn't create a proper appxmanifest for Windows 10 - it assumes the Windows 8.1 version. We should probably just have it make use of the appxmanifests we have in the templates directory and populate them with some hard-coded app id/publisher/etc from each example."
Answer: 279.0

User story: "We have a setup.js script we use to help get SDK developers (and the build machine) configured for doing development and builds. When run on Windows 10, It says it's setting the JavaScriptCore_HOME, GTEST_ROOT, and BOOST_ROOT - but if I close and open a new cmd shell, those values aren't set."
Answer: 27395.0

User story: "Hello,  Ti.barcode stopped to work in IOS8 after adding 64 bit support in our App.  Can you please see if we are missing something in integration?  Thank you."
Answer: 221400.0

User story: We currently use macros that will effectively compile one block or another depending on whether the code works/is available on phone or desktop.  i.e.  {code:cpp}  #if WINAPI_FAMILY != WINAPI_FAMILY_PHONE_APP  {code}    This is the right approach for Windows 8, but in Windows 10 a universal app is generated and the check must be done at runtime. We need to convert these checks into a macro and have the macro defined to do different things for 8.1 versus 10.    See https://msdn.microsoft.com/en-us/library/windows/apps/mt188202.aspx and https://msdn.microsoft.com/en-us/library/windows/apps/mt188203.aspx#reviewing_conditional_compilation    I think we can extract a simple macro like:  {code:cpp}  // Only on Win 8.1  #define PHONE_ONLY_START \  #if WINAPI_FAMILY == WINAPI_FAMILY_PHONE_APP    #define PHONE_ONLY_END \  #endif    // Only on Win 10  #define PHONE_ONLY_START \  if (Windows::System::Profile::AnalyticsInfo::VersionInfo::DeviceFamily == "Windows.Mobile") {    #define PHONE_ONLY_END \  }  {code}    We may of course need more variants for things where the API is now available in Win10, but was only available for phone or store on 8.1, etc. (i.e. Clipboard was only for store.desktop in 8.1, but is universal in 10)
Answer: 38801.0

User story: "We should cache instance proxies and ensure we always re-use/return the same hyperloop proxy for the same underlying Java object. Right now we wrap and unwrap with new instances every time. This will involve some caching mechanism. We should also look into doing a cache of class proxies to improve performance, since we hang static fields, methods and constructors off the class proxy instances."
Answer: 364707.0

User story: "When we target Windows 10 as the end SDK target for a user's app, we need to be sure we use the Win10 compiled SDK libraries."
Answer: 491.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We have separate builds of the SDK done against Win 8.1 and Win 10. We need to package both versions up into a single zip that is used in the main SDK.    We can't just mash together the two zips, as we need to adjust where the WIn10 builds get packaged up in the final zip. Right now they're under store/x86 and store/ARM. They probably should be under something like "win10/x86" and win10"ARM" since they're supposed to be universal for Win10 store/phone.
Answer: 10004.0

User story: "We currently run mocha tests against the Windows emulator when we build on Windows 8.1. We should do the equivalent for Windows 10 builds.    I'm not sure if that means we'd need to run the tests against Windows Store deploy target, or if we can just run normally against the Win10 phone emulator (which likely will require CLI work to know which lib versions are OK for win10 universal)"
Answer: 41834.0

User story: "To improve the quality of the SDK, we now include automated unit tests in Travis CI, such that unit tests are performed on iOS and Android. If a certain pass criteria is not met, Travis CI will indicate a build fail for the pull request."
Answer: 375828.0

User story: "If we generate a native UI proxy (say an android.view.View) and add it to a Titanium UI, we don't properly clean up all the native proxies we've generated leading to a large memory leak. Specifically we need a way to track all UI proxies added as children in the view hierarchy and explicitly release them when the top-level native view is asked to release in our Java code (TiUIView.releaseAllViews())"
Answer: 376542.0