id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
3,726 |
TIMOB-27338
|
08/15/2019 11:09:00
|
iOS: Invalid iOS simulator error is shown when doing concurrent builds with iOS 13
|
When running concurrent iOS builds on simulators the following error is seen in Studio: {code:java} [ERROR] : Invalid "--device-id" value "8B89634B-0E8B-4286-8839-7CEE6A035700" {code} The cli also shows this error: {code:java} [ERROR] Invalid iOS simulator "8B89634B-0E8B-4286-8839-7CEE6A035700" {code} *Test Steps* # Create a titanium project # Run the project in APPC studio or through the CLI (e.g. {{appc run -p ios -C 8B89634B-0E8B-4286-8839-7CEE6A035700 -I 13.0}}) # Re-run the project without closing the Simulator *Actual result* Above error is shown *Expected result* Above error should not be shown and application should launch on the simulator
| 0 |
3,727 |
TIMOB-27342
|
08/19/2019 11:37:43
|
iOS regression: Console.warn/error don't log all parameters
|
When using console.log/warn/error usually all parameters get logged, however since SDK 8.1.0 this is no longer the case. If you run this code: {code:js} console.log('a', 'b'); console.warn('a', 'b'); console.error('a', 'b'); {code} it will log: {code} [INFO] a b [WARN] a [ERROR] a {code} It should log {{a b}} for all 3 types. It works fine for Android and iOS SDK 8.0.0.GA
| 5 |
3,728 |
TIMOB-27406
|
08/21/2019 19:33:04
|
Android: Cannot select content from downloads
|
I downloaded the following image to the device, so after that in the app I am selecting the image from the gallery of download, and it is causing a black/ gray window after selecting the image. http://www.effigis.com/wp-content/uploads/2015/02/Airbus_Pleiades_50cm_8bit_RGB_Yogyakarta.jpg The purpose of use this huge image it is that I am using the ti.imagefactory module to compress the image, but at the moment I am selecting the image downloaded the app is behaving in this way showing a black or gray window. Note this issue is not happening in iOS. XML: {code:java} <Alloy> <Window class="container"> <Label id="label" onClick="doClick">Hello, World</Label> <ImageView id="mImageContainer" bottom="30"/> </Window> </Alloy> {code} JS: {code:java} function doClick(e) { alert($.label.text); Titanium.Media.openPhotoGallery({ success:function(event) { if (event.mediaType == Ti.Media.MEDIA_TYPE_PHOTO) { Ti.API.info("success"); $.mImageContainer.image = event.media; } }, cancel: function(e){ Ti.API.info(e); }, error:function(e) { Ti.API.info(e); }, mediaTypes:[Ti.Media.MEDIA_TYPE_PHOTO] }); } $.index.open(); {code} {code:java} [ERROR] TiExceptionHandler: (main) [15193,15193] Failure delivering result ResultInfo{who=null, request=1, result=-1, data=Intent { dat=co ntent://com.android.providers.downloads.documents/document/raw:/storage/emulated/0/Download/x.jpg flg=0x1 }} to activity {com.tony.tony/or g.appcelerator.titanium.TiActivity}: java.lang.NumberFormatException: For input string: "raw:/storage/emulated/0/Download/x.jpg" [ERROR] TiExceptionHandler: [ERROR] TiExceptionHandler: java.lang.Long.parseLong(Long.java:594) [ERROR] TiExceptionHandler: java.lang.Long.valueOf(Long.java:808) [ERROR] TiExceptionHandler: org.appcelerator.titanium.io.TitaniumBlob.init(TitaniumBlob.java:89) [ERROR] TiExceptionHandler: org.appcelerator.titanium.io.TitaniumBlob.<init>(TitaniumBlob.java:41) [ERROR] TiExceptionHandler: org.appcelerator.titanium.io.TiFileFactory.createTitaniumFile(TiFileFactory.java:112) [ERROR] TiExceptionHandler: ti.modules.titanium.media.MediaModule.createImageData(MediaModule.java:1276) [ERROR] TiExceptionHandler: ti.modules.titanium.media.MediaModule.createDictForImage(MediaModule.java:1267) [ERROR] TiExceptionHandler: ti.modules.titanium.media.MediaModule$1.onResult(MediaModule.java:1199) [ERROR] TiExceptionHandler: org.appcelerator.titanium.util.TiActivitySupportHelper$1.onResult(TiActivitySupportHelper.java:60) [ERROR] TiExceptionHandler: org.appcelerator.titanium.util.TiActivitySupportHelper.onActivityResult(TiActivitySupportHelper.java:117) [ERROR] TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.onActivityResult(TiBaseActivity.java:905) [ERROR] TiExceptionHandler: android.app.Activity.dispatchActivityResult(Activity.java:7797) [ERROR] TiExceptionHandler: android.app.ActivityThread.deliverResults(ActivityThread.java:5071) [ERROR] TiExceptionHandler: android.app.ActivityThread.handleSendResult(ActivityThread.java:5120) [ERROR] TiExceptionHandler: android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:49) [ERROR] TiExceptionHandler: android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108) [ERROR] TiExceptionHandler: android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68) [ERROR] TiExceptionHandler: android.app.ActivityThread$H.handleMessage(ActivityThread.java:2199) [ERROR] TiExceptionHandler: android.os.Handler.dispatchMessage(Handler.java:112) [ERROR] TiExceptionHandler: android.os.Looper.loop(Looper.java:216) [ERROR] TiExceptionHandler: android.app.ActivityThread.main(ActivityThread.java:7625) [ERROR] TiExceptionHandler: java.lang.reflect.Method.invoke(Native Method) [ERROR] TiExceptionHandler: com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524) [ERROR] TiExceptionHandler: com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987) {code} Please let me know whether you have any doubt or question. Thanks, and best, Francisco Antonio Duran Ramirez.
| 3 |
3,729 |
TIMOB-27348
|
08/22/2019 19:07:04
|
Android: WebView.stopLoading() is not functional when triggered by events
|
{{Titanium.WebView.stopLoading()}} has no effect when called from events. *TEST CASE* {code:js} const win = Ti.UI.createWindow(); const webView = Ti.UI.createWebView({ url: 'https://google.com/' }); // prevent page from loading. webView.addEventListener('beforeload', e => { webView.stopLoading(); }); win.add(webView); win.open(); {code} *EXPECTED* - Page is prevented from load, displaying a blank screen. *ACTUAL* - Page loads.
| 5 |
3,730 |
TIMOB-27350
|
08/23/2019 16:09:27
|
iOS: httpClient returning image response as undefined.
|
*Customer issue:* As part of Titanium SDK migration from 7.5.2.GA to 8.1.0.GA titanium SDK, we are encountering an issue when we are fetching image from server and checking if the response is Blob or not by converting to .toString(). It is returning “undefined” with 8.1.0.GA but returning blob object with 8.0.2.GA, 7.5.2.GA. Steps to reproduce: 1. Create a classic mobile app with 8.1.0 SDK. 2. Replace app.js file content with attached app.js. 3. Run on iOS device. 4. check the info in the console. Thanks
| 2 |
3,731 |
TIMOB-27351
|
08/23/2019 16:17:40
|
iOS: Unit tests failing on Xcode 11 / iOS 13
|
Once we started building and running against Xcode 11 and iOS 13, we have two unit tests that started failing: ios.Titanium.UI.iOS.#createPreviewContext() - expected 0 to equal 300 ios.Titanium.UI.Window..safeAreaPadding for window inside navigation window with extendSafeArea true - expected 34 to equal 0 This can be found on any of our recent master branch builds on master
| 5 |
3,732 |
TIMOB-27352
|
08/23/2019 22:53:58
|
Analytics: Improve event batching
|
- Improve event batching for both iOS and Android - Send batches of 20 events for improved reliability in low connectivity environments - Increase batch frequency to accommodate for a large number of events
| 8 |
3,733 |
TIMOB-27353
|
08/23/2019 22:56:36
|
iOS: Unable to send Date() object in event payload
|
- iOS is unable to properly serialize a Javascript {{Date}} object in an event payload *TEST* {code:js} Ti.Analytics.featureEvent('test.date', { date: new Date() }); {code} *EXPECTED* - Should not crash *ACTUAL* - Crashes application
| 5 |
3,734 |
TIMOB-27358
|
08/27/2019 11:44:05
|
iOS: Support Apple Developer certificates
|
h5.Description Apple has introduced a new "Apple Developer" certificate that encompasses signing for iOS, MacOS, tvOS, and WatchOS applications. I believe this was the root cause of TIMOB-27330. Places we need to update: Titanium CLI/SDK: ioslib@v1 - update cert.js to also scan for "Apple Development" and "Apple Distribution" Daemon: ioslib@v2 & v3: Update the regex to include "Apple Development" and "Apple Distribution" Studio: Might need to update the property it uses from the cert object to display in the UI, currently it's possible for two certs to share an identical {{name}} i.e. {{Ewan Harris (EH123J4ST56)}}, so only one appears to be added to the cert list, the only way to differentiate is via the {{fullname}} i.e. {{Apple Distribution: Ewan Harris (EH123J4ST56)} vs {{iPhone Distribution: Ewan Harris (EH123J4ST56)}}
| 8 |
3,735 |
TIMOB-27360
|
08/27/2019 18:50:09
|
Watch app does not get installed on the watch with watch OS 6.0 & IOS 13
|
h5. Steps to reproduce: 1. Use the watch app here : https://github.com/appcelerator-developer-relations/appc-sample-watchos2 2. Build it to a watch & iPhone simulator. h5.Actual result: 1. You will see the app installs on the phone but does not install on the watch. h5.Expected result: 1. The app should install on both phone & watch.
| 8 |
3,736 |
TIMOB-27430
|
08/28/2019 21:52:57
|
EncryptedDB ResultSet field and fieldByName functions are returning incorrect values on Android
|
Calling .field() or .fieldByName() on an encrypteddatabase (3.0.4) ResultSet returns a boolean false if the value of the field is NULL. This issue seems to be isolated to this module on Android with the 8.1.0.GA SDK. 8.0.0.GA and iOS don't have this issue, nor does the built-in Ti.Database.ResultSet. A small sample project is linked below. Run this app on an Android device and see the discrepancies between the console log outputs for non-encDB and encDB. Running on iOS or switching back to 8.0.0.GA alleviates the discrepancy. Sample project: https://drive.google.com/file/d/1HW1jxvUPZ67_HVx1Phe-PqgJKeVQygLp/view?usp=sharing
| 5 |
3,737 |
TIMOB-27362
|
08/28/2019 22:47:08
|
Hyperloop example with Xcode 11 throws error on pod
|
**Steps To Reproduce:** 1.import Hyperloop example 2.Run on iOS simulator 13 *Expected:* Hyperloop should be installed and launch fine *Actual:* throws error [WARN] [Hyperloop] CocoaPods 2019-08-28 16:10:45.042 xcodebuild[36945:2593098] DTDeviceKit: deviceType from aa9928797e2fd58e6dce8e858e5e8afcbce393bf was NULL [WARN] [Hyperloop] CocoaPods 2019-08-28 16:10:45.085 xcodebuild[36945:2593092] DTDeviceKit: deviceType from aa9928797e2fd58e6dce8e858e5e8afcbce393bf was NULL [TRACE] [Hyperloop] CocoaPods note: Using new build system [WARN] [Hyperloop] CocoaPods 2019-08-28 16:10:45.387 xcodebuild[36945:2593095] unable to create build operation: Error Domain=com.apple.xcbuild Code=1 "unknown error while handling message: missingTarget(guid: "345a28d23c8e4235945c90e2e6ffcfba1a6c203c29e67926a1f49846b3a914d9")" UserInfo={NSLocalizedDescription=unknown error while handling message: missingTarget(guid: "345a28d23c8e4235945c90e2e6ffcfba1a6c203c29e67926a1f49846b3a914d9")} [WARN] [Hyperloop] CocoaPods ** BUILD FAILED ** [ERROR] An error occurred during build after 5s 671ms [ERROR] the xcodebuild failed running from /Users/kmahalingam/Documents/Appcelerator_Studio_Workspace/hyperloop-examples2/Pods Note: on Xcode 10 it is hyperloop example works fine with cocoa pod version less that 1.6 on Xcode 11 it throws the error
| 13 |
3,738 |
TIMOB-27366
|
08/29/2019 20:00:08
|
iOS: Video player not getting closed in iOS version 10.x.x and below
|
Hello, Video player is not getting closed in iOS version 10.x.x and below but on iOS version 12 or above it's working fine. *Test Environment:* Appcelerator Command-Line Interface, version 7.1.0 Operating System Name = Mac OS X Version = 10.14.5 Architecture = 64bit # CPUs = 4 Memory = 8589934592 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.2.1 Titanium SDK SDK Version = 8.1.0.GA iOS device: iPhone 6plus(12.4), iPod 5G(9.3.3), iPhone OS 10.3.3 *Test code:* app.js {code} var win = Ti.UI.createWindow({ backgroundColor : 'red' }); var label2 = Ti.UI.createLabel({ color : 'blue', text : 'Play Video', width : 300, height : 200 }); label2.addEventListener('click', function(e) { //alert('hi') require('playvid').playvideo(); }); win.add(label2); win.open(); {code} playvid.js {code} exports.playvideo = function() { var url = "https://storage.googleapis.com/onfvideo/Dialogue%202019/2%20compress%2006-04-2019/012%20S%20Shantakumari/Intro%20Dr%20S%20Shanthakumari.mp4"; var vidWin = Titanium.UI.createWindow({ title : 'Video View Demo', backgroundColor : '#000000', // top : (require('main').checkiPhoneX) ? '40dp' : require('main').isiOS7Plus() ? '20dp' : '0dp', orientationModes : [Titanium.UI.LANDSCAPE_LEFT, Titanium.UI.LANDSCAPE_RIGHT, Titanium.UI.PORTRAIT, Titanium.UI.UPSIDE_PORTRAIT] }); vidWin.open(); var videoPlayer = Titanium.Media.createVideoPlayer({ //top : (require('main').checkiPhoneX) ? '45dp' : require('main').isiOS7Plus() ? '32dp' : '0dp', //bottom : (require('main').checkiPhoneX) ? '32dp' : '0dp', url : url, autoplay : true, fullscreen : true, backgroundColor : '#000000', height : Ti.UI.FILL, width : Ti.UI.FILL, //initialPlaybackTime : timemili, mediaControlStyle : Titanium.Media.VIDEO_CONTROL_DEFAULT, scalingMode : Titanium.Media.VIDEO_SCALING_ASPECT_FIT }); videoPlayer.addEventListener('complete', function(e) { if (vidWin !== null) { vidWin.close(); vidWin = null; } }); vidWin.add(videoPlayer); }; {code} *Steps to reproduce the issue:* 1. Run the project on iOS 10.x.x enable device 2. Click on the red window video play button. 3. Opened the video player window and it's paying the video 4. Make it full Screen and wait until complete the video 5. It's not returning to the Red window on iOS 10.x.x device(Check Screenshot). But it's working fine on iOS 12 or above device. Thanks
| 1 |
3,739 |
TIMOB-27367
|
08/30/2019 11:54:25
|
iOS: Apps can be rejected when including UIWebView refs
|
Users submitting apps this week are seeing the following notification: {quote} ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information. {quote} This even occurs for SDK 8+ apps that use the WKWebView instead of the (deprecated) UIWebView. The reason is (I think) that there are still some UIWebView* left overs that aren't even used anymore. Removing them will very likely fix the issue.
| 5 |
3,740 |
TIMOB-27376
|
09/04/2019 12:35:15
|
iOS: Malformed Xcode project warning printed on every build
|
The following is printed as red error text when building for iOS: {code} >> [ERROR] 2019-08-22 23:51:47.821 xcodebuild[39858:743045] warning: The file reference for "" is a member of multiple groups ("TableView & ListView" and "UI"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path. >> [ERROR] 2019-08-22 23:51:47.821 xcodebuild[39858:743045] warning: The file reference for "" is a member of multiple groups ("UI" and "UI"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path. >> [ERROR] 2019-08-22 23:51:47.821 xcodebuild[39858:743045] warning: The file reference for "" is a member of multiple groups ("UI" and "UI"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path. >> [ERROR] 2019-08-22 23:51:47.821 xcodebuild[39858:743045] warning: The file reference for "" is a member of multiple groups ("UI" and "UI"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path. {code} Those are warnings that indicate a malformed Xcode project. Since they will be printed as red warning messages they get especially confusing when the build actually fails.
| 1 |
3,741 |
TIMOB-27379
|
09/05/2019 07:28:06
|
Windows:Using hint text on Textfield and 'passwordMask' property is true, the hint text is not shown when the TextField is cleared programmatically
|
For a TextField with hint text, if the 'passwordMask' property is true, the hint text is not shown when the TextField is cleared programmatically like on click of a button like below. {code} btnReset.addEventListener('click', function (e) { txtUsername.value = ""; txtPassword.value = ""; }); {code} But, it works fine case of manual clearing of the same TextField. Also, for a TextField with 'passwordMask' property as false, it works without any issue in both manual and programatic clearing of the field.The customer is facing issue on *Windows 10 version 1809 desktop*.It Works fine for Android and iOS. A screenshot is posted to the click of Reset button. On that button click, text fields are cleared. But, hint text is restored only for the Username field and not for Password field. *Testing Environment:* {code} SDK version: 7.2.0 GA,8.1.1.GA,8.0.2.GA, CLI version: 7.0.12 Device: Windows 10 version 1809 desktop. {code} *Sample test case:* {code} AppStart(); function AppStart() { var loginWindow = createLogin("Login", "Login to App"); loginWindow.open(); } function createLogin(title, message) { var win = Ti.UI.createWindow({ title: title, backgroundColor: '#fff' }); var label = Ti.UI.createLabel({ text: message, color: "#333", font: { fontSize: 20 } }); label.top = "10%"; label.left = "5%"; label.height = "6%"; label.width = "35%"; label.title = "Login"; win.add(label); var txtUsername = Ti.UI.createTextField({ top: "20%", left: "5%", height: "6%", width: "55%", passwordMask: false, paddingLeft: 15 }); var txtPassword = Ti.UI.createTextField({ top: "30%", left: "5%", height: "6%", width: "55%", passwordMask: true, paddingLeft: 15 }); txtUsername.hintText = 'Username'; txtPassword.hintText = 'Password'; win.add(txtUsername); win.add(txtPassword); var btnReset = Ti.UI.createButton(); btnReset.top = "40%"; btnReset.left = "35%"; btnReset.height = "6%"; btnReset.width = "25%"; btnReset.title = "Reset"; btnReset.addEventListener('click', function (e) { ResetFields(); }); function ResetFields() { txtUsername.value = ""; txtPassword.value = ""; } win.add(btnReset); return win; } {code} *Test Steps:* 1. Open the app. 2. Enter some values in Username and Password fields. 3.Click the Reset button which programmatically clear the Text Fields. *Test Output:* *Curent Result:* Password field cleared and hint text is not shown. *Expected Result:* Password field cleared and hint text to be shown.
| 8 |
3,742 |
TIMOB-27382
|
09/06/2019 11:48:24
|
iOS: CORS Issue, origin of header is always null since SDK 8
|
h6.Problem Description: As of SDK 8, any XMLHttpRequest performed inside a WebView from a file has a header of origin: null. This is a behavior that was not present in SDK 7 and only affects IOS. (It seems to be due to the change to WKWebview.) We use the WebView in an authentication workflow where we have an intermediate HTML file with the necessary javascript to perform the redirections/progress the sign in. This is an HTML page in resources/www. Due to the fact this header is now A) Being set for seemingly all requests, even GET B) is always null This is breaking our authentication process and we cannot continue developing our application until it is fixed. There does not appear to be any way to currently set this via titanium, there is also nothing in the documentation. We cannot set Access-Control-Allow-Origin * / null as this would pose a security risk server-side. We need to be able to switch back to using UIWebview in the new SDK, the origin header dropped, or, the origin header has a correct value (https://localhost/.....). h6.Reproduce 1. Create a new alloy projet. 2. Add attached file. 3. Run the app to iOS device 4. Monitor network traffic so you can see the request headers (as per screenshot attached).
| 0 |
3,743 |
TIMOB-27398
|
09/07/2019 19:19:22
|
Android: Random assets missing after compiling
|
{code} Operating System Name = Fedora Version = 30 Architecture = 64bit # CPUs = 12 Memory = 15.3GB Node.js Node.js Version = 10.16.3 npm Version = 6.9.0 Appcelerator CLI Installer = 4.2.15 Core Package = 7.1.1 Titanium CLI CLI Version = 5.2.1 node-appc Version = 0.2.49 {code} I have some local websites in my "/app/assets/www/" folder to display charts and barcodes. While it worked fine with 8.0.2.GA I have some big issues with the latest 8.1.1.GA or CLI version listed above. Every compile a different item out of the "/app/assets/www" is missing! !Screenshot_20190907_200524.png|thumbnail! on the left side is my folder. I've open the APK inside a zip tool: the middle is the first run, the right image is the last run. Some files are the same but some files are missing. I've tried to rename the files but that didn't work either
| 5 |
3,744 |
TIMOB-27384
|
09/08/2019 21:15:35
|
iOS 13: App can crash if deprecated "statusBarFrame" property is called
|
When accessing the (in iOS 13 deprecated) "statusBarFrame" property, e.g. for rare view controller changes, the app can crash. Migrating to the iOS 13+ "statusBarManager" API of the "UIWindowScene" will fix the issue. It can be reproduced by trying my [titanium-scanner|https://github.com/hansemannn/titanium-scanner] module and clicking "Cancel" on the scanner view controller. Pull request: https://github.com/appcelerator/titanium_mobile/pull/11201
| 0 |
3,745 |
TIMOB-27386
|
09/09/2019 14:12:07
|
iOS: Correctly decode push notification token
|
h5.Description On iOS 13 registering for push notifications returns an invalid device token, this is because the way we decode the device token has been broken by apple (although it seems it wasnt a recommended way anyways) See https://github.com/OneSignal/OneSignal-iOS-SDK/pull/509 {code} Ti.App.iOS.addEventListener('usernotificationsettings', function registerForPush() { // Remove event listener once registered for push notifications Ti.App.iOS.removeEventListener('usernotificationsettings', registerForPush); Ti.Network.registerForPushNotifications({ success: deviceTokenSuccess, error: deviceTokenError, callback: receivePush }); }); // Register notification types to use Ti.App.iOS.registerUserNotificationSettings({ types: [ Ti.App.iOS.USER_NOTIFICATION_TYPE_ALERT, Ti.App.iOS.USER_NOTIFICATION_TYPE_SOUND, Ti.App.iOS.USER_NOTIFICATION_TYPE_BADGE ] }); // Process incoming push notifications function receivePush(e) { alert('Received push: ' + JSON.stringify(e)); } // Save the device token for subsequent API calls function deviceTokenSuccess(e) { console.log('Yay it worked!'); console.log(e); } function deviceTokenError(e) { console.log('Failed to register for push notifications! ' + e.error); console.log(e); } {code} h5.Steps to reproduce 1. Add the below code to an app.js or alloy.js h5.Actual The device token printed looks like {code} {length=32,bytes=0x17b4427542a3d1e6a4d69d976b4539bc...7edb18a21200a8d2} {code} h5.Expected The device token should look like {code} 17b4427542a3d1e6a4d69d976b4539bcf227f216b02b5fd97edb18a21200a8d2 {code}
| 3 |
3,746 |
TIMOB-27390
|
09/10/2019 18:06:38
|
Update Hyperloop to 4.0.4
|
Update the SDK's bundled Hyperloop version to 4.0.4
| 3 |
3,747 |
TIMOB-27395
|
09/12/2019 00:26:54
|
iOS: Support new devices in os.cpus()
|
- {{os.cpus()}} will fail for newer devices **TEST CASE** {code:js} const os = require('os'); console.log(JSON.stringify(os.cpus(), 1)); {code}
| 3 |
3,748 |
TIMOB-27403
|
09/16/2019 14:03:56
|
CLI: Semantic colors file lookup does not work correctly in classic applications
|
h5.Description When looking up the {{semantic.colors.json}} file for classic applications we look in {{Resources/iphone}} this isn't really the place we want to find it. We want to also look in {{Resources}} as it's intended to be cross-platform h5.Steps to reproduce 1. Get the project from https://github.com/ewanharris/darkmode-example-classic 2. Build to an iOS 13 sim/device 3. Toggle dark mode h5.Actual App has white window and black label always h5.Expected App should change between a yellow window with a red label (light mode) and green window with a pink label (dark moe)
| 3 |
3,749 |
TIMOB-27409
|
09/19/2019 05:53:14
|
Kitchensink : Liveview is not working
|
Steps To Reproduce: 1.import kitchen sink 2.run on android or iOS device./simulator with live view Notes: live view works fine on default classic and alloy app Expected: live view should work fine Actual: [ERROR] : Script Error { [ERROR] : column = 24; [ERROR] : line = 666; [ERROR] : message = "[LiveView] File Server unavailable. Host Unreachable @ 192.168.0.17:8324\n[LiveView] Please ensure your device and computer are on the same network and the port is not blocked."; [ERROR] : sourceURL = "file:///Users/kmahalingam/Library/Developer/CoreSimulator/Devices/2A09648F-A541-4DD5-9E06-3B6087C54CB3/data/Containers/Bundle/Application/BFC9131E-82B1-42A3-AABC-3756D8287256/KitchenSink.app/app.js"; [ERROR] : stack = " at _getRemoteSource(/app.js:666:24)\n at _getSource(/app.js:682:35)\n at _compile(/app.js:718:30)\n at require(/app.js:586:25)\n at patch(/app.js:424:45)\n at (/app.js:763:15)\n at (/app.js:768:3)\n at global code(/app.js:771:70)\n at require@[native code]\n at (/ti.main.js:11677:10)\n at loadAsync(/ti.main.js:11603:13)\n at global code(/ti.main.js:11674:10)"; [ERROR] : toJSON = "<KrollCallback: 0x600001d9dfc0>"; [ERROR] : } [DEBUG] : Firing app event: uncaughtException [ERROR] : Script Error { [ERROR] : column = 10; [ERROR] : line = 11677; [ERROR] : message = "Module \"app.js\" failed to leave a valid exports object"; [ERROR] : sourceURL = "file:///Users/kmahalingam/Library/Developer/CoreSimulator/Devices/2A09648F-A541-4DD5-9E06-3B6087C54CB3/data/Containers/Bundle/Application/BFC9131E-82B1-42A3-AABC-3756D8287256/KitchenSink.app/ti.main.js"; [ERROR] : stack = " at require@[native code]\n at (/ti.main.js:11677:10)\n at loadAsync(/ti.main.js:11603:13)\n at global code(/ti.main.js:11674:10)"; [ERROR] : toJSON = "<KrollCallback: 0x600001d87400>"; [ERROR] :
| 5 |
3,750 |
TIMOB-27419
|
09/23/2019 00:06:08
|
Ti.Contacts.getAllPeople() fails on iOS 13
|
Apple have added a new entitlement com.apple.developer.contacts.notes which allows apps to access the notes field of the contact db. The new entitlement is on a per app basis with developers required to put their case to Apple to gain it. Titanium requests CNContactNoteKey as part of the Ti.Contacts.getAllPeople method. This triggers a CNErrorDomain error 102. Any app compiled for iOS 13 without this entitlement will not be able to use the Ti.Contacts module for anything; regardless of needing the notes field. To test create an empty project with the following in tiapp.xml <key>NSContactsUsageDescription</key> <string>Contacts test</string> Add the following to alloy.js var people = Ti.Contacts.getAllPeople(); error in console
| 5 |
3,751 |
TIMOB-27413
|
09/23/2019 13:01:40
|
iOS: Window hideShadow and shadowImage property doesn't works on iOS 13
|
There was a trick to remove the shadow on navigation bar. It consisted on set a image of the same color as the background and set it to *barImage* property and set *hideShadow* to true. It is working with 8.2.0.GA on iOS 13 < but not on iOS 13. tss: {code:javascript} "Window" : { navTintColor: 'black', translucent: false, hideShadow: true, barImage: '/images/barBackground.png', //white imagen 1px size } {code} This line could be related with: https://github.com/appcelerator/titanium_mobile/blob/11aef9cc1069c395e8f9a45570633e40dd80f76e/iphone/TitaniumKit/TitaniumKit/Sources/Modules/TiUIWindowProxy.m#L442 On the screenshot attached: - iOS 13 on the left side. - iOS 12 on the right side.
| 5 |
3,752 |
TIMOB-27412
|
09/23/2019 13:05:54
|
Android: App stuck at launch screen when opened through notification
|
We noticed a strange behavior where the app sometimes hangs on the launch screen when opened through the click on a notification (Firebase powered). For sample code, please refer to our app thats internally shared.
| 5 |
3,753 |
TIMOB-27420
|
09/25/2019 20:54:59
|
Android: ImageView.toImage() does not return the correct Ti.Blob
|
- {{Titanium.UI.ImageView.toImage}} does not return the image {{Blob}} for the current image. *TEST CASE* {code:js} const Map = require('ti.map'); const win = Ti.UI.createWindow({ backgroundColor: 'white' }); const img = Ti.UI.createImageView({ width: 28, height: 28, image: 'appicon.png' }); const map = Map.createView({ region: { latitude: -33.87365, longitude: 151.20689, latitudeDelta: 0.1, longitudeDelta: 0.1 }, annotations: [ Map.createAnnotation({ latitude: -33.87365, longitude: 151.20689, title: 'Icon', image: img.toImage() // Should see icon center of map // image: 'appicon.png' }) ], }); win.add(map); win.open(); {code}
| 3 |
3,754 |
TIMOB-27424
|
09/27/2019 13:27:05
|
Android: Video player splashing black screen just before playing video
|
*Issue Description:* When trying to play video in video player, it shows a black screen just before playing video using Ti SDK 8.2.0 on android 8 and 8.1.0 *Steps to reproduce:* 1. Create an alloy project and replace the code 2. Download "test.mp4" video file from the attachment and place that in app/assets/android/video folder. 2. Build the project and observe it'll show a black screen before playing the video. *Expected:* Shouldn't show any black screen before playing the video. *Actual:* Shows a black screen before playing the video. *Attachment:* See the screencast "black_screen_issue.mp4" *Test Code:* *index.xml:* {code} <Alloy> </Alloy> {code} *index.js* {code} var vidWin = Titanium.UI.createWindow({ title : 'Video View Demo', backgroundColor : '#fff' }); var videoPlayer = Titanium.Media.createVideoPlayer({ top : 2, autoplay : true, backgroundColor : 'blue', //height : 300, //width : 300, height: Titanium.UI.SIZE, width: Titanium.UI.FILL, mediaControlStyle : Titanium.Media.VIDEO_CONTROL_NONE, scalingMode : Titanium.Media.VIDEO_SCALING_ASPECT_FIT }); videoPlayer.url = '/video/test.mp4'; vidWin.add(videoPlayer); vidWin.open(); {code}
| 0 |
3,755 |
TIMOB-27427
|
09/30/2019 08:31:58
|
iOS 13: Natively presented modal windows are not dismissed properly
|
When using iOS 13, native modal windows like the one from {{Ti.Media.showCamera}} are not presented correctly, causing the underlaying view controller to not be dismissed correctly. {code:js} var win = Ti.UI.createWindow(); var btn = Ti.UI.createButton({ title: 'Show camera' }); btn.addEventListener('click', () => { Ti.Media.requestCameraPermissions(event => { Ti.Media.showCamera({ success: () => {}, error: () => {}, cancel: () => {}, }); }); }); win.add(btn); win.open(); {code}
| 5 |
3,756 |
TIMOB-27434
|
10/02/2019 03:10:44
|
Android: Re-layout of deeply nested views can cause performance issues as of 7.5.0
|
*Summary:* If you have very deeply nested views (say 15 or more), then anything that causes them to be re-laid out can cause noticeable performance issues as of Titanium 7.5.0. *Steps to reproduce:* # Build and run the below code on Android. # Tap and hold on the text within the {{TextField}}. # Notice that the app hangs for a couple of seconds. # Rotate the device to landscape. # Notice that the app hangs for a couple of seconds. {code:javascript} var window = Ti.UI.createWindow(); var rootView = Ti.UI.createView({ width: Ti.UI.FILL, height: Ti.UI.FILL }); var topView = rootView; for (var index = 0; index < 20; index++) { var nextView = Ti.UI.createView({ width: Ti.UI.FILL, height: Ti.UI.FILL }); topView.add(nextView); topView = nextView; } var textField = Ti.UI.createTextField({ value: "Hello World", width: "80%", }); topView.add(textField); window.add(rootView); window.open(); {code} *Cause:* This regression was introduced in 7.5.0 when we added the "extendSafeArea" and "safeAreaPadding" feature. The performance issue is caused by our Java [TiCompositeLayout.onApplyWindowInsets()|https://github.com/appcelerator/titanium_mobile/blob/3b925d3b89e0d59bf89b846bfa127e9656746dbf/android/titanium/src/java/org/appcelerator/titanium/view/TiCompositeLayout.java#L460] method when you have deeply nested views (say 15 or more layers). The dispatched window inset handling appears to get exponentially worse the more views you have nested. Especially since each child view that applies those insets triggers a request-layout. *Work-around:* Only known work-around is to not nest your views so deeply. Try not to nest more than 10 layers deep.
| 5 |
3,757 |
TIMOB-27435
|
10/02/2019 12:33:11
|
iOS: Building using Xcode 10.3 and 8_2_X Throws a Compile Error
|
Building for target 12.4 simulators on Xcode 10.3 errors out with a compile error when building on SDK 8.2.1.v20191001063013. {code} [ERROR] ** BUILD FAILED ** [ERROR] The following build commands failed: [ERROR] CompileC /Users/shaig/Workspace/GitHub/qe-FeatureTest/ActivityIndicator/module_activityindicator/build/iphone/build/Intermediates/module_activityindicator.build/Debug-iphonesimulator/module_activityindicator.build/Objects-normal/x86_64/TiUIiOSApplicationShortcutsProxy.o /Users/shaig/Workspace/GitHub/qe-FeatureTest/ActivityIndicator/module_activityindicator/build/iphone/Classes/TiUIiOSApplicationShortcutsProxy.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler [ERROR] (1 failure) {code} [~eharris] points to this being from the following changes: https://github.com/appcelerator/titanium_mobile/commit/b1d6ce01a164e8a7d23edae8ba22d0f788a87716#diff-e1a4da0f4a0b16271e27fc854bcd357fR10 https://github.com/appcelerator/titanium_mobile/commit/b1d6ce01a164e8a7d23edae8ba22d0f788a87716#diff-e1a4da0f4a0b16271e27fc854bcd357fR215-R223
| 2 |
3,758 |
TIMOB-27460
|
10/10/2019 10:55:21
|
iOS: tintColor not working for TabbedBar/ButtonBar on iOS 13
|
With iOS 13 the styling of the {{UISegmentedControl}} significantly changed. Previously the color of the selected element and the border color could simply be set with {{tintColor}}. Now this requires a combination of {{backgroundColor}} / {{selectedSegmentTintColor}} / {{setTitleTextAttributes}} and manual settings for borders using the underlying {{layer}}. See also https://stackoverflow.com/a/56874473/1168989 *Steps to reproduce the behavior* {code:js} const win = Ti.UI.createWindow({ backgroundColor: 'black' }); var test = Ti.UI.createTabbedBar({ labels: [ '1', '2', '3', 'AUTO' ], tintColor: 'white' }); win.add(test); win.open(); {code} *Actual behavior* The controls has no border and unselected elements are barely visible. !Schermata 2019-10-10 alle 11.21.28.png|thumbnail! *Expected behavior* The control has a border and unselected element are colored according to {{tintColor}}. !Schermata 2019-10-10 alle 11.21.24.png|thumbnail!
| 5 |
3,759 |
TIMOB-27461
|
10/10/2019 11:09:48
|
Android:Extra padding if enableZoomControl is true for imageView on 8.2.0.GA
|
The customer has a requirement where they need to display an image inside a scrollview and provide zoom controls for that image. But they are able to see the extra spacing at top and bottom of the image. If the "enableZoomControls" is set to false, image displayed properly without any extra spaces. Currently they are using 8.0.2.GA SDK. Note: We tested the issue on 8.2.0.GA, Huawei Gr3 2017(Android 7) and the issue is reproduced on our end. *Test steps:* * Create a classic project * Download the image file and paste it on resources * Paste the sample code to app.js * Run the project on device. After running, we are able to see the extra spacing at top and bottom of the image. *Test Code:* {code} var win = Ti.UI.createWindow({ backgroundColor: '#fff', layout : 'vertical' }); var scrollView = Ti.UI.createScrollView({ layout : 'vertical', width : Ti.UI.FILL, contentWidth : '100%', height : Ti.UI.FILL }); var imageViewContainer = Ti.UI.createView({ height : Ti.UI.SIZE, width : Ti.UI.SIZE, }); var file = Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory,'test.png'); imageViewContainer.add(Ti.UI.createImageView({ image : file, width:Ti.UI.SIZE, height:Ti.UI.SIZE, enableZoomControls : true, borderColor:'red' })); scrollView.add(imageViewContainer); win.add(scrollView); win.open(); {code} *Test Output:* "enableZoomControls" is true: !Screenshot_20191010-155604.png|thumbnail! "enableZoomControls" is false: !Screenshot_20191010-155205.png|thumbnail!
| 1 |
3,760 |
TIMOB-27469
|
10/15/2019 09:11:28
|
iOS: SelectedBGColor of list item is overriding the BG color view
|
h6.Problem When adding background color for Ti.UI.View/Label of the ListView item. But on the select of list view item, "selectedBackgroundColor" of the list item is overriding the background color of the Ti.UI.View. h6.Reproduce 1. Create a default classic app. 2. Use the attached app.js code. 3. Run the code on SDK 8.1.0 and 8.2.0 h6.Expected When clicking on the ListView item, we should still see the background color of the Ti.UI.View. h6.Actual When clicking on the ListView item, unable to see the background color of the Ti.UI.View. (attached screenshot) h6.Note 1. This happens on simulator and device on iOS 12 and below 2. Based on the customer's comment, it happened to the iOS 13 devices. 3. I do test that It is working well on iOS 13 simulator.
| 5 |
3,761 |
TIMOB-27471
|
10/15/2019 12:19:24
|
Android: Unable to load large image to image view
|
The customer has a requirement where they need to get image and display it in the image view. Few images are not displayed even though images are bind to the image view. *It is throwing warning “[WARN] : OpenGLRenderer: Bitmap too large to be uploaded into a texture (4196x3363, max=4096x4096)”.* I {panel} This issue is happening because of size 4196x3363, max=4096x4096. The log mentions the max size max=4096x4096. Is there any solution or workaround for this issue? Note : This issue is on Nexus 7(OS 6.0.1) and Samsung s4(OS 4.4) devices. It is working fine on Pixel(9.0) device. Tested with 8.0.2.GA Ti SDK and 8.2.0.GA Ti SDK. {panel} Sample Test Code: {code} var win = Ti.UI.createWindow({ backgroundColor : '#fff' }); win.add(Ti.UI.createImageView({ image : Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory, 'test.png'), width : Ti.UI.SIZE, height : Ti.UI.SIZE, borderColor : 'red' })); win.open(); {code} *Steps to reproduce:* 1. Create a sample classic project 2. Replace the app.js with attached app.js content. 3. Place the attached test.png under “Resources” folder. 4. Run the app in Nexus 7 device. *Expected*: Image should bee rendered properly. *Actual:* Image not rendered and throwing warning in the console. *Note:* We tested it and able to reproduce with the big image as like the customer image on HTC M8 eye v6.0.1
| 1 |
3,762 |
TIMOB-27472
|
10/16/2019 01:15:23
|
Android: Add Java 8 support
|
*Summary:* Titanium currently support "Java 7" language features. In Titanium 9.0.0, we would like to add "Java 8" language features for the core SDK and all modules. This is needed since some 3rd party Android libraries use the Java 8 language, but we're currently unable to compile them into a module or via hyperloop. *Limitations:* Android has limited support for Java 8 language features which Google documents below. Note that older Android OS versions support less Java 8 features. https://developer.android.com/studio/write/java8-support#supported_features *Recommended Solution:* We don't support Java 8 because Titanium is currently limited to using the "dex" command line tool in the Android SDK which only supports up to Java 7. Google's "d8" command line tool supports Java 8. If we update our Titanium build system to use gradle, then we can easily add support for this. Support can be added via the following "build.gradle" settings... {code:groovy} android { compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 } // When we add Kotlin support in the future, // then we must do the following as well. kotlinOptions { jvmTarget = "1.8" } } {code} *Testing:* We should add a Java 8 feature to our core Titanium code to prove that Java 8 compilation works for both the SDK and an app build. In our [TiUIView.java|https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/src/java/org/appcelerator/titanium/view/TiUIView.java] code, I recommend that we change the following code... {code:java} protected void setOnClickListener(View view) { view.setOnClickListener(new OnClickListener() { public void onClick(View view) { fireEvent(TiC.EVENT_CLICK, dictFromEvent(lastUpEvent)); } }); } {code} ...to use a Java 8 lambda as follows... {code:java} protected void setOnClickListener(View view) { view.setOnClickListener((clickedView) -> { fireEvent(TiC.EVENT_CLICK, dictFromEvent(lastUpEvent)); }); } {code} We can then test the above via a Titanium {{Ti.UI.Button}} object's "click" event. {code:javascript} var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Show Alert" }); button.addEventListener("click", function() { alert("Button clicked!"); }); window.add(button); window.open(); {code}
| 5 |
3,763 |
TIMOB-27473
|
10/16/2019 02:23:12
|
Android: Replace clang Java formatter with gradle "checkstyle" tool
|
*Summary:* The Android gradle build system includes its own "checkstyle" tool. This tool is used to enforce Java coding standards and to check for common Java coding errors. It can be used to trigger build errors that fails to pass the configured rules defined in a "checkstyle.xml" file. https://docs.gradle.org/current/userguide/checkstyle_plugin.html https://checkstyle.org/index.html *To-Do:* We should replace our existing clang-format tool in favor of this gradle checkstyle tool. The main reason is because the dev team does not know they are violating the clang linter's rules until its been ran on Jenkins (or ran manually via node). * Jenkins is verifying the clang formatting rules by reformatting changed Java files and doing a comparison of files. This is too restrictive because the reformat of the files sometimes looks worse from a readability standpoint. (Too restrictive.) * The dev team sometimes doesn't know they are violating clang's rules until a PR has been submitted to Jenkins or we run it manually via node. (Common mistake.)
| 8 |
3,764 |
TIMOB-27476
|
10/16/2019 22:07:35
|
docs: deprecate Ti.Analytics.navEvent
|
- Deprecate old and unused {{Ti.Analytics.navEvent}}
| 2 |
3,765 |
TIMOB-27479
|
10/17/2019 13:34:34
|
Webpack: Automatically exclude Titanium modules
|
Titanium modules need to be marked as external so Webpack does not try to parse/bundle them.
| 5 |
3,766 |
TIMOB-27482
|
10/18/2019 08:24:32
|
iOS: App is crashing with SDK 8.2.0.GA on iOS 13 devices
|
If repeat the following operations on ios13, the app will crash. Crash logs and videos are attached herewith.What is the cause? *Test steps:* 1. Start application 2. Select a video 3. Click on Choose 4. Wait for compressing video 5. Then move the app to the background with the home button. Wait for a few seconds after moving the app to the background and then click on the App icon for opening it. It should be reproducible if repeated several times. *Test project:* Click [here|https://drive.google.com/file/d/1d8KSP9olLafRle2O44ydMztlJ5H_oPkh/view?usp=sharing] *Output:* [Video|https://drive.google.com/open?id=1np1TSXQ52D-1Op4cZXj8y30w0kmU-z_E] *Note:* We also tested this on iPhone SE(13.1.3) and the issue is reproduced on our end. Video is uploaded on output section.
| 8 |
3,767 |
TIMOB-27484
|
10/21/2019 11:08:51
|
iOS: App fails to launch with "undefined is not an object" on iOS 9
|
h5.Description When building to an iOS 9 device/simulator the following error is seen, it's probable this is down to some of the recent refactorings in the build scripts relating to ti.main {code} [ERROR] Script Error { [ERROR] column = 119; [ERROR] line = 5633; [ERROR] message = "undefined is not an object (evaluating 'Object.getOwnPropertyDescriptor(TypedArrayPrototype, Symbol.toStringTag).get')"; [ERROR] sourceURL = "file:///Users/awam/Library/Developer/CoreSimulator/Devices/D1F3D800-B22D-43F1-A517-7BF234508D73/data/Containers/Bundle/Application/4F541A06-7C24-4A32-9595-CBD8F3410E48/ticreateapp.app/ti.main.js"; [ERROR] stack = " at global code(/ti.main.js:5633:119)"; [ERROR] } {code} h5.Steps to reproduce 1. Build an app to iOS 9 h5.Actual Error above h5.Expected App should launch fine
| 5 |
3,768 |
TIMOB-27487
|
10/21/2019 21:54:52
|
Android: Build x86_64 module libraries
|
- Include {{x86_64}} ABI by default - Build {{x86_64}} compatible V8 library - Possibly drop {{x86}} ABI from defaults?
| 5 |
3,769 |
TIMOB-27493
|
10/23/2019 11:34:02
|
Android: Videos do not play correctly on Android 5.1 (API 22)
|
*Summary* When playing a video from URL using Media.VideoPlayer, the video freezes after 2-3 seconds and errors are displayed on Android 5.1 (API level 22). *Steps to reproduce* # Create a Classic titanium app project # Add the below code to _app.js_ # Use any of the affected SDK versions (e.g. 8.2.0.GA) # Run on Android API 22 emulator or device {code:js} var window = Ti.UI.createWindow({ fullscreen: true }); var videoView = Ti.Media.createVideoPlayer({ url: "http://assets.appcelerator.com.s3.amazonaws.com/video/media.m4v", autoplay: true, width: Ti.UI.FILL, height: Ti.UI.FILL, }); window.add(videoView); window.open(); {code} *Result* The video freezes after 2-3 seconds. "Titanium apps have rich multimedia" is shown. Errors also displayed in terminal: {code:js} [WARN] MediaHTTPConnection: readAt 3113714 / 32768 => java.net.ProtocolException [ERROR] MediaPlayer: Should have subtitle controller already set [DEBUG] EGL_emulation: eglMakeCurrent: 0xb42baa60: ver 2 0 (tinfo 0xb43a2e60) [ERROR] MediaPlayer: error (1, -19) [ERROR] MediaPlayer: Error (1,-19) [DEBUG] TiVideoView8: (main) [27668,27793] Error: 1,-19 [DEBUG] EGL_emulation: eglMakeCurrent: 0xb42baa60: ver 2 0 (tinfo 0xb43a2e60) [DEBUG] EGL_emulation: eglMakeCurrent: 0xb42baa60: ver 2 0 (tinfo 0xb43a2e60) [WARN] MediaPlayer: info/warning (3, 0) [ERROR] MediaPlayer: error (1, -1004) [ERROR] MediaPlayer: Error (1,-1004) [DEBUG] TiVideoView8: (main) [2109,29902] Error: 1,-1004 {code} *Expected Result* The video should play as normal and there should not be any errors in the terminal.
| 5 |
3,770 |
TIMOB-27496
|
10/24/2019 03:14:09
|
Android: Setting ListView row item property not in template will be wrongly duplicated on offscreen rows
|
The customer discovered a bug with ListView on Android. The issue happens when having a very long list. They use one template for all items and show/hide certain parts of it depending on their business logic. They've noticed that when scrolling below the fold and scroll back up items are being re-rendered using styles from the LAST item in the list. Instead of showing/hiding items, they colored them red. Notice that when rendered it looks correct. When scrolling down and encounter accounts colored with red background and scroll up - previously non-colored accounts also get the red background. The customer tested on Samsung S6, S7, S8, S9, S10 with SDK 8.2.0 GA. Note: We tested the issue on 8.2.0.GA, Sumsang Galaxy A7(Android 9) and the issue is reproducible on our end. *Test steps:* 1. Download the attached project. 2. Open appcelerator studio and import the project. 2. Run the project on a device. *Test code:* https://drive.google.com/file/d/14BetKOnAO_JN7Kr33sJti65Jcmdrkga3/view?usp=sharing *Test result:* https://drive.google.com/file/d/10PFwqwx-CYTnJzfft6PmFpZG_UF1TDGp/view?usp=sharing Note: On iOS it works as expected.
| 5 |
3,771 |
TIMOB-27498
|
10/24/2019 19:02:18
|
iOS: Intermittent UI Layout test failures
|
We are seeing intermittent UI Layout test failures. Specifically here's a failure from a build: https://jenkins.appcelerator.org/job/titanium-sdk/job/titanium_mobile/job/8_2_X/46/testReport/ The test failures are variants of a test around TIMOB-23372, and expect a post layout event to have a rect with an x property equal to 10 (the left padding). Sometimes this event fires with a value of 9. This appears to be related to simulators being created by our appium suite? Failures: Building for iOS Simulator: appiumTest-63D0910A-9E17-4437-AF50-781E3BCBC590-iPhone 7 Building for iOS Simulator: appiumTest-C4E4A63F-7A15-4130-A574-6E7FA5B5D620-iPhone 7 Passed: Building for iOS Simulator: iPhone 11 Pro Max Building for iOS Simulator: iPhone 11 Pro Max
| 1 |
3,772 |
TIMOB-27503
|
10/25/2019 10:44:43
|
iOS : Open an iPad Popover crash the app
|
From SDK > 8.2.0.GA opening a Popover crash the app. Tested on iOS 11,12,13 simulator. With SDK 8.2.0.GA no problems. Code from http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.iPad.Popover {code} var win = Ti.UI.createWindow({backgroundColor: 'white'}); var button = Ti.UI.createButton({title: 'Open Popover!'}); button.addEventListener('click', function(e){ popover.show({ view: button }); }) win.add(button); var rightButton = Ti.UI.createButton({title: 'Robin'}); rightButton.addEventListener('click', function(e){ alert("But green's the color of spring."); }); var contentWindow = Ti.UI.createWindow({ rightNavButton: rightButton, title: 'Kermit' }); contentWindow.add(Ti.UI.createLabel({text: "It's not easy being green."})); var popover = Ti.UI.iPad.createPopover({ backgroundColor: 'green', contentView: Ti.UI.createNavigationWindow({ width: 250, height: 100, window: contentWindow }) }); win.open(); {code}
| 5 |
3,773 |
TIMOB-27525
|
10/25/2019 14:33:15
|
Commented out line with Ti.include in it causes LiveView failure
|
On any project, add the following line: {code:java} //Ti.include('vendor/pubnub.js'); {code} Make sure the line is *COMMENTED OUT* with the single line prefix *//*. Compile the app with LiveView turned on. The file load will fail. Remove the line and save, the file will load without issue. It seems that somehow, LiveView is ignoring the fact the line is commented out and trying to process the 'include' function, causing the error. If you surround by a multi line comment like this instead, then it works. {code:java} /*Ti.include('vendor/pubnub.js');*/ {code}
| 3 |
3,774 |
TIMOB-27616
|
11/01/2019 14:22:48
|
Android: TextField with decimal keyboard type does not allow comma for decimal separator
|
*Summary:* When using a {{TextField}} with "keyboardType" set to {{KEYBOARD_TYPE_DECIMAL_PAD}} or {{KEYBOARD_TYPE_NUMBERS_PUNCTUATION}}, the end-user is only allowed to enter a period '.' for the decimal point. It ignores the current locale and does not allow other types of decimal separators such as a comma ',' which is used Europe and South America. *How to add languages on Android:* # Go to Android's main Settings screen. # Tap on "System". # Tap on "Language & Input". # Tap on "Languages". # Tap on "Add Language". # Select a European language such as "German"/"Deutsch". # Drag-and-drop the language to the top of the list. *Steps to reproduce:* # Build and run the below code on Android. # Select a European language. (See language instructions above.) # Tap on the {{TextField}}. # Attempt to enter {{1,5}} with a comma. # Notice it won't let you use a comma ',' for the decimal separator. # Enter {{1.5}} with a period. # Notice that it allows a period, but this is not correct for the current locale. {code:javascript} var window = Ti.UI.createWindow(); window.add(Ti.UI.createTextField({ keyboardType: Ti.UI.KEYBOARD_TYPE_DECIMAL_PAD, width: "90%", })); window.open(); {code} *Note:* This is actually a bug on Google's end. They have a *+partial+* fix for it as of Android 8.0 by using passing the current {{Locale}} to a {{DigitsKeyListener}} constructor. https://developer.android.com/reference/android/text/method/DigitsKeyListener#DigitsKeyListener(java.util.Locale) Unfortunately, Google's fix is incomplete and has the following issues: * Fullscreen edits (when in landscape) is not fixed. Only allows period for decimal point. * Does not support Arabic decimal separator at all. * Android OS versions older than 8.0 can't use their fix. We need a solution for Android 4.4 too. \\ \\ ---- *Original Post:* In Denmark the decimal separator is comma (,) But when setting {code} TextField.keyboardType = Ti.UI.KEYBOARD_TYPE_NUMBERS_PUNCTUATION; {code} Titanium Shows a keyboard with a dot (.) instead... And when parsing a value with Danish Locale 20.50 becomes 2050 On IOS the keyboard is shown with a comma (,) and everything works as expected
| 13 |
3,775 |
TIMOB-27524
|
11/04/2019 16:10:00
|
Android: imageView toBlob() method returns null.
|
*Issue:* imageview toBlob() method returns null but it should return as a blob object. It returns a proper value in iOS Steps to Reproduce 1. Run the following sample code on an emulator or a device 2. Then check the console log. {code:title=app.js} var win = Titanium.UI.createWindow({ className : 'win' }); var img = Ti.UI.createImageView({ image : 'http://ursinus.prestosports.com/sports/wbkb/2019-20/photos/KRR_48190-1.jpg?max_width=160&max_height=120', top : 40, width : 200, height : 200 }); win.add(img); Ti.API.info("ImgeView:", img.toBlob()); win.open(); {code} {code:java} WARN] : TiDrawableReference: (main) [137661,138015] Could not open stream to get bitmap [INFO] : ImgeView: null [INFO] : Choreographer: Skipped 1797 frames! The application may be doing too much work on its main thread. [INFO] : APSAnalyticsStore: session.end [INFO] : APSAnalyticsService: Successfully sent 1 stored event(s) {code}
| 0 |
3,776 |
TIMOB-27530
|
11/06/2019 16:21:27
|
Android: UI glitches out when using 'applyProperties' with Scroll View Touch Listeners
|
Application UI glitches out when trying to drag a label horizontally. *Test case:* {code:java} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var scroll = Ti.UI.createScrollView({ scrollType: 'vertical', contentHeight: 3010, text: 'Scroll View' }); var width = 150, height = 90; for (var i = 0; i < 30; i++) { scroll.add(Ti.UI.createLabel({ draggable: true, text: 'Drag Me Horizontally ' + (i + 1), textAlign: 'center', color: '#000', top: i * 100 + 10, width: width, height: height, backgroundColor: '#eee' })); } scroll.addEventListener('touchstart', doDrag); scroll.addEventListener('touchmove', doDrag); scroll.addEventListener('touchcancel', doDrag); scroll.addEventListener('touchend', doDrag); function doDrag(evt) { Ti.API.info('Event Fired On: ' + evt.source.text); if (evt.source.draggable) { var global = evt.source.convertPointToView({ x: evt.x, y: evt.y }, scroll); evt.source.applyProperties({ left: global.x - width / 2 }); } } win.add(scroll); win.open(); {code} *Test Steps* # Create a Titanium application # Add the code above in to the ((app.js}} # Run on Android # Try to drag a label horizontally *Actual result* Whole application moves and UI glitches out *Expected result* Only label should move horizontally
| 5 |
3,777 |
TIMOB-27533
|
11/09/2019 13:28:52
|
iOS: TabbedBar backgroundColor is not working with latest SDK
|
Hello! TabbedBar backgroundColor is not working with the latest SDK on iOS. *Test Code*: {code} var win = Ti.UI.createWindow({ layout : "vertical" }); var bb1 = Titanium.UI.createTabbedBar({ labels : ['One', 'Two', 'Three'], backgroundColor : 'red', top : 50, height : 25, width : 200 }); win.add(bb1); win.open(); {code} *Test Environment*: I tested with 12.1 simulators both Ti SDK 8.2.0.GA, 8.2.1.GA Please take a look at the attached screenshot.
| 5 |
3,778 |
TIMOB-27573
|
11/11/2019 07:07:13
|
Android: Hiding/Showing progress indicator back-to-back puts it in a bad state as of 8.1.1
|
*Summary:* Hiding and showing a progress indicator dialog like the below prevents the dialog from being hidden ever again. {code:javascript} // Hide/show dialog back-to-back. progressIndicator.hide(); progressIndicator.show(); // Uh-oh. Can never hide dialog ever again now. {code} *Steps to reproduce:* # Build and run the below code on Android. # Tap on the button. # Notice the progress dialog never closes. (Supposed to close in 5 seconds.) {code:js} var self = Ti.UI.createWindow({ backgroundColor:'#ffffff', navBarHidden:true, exitOnClose:true }); var button = Ti.UI.createButton({ title: 'Show Progress Dialog' }); var progressIndicator = Ti.UI.Android.createProgressIndicator({ message: 'Loading...', location: Ti.UI.Android.PROGRESS_INDICATOR_DIALOG, cancelable: true, }); button.addEventListener('click', function (e) { progressIndicator.show(); setTimeout(function(){ progressIndicator.hide(); progressIndicator.show(); }, 3000); setTimeout(function(){ progressIndicator.hide(); }, 5000); }); self.add(button); self.open(); {code}
| 3 |
3,779 |
TIMOB-27574
|
11/13/2019 01:35:09
|
Android: Replace SDK "build.properties" with gradle generated "BuildConfig" class
|
*Summary:* When building the Titanium SDK, we generate a "build.properties" file (similar to an {{INI}} file) providing the Titanium library's version and build time information. This file is stored under APK "assets" and is read on app startup via the Java method below. [TiApplication.loadBuildProperties()|https://github.com/appcelerator/titanium_mobile/blob/5fbe78276e04049874e13bcc0a3874593f27254e/android/titanium/src/java/org/appcelerator/titanium/TiApplication.java#L300] By default, gradle generates a {{BuildConfig}} Java class for all libraries and apps. We should use this feature instead of generating our own "build.properties" file. It will simplify our build process... and access to this info at runtime will be faster. https://developer.android.com/studio/build/gradle-tips#share-custom-fields-and-resource-values-with-your-app-code *Example:* {code:groovy} // The "build.gradle" file. android { defaultConfig { buildConfigField('String', 'BUILD_VERSION', '"9.x.x"') buildConfigField('String', 'BUILD_TIMESTAMP', '"YYYY/MM/DD HH:MM"') buildConfigField('String', 'BUILD_GIT_HASH', '"HEAD"') } } {code} *Note:* This information is logged on app startup as... {code} <AppName> <AppVersion> (Powered by Titanium <Version>.<GitHash>) {code} The above message gets logged in the code below... [ti.main.js#L15|https://github.com/appcelerator/titanium_mobile/blob/5fbe78276e04049874e13bcc0a3874593f27254e/common/Resources/ti.main.js#L15]
| 5 |
3,780 |
TIMOB-27601
|
11/14/2019 13:43:47
|
Windows: remove analyzeJsFile hook from titanium_mobile & hyperloop code
|
h5.Description Windows uses a non standard hook in the hyperloop module which we currently patch around in the processjstask, we should try to remove that hook from hyperloop and use the standardized hook if possible
| 5 |
3,781 |
TIMOB-27605
|
11/14/2019 20:12:39
|
Drop support for Node 8, Make Node.JS 10.13 new minimum
|
Node.JS is officially ending support for Node 8 at the end of this year (12-31-2019). In preparation we should move to the next LTS line, which is Node 10.13+. https://nodejs.org/en/about/releases/ (Note that Node 10 will go into maintenance LTS starting in April next year, and Node 12 has just become an active LTS)
| 3 |
3,782 |
TIMOB-27611
|
11/18/2019 19:25:57
|
[Windows - Android] 'Failed to read "bootstrap.json". Reason: Unexpected token � in JSON at position 0' can be seen intermittently
|
When running a Titanium/alloy application sometimes the error below can be seen in the logs, although it seems to have no effect on the app. {code:java} [ERROR] : Failed to read "bootstrap.json". Reason: Unexpected token � in JSON at position 0 {code} *Test Steps:* # Create a Alloy/Titanium application # Run app to an Android emulator # Check logs for above message *Actual result* Above error can be seen intermittently. *Expected result* Error should not be seen.
| 1 |
3,783 |
TIMOB-27639
|
11/20/2019 12:51:58
|
Documentation for events' properties
|
1. Current documentation validator considers "type" fiels for "properties" on "events" as optional. Information about types must be always provided in documentation. 2. Validator does not allow "property" on "event" to be optional. Actually in the SDK they could be missing (for [example|https://github.com/appcelerator/titanium_mobile/blob/bf8a6bfd3ca17d3389cb6c8fc775886638226093/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUIImageView.java#L520]: "image" property on event "error" for "Titanium.UI.ImageView" on Android)
| 13 |
3,784 |
TIMOB-27618
|
11/21/2019 18:46:50
|
Android: remove Ti.UI.WebView.onStopBlacklistedUrl event
|
Since we now have a cross-platform event, we should remove this event which has been deprecated since 6.1.0
| 5 |
3,785 |
TIMOB-27619
|
11/21/2019 19:59:00
|
iOS: Remove Ti.Network.createTCPSocket
|
We *still* have {{Ti.Network.createTCPSocket}} hanging around even though it has been deprecated since SDK 1.7.0! My understanding is that it is only used in the Ti.Network.BonjourService class. That implementation should be modified to use/accept Ti.Network.Socket.TCP proxies. Then we can mark Ti.Network.TCPSocket and Ti.Network.createTCPSocket as removed in our apidocs; and we can get rid of the TiNetworkTCPSocketProxy source files in the SDK.
| 8 |
3,786 |
TIMOB-27620
|
11/21/2019 22:43:09
|
Windows: Remove deprecated Geolocation values, only use new ones
|
http://docs.appcelerator.com/platform/latest/#!/api/GeocodedAddress Specifically, it is insane that we: - have a postalCode property on Android, but zipcode on iOS/Windows. - latitude and longitude are Numbers on iOS/Windows, but String on Android. - have both country_code (on all platforms), and countryCode (only on Android) (we should likely have the same property, and given our naming scheme, it should be called "countryCode") {{zipcode}} and {{country_code}} were deprecated as part of TIMOB-23496 and should be removed.
| 8 |
3,787 |
TIMOB-27627
|
11/25/2019 22:13:34
|
Android: Prevent snapshot failure from breaking build
|
- Depending on build platform, some snapshots may not be generated. This can cause issues as applications may attempt to load snapshots that don't exist. - To resolve this, we need to implement a fallback for when snapshots do not exist for particular platforms.
| 5 |
3,788 |
TIMOB-27633
|
11/26/2019 19:19:27
|
Android: Additional parameters in require cause app to crash
|
*Steps to reproduce the behavior* # Create a new JS files that can be required, for example {{test.js}}. The content doesn't matter # Require that JS file with an additional parameter {code} require('./test.js', true); {code} # Run on Android *Actual behavior* The app crashes during runtime with the following error: {code} [ERROR] TiExceptionHandler: (main) [157,157] ti:/module.js:596 [ERROR] TiExceptionHandler: context.sourceUrl = url; [ERROR] TiExceptionHandler: ^ [ERROR] TiExceptionHandler: TypeError: Cannot create property 'sourceUrl' on boolean 'true' [ERROR] TiExceptionHandler: at Module._runScript (ti:/module.js:596:20) [ERROR] TiExceptionHandler: at Module.load (ti:/module.js:107:7) [ERROR] TiExceptionHandler: at Module.loadJavascriptText (ti:/module.js:453:9) [ERROR] TiExceptionHandler: at Module.loadAsFile (ti:/module.js:503:15) [ERROR] TiExceptionHandler: at Module.loadAsFileOrDirectory (ti:/module.js:425:20) [ERROR] TiExceptionHandler: at Module.require (ti:/module.js:255:17) [ERROR] TiExceptionHandler: at Module.global.Module.require (/ti.main.js:9505:34) [ERROR] TiExceptionHandler: at require (ti:/module.js:566:15) [ERROR] TiExceptionHandler: at /app.js:20:1 [ERROR] TiExceptionHandler: at Module._runScript (ti:/module.js:608:9) [ERROR] TiExceptionHandler: [ERROR] TiExceptionHandler: org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModuleBytes(Native Method) [ERROR] TiExceptionHandler: org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModuleBytes(V8Runtime.java:162) [ERROR] TiExceptionHandler: org.appcelerator.kroll.KrollRuntime.runModuleBytes(KrollRuntime.java:212) [ERROR] TiExceptionHandler: org.appcelerator.titanium.TiLaunchActivity.loadScript(TiLaunchActivity.java:101) [ERROR] TiExceptionHandler: org.appcelerator.titanium.TiRootActivity.loadScript(TiRootActivity.java:480) [ERROR] TiExceptionHandler: org.appcelerator.titanium.TiLaunchActivity.onResume(TiLaunchActivity.java:192) [ERROR] TiExceptionHandler: org.appcelerator.titanium.TiRootActivity.onResume(TiRootActivity.java:499) [ERROR] TiExceptionHandler: android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1355) [ERROR] TiExceptionHandler: android.app.Activity.performResume(Activity.java:7117) [ERROR] TiExceptionHandler: android.app.ActivityThread.performResumeActivity(ActivityThread.java:3556) {code} *Expected behavior* Additional parameter to require will be ignored. *Additional notes* If the file was required before without any additional parameters the require works as expected. {code} // This won't crash require('./test'); require('./test', true); {code}
| 8 |
3,789 |
TIMOB-27638
|
11/27/2019 12:43:23
|
Windows app fonts become small when titanium sdk version changed from 7.0.2.GA to 8.2.1 GA
|
Hi , I have upgraded the titanium SDK 7.0.2.GA to 8.2.1 GA in Windows Desktop application. After upgrade the application font becomes smaller than the previous. Also font changes happen in all pages in the application Find below tiapp.xml details: <property name="ti.ui.defaultunit" type="string">dp</property> <property name="run-on-main-thread" type="bool">true</property> <deployment-targets> <target device="iphone">false</target> <target device="ipad">false</target> <target device="android">false</target> <target device="windows">true</target> </deployment-targets> <sdk-version>8.2.1.GA</sdk-version> <windows> <manifest> <Capabilities> <Capability Name="internetClient"/> <Capability Name="internetClientServer"/> <Capability Name="privateNetworkClientServer"/> <!-- in case you need Internet connection --> <Capability Name="picturesLibrary"/> <!-- This line is required to request access to the photo library --> <Capability Name="videosLibrary"/> <DeviceCapability Name="location"/> <DeviceCapability Name="webcam"/> </Capabilities> <Applications> <Application> <VisualElements> <SplashScreen BackgroundColor="#FFFFFF"/> </VisualElements> </Application> </Applications> </manifest> <TargetPlatformVersion>10.0.16299.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.14393.0</TargetPlatformMinVersion> </windows> Can you please provide the reason for smaller font and how to fix
| 8 |
3,790 |
TIMOB-27640
|
12/03/2019 08:43:41
|
Windows: unit specifier for fontSize should be ignored
|
Setting {{fontSize}} with unit specifier for {{Font}} shows smaller fonts. It also could end up throwing runtime exception when display information is not provided by Windows. We might want to just "ignore" unit specifier in order to keep parity between iOS. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green', layout: 'vertical', title: 'Label Demo' }); var label1 = Ti.UI.createLabel({ color: '#900', font: { fontSize: '48dp' }, text: 'A simple label', top: 30, width: Ti.UI.SIZE, height: Ti.UI.SIZE }); var label2 = Ti.UI.createLabel({ color: '#900', font: { fontSize: 48 }, text: 'A simple label', width: Ti.UI.SIZE, height: Ti.UI.SIZE }); win.add(label1); win.add(label2); win.open(); {code} Expected: Both Labels should be shown with same font size {{48}}.
| 5 |
3,791 |
TIMOB-27641
|
12/03/2019 19:07:33
|
iOS: Drop support for iOS 9
|
Analytics suggest that only < 1.5% events are from iOS 9 devices. We should stop supporting iOS 9 and make iOS 10 as minimum target. It will help us to clean our conditional codes.
| 1 |
3,792 |
TIMOB-27805
|
12/06/2019 22:24:19
|
Open Photo Gallery not requiring permissions
|
When requesting access to the user's photo gallery on iOS, the app should not allow the gallery to display if permission has not been granted. Simple test: index.js {code:java} Titanium.Media.openPhotoGallery({ success: function (event) { // alert( 'libraryHandler success: ' + JSON.stringify( event, null, 2 ) ); _params.event = event; processImage(_params, false); }, error: function (event) { alert('libraryHandler error: ' + JSON.stringify(event, null, 2)); Titanium.API.info('Sending file error'); Titanium.API.info(event); }, mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO], allowEditing: true }); {code} The photo gallery will display and you can select a photo and get a successful result.
| 3 |
3,793 |
TIMOB-27697
|
12/09/2019 14:45:07
|
Add "progress" event to Ti.UI.WebView for Android (parity)
|
For some reason the progress event in Ti.UI.WebView is only available for iOS, so I did an attempt to add it (disclaimer: I am not a java programmer) Adding this function to TiWebChromeClient.java seems to fix it; {code:java} public void onProgressChanged(WebView view, int progress) { WebViewProxy proxy = (WebViewProxy) tiWebView.getProxy(); if (proxy != null) { KrollDict data = new KrollDict(); data.put("progress", progress); proxy.fireEvent("progress", data); } } {code} I tested it on SDK 8.3.0 and 9.0.0. Both tests successful. EDIT: created a PR: https://github.com/appcelerator/titanium_mobile/pull/11383
| 5 |
3,794 |
TIMOB-27779
|
12/10/2019 06:32:33
|
Android: Setting "labels" via TabbedBar "click" event hangs app
|
*Steps to reproduce:* # Build and run the below code on Android. # Tap on one of the tabs. # Notice that the app hangs. {code:javascript} var window = Ti.UI.createWindow(); var tabbedBar = Ti.UI.createTabbedBar(); tabbedBar.labels = ["One", "Two", "Three"]; tabbedBar.addEventListener("click", function() { console.log(new Date() + " tbrSortTLby Click event triggerred"); tabbedBar.labels = ['Three', 'Four', 'Five']; }); window.add(tabbedBar); window.open(); {code} *Cause:* Setting the "labels" property causes the "click" event to be fired. So, setting "labels" within a "click" event listener will cause infinite recursion to occur which will eventually cause a crash. *Work-Around:* Defer setting the "labels" property via {{setTimeout()}} within the "click" listener.
| 5 |
3,795 |
TIMOB-27650
|
12/12/2019 13:57:39
|
Remove deprecated modules from SDK distribution
|
h5.Description We have a couple modules that we have deprecated due to them being replaced, these should be removed from distribution to avoid people using them going forward * ti.safaridialog - replaced with ti.webdialog * ti.touchid - replaced with ti.indentity
| 5 |
3,796 |
TIMOB-27684
|
12/13/2019 18:49:14
|
Android: Cold-start launch animation may occur twice
|
- Launching a Titanium application may show a duplicate window launch animation
| 3 |
3,797 |
TIMOB-27685
|
12/14/2019 00:18:51
|
Android: Update hyperloop module to support gradle dependencies
|
*Summary:* In Titanium 9.0.0, we will be changing the Android app build system from "ant" to "gradle". This will be a breaking-change that will require the hyperloop module to change how it hooks into the build. But this is also a good opportunity to support gradle's "dependencies" feature which allows the hyperloop user to reference dependencies via their maven {{<groupId>:<libraryName>:<version>}} references. *Recommended Solution:* Add support for an optional "build.gradle" file to the following Titanium app project directory... {{./platform/android/build.gradle}} The file can then reference dependences like this... {code:groovy} repositories { google() jcenter() } dependencies { implementation 'com.google.android.gms:play-services-ads:18.3.0' } {code} *Note:* This feature depend on [TIMOB-19300] to be completed first.
| 13 |
3,798 |
TIMOB-27686
|
12/14/2019 05:43:03
|
Android: Auto-download build system dependencies via gradle
|
*Summary:* Gradle supports automatically downloading build system related dependencies such as Google's "build-tools" and targeted API Level libraries. We should leverage this feature so that app developer's won't have to download/install them manually via Google's "Android SDK Manager" dialog. This will make building Android apps more convenient and minimize tech-support issues. *Recommended Solution:* Once gradle build support has been added via [TIMOB-19300] in Titanium 9.0.0, we get this feature for free when we start the "gradlew" app build. But in order for this to happen, we need to ignore some of the error results returned by our [node-titanium-sdk|https://github.com/appcelerator/node-titanium-sdk] module's Android detect API [here|https://github.com/appcelerator/node-titanium-sdk/blob/master/lib/android.js] in our Titanium SDK's [_build.js|https://github.com/appcelerator/titanium_mobile/blob/master/android/cli/commands/_build.js] script's {{validate()}} function. The error string IDs we need to ignore are: * {{'ANDROID_BUILD_TOOLS_TOO_NEW'}} * {{'ANDROID_BUILD_TOOLS_NOT_SUPPORTED'}} * {{'ANDROID_BUILD_TOOLS_CONFIG_SETTING_NOT_INSTALLED'}} * {{'ANDROID_API_TOO_OLD'}} * {{'ANDROID_API_TOO_NEW'}} * {{'ANDROID_NO_APIS'}} * {{'ANDROID_NO_VALID_APIS'}} * {{'ANDROID_SDK_MISSING_PROGRAMS'}} *Note 1:* We still need our Android SDK/NDK detection code, because there is no way to run the Android gradlew tool without first setting up a "local.properties" file that reference the SDK/NDK directories. *Note 2:* Our Titanium CLI still needs to keep its existing Android tooling detection code since the CLI needs to support Titanium SDK versions older than 9.0.0.
| 5 |
3,799 |
TIMOB-27687
|
12/16/2019 18:53:10
|
Android: Update V8 runtime to 7.9
|
- Upgrade V8 to the latest stable version {{7.9.317.32}} {code} https://omahaproxy.appspot.com/ https://github.com/v8/v8/tree/7.9-lkgr {code} - Maintain backwards compatibility
| 8 |
3,800 |
TIMOB-27688
|
12/16/2019 19:25:25
|
TiAPI: Clean up apidocs to use common types
|
Our APIdocs frequently re-use similar arguments to methods but are not consistent in referring to those object shapes as defined types. Additionally, there may be duplicated types, types that haven't been defined but should be, or types that are defined but methods/properties don't refer to them and instead use generic Object/Dictionary type. This is relevant to have properly define docs, but also in that we have started to ship typescript definitions generated from he docs and can rely on these more formal definitions in editors/IDE for more reliable content assist.
| 13 |
3,801 |
TIMOB-27691
|
12/17/2019 13:41:41
|
iOS: App is crashing after recording the video on device
|
Hello, Customer have an issue very strange. This app is for ios, He is working with TiSDK 8.3.0. Please have a look at the video. The error has not logs files on Studio console but it is crashing on physical device. The first error is related to crash app after recording video. The other error is related to go to background navigate between apps and return to my app. The same situation the app is crashing. Example code: Available on [Here| https://github.com/jorgehip/hipCameraCrash/tree/02-MoveCameraToAlloy] I have tested on following environment and able to reproduce the issue: SDK: 8.3.0.GA, 8.1.0.GA Appcelerator Command-Line Interface, version 7.1.2 Device: iPhone 6 plus (12.4.3) Customer is getting this issue on iPhone X (iOS 13.x) 1. I cannot reproduce the second issue (background crash issue). 2. I can reproduce the first issue but not every time. It occurs after capturing video 3/4 times. Please let us know if you need any more information. Thanks
| 2 |
3,802 |
TIMOB-27694
|
12/20/2019 14:24:47
|
Android: Textfield.focus() method is not working in Ti SDK 8.3.0.GA
|
*Issue:* Textfield.focus() method is not working properly on android after updating to 8.3.0. It is getting focused but no keyboard is shown. The keyboard is only showing on the click of the TextField but if I call TextField.focus() then textfield is getting focused without a keyboard. *Steps To Reproduce:* 1. Create a classic project 2. Paste this code in app.js file 3. Run it on android device or emulator 4. Click on the "Focus Test" Button *Note: Works as expected with Ti SDK 8.2.0.GA* {code:title=app.js} var win = Ti.UI.createWindow({ title : "Focus Test", backgroundColor : 'red', layout : "vertical" }); // Create a TextField. var aTextField = Ti.UI.createTextField({ height : 40, top : 30, left : 20, right : 20, backgroundColor : "gray", hintText : 'This is hint text', softKeyboardOnFocus : Ti.UI.Android.SOFT_KEYBOARD_DEFAULT_ON_FOCUS, // Android only keyboardType : Ti.UI.KEYBOARD_DEFAULT, returnKeyType : Ti.UI.RETURNKEY_DEFAULT, borderStyle : Ti.UI.INPUT_BORDERSTYLE_ROUNDED }); // Listen for return events. aTextField.addEventListener('return', function(e) { aTextField.blur(); alert('Input was: ' + aTextField.value); }); // Add to the parent view. win.add(aTextField); // Create a Button. var test = Ti.UI.createButton({ title : 'Focus Test', height : Ti.UI.SIZE, width : Ti.UI.SIZE, top : 50, }); // Listen for click events. test.addEventListener('click', function() { aTextField.focus(); //alert('\'aButton\' was clicked!'); }); // Add to the parent view. win.add(test); win.open(); {code}
| 3 |
3,803 |
TIMOB-27696
|
12/22/2019 10:23:33
|
Android: Add "gradle.properties" support to app builds
|
*Summary:* Titanium app developers would like the ability to set up their own "gradle.properties" file according to Google's documentation. We should add support for this and allow this file to override the properties defined by Titanium's build system. https://developer.android.com/studio/build#properties-files *Recommended Solution:* Copy the properties from the following project file... {code} ./platform/android/gradle.properties {code} These properties should be copied to the end of the Titanium generated "gradle.properties" file so that the app dev's properties can override the ones we set.
| 5 |
3,804 |
TIMOB-27720
|
12/28/2019 11:28:41
|
Android: Error building SDK if python 3 is installed
|
Using Fedora 31 (Linux) to compile the latest (2019-12-28) git SDK code you will run into problems {code} Running Titanium "prebuild.js" script. Error: Command failed: python "titanium_mobile/android/runtime/v8/tools/genBootstrap.py" --runtime=v8 Traceback (most recent call last): File "titanium_mobile/android/runtime/v8/tools/genBootstrap.py", line 92, in <module> main() File "titanium_mobile/android/runtime/v8/tools/genBootstrap.py", line 80, in main b = bootstrap.Bootstrap(bindings, moduleId="titanium", moduleName="Titanium") File "titanium_mobile/android/runtime/v8/tools/bootstrap.py", line 93, in __init__ self.addToInitTable(proxy) File "titanium_mobile/android/runtime/v8/tools/bootstrap.py", line 120, in addToInitTable namespaces.insert(0, moduleNs) AttributeError: 'map' object has no attribute 'insert' {code} {code} at ChildProcess.exithandler (child_process.js:295:12) at ChildProcess.emit (events.js:210:5) at maybeClose (internal/child_process.js:1021:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) { killed: false, code: 1, signal: null, cmd: 'python "titanium_mobile/android/runtime/v8/tools/genBootstrap.py" --runtime=v8', stdout: '', stderr: 'Traceback (most recent call last):\n' + ' File "titanium_mobile/android/runtime/v8/tools/genBootstrap.py", line 92, in <module>\n' + ' main()\n' + ' File "titanium_mobile/android/runtime/v8/tools/genBootstrap.py", line 80, in main\n' + ' b = bootstrap.Bootstrap(bindings, moduleId="titanium", moduleName="Titanium")\n' + ' File "titanium_mobile/android/runtime/v8/tools/bootstrap.py", line 93, in __init__\n' + ' self.addToInitTable(proxy)\n' + ' File "titanium_mobile/android/runtime/v8/tools/bootstrap.py", line 120, in addToInitTable\n' + ' namespaces.insert(0, moduleNs)\n' + "AttributeError: 'map' object has no attribute 'insert'\n" {code} since it is using "python" to run genBootstrap.py. But in Fedora it will use python 3 since that is mapped as a default python. Changing https://github.com/appcelerator/titanium_mobile/blob/f687e3bbf8266707e6e5fdfdba6580e141a2221b/android/titanium/prebuild.js#L111 and https://github.com/appcelerator/titanium_mobile/blob/f687e3bbf8266707e6e5fdfdba6580e141a2221b/android/titanium/prebuild.js#L141 to python2 fixed the issue. A better solution to either port it to python3 or check for the correct python version at the beginning would be better. Python 2 won't be supported after April 2020 (last version was released 19th October) *Recommended Solution:* Use "python2" command line tool if available on system before using "python" command. *Best Solution:* Remove python dependency via ticket: [TIMOB-27719] We'll need to do this in the near future since Apple will no longer pre-install python on future macOS versions.
| 3 |
3,805 |
TIMOB-27705
|
01/07/2020 04:21:11
|
Android: Can't set versionCode via AndroidManifest.xml as of 9.0.0
|
*Summary:* As of Titanium 9.0.0, setting the "versionCode" via the "AndroidManifest.xml" file no longer works. _(This regression was caught before release.)_ *Steps to reproduce:* # Create a Titanium app project. # Set up the "tiapp.xml" file with the below. # Build for Android. # Go to folder: {{./build/android/app/build/intermediates/merged_manifests/debug}} # Open the "AndroidManfiest.xml" file. # Notice {{android:versionCode}} attribute is set to {{"1"}}. _(This is the bug.)_ {code:xml} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> <android xmlns:android="http://schemas.android.com/apk/res/android"> <manifest android:versionCode="5"/> </android> </ti:app> {code} *Reason:* When building with gradle, the "versionCode" and "versionName" attributes are ignored in the "AndroidManifest.xml" file. These settings can only be set via a "build.gradle" file. This is by Google's design. *Recommended Solution:* Titanium's build script should read the "versionCode" from the app developer's "AndroidManifest.xml" write it to the Titanium generated "build.gradle" file. This way it will be backward compatible. *Work-Around:* Set the "versionCode" via your own "build.gradle" file as shown below. {{./platform/android/build.gradle}} {code:groovy} android { defaultConfig { versionCode 5 } } {code}
| 3 |
3,806 |
TIMOB-27706
|
01/07/2020 05:50:39
|
Android: Native modules having uppercase "name" are excluded from build on case-sensitive systems
|
*Summary:* Native Android modules such as "ti.facebook" will not have their main JAR included in the app if built from a case-sensitive file system. The app will succeed to build, but attempting to use the module's APIs will fail. For "ti.facebook", the following warning will be logged when doing a build. {code:java} [WARN] Module facebook version 8.0.0 does not have a main jar file {code} _(This is more of an issue on Linux where the file system is case-sensitive by default.)_ *How to create case-sensitive disk image on macOS:* # Open the "Disk Utility" app. # From the menu, click: {{File -> New Image -> Blank Image}} # Click on the "Image Format" drop-down and select "sparse bundle disk image". # In "Save As" field, enter: {{CaseSensitive.sparsebundle}} # In "Where" field, select destination to write this image file to. # In "Name" field, enter: {{CaseSensitive}} # In "Size" field, enter: {{1 GB}} # Click "Format" drop-down and select "Mac OS Extended (Case-sensitive)". # Click the "Save" button. You can mount the above image by double clicking the "CaseSensitive.sparsebundle" file. You can find the "CaseSensitive" volume in "Finder" under the "Locations" section. *Steps to reproduce:* # Download [kitchensink-v2|https://github.com/appcelerator/kitchensink-v2] to the case sensitive volume. # Download the newest release version of the [ti.facebook|https://github.com/appcelerator-modules/ti.facebook] module. # Unzip module to folder: {{kitchensink-v2/modules/ti.facebook/...}} # Open the "tiapp.xml" file. # Build and run on Android. # Notice the following gets logged: {code} [WARN] Module facebook version 8.0.0 does not have a main jar file {code} # Tap on the app's "Mashups" tab. # Tap on the Facebook row. # Notice the app crashes. *Reason:* Titanium's build script is doing a {{toLowerCase()}} on the JAR file name [here|https://github.com/appcelerator/titanium_mobile/blob/243afd00e0760f2060e797312942ee65d47b9f5f/android/cli/commands/_build.js#L1575]. *Note:* This issue causes a build failure in Titanium 9.0.0 since moving to gradle.
| 5 |
3,807 |
TIMOB-27709
|
01/07/2020 15:13:49
|
Remove windows platform from SDK build/bundling
|
Since we no longer will be supporting Windows universal as app targets, we should remove the download/inclusion of windows in the SDK builds.
| 8 |
3,808 |
TIMOB-27711
|
01/08/2020 15:40:38
|
TiAPI: Add state querying methods to UI components
|
This is a glaring issue when we look at our test suite and see the common {{before}} hooks we've written to clean up open windows/etc. We have no means of telling if a Window is closed or open. So instead we fire off a 3-second {{setTimeout}} fallback to handle the "isClosed" case, and then hang an event listener for the close event and try to close the window. So in the case where the test never opened the window (or already closed it), we basically do nothing for 3 seconds and assume since the {{close}} event never fired that it must have been closed. We have {{Ti.UI.View.visible}} which should tell us if a view is hidden or visible. Proposed APIs: {{Ti.UI.Window.closed}} - {{boolean}}, {{true}} or {{false}} * tells us if the window is closed (do we need {{opened}} equivalent? I assume they'd just be inversions of one another) * Potential alternates? {{isClosed}}, {{closed}}, {{opened}}, {{isOpened}} (properties versus methods?) * Note that JavaFX uses {{showing}} as a roughly equivalent API here: https://openjfx.io/javadoc/13/javafx.graphics/javafx/stage/Window.html * Android equivalent may be {{isActive}}? https://developer.android.com/reference/android/view/Window.html#isActive() {{Ti.UI.View.focused}} - {{boolean}}, {{true}} or {{false}} * Potential alternates? {{isFocused}}, {{hasFocus}} (properties versus methods?) * https://developer.android.com/reference/android/view/View#hasFocus()
| 13 |
3,809 |
TIMOB-27715
|
01/10/2020 10:56:24
|
Remove windows platform from hyperloop
|
h5.Description With Windows platform being removed from the SDK in 9, we should also remove it from the hyperloop distribution
| 5 |
3,810 |
TIMOB-27717
|
01/10/2020 18:56:19
|
iOS: 'click' event in Ti.UI.TextField is not working for iOS >= 11.x
|
In iOS 10.x 'click' event is working fine for TI.UI.TextField but for iOS >= 11.x it is not working. On some experiment I found that in iOS >= 11.x there are restriction on touch event callbacks. Probably document need to be updated. Workaround to this issue is - Use 'touchstart' event or set 'enabled' property to false. Test Case - {code:java} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var textField = Ti.UI.createTextField({ top: 120, hintText: 'Trigger', backgroundColor: 'yellow', //enabled: false }); textField.addEventListener('touchstart', function() { Ti.API.info('touchstart event fired'); }); textField.addEventListener('click', function() { Ti.API.info('click event fired'); }); win.add(textField); win.open(); {code}
| 1 |
3,811 |
TIMOB-27718
|
01/16/2020 01:31:23
|
Android: Log build warnings if "res" files have invalid names
|
*Preface:* An Android APK's "res" files (such as drawables) have the following restictions: * File names can only have lower-case letters, numbers, or underscores. * File names cannot start with a number. * Cannot be placed in subdirectories. The above limitations are by Google's design, because the Android build system turns "res" file names into Java constants under the generated {{R}} class. Violating the above will result in a build failure. However, Titanium allows app developers to violate the above rules and will lower-case the file name and replace illegal characters and directory separators with {{'_'}} underscores. *App Changes for Titanium 9.0.0:* For app builds, we want to maintain backward compatibility. This means allowing app developer to continue to violate Google's "res" file naming rules, but we should log a build +WARNING+ for every "res" file in violation to compel app developer's to follow Google's best-practices. This will also help minimize confusion when attempting to access a "res" file via native Java APIs using the illegal name, which won't work. *Module Changes for Titanium 9.0.0:* Native modules built with Titanium 9.0.0 and higher will no longer be allowed to violate Google's "res" file naming rules. This is because we're now building a native module to an AAR library which packages the module's "res" files. So, illegal "res" file names will cause a build failure just like how it works in Android Studio. *Test:* The attached [^Resources.zip] contains a directory tree of image files which violate Google's "res" naming conventions.
| 5 |
3,812 |
TIMOB-27719
|
01/17/2020 00:04:13
|
Android: Remove python dependency from SDK build
|
*Summary:* When building the Titanium SDK, the Android side currently uses python scripts to do some code generation. We should replace python scripts with node.js scripts so that we can get rid of our python dependency, thus simplifying the SDK build. Apple will not pre-install "python" on the next version of macOS in the year 2020 https://developer.apple.com/documentation/macos_release_notes/macos_catalina_10_15_release_notes *Note:* Titanium's app and module builds do not require python. This is only an issue with SDK builds. *Recommended Changes:* In Titanium 9.0.0, we only run 2 python scripts via our "prebuild.js" script. These are the scripts we need to replace. [titanium_mobile/android/titanium/prebuild.js|https://github.com/appcelerator/titanium_mobile/blob/70c16f7ca213f39791330758489be4f951dfa1ab/android/titanium/prebuild.js] Once the above is done, we should be able to delete all python scripts from the following folder... [titanium_mobile/android/runtime/v8/tools|https://github.com/appcelerator/titanium_mobile/tree/70c16f7ca213f39791330758489be4f951dfa1ab/android/runtime/v8/tools]
| 8 |
3,813 |
TIMOB-27723
|
01/21/2020 19:19:05
|
Android: Build fails and emulator does not launch
|
- Titanium application build fails when attempting to launch emulator using latest nodejs: {code} [INFO] Building for target: emulator [INFO] Building for emulator: Q_29 [INFO] Targeting Android SDK API: 29 [INFO] Building for the following architectures: arm64-v8a, armeabi-v7a, x86 [INFO] Launching emulator: Q_29 {code} For the build to complete, the emulator must be started manually.
| 3 |
3,814 |
TIMOB-27724
|
01/22/2020 19:27:40
|
Android: Build "ti.map" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/ti.map
| 5 |
3,815 |
TIMOB-27725
|
01/22/2020 19:29:16
|
Android: Build "ti.facebook" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/ti.facebook
| 5 |
3,816 |
TIMOB-27726
|
01/22/2020 19:33:32
|
Android: Build "ti.identity" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/titanium-identity
| 5 |
3,817 |
TIMOB-27727
|
01/22/2020 19:35:22
|
Android: Build "appcelerator.encrypteddatabase" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/appcelerator.encrypteddatabase
| 5 |
3,818 |
TIMOB-27728
|
01/22/2020 19:37:44
|
Android: Build "cloudpush" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/cloudpush
| 5 |
3,819 |
TIMOB-27729
|
01/22/2020 19:38:52
|
Android: Build "ti.playservices" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/ti.playservices
| 5 |
3,820 |
TIMOB-27730
|
01/22/2020 19:40:00
|
Android: Build "ti.webdialog" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator-modules/titanium-web-dialog
| 5 |
3,821 |
TIMOB-27731
|
01/22/2020 21:41:36
|
Android: Camera fails to open when using saveToPhotoGallery: true
|
h5.Description When using the following code, the camera fails to open and I get the following error log. This looks to be a regression from 8.2.0.GA {code} [ERROR] TiMedia: (main) [122857,122924] Failed to create file: Permission denied [DEBUG] DecorView: onWindowFocusChangedFromViewRoot hasFocus: true, DecorView@701a6fd[TiActivity] [INFO] { code: 2, error: 'Unable to create file for storage', success: false } [INFO] error, womp womp {code} {code} const win = Ti.UI.createWindow(); win.addEventListener('click', _ => { Ti.Media.requestCameraPermissions(e => { if (!e.success) { console.warn('Failed to get permissions.'); return; } Ti.Media.showCamera( { success(e) { console.log(e); }, cancel(e) { console.warn(e); }, error(e) { console.error(e); }, saveToPhotoGallery: true, mediaTypes: [ Ti.Media.MEDIA_TYPE_PHOTO ] }); }) }); win.open(); {code} h5.Steps to reproduce 1. Add the code above to an existing app.js 2. Build to Android h5.Actual Above error log h5.Expected Camera should open
| 8 |
3,822 |
TIMOB-27737
|
01/23/2020 22:48:19
|
Android: Build "analytics" module with gradle
|
Module needs to be rebuilt for Titanium 9.0.0 to support the following: * Built as an Android "AAR" library. * Provide a "POM" file defining its dependencies. (Resolves library version conflicts.) * Support AndroidX libraries. * Add x86_64 architecture support. Repository: https://github.com/appcelerator/aps_sdk
| 5 |
3,823 |
TIMOB-27739
|
01/25/2020 05:05:12
|
Android: Location permissions not auto-added when using Ti.Geolocation API as of 9.0.0
|
_This issue was caught before release._ *Summary:* When doing a "device" or "production" build, Titanium's build system is supposed to auto-add the below permissions to the "AndroidManifest.xml" when the app uses the {{Ti.Geolocation}} APIs. * {{android.permission.ACCESS_COARSE_LOCATION}} * {{android.permission.ACCESS_FINE_LOCATION}} This has stopped working as of Titanium 9.0.0 (before release). *Steps to reproduce:* # Set up a Classic app with the below code. # Build and run on an Android device. (Not an emulator.) # Notice app reports error: {{Failed to acquire location permission}} app.js {code:javascript} function monitorLocation() { function start() { Ti.Geolocation.addEventListener("location", function(e) { label.text = JSON.stringify(e, null, 4); Ti.API.info("@@@ location received: " + JSON.stringify(e)); }); } var hasPermission = Ti.Geolocation.hasLocationPermissions(Ti.Geolocation.AUTHORIZATION_WHEN_IN_USE); if (!hasPermission) { Ti.Geolocation.requestLocationPermissions(Ti.Geolocation.AUTHORIZATION_WHEN_IN_USE, function(e) { Ti.API.info("@@@ permission result: " + JSON.stringify(e)); if (e.success) { start(); } else { label.text = "\nFailed to acquire location permission from end-user."; } }); } else { start(); } } var window = Ti.UI.createWindow(); var scrollView = Ti.UI.createScrollView({ layout: "vertical", scrollType: "vertical", width: Ti.UI.FILL, height: Ti.UI.FILL, }); var label = Ti.UI.createLabel({ text: "\nWaiting for GPS data...", top: (Ti.App.iOS ? "25dp" : "5dp"), height: Ti.UI.SIZE, left: "5dp", right: "5dp", bottom: "5dp", }); scrollView.add(label); window.add(scrollView); window.addEventListener("open", function(e) { monitorLocation(); }); window.open(); {code}
| 5 |
3,824 |
TIMOB-27740
|
01/28/2020 01:21:48
|
TiAPI: Extend removal of deprecated get/set property methods from 9.0.0 to 10.0.0
|
When your JS code invokes a get/set property method, such as {{Label.getText()}} and {{Label.setText()}} instead of accessing the {{Label.text}} property, the following warning will be logged. {code} [WARN] Proxy: Automatic setter methods for properties are deprecated in SDK 8.0.0 and will be removed in SDK 9.0.0. {code} We don't want to remove these method in Titanium 9.0.0. We should extend the removal of these deprecated APIs from Titanium 9.0.0 to 10.0.0.
| 5 |
3,825 |
TIMOB-27741
|
01/28/2020 17:57:55
|
Android: Allow requestPermissions to succeed if already granted
|
Allow {{requestPermissions}} to succeed when when permissions have already been granted. This prevents the need for calling {{hasPermissions}} and simplified code. *EXAMPLE* {code:js} const overlay = Ti.UI.createView({}); const takePicture = Ti.UI.createButton({ title: 'Take Picture' }); takePicture.addEventListener('click', _ => { Ti.Media.takePicture(); }); overlay.add(takePicture); // Should not need to call 'hasCameraPermissions', 'requestCameraPermissions' should succeed. Ti.Media.requestCameraPermissions(e => { if (e.success) { Ti.Media.showCamera({ success: e => { if (e.success) { console.log('Taken picture successfully!'); } else { console.error(JSON.stringify(e, null, 2)); } }, saveToPhotoGallery: true, autohide: false, overlay: overlay, mediaTypes: [ Ti.Media.MEDIA_TYPE_PHOTO ] }); } }); {code}
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.