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,626 |
TIMOB-27064
|
05/07/2019 17:34:02
|
iOS: Unable to load image on imaveView from nativePath on physical device
|
Hello, We are unable to load image on imaveView from nativePath on physical device but it's showing the image on lower version of SDK (7.5.2.GA) and Simulator (with latest version of SDK). *Test code:* {code} function DoTest() { //download image, then show it in a web view //create directory sDir = Ti.Filesystem.applicationDataDirectory + "/productimages/"; d = Ti.Filesystem.getFile(sDir); if (!d.exists()) { d.createDirectory(); } sImageName = "Fortune-Cookie-2748_large.png"; sURL = "https://boomboom.cart32.com/productimages/" + sImageName; var xhr = Titanium.Network.createHTTPClient(); xhr.onload = function() { f = Ti.Filesystem.getFile(sDir + sImageName); //write file Ti.API.info('Status = ' + xhr.status); if (xhr.status == 200) { Ti.API.info('SUCCESS - Size= ' + xhr.responseData.size + ' Downloaded image(' + sImageName + ') - Writing ' + f.nativePath); //write PNG file f.write(xhr.responseData); ShowImageInWebView(sDir + sImageName); } }; xhr.onerror = function(e) { Ti.API.info('Error: ' + e.error); }; Ti.API.info('Calling ' + sURL); xhr.open('GET', sURL); xhr.send(); } function ShowImageInWebView(sImageFile) { var f = Ti.Filesystem.getFile(sImageFile); Ti.API.info('f.nativePath = ' + f.nativePath); sHTML = 'Image<br><img src="' + f.nativePath + '" />'; var wv = Ti.UI.createWebView({}); wv.html = sHTML; var win = Titanium.UI.createWindow({ title : 'Test', modal : true, backgroundColor : '#ff0000' }); win.add(wv); win.open(); } DoTest(); {code} *Test Results on device:* {code} [INFO] : Calling https://boomboom.cart32.com/productimages/Fortune-Cookie-2748_large.png [INFO] : Status = 200 [INFO] : SUCCESS - Size= 390580 Downloaded image(Fortune-Cookie-2748_large.png) - Writing file:///var/mobile/Containers/Data/Application/061D8DA1-A61B-47C8-8279-F9571E19D402/Documents/productimages/Fortune-Cookie-2748_large.png [INFO] : f.nativePath = file:///var/mobile/Containers/Data/Application/061D8DA1-A61B-47C8-8279-F9571E19D402/Documents/productimages/Fortune-Cookie-2748_large.png {code} *Test Environment:* Appcelerator Command-Line Interface, version 7.0.10 Operating System Name = Mac OS X Version = 10.14.4 Architecture = 64bit # CPUs = 4 Memory = 8589934592 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.1.1 Titanium SDK SDK Version = 8.0.0.GA Note: I have tried it with WKWebView for 8.0.0.GA but got the same results. Thanks
| 5 |
3,627 |
TIMOB-27067
|
05/07/2019 22:53:34
|
Android: UI sometimes disappears on Android 9.0 and higher when battery saver turns on/off
|
*Summary:* On Android 9.0 and higher, a Titanium window's UI may disappear when the system's battery optimizer turn on or off. This can happen if the XML activities defined in the "tiapp.xml" are missing "android:configChanges" value "uiMode". This issue can be reproduced consistently in an Android 9 (API 28) emulator. *Steps to reproduce:* # Create a new Titanium Classic "Default Project". # Build and run on an Android 9 (aka: API 28) emulator. # In the Android emulator's toolbar, click the "..." button. # An "Extended Controls" window will open next to the emulator. # Click on the "Battery" tab in this window. # Go to the "Charge level" and lower it to 10%. # Click the "Charge connection" drop-down and change it from "AC charger" to "None" (or vice-versa). # In the emulator, if it asks if you want to enable the battery optimizer, tap "Yes". # Notice that the Titanium app's UI disappears. # Press the Android "Back" button. # Relaunch the app. (The UI will appear as normal.) # Click the emulator's "Charge connection" drop-down and change it back to "AC charger". # Notice that the Titanium app's UI disappears again. *Cause:* The "AndroidManifest.xml" that is being generated by Titanium's build system is missing a setting. We need to add "uiMode" to every Titanium {{<activity/>}} elements "android:configChanges" attribute. *Work-Around:* You can work-around this issue by adding the following "activity" XML settings to the "tiapp.xml" file. The key thing here is to add all of the missing "configChanges" values. Particularly the "uiMode" value which solves this ticket's specific issue. {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> <application> <activity android:name="org.appcelerator.titanium.TiActivity" android:configChanges="density|fontScale|keyboard|keyboardHidden|layoutDirection|locale|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode"/> <activity android:name="org.appcelerator.titanium.TiTranslucentActivity" android:configChanges="density|fontScale|keyboard|keyboardHidden|layoutDirection|locale|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:theme="@style/Theme.Titanium.Translucent"/> </application> </manifest> </android> </ti:app> {code}
| 3 |
3,628 |
TIMOB-27068
|
05/08/2019 03:15:48
|
Windows: Layout does not match with view size property
|
Following code reports {{height=200}} (which is right) but the {{viewChild}} red view does not display {{200}} height actually. It looks to have {{100}} height. {code} var view = Ti.UI.createView({ height: 200, width: 200, backgroundColor: 'yellow' }), viewChild = Ti.UI.createView({ backgroundColor: 'red', center: { x: 100, }, right: 50 }); var win = Ti.UI.createWindow(); viewChild.addEventListener('postlayout', function () { console.log('height=' + viewChild.size.height); }); view.add(viewChild); win.add(view); win.open(); {code} Expected: {{viewChild}} should display {{200}} height. Same thing happens on {{width}} property. {code} var view = Ti.UI.createView({ height: 200, width: 200, backgroundColor: 'yellow' }), viewChild = Ti.UI.createView({ backgroundColor: 'red', center: { y: 100, }, bottom: 50 }); var win = Ti.UI.createWindow(); viewChild.addEventListener('postlayout', function () { console.log('width=' + viewChild.size.width); }); view.add(viewChild); win.add(view); win.open(); {code} Expected: {{viewChild}} should display {{200}} width.
| 8 |
3,629 |
TIMOB-27159
|
05/09/2019 10:18:49
|
iOS: Ti.UI.WebView cannot load html files from cache
|
*Note: Issue can be reproduced only on device, webview works as expected on simulator* New WebView fails to load html files stored in the app with the error: {code:java} default 11:34:49.407006 +0300 com.apple.WebKit.Networking 0x1075e8000 - NetworkResourceLoader::startNetworkLoad: (pageID = 5, frameID = 1, resourceID = 1, isMainResource = 1, isSynchronous = 0) default 11:34:49.407054 +0300 com.apple.WebKit.Networking Task <0AF948FB-871A-4EDD-A632-D67CBB10B3BC>.<1> resuming, QOS(0x19) default 11:34:49.407103 +0300 com.apple.WebKit.Networking [Telemetry]: Activity <nw_activity 16:2 [3A7E50A1-6DED-43AC-8750-A3865F7FCB48] (reporting strategy default)> on Task <0AF948FB-871A-4EDD-A632-D67CBB10B3BC>.<1> was not selected for reporting error 11:34:49.407332 +0300 kernel Sandbox: com.apple.WebKit(10340) deny(1) file-read-data /private/var/mobile/Containers/Data/Application/B7D5C2EF-634E-4F7E-A7EC-BAB4DDF48868/Library/Caches/307/platform_article_1112110663/article.html default 11:34:49.407402 +0300 com.apple.WebKit.Networking 0x1075e8000 - NetworkResourceLoader::startNetworkLoad: (pageID = 5, frameID = 1, resourceID = 1, description = LocalDataTask <0AF948FB-871A-4EDD-A632-D67CBB10B3BC>.<1>) error 11:34:49.407557 +0300 com.apple.WebKit.Networking Task <0AF948FB-871A-4EDD-A632-D67CBB10B3BC>.<1> finished with error - code: 1 error 11:34:49.407608 +0300 com.apple.WebKit.Networking Task <0AF948FB-871A-4EDD-A632-D67CBB10B3BC>.<1> load failed with error Error Domain=kCFErrorDomainCFNetwork Code=1 UserInfo={_NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>} [1] default 11:34:49.408142 +0300 com.apple.WebKit.Networking 0x1075e8000 - NetworkResourceLoader::didFailLoading: (pageID = 5, frameID = 1, resourceID = 1, isTimeout = 0, isCancellation = 0, isAccessControl = 0, errCode = 1) {code} Reading iOS documentation I noticed that local files should be loaded using *loadFileURL* method as in https://github.com/appcelerator-modules/Ti.WKWebView/blob/master/ios/Classes/TiWkwebviewWebView.m#L198 but I don't see that in https://github.com/appcelerator/titanium_mobile/blob/master/iphone/Classes/TiUIWebView.m#L664
| 5 |
3,630 |
TIMOB-27075
|
05/09/2019 21:24:05
|
Android: Cannot change TabGroup tab icon or title after creation
|
Setting a new icon on a tab does not update the icon. Works in 7.5.x. Icon renders properly on creation or add of a tab, but you cannot change/update it. $.tab.icon = 'image.png';
| 5 |
3,631 |
TIMOB-27074
|
05/10/2019 00:43:14
|
IOS: Rebuilding the app with simulator fails with due to log port being occupied
|
h5. Steps to reproduce: 1. Create a default app. 2. Build for IOS simulator. 3. After app launch, rebuild the app for the same simulator, without quitting the current simulator. h5.Actual results: 1. The build fails with : {code} [DEBUG] : Log server port 28544 is in use, testing if it's the app we're building [ERROR] : Another process is currently bound to port 28544 [ERROR] : Set a unique <log-server-port> between 1024 and 65535 in the <ios> section of the tiapp.xml {code} 2. Works fine after quitting the emulator & then rebuilding. h5.Expected result: 1. The build should not fail.
| 8 |
3,632 |
TIMOB-27094
|
05/13/2019 00:41:13
|
Android: ListView's SearchBar/SearchView wrongly overlaps rows as of 8.0.1
|
Android searchView is broken in 8.0.1.RC Adding an Android.searchView to a listView is positioning it underneath the first item in the list and so can not be accessed at all. (see screenshots). !8.0.1.v20190423123234.jpg|thumbnail! Shows the expected behaviour !8.0.1.v20190426162041.jpg|thumbnail! Shows the exact same app with a different sdk selected and the search view is hidden under the first row. 8.0.1.v20190423123234 works correctly, 8.0.1.v20190426162041 does not.
| 5 |
3,633 |
TIMOB-27080
|
05/14/2019 14:43:43
|
iOS: Memory leak and deadlock in SDK 8+
|
This is the follow-up ticket of TIMOB-27053. That ticket fixed some critical issues in regards to JSCore crashes, but now we still see *a lot* (on older iPhones every time) dead locks that cause the app to freeze and crash later. The worst thing is that those logs also do not show up on Crashlytics, so cannot know exactly where it crashes, although I assume it is JSCore as well. Notable is that before every crash, it shows the following warning: {code} [DEBUG] Firing app event: memorywarning {code} As discussed with [~jvennemann], this is likely the reason why it crashes - a deadlock in firing the event. Unfortunately he was not able to provide a workaround or fix to test so far, so we are escalating this ticket now.
| 5 |
3,634 |
TIMOB-27112
|
05/15/2019 19:03:08
|
iOS : No javascript trace on IOS for requiring an unavailable module
|
h5. Steps to reproduce: 1. In the app.js use {{require('zzzz')}}. 2. Build it for IOS device/simulator. 3. The app will throw error/exception. 4. Go to the dashboard & check if you get the crash/exception logs from ACA. h5.Actual results: 1. We do not see any javascript trace just native Objective C: Please refer the attached screenshot. h5.Expected result: 1. Javascript stack trace should be shown.
| 8 |
3,635 |
TIMOB-27082
|
05/15/2019 20:41:52
|
iOS: Modules using TiBlob and built before SDK 8.1 causing app crash
|
Not much more to say. Reproducible using common modules like [Ti.AWS|https://github.com/hansemannn/titanium-aws/blob/master/ios/Classes/TiAwsMachineIoTDataManagerProxy.m#L125-L127] or the official [Ti.Map|https://github.com/appcelerator-modules/ti.map/blob/master/ios/Classes/TiMapSnapshotterProxy.m#L94].
| 2 |
3,636 |
TIMOB-27084
|
05/17/2019 04:53:11
|
Android: "tiapp.xml" is unable to override "AndroidManifest.xml" settings defined in AAR or "timodule.xml"
|
*Summary:* The "tiapp.xml" file's "AndroidManifest.xml" settings is unable to override the XML elements such as {{<activity/>}}, {{<receiver/>}}, etc. that are defined in a native module's "timodule.xml" or a native AAR library's embedded "AndroidManifest.xml". *Example Use-Case:* Microsoft's authentication library (aka: MSAL) requires the app developer to override its {{com.microsoft.identity.client.BrowserTabActivity}} in the app project's "AndroidManifest.xml" and add an intent-filter to it. This is needed the Chrome web browser app will return the end-user back to the app that requested single-signon. https://github.com/Azure-Samples/ms-identity-android-native *Steps to Reproduce:* # Create a Titanium Classic "Default Project". # Insert the android manifest XML settings below into the "tiapp.xml" file. # Create the follow subfolders under the project: {{./platform/android}} # Copy this ticket's [^msal-0.2.2.aar] file to the {{./platform/android}} folder. # Build the app for Android. # Go to the project's {{./build/android}} directory via Finder/WindowsExplorer. # Open the "AndroidManifest.xml" file. # Notice that the {{<intent-filter/>}} shown below was not injected into the "AndroidManifest.xml" file. _(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> <application> <activity android:name="com.microsoft.identity.client.BrowserTabActivity"> <intent-filter> <action android:name="android.intent.action.VIEW"/> <category android:name="android.intent.category.DEFAULT"/> <category android:name="android.intent.category.BROWSABLE"/> <data android:scheme="msauth" android:host="my.domain.com" android:path="my-path"/> </intent-filter> </activity> </application> </manifest> </android> </ti:app> {code} *Recommended Fix:* We should change the {{finalAndroidManifest}} merge order in the SDK's "_build.js" script [here|https://github.com/appcelerator/titanium_mobile/blob/2a16df7481b0a3331d2f56365463f0a9a8031d09/android/cli/commands/_build.js#L3909]. The order should be: # {{this.androidLibraries.forEach(/* finalAndroidManifest.merge(am) */)}} # {{this.modules.forEach(/* finalAndroidManifest.merge(am) */)}} # {{finalAndroidManifest.merge(customAndroidManifest)}} # {{finalAndroidManifest.merge(tiappAndroidManifest)}} ---- *Work-Around:* Delete the XML setting that you want to override from the "timodule.xml" file or AAR file. Note that you can unzip an AAR file, change its embedded "AndroidMainfest.xml" file, and then re-zip it. Changing the AAR library's extension from ".aar" to ".zip" is an easy way to unzip it.
| 3 |
3,637 |
TIMOB-27099
|
05/17/2019 23:33:44
|
iOS Debug: Error in console on variable view refresh during debug
|
When stepping through during debug an error is logged in console as the variable view refreshes on each step. The error is shown only during debug on iOS with 8.1 Ti SDK. If we close the variable window the error would not be shown. Steps to reproduce: 1. Create a classic/alloy project 2. Add some breakpoints 3. Debug on iOS simulator 4. When the debugger suspends on a breakpoint click on Step in. Actual Result: An error is shown as soon as the debugger suspends for the first time. After step in the same error is shown in console again. The error shown is: {code} [ERROR] : Blob.file property requested but the Filesystem API was never requested. {code} Expected Result: No error should be shown
| 2 |
3,638 |
TIMOB-27089
|
05/19/2019 12:58:27
|
iOS: App crashes when asking for location permissions (SDK 8.1.0+)
|
Our app crashes when asking for location permissions on SDK 8.1.0. The feature has not changed since a while and we noticed the crash after upgrading to latest master. Error: {code} [ERROR] The application has crashed with an uncaught exception 'NSInvalidArgumentException'. [ERROR] Reason: [ERROR] -[__NSMallocBlock__ value]: unrecognized selector sent to instance 0x60000236eee0 [ERROR] Stack trace: [ERROR] 0 CoreFoundation 0x000000011403b1bb __exceptionPreprocess + 331 [ERROR] 1 libobjc.A.dylib 0x000000010f334735 objc_exception_throw + 48 [ERROR] 2 CoreFoundation 0x0000000114059f44 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132 [ERROR] 3 CoreFoundation 0x000000011403fed6 ___forwarding___ + 1446 [ERROR] 4 CoreFoundation 0x0000000114041da8 _CF_forwarding_prep_0 + 120 [ERROR] 5 Lambus 0x00000001098366a6 __66-[GeolocationModule locationManager:didChangeAuthorizationStatus:]_block_invoke + 198 [ERROR] 6 Lambus 0x00000001098364ef -[GeolocationModule locationManager:didChangeAuthorizationStatus:] + 495 [ERROR] 7 CoreLocation 0x000000010e99dd74 CLClientStopVehicleHeadingUpdates + 71531 [ERROR] 8 CoreLocation 0x000000010e99da15 CLClientStopVehicleHeadingUpdates + 70668 [ERROR] 9 CoreLocation 0x000000010e988210 CLClientInvalidate + 1351 [ERROR] 10 CoreFoundation 0x0000000113fa062c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 [ERROR] 11 CoreFoundation 0x0000000113f9fde0 __CFRunLoopDoBlocks + 336 [ERROR] 12 CoreFoundation 0x0000000113f9ac2b __CFRunLoopRun + 2779 [ERROR] 13 CoreFoundation 0x0000000113f99e11 CFRunLoopRunSpecific + 625 [ERROR] 14 GraphicsServices 0x0000000118a8d1dd GSEventRunModal + 62 [ERROR] 15 UIKitCore 0x000000011cb0381d UIApplicationMain + 140 [ERROR] 16 Lambus 0x000000010967fcbc main + 988 [ERROR] 17 libdyld.dylib 0x0000000115c13575 start + 1 {code} Some quick research shown that the issue is in the GeolocationModule.m where the callback {{authorizationCallback}} (a {{JSManagedValue}} type) seems to be deallocated already: {code} TiThreadPerformOnMainThread(^{ NSMutableDictionary *propertiesDict = [TiUtils dictionaryWithCode:code message:errorStr]; [propertiesDict setObject:NUMINT([CLLocationManager authorizationStatus]) forKey:@"authorizationStatus"]; [[authorizationCallback value] callWithArguments:@[ propertiesDict ]]; }, YES); {code} JS code to reproduce: {code:js} /* eslint-disable strict */ var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var btn = Ti.UI.createButton({ title: 'Request location permissions' }); btn.addEventListener('click', function () { Ti.Geolocation.requestLocationPermissions(Ti.Geolocation.AUTHORIZATION_WHEN_IN_USE, event => { alert(event); }); }); win.add(btn); win.open(); {code} Notes: * We do have the {{NSLocationWhenInUseUsageDescription}} and {{NSLocationAlwaysAndWhenInUseUsageDescription}} plist keys added. * We do not use the {{UIBackgroundModes}} key {{location}} since we only request the location while using the app
| 3 |
3,639 |
TIMOB-27090
|
05/19/2019 13:11:25
|
iOS: Using a non-string value in alert() causes app to crash in SDK 8.0.0+
|
When using a non-string value like an object, the app crashes. This is a regression from moving to TitaniumKit and was caused by using the {{UIAlertController}} in the {{AlertCallback}} method directly instead of the {{TiUiAlertDialog}} proxy.
| 3 |
3,640 |
TIMOB-27091
|
05/19/2019 16:51:41
|
Android: App crashes on incremental build in SDK 8.1.0+
|
We recently updated to latest master and noticed that our Android app (tested inside Simulator) sometimes randomly crashes with the following error: {code} [INFO] Project built successfully in 47s 475ms [INFO] TiApplication: (main) [164,164] Analytics have been disabled [INFO] TiApplication: (main) [175,339] Titanium Javascript runtime: v8 [DEBUG] TiAnimationModule: (main) [29,368] inside onAppCreate [INFO] TiRootActivity: (main) [0,0] checkpoint, on root activity create, savedInstanceState: null [INFO] TiRootActivity: (main) [0,0] checkpoint, on root activity resume. activity = io.lambus.app.LambusActivity@e50663d [ERROR] TiAssetHelper: Error while reading asset "Resources/ti.main.js": [ERROR] TiAssetHelper: java.io.FileNotFoundException: Resources/ti.main.js [ERROR] TiAssetHelper: at android.content.res.AssetManager.nativeOpenAsset(Native Method) [ERROR] TiAssetHelper: at android.content.res.AssetManager.open(AssetManager.java:744) [ERROR] TiAssetHelper: at android.content.res.AssetManager.open(AssetManager.java:721) [ERROR] TiAssetHelper: at org.appcelerator.kroll.util.KrollAssetHelper.readAsset(KrollAssetHelper.java:165) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiLaunchActivity.loadScript(TiLaunchActivity.java:99) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiRootActivity.loadScript(TiRootActivity.java:466) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiLaunchActivity.onResume(TiLaunchActivity.java:183) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiRootActivity.onResume(TiRootActivity.java:485) [ERROR] TiAssetHelper: at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412) [ERROR] TiAssetHelper: at android.app.Activity.performResume(Activity.java:7292) [ERROR] TiAssetHelper: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776) [ERROR] TiAssetHelper: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816) [ERROR] TiAssetHelper: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51) [ERROR] TiAssetHelper: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145) [ERROR] TiAssetHelper: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70) [ERROR] TiAssetHelper: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808) [ERROR] TiAssetHelper: at android.os.Handler.dispatchMessage(Handler.java:106) [ERROR] TiAssetHelper: at android.os.Looper.loop(Looper.java:193) [ERROR] TiAssetHelper: at android.app.ActivityThread.main(ActivityThread.java:6669) [ERROR] TiAssetHelper: at java.lang.reflect.Method.invoke(Native Method) [ERROR] TiAssetHelper: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) [ERROR] TiAssetHelper: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) [ERROR] TiAssetHelper: Error while reading asset "Resources/ti.main.js": [ERROR] TiAssetHelper: java.io.FileNotFoundException: Resources/ti.main.js [ERROR] TiAssetHelper: at android.content.res.AssetManager.nativeOpenAsset(Native Method) [ERROR] TiAssetHelper: at android.content.res.AssetManager.open(AssetManager.java:744) [ERROR] TiAssetHelper: at android.content.res.AssetManager.open(AssetManager.java:721) [ERROR] TiAssetHelper: at org.appcelerator.kroll.util.KrollAssetHelper.readAsset(KrollAssetHelper.java:165) [ERROR] TiAssetHelper: at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(Native Method) [ERROR] TiAssetHelper: at org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModule(V8Runtime.java:162) [ERROR] TiAssetHelper: at org.appcelerator.kroll.KrollRuntime.runModule(KrollRuntime.java:207) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiLaunchActivity.loadScript(TiLaunchActivity.java:99) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiRootActivity.loadScript(TiRootActivity.java:466) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiLaunchActivity.onResume(TiLaunchActivity.java:183) [ERROR] TiAssetHelper: at org.appcelerator.titanium.TiRootActivity.onResume(TiRootActivity.java:485) [ERROR] TiAssetHelper: at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412) [ERROR] TiAssetHelper: at android.app.Activity.performResume(Activity.java:7292) [ERROR] TiAssetHelper: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776) [ERROR] TiAssetHelper: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816) [ERROR] TiAssetHelper: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51) [ERROR] TiAssetHelper: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145) [ERROR] TiAssetHelper: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70) [ERROR] TiAssetHelper: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808) [ERROR] TiAssetHelper: at android.os.Handler.dispatchMessage(Handler.java:106) [ERROR] TiAssetHelper: at android.os.Looper.loop(Looper.java:193) [ERROR] TiAssetHelper: at android.app.ActivityThread.main(ActivityThread.java:6669) [ERROR] TiAssetHelper: at java.lang.reflect.Method.invoke(Native Method) [ERROR] TiAssetHelper: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) [ERROR] TiAssetHelper: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) [ERROR] v8: [ERROR] v8: [ERROR] v8: # [ERROR] v8: # Fatal error in , line 0 [ERROR] v8: # [ERROR] v8: unreachable code [ERROR] v8: [ERROR] v8: # [ERROR] v8: # [ERROR] v8: # [ERROR] v8: #FailureMessage Object: 0xffd60bb0 {code} We have no idea how to workaround this right now.
| 1 |
3,641 |
TIMOB-27106
|
05/21/2019 11:44:57
|
iOS: MusicLibrary compilation error in 8.0.1.GA
|
A simple ios project get a compilation error with 8.0.1.GA when using Music Library: E.g. {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); win.open(); win.addEventListener('open', function() { Titanium.Media.openMusicLibrary(); }); {code} Gets the following error: {code} [ERROR] ** BUILD FAILED ** [ERROR] The following build commands failed: [ERROR] CompileC /Users/david/Titanium-Projects/test-2/build/iphone/build/Intermediates/test-2.build/Debug-iphoneos/test-2.build/Objects-normal/armv7/MediaModule.o /Users/david/Titanium-Projects/test-2/build/iphone/Classes/MediaModule.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler [ERROR] (1 failure) {code} Note the project must be cleaned (e.g. `ti clean`) before building in order to replicate the bug.
| 2 |
3,642 |
TIMOB-27097
|
05/22/2019 22:17:24
|
iOS: Incremental builds fail to install app when using dynamic frameworks
|
If a framework contains .png or .plist files our build will try to optimize those. Xcode will update code signing on the first build but fails to do so on subsequent builds. Frameworks should be left untouched to avoid this issue. *Steps to reproduce the behavior* # Place any framework containing PNG files into {{platform/ios}} (https://github.com/cjwirth/RichEditorView for example) # Build and run the app for device # Repeat! *Actual behavior* On incremental builds the app fails to install with the following error: {code} [ERROR] An error occurred during build after 6s 579ms [ERROR] Failed to install app on device (0xe8008001) [ERROR] For some reason the app failed to install on the device. Try reconnecting your device and check your provisioning profile and entitlements. {code} *Expected behavior* The app can be installed as usual even on subsequent builds.
| 3 |
3,643 |
TIMOB-27100
|
05/23/2019 17:44:00
|
Android: TabGroup labels not displayed anymore (SDK 8.1.0+)
|
On SDK 8.1.0+, our tab-group labels are not visible anymore. Reverting [this commit|https://github.com/appcelerator/titanium_mobile/commit/2653e9c8f2d62862f5742c61a9ff1607fd7e870b] locally fixed it for us.
| 5 |
3,644 |
TIMOB-27101
|
05/25/2019 05:16:28
|
Android: Window open() wrongly does a shared-element fade-in animation by default as of 8.0.1
|
*Summary:* As of Titanium 8.0.1, a {{Window.open()}} method call is opening with a fade-in animation instead of the system default animation (typically slides-up). What's happening is that the window is doing a "shared-element" animation instead, which is mostly intended to show a view moving from one window to another. This regression was caused by [TIMOB-25678] which was intended to allow app developers to use the shared-element transition animation properties such as "activityEnterTransition" without having to set up any views as shared-elements via {{Window.addSharedElement()}}. This was meant to be more convenient to use than the {{Window.open()}} method's "activityEnterAnimation" and "activityExitAnimation" properties. The negative consequence of this change was that it was always defaulting to shared-element transition animations even if none of the transition properties were assigned. *Steps to reproduce:* # Build and run the below code on Android. # Tap on the "Open" button to open a child window. {code:javascript} var windowCount = 0; function openWindow() { windowCount++; var window = Ti.UI.createWindow({ title: "Window " + windowCount, }); var openButton = Ti.UI.createButton({ title: "Open" }); openButton.addEventListener("click", function() { openWindow(); window.close(); }); window.add(openButton); window.open(); } openWindow(); {code} *Result:* After pressing the "Open" button, it looks like the app fades to the Android system's home screen and then the app's child window fades-in. *Expected Result:* Child window should open with a slide-in animation instead.
| 5 |
3,645 |
TIMOB-27104
|
05/28/2019 12:41:51
|
Android: ProgressIndicator logs "WindowLeaked" exception when hiding dialog and closing window at same time as of 8.0.2
|
*Summary:* As of Titanium 8.0.2, hiding a {{Ti.UI.Android.ProgressIndicator}} and closing its parent window at the same time will log a "WindowLeaked" exception. This is not a crash. Nothing harmful occurs. This is merely an unsightly exception stack trace error that occurs in the log. *Steps to reproduce:* # Build and run the below code on Android. # Tap on the "Show Progress Dialog" button. # Wait 2 seconds for the progress dialog and its window to close. # Observe the log. {code:javascript} var progressIndicator = Ti.UI.Android.createProgressIndicator({ message: "Progressing...", location: Ti.UI.Android.PROGRESS_INDICATOR_DIALOG, type: Ti.UI.Android.PROGRESS_INDICATOR_INDETERMINANT, cancelable: false, persistent: true, }); var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Show Progress Dialog" }); button.addEventListener("click", function(e) { var childWindow = Ti.UI.createWindow({ title: "Child Window" }); childWindow.addEventListener("open", function() { progressIndicator.show(); setTimeout(function() { progressIndicator.hide(); childWindow.close(); // This works-around the problem. // setTimeout(function() { childWindow.close(); }, 1); }, 2000); }); childWindow.open(); }); window.add(button); window.open(); {code} *Result:* The following gets logged when the progress dialog closes. {code} [ERROR] WindowManager: android.view.WindowLeaked: Activity org.appcelerator.titanium.TiActivity has leaked window DecorView@e74eabe[TiActivity] that was originally added here [ERROR] WindowManager: at android.view.ViewRootImpl.<init>(ViewRootImpl.java:518) [ERROR] WindowManager: at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:346) [ERROR] WindowManager: at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:94) [ERROR] WindowManager: at android.app.Dialog.show(Dialog.java:329) [ERROR] WindowManager: at ti.modules.titanium.ui.widget.TiUIProgressIndicator.handleShow(TiUIProgressIndicator.java:236) [ERROR] WindowManager: at ti.modules.titanium.ui.widget.TiUIProgressIndicator.show(TiUIProgressIndicator.java:146) [ERROR] WindowManager: at ti.modules.titanium.ui.android.ProgressIndicatorProxy.handleShow(ProgressIndicatorProxy.java:59) [ERROR] WindowManager: at org.appcelerator.titanium.proxy.TiViewProxy.show(TiViewProxy.java:765) [ERROR] WindowManager: at ti.modules.titanium.ui.TiDialogProxy.access$001(TiDialogProxy.java:29) [ERROR] WindowManager: at ti.modules.titanium.ui.TiDialogProxy$1.onCurrentActivityReady(TiDialogProxy.java:47) [ERROR] WindowManager: at org.appcelerator.titanium.util.TiUIHelper.waitForCurrentActivity(TiUIHelper.java:195) [ERROR] WindowManager: at ti.modules.titanium.ui.TiDialogProxy.show(TiDialogProxy.java:42) [ERROR] WindowManager: at org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method) [ERROR] WindowManager: at org.appcelerator.kroll.runtime.v8.V8Object.fireEvent(V8Object.java:63) [ERROR] WindowManager: at org.appcelerator.kroll.KrollProxy.doFireEvent(KrollProxy.java:978) [ERROR] WindowManager: at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1207) [ERROR] WindowManager: at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:266) [ERROR] WindowManager: at android.os.Handler.dispatchMessage(Handler.java:102) [ERROR] WindowManager: at android.os.Looper.loop(Looper.java:193) [ERROR] WindowManager: at android.app.ActivityThread.main(ActivityThread.java:6694) [ERROR] WindowManager: at java.lang.reflect.Method.invoke(Native Method) [ERROR] WindowManager: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) [ERROR] WindowManager: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) {code} *Note:* The error appears to be harmless. The exception is being caught and logged. The reason it is happening is because the dialog is being shown again in a destroyed activity window. Why the code is automatically calling its {{show()}} method again after hiding/closing is what we need to track down (this is the real bug; but our safety mechanisms are catching it). *Comment from Hans Knöchel:* We suspect it being related to showing our [loader class|https://gist.github.com/hansemannn/20297e983e2b8c898975b600e7ab8418] that uses a {{Ti.UI.ActivityIndicator}}. This did not happen on earlier versions of the SDK. *Work-around:* Instead of hiding the dialog and closing its parent window back-to-back like this... {code:javascript} progressIndicator.hide(); childWindow.close(); {code} Delay closing the window after hiding the dialog like this... {code:javascript} progressIndicator.hide(); setTimeout(function() { childWindow.close(); }, 1); {code}
| 5 |
3,646 |
TIMOB-27108
|
05/28/2019 23:30:59
|
Android: HTTPClient "responseData" blob returns 0 width/height for images over 512kb
|
*Summary:* When downloading an image file greater than 512 KB via {{HTTPClient}}, the resulting "responseData" {{Blob}} will return zero "width" and "height". This is not an issue with smaller image files. *Steps to reproduce:* # Acquire an Android device that has Internet access. # Build and run the below code on that Android device. # Tap on the "Download" button. # An alert is displayed indicating that the image blob width/height is {{0x0}}. _(This is the bug.)_ # Notice that the image blob is successfully displayed in an {{ImageView}}. Meaning this is only an issue with the "width" and "height" returned by the blob object. {code:javascript} var imageUrl = "https://jira.appcelerator.org/secure/attachment/66701/NasaMars.png"; var activityIndicator = Ti.UI.createActivityIndicator({ indicatorColor: (Ti.App.iOS ? "blue" : "white"), style: Ti.UI.ActivityIndicatorStyle.BIG, }); var window = Ti.UI.createWindow({ title: "Download Image Test", exitOnClose: false, }); var imageView = Ti.UI.createImageView({ autorotate: true, top: 0, }); window.add(imageView); var downloadButton = Ti.UI.createButton({ title: "Download", bottom: "20dp", }); downloadButton.addEventListener("click", function(e) { var httpClient = Ti.Network.createHTTPClient({ onload: function(e) { activityIndicator.hide(); downloadButton.enabled = true; var imageBlob = httpClient.responseData; imageView.image = imageBlob; Ti.API.info("@@@ onload() imageBlobSize: " + imageBlob.width + "x" + imageBlob.height); alert("Image Size: " + imageBlob.width + "x" + imageBlob.height); }, onerror: function(e) { Ti.API.info("@@@ onerror()"); alert("Download Failed"); activityIndicator.hide(); downloadButton.enabled = true; }, }); activityIndicator.show(); imageView.image = null; downloadButton.enabled = false; httpClient.open("GET", imageUrl); httpClient.setRequestHeader("Accept-Encoding", "identity"); httpClient.send(); }); window.add(downloadButton); window.add(activityIndicator); window.open(); {code} *Cause:* When the HTTP response is over 512 KB (Titanium's default max buffer size), then {{HTTPClient}} will download the response to a temp file instead of in memory. This bug happens because {{HTTPClient}} immediately wraps this temp file with a "responseData" blob before any bytes have been written to it (ie: the temp file is currently empty). This means that the blob will fail to fetch image info. The solution is to re-read the image file's info once {{HTTPClient}} finishes the download. *Work-around:* In the {{HTTPClient}} object's "onload" callback, you can work-around this issue by creating a new blob from the "responseData" blob's file. The new blob will re-read the image file's info now that it has finished downloading. {code:javascript} var imageBlob = httpClient.responseData; if (imageBlob.file) { imageBlob = imageBlob.file.read(); } {code}
| 8 |
3,647 |
TIMOB-27111
|
05/29/2019 21:40:15
|
Android: Implement async Ti.Database.DB methods
|
- Implement asynchronous {{Ti.Database.DB}} methods for executing SQL queries. - Implement method for executing multiple queries in one shot. (Useful for transactions) {code:js} Ti.Database.DB.executeAsync(callback, query, parameters...); Ti.Database.DB.executeAll(queries); Ti.Database.DB.executeAllAsync(callback, queries); {code}
| 13 |
3,648 |
TIMOB-27114
|
05/31/2019 01:37:08
|
iOS: Support iOS 13 and Xcode 11
|
This epic will track all the items required to enable support for iOS 13.
| 5 |
3,649 |
TIMOB-27117
|
05/31/2019 19:17:47
|
Android: TabGroup bar's background color is wrongly transparent on Android 4.4 as of 8.0.0
|
*Summary:* As of Titanium 8.0.0, the {{TabGroup}} tab bar's background color is transparent on Android 4.4. On Android 5.0 and higher, it shows the correct background color (defaults to dark gray). This issue happens with both the top and bottom tab bar styles. *Steps to reproduce:* # Set up a Classic Titanium app project with the below code. # Build with Titanium 8.0.0 and run it on Android 4.4 # Observe the displayed tab bar. {code:javascript} function createTab(title) { var window = Ti.UI.createWindow({ title: title }); window.add(Ti.UI.createLabel({ text: title + " View" })); var tab = Ti.UI.createTab({ title: title, window: window, }); return tab; } var tabGroup = Ti.UI.createTabGroup({ tabs: [createTab("Tab 1"), createTab("Tab 2"), createTab("Tab 3")], // style: Ti.UI.Android.TABS_STYLE_BOTTOM_NAVIGATION, }); tabGroup.open(); {code} *Result:* The {{TabGroup}} tab bar's background color is transparent when it shouldn't be. !TabGroup-bad.png|thumbnail! *Expected Result:* The tab bar should use the same background color as the {{ActionBar}}, which by default is dark gray (depending on the assigned theme). !TabGroup-good.png|thumbnail! *Work-around:* Set {{TabGroup}} property "tabsBackgroundColor" to the color you want. The original dark gray color is {{"#FF212121"}}.
| 5 |
3,650 |
TIMOB-27119
|
06/01/2019 04:00:27
|
Android: Views inside horizontal layout are clipped to the top
|
Subviews inside a horizontal parent view are clipping to the top on Android. On iOS, they are centered on the y-axis like other views are as well. This is a parity issue. Example: {code:js} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var view = Ti.UI.createView({ layout: 'horizontal', height: 50, backgroundColor: 'gray' }); view.add(Ti.UI.createView({ left: 10, width: 40, right: 10, backgroundColor: '#ff0', height: 20 })); view.add(Ti.UI.createView({ left: 0, width: Ti.UI.FILL, right: 10, backgroundColor: '#f00', height: 20 })); win.add(view); win.open(); {code}
| 0 |
3,651 |
TIMOB-27124
|
06/04/2019 00:14:28
|
iOS 13: Support running on Xcode 11 Simulators
|
In order to run with Xcode 11, ioslib and it's mappings need to be updated. Pull ready [here|https://github.com/appcelerator/ioslib/pull/88].
| 3 |
3,652 |
TIMOB-27128
|
06/04/2019 17:00:51
|
iOS: Install Xcode 11 betas on some build nodes
|
We should being the process of trying to install Xcode 11 betas on one or more of our Mac build nodes so that we can start adding PRs to target iOS 13/Xcode 11.
| 5 |
3,653 |
TIMOB-27130
|
06/05/2019 05:45:58
|
Windows: Support Node-compatible log formatting
|
- Log formatting is currently not supported on any platforms - Our docs suggest our support is equivalent to node.js, which in this case is not true {code:js} console.log('%s', 'test'); // test {code}
| 13 |
3,654 |
TIMOB-27133
|
06/05/2019 16:32:13
|
iOS 13: Add support for SF Symbols
|
SF symbols is a new iOS 13 feature that allows developers to use build-in icons (1500 icons!) in iOS apps. We should allow users to use these icons. They're supposed to replace the system icons up-to iOS 12 Source: https://developer.apple.com/design/human-interface-guidelines/sf-symbols/overview
| 5 |
3,655 |
TIMOB-27135
|
06/05/2019 23:53:53
|
Android: Broken incremental builds when using encrypted assets or referencing JS from HTML
|
*Summary:* The changes made by [TIMOB-27043] is causing Android build issues as of 8.1.0. Note that this issue was never released. We've caught it before RC. ---- *Issue 1:* Building an Android project with asset encryption enabled (which "device" and "production" builds do by default) will fail when built the 2nd time. To reproduce, run the below command on a project twice. It'll fail on the 2nd attempt. {code} appc run -p android --build-only --deploy-type test {code} The above will typically fail on the 2nd attempt with... {code} [ERROR] : Failed to compile Java source files: [ERROR] : [ERROR] : /Users/lchoudhary/Desktop/workspaces/workspace_2019/kitchensink-v2-master/build/android/gen/com/appcelerator/kitchensink/KitchensinkApplication.java:40: error: cannot find symbol [ERROR] : KrollAssetHelper.setAssetCrypt(new AssetCryptImpl()); [ERROR] : ^ [ERROR] : symbol: class AssetCryptImpl [ERROR] : location: class KitchensinkApplication [ERROR] : Note: /Users/lchoudhary/Desktop/workspaces/workspace_2019/kitchensink-v2-master/build/android/gen/com/appcelerator/kitchensink/KitchensinkApplication.java uses unchecked or unsafe operations. [ERROR] : Note: Recompile with -Xlint:unchecked for details. [ERROR] : 1 error [ERROR] Application Installer abnormal process termination. Process exit value was 1 {code} ---- *Issue 2:* A local HTML file that references a JavaScript file via the {{<script/>}} tag will cause an immediate build failure. Steps to reproduce: # Copy the below files to a Classic app. # Build to an Android device or emulator. # Note that the build will immediately fail. _app.js_ {code:javascript} var window = Ti.UI.createWindow(); window.add(Ti.UI.createWebView({ url: "my.html", })); window.open(); {code} _my.html_ {code:html} <!DOCTYPE html> <html> <head> <script src="myHtmlScript.js"></script> </head> <body onload="onPageLoaded();"> This verifies that a local HTML file can access a local JS file. </body> </html> {code} _myHtmlScript.js_ {code:javascript} function onPageLoaded() { alert("Embedded script successfully accessed via HTML file."); } {code} \\ \\ The above will cause the following build failure... {code} [ERROR] : TypeError: Cannot read property 'cyan' of undefined at AndroidBuilder.copyFile (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/android/cli/commands/_build.js:2352:53) at AndroidBuilder.next (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/android/cli/commands/_build.js:2711:16) at /Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/async/dist/async.js:3880:24 at eachOfArrayLike (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/async/dist/async.js:1069:9) at eachOf (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/async/dist/async.js:1117:5) at _parallel (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/async/dist/async.js:3879:5) at Object.parallelLimit [as parallel] (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/async/dist/async.js:3962:5) at Object.parallel (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/node-appc/lib/async.js:56:8) at task.run.then (/Users/jquick2/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/android/cli/commands/_build.js:2707:16) {code}
| 5 |
3,656 |
TIMOB-27153
|
06/15/2019 00:23:28
|
Android: Prevent multiple exception logs
|
- Prevent multiple exception logs when multiple handlers are present *TEST CASE* - Include {{com.appcelerator.aca}} module - Throw an exception {code:js} throw new Error('exception'); {code} - Should NOT see multiple {{TiExceptionHandler}} logs
| 3 |
3,657 |
TIMOB-27155
|
06/15/2019 21:22:35
|
iOS: Incremental builds broken as of 8.1.0
|
_This issue is not in a released version. It was caught before release._ ---- Incremental builds are broken on "master"… I informed the team via the related tickets on GitHub weeks ago but it seems like it has still not been fixed on latest master. In summary: Either TIMOB-27043 or TIMOB-27045. Please handle this asap, it causes a horrible dev exp. Steps to reproduce: 1. Run a clean build with latest master 2. Change nothing and run again Expected: A fast, incremental build happens Actual: A slow, full build happens every time
| 5 |
3,658 |
TIMOB-27161
|
06/18/2019 11:53:21
|
iOS: Remove TestModule from main repository
|
The [TestModule|https://github.com/appcelerator/titanium_mobile/tree/673a3b9117e3d185a09882b5f0409ead47454179/iphone/TestModule] directory in our main repo was used during development of Swift support and is no longer needed so it can be safely removed.
| 1 |
3,659 |
TIMOB-27163
|
06/18/2019 14:55:49
|
iOS: Update Xcode project template settings and resolve warnings
|
The Xcode project template was last update to recommended settings for Xcode 8.3. This needs to be updated for Xcode 10.2. The compiler also prints several warnings (including missing method selectors, nullability flags and strict prototypes) which should be addressed.
| 5 |
3,660 |
TIMOB-27164
|
06/18/2019 19:24:29
|
iOS: Implement async Ti.Database.DB methods
|
- *Parity ticket for Android implementation TIMOB-27111* - Implement asynchronous {{Ti.Database.DB}} methods for executing SQL queries. - Implement method for executing multiple queries in one shot. (Useful for transactions) {code:js} Ti.Database.DB.executeAsync(callback, query, parameters...); Ti.Database.DB.executeAll(queries); Ti.Database.DB.executeAllAsync(callback, queries); {code}
| 13 |
3,661 |
TIMOB-27167
|
06/19/2019 14:01:46
|
CLI: Move Alloy optimizations into core SDK build
|
Alloy does some additional work in specialized Babel plugins to "optimize" Alloy applications. But most of these can be generally useful for Titanium apps and should be moved into the mainline build process to benefit all apps (and to simplify Alloy's build process which is poorly written resulting in some hard to fix build/source map bugs and performance issues). Specifically Alloy allows developers to make use of special references that get replaced by true/false: - OS_IOS, OS_ANDROID, OS_WINDOWS - ENV_DEV, ENV_DEVELOPMENT, ENV_TEST, ENV_PROD, ENV_PRODUCTION - DIST_ADHOC, DIST_STORE Then it strips out dead code as a result (because these are typically use in if/else guards for platform-specific code)
| 13 |
3,662 |
TIMOB-27169
|
06/19/2019 18:38:04
|
iOS 13: Prevent modal windows from being swiped down
|
iOS 13 will display modal windows as page sheets by default. To prevent this for certain screens, the {{isModalInPresentation}} property can be configured on the internal view controller. This should be exposed as a {{forceModal}} boolean property. Since Android does not support this so far, it'd be an iOS only property for now, but could be extended once Android supports it as well. https://developer.apple.com/documentation/uikit/uiviewcontroller/3229894-modalinpresentation
| 3 |
3,663 |
TIMOB-27171
|
06/19/2019 19:11:27
|
iOS 13: Support new UITableViewStyleInsetGrouped style in list-view
|
The new {{UITableViewStyleInsetGrouped}} should be supported in the list-view and table-view.
| 5 |
3,664 |
TIMOB-27256
|
06/20/2019 02:29:00
|
Android: AlertDialog cannot be re-shown in a different window as of 8.0.1
|
It is working fine in 8.0.0 but not in 8.0.1 in 8.0.1 it return "Dialog activity is destroyed, unable to show dialog with message: null" so here the case 1. i have 1 component of alert dialog with android view which used in multiple page of screen 2. when i show the alert dialog in first screen it works fine 3. when i show the same alert dialog in second screen, the alertdialog not showing, but instead it's on the first screen (when i close the second page, i saw the alert dialog in 1st page) 4. in first page when i try to show the same alertdialog, it return error "Dialog activity is destroyed, unable to show dialog with message: null" Workaround for this issue 1. Keep re-creating new alertdialog unlike previous approach which using 1 alertdialog and used in multiple places.
| 5 |
3,665 |
TIMOB-27175
|
06/20/2019 16:32:11
|
iOS: Ti.Platform.id changes when updating to SDK 8.0.0
|
*Steps to reproduce the behavior* # Create a new classic app # Add {{console.log(Ti.Platform.id);}} # Build and run the app using SDK 7.5.1.GA # Note the identifier printed to the log # Build and run the app again using SDK 8.0.0.GA # Note the identifier printed to the log *Actual behavior* Two different identifiers are logged *Expected behavior* The same identifier is logged
| 5 |
3,666 |
TIMOB-27182
|
06/24/2019 14:11:32
|
Update Hyperloop to 4.0.3
|
Update the SDK's bundled Hyperloop version to 4.0.3
| 3 |
3,667 |
TIMOB-27185
|
06/26/2019 07:59:08
|
Windows: Add VideoPlayer "scalingMode" constants VIDEO_SCALING_RESIZE_*
|
*Summary:* As of Titanium 7.0.0, we've added the following iOS-only {{Ti.Media.ViewPlayer}} constants. We need to add them to Windows as well for parity. * [Ti.Media.VIDEO_SCALING_RESIZE|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Media-property-VIDEO_SCALING_RESIZE] * [Ti.Media.VIDEO_SCALING_RESIZE_ASPECT|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Media-property-VIDEO_SCALING_RESIZE_ASPECT] * [Ti.Media.VIDEO_SCALING_RESIZE_ASPECT_FILL|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Media-property-VIDEO_SCALING_RESIZE_ASPECT_FILL] *Note:* The above constants were added to iOS via [TIMOB-19040].
| 8 |
3,668 |
TIMOB-27188
|
06/26/2019 22:28:59
|
Android: TabGroup crashes if tab "title" property is not set as of 8.0.2
|
*Summary:* As of Titanium 8.0.2, setting up a {{TabGroup}} tab without setting the "title" property will cause a crash. This happens to both the top and bottom tab styles. *Use-Case:* Apps which want to show icon-only tab groups. *Steps to reproduce:* # Create a Classic "Default Project". # Set up the project to build with Titanium 8.0.2.GA. # Replace the project's "app.js" with the code below. # Build and run on Android {code:javascript} function createTab(title) { var window = Ti.UI.createWindow({ title: title }); window.add(Ti.UI.createLabel({ text: title + " View" })); var tab = Ti.UI.createTab({ // Setting "title" property to empty string works-around the problem. // title: "", icon: "/assets/images/tab1.png", window: window, }); return tab; } var tabGroupSettings = { tabs: [createTab("Tab 1"), createTab("Tab 2"), createTab("Tab 3")], }; if (Ti.Android) { // tabGroupSettings.style = Ti.UI.Android.TABS_STYLE_BOTTOM_NAVIGATION; } var tabGroup = Ti.UI.createTabGroup(tabGroupSettings); tabGroup.open(); {code} *Result:* App crashes with the following stack trace when using the top bar style. {code} [ERROR] : TiExceptionHandler: (main) [122,122] Unable to start activity ComponentInfo{com.appcelerator.testing/org.appcelerator.titanium.TiActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Object.toString()' on a null object reference [ERROR] : TiExceptionHandler: [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUITabLayoutTabGroup.updateTabTitle(TiUITabLayoutTabGroup.java:222) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUITabLayoutTabGroup.addTabItemInController(TiUITabLayoutTabGroup.java:155) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUIAbstractTabGroup.addTab(TiUIAbstractTabGroup.java:241) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.TabGroupProxy.handlePostOpen(TabGroupProxy.java:448) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.TabGroupProxy.onWindowActivityCreated(TabGroupProxy.java:430) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:752) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiActivity.onCreate(TiActivity.java:47) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:7144) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:7135) [ERROR] : TiExceptionHandler: android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271) [ERROR] : TiExceptionHandler: android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2894) [ERROR] : TiExceptionHandler: android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3049) [ERROR] : TiExceptionHandler: android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78) [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:1809) [ERROR] : TiExceptionHandler: android.os.Handler.dispatchMessage(Handler.java:106) [ERROR] : TiExceptionHandler: android.os.Looper.loop(Looper.java:193) [ERROR] : TiExceptionHandler: android.app.ActivityThread.main(ActivityThread.java:6680) [ERROR] : TiExceptionHandler: java.lang.reflect.Method.invoke(Native Method) [ERROR] : TiExceptionHandler: com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) [ERROR] : TiExceptionHandler: com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) {code} When using the bottom tab style, it crashes with the following stack trace... {code:javascript} [ERROR] : TiExceptionHandler: (main) [114,114] Unable to start activity ComponentInfo{com.appcelerator.testing/org.appcelerator.titanium.TiActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Object.toString()' on a null object reference [ERROR] : TiExceptionHandler: [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUIBottomNavigationTabGroup.updateTabTitle(TiUIBottomNavigationTabGroup.java:262) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUIBottomNavigationTabGroup.updateDrawablesAfterNewItem(TiUIBottomNavigationTabGroup.java:162) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUIBottomNavigationTabGroup.addTabItemInController(TiUIBottomNavigationTabGroup.java:150) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.widget.tabgroup.TiUIAbstractTabGroup.addTab(TiUIAbstractTabGroup.java:241) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.TabGroupProxy.handlePostOpen(TabGroupProxy.java:448) [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.TabGroupProxy.onWindowActivityCreated(TabGroupProxy.java:430) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:752) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiActivity.onCreate(TiActivity.java:47) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:7144) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:7135) [ERROR] : TiExceptionHandler: android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271) [ERROR] : TiExceptionHandler: android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2894) [ERROR] : TiExceptionHandler: android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3049) [ERROR] : TiExceptionHandler: android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78) [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:1809) [ERROR] : TiExceptionHandler: android.os.Handler.dispatchMessage(Handler.java:106) [ERROR] : TiExceptionHandler: android.os.Looper.loop(Looper.java:193) [ERROR] : TiExceptionHandler: android.app.ActivityThread.main(ActivityThread.java:6680) [ERROR] : TiExceptionHandler: java.lang.reflect.Method.invoke(Native Method) [ERROR] : TiExceptionHandler: com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) [ERROR] : TiExceptionHandler: com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) {code} *Work-around:* Set tab title to empty string like this... {code:javascript} var tab = Ti.UI.createTab({ title: "", // <- This works-around issue. icon: "/assets/images/tab1.png", window: window, }); {code}
| 5 |
3,669 |
TIMOB-27191
|
06/27/2019 15:11:05
|
Android: Ti.Filesystem.getFile is not tolerant of file: URIs without file:// prefix
|
A URI like this: "file:/data/user/0/com.appcelerator.testApp.testing/cache/_tmp/rmdir1561643019762/myfile.txt" should be valid and supported. However, Android's logic uses some string matching rather than URI parsing to handle the value and it appears to use incorrect logic when the file URI does not have the two trailing slashes before the path.
| 5 |
3,670 |
TIMOB-27193
|
06/27/2019 18:27:19
|
Android: Ti.Filesystem.File.createFile() may alter location of specified path
|
If I build a file path using path.join(Ti.Filesystem.tempDirectory, "dir/file.txt") and then attempt to create the file, Android will actually ignore the file path/URL I passed in and will try to force it to be created under appdata-private. https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/src/java/org/appcelerator/titanium/TiFileProxy.java#L172-L177
| 5 |
3,671 |
TIMOB-27194
|
06/28/2019 03:01:32
|
Windows: WebView should expose Ti.API.warn and Ti.API.log
|
Windows WebView does not expose {{Ti.API.warn}} and {{Ti.API.log}} in its script content. Windows only exposes {{Ti.API.info}}, {{Ti.API.debug}} and {{Ti.API.error}} now. https://github.com/appcelerator/titanium_mobile_windows/blob/master/Source/TitaniumKit/src/UI/webview.js#L6
| 5 |
3,672 |
TIMOB-27195
|
06/28/2019 13:10:48
|
iOS: Using a commonjs module in an itemtemplate fails in a classic app
|
h5.Description When using a commonjs module as in an ItemTemplate the file fails to get required as it tries alloy first which throws an error, and then the classic code require is never executed, we need to nest the try catches to allow moving on h5.Steps to reproduce 1. Get https://github.com/ewanharris/ti.imageview-listview-example 2. Build to iOS h5.Actual Error is thrown h5.Expected No error thrown
| 5 |
3,673 |
TIMOB-27207
|
06/28/2019 15:06:11
|
TableView / TableViewRow memory leak
|
Old table row references are not cleared when calling *tableView.setData(rows)*. In a production app running SDK 7.4.1.GA this is causing serious memory issues. Because the row structure is quite complex, it's important that old rows are completely cleaned from memory before new ones are set. We've been able to reproduce this issue in a example application for multiple SDK's (8.0.0.GA, 7.4.1.GA, 8.0.1.GA). As demonstrated in the attached video you can see that the objects are not cleared from memory. The source code for the app running in the video has also been attached to this issue. We've tried calling `$.off();$.destroy();` on the `controllers/imagerow` controller, this does not destroy the proxies.
| 8 |
3,674 |
TIMOB-27205
|
07/01/2019 17:34:17
|
Webview http redirects not working as on 7.5.1
|
We have an integration with Plaid (https://plaid.com/) where we use a web view and capture redirects on the site. From their docs: “Communication between the WebView and your app is handled by HTTP redirects rather than client-side JavaScript callbacks. These redirects should be intercepted by your app.” Working code: $.bankPlaidLinkWebView.addEventListener('beforeload', function(_e) { if (_e.url.indexOf(schemaOrString) > -1) { $.bankPlaidLinkWebView.stopLoading(); handleCommand(_e.url); } }); beforeload triggers with an url the same as the one I sent. After that we should listen for an url that has "plaidlink" as the scheme. From the docs: "All redirect URLs have the scheme plaidlink. The event type is communicated via the URL host and data is passed via the querystring. There are two supported events, connected and exit, which are documented below." These redirects are never triggered and it always trigger my original url. This is working on a published app but has stopped working since SDK 8.0.0.GA, I guess it’s related to the switch to WKWebview. Checking TiUIWebView.m I found that changing line #995 from @"url" : webView.URL.absoluteString to: @"url" : navigationAction.request.URL fixes the problem. Don't know if you should fix it here or on the newly introduced 'redirect' event. This was working before 8.0 and works if I change the mentioned line.
| 5 |
3,675 |
TIMOB-27202
|
07/02/2019 05:38:36
|
IOS:Rebuilding app on device throws Couldn't find module error
|
*Steps To Reproduce:* 1.Create a classic/alloy app with latest 8_1_X sdk or master. 2.Run against iOS device 3.Re run against same device again. *Expected:* App should get installed and should be able to launch successfully *Actual:* Throws the following error after launching [ERROR] : column = 25; [ERROR] : line = 9498; [ERROR] : message = "Couldn't find module: ./app for architecture: arm64"; [ERROR] : sourceURL = "file:///var/containers/Bundle/Application/EC162335-7334-496E-B04D-39FFDFBAE114/test23.app/ti.main.js"; [ERROR] : stack = " at require@[native code]\n at require(/ti.main.js:9498:25)\n at (/ti.main.js:9719:10)\n at loadAsync(/ti.main.js:9642:13)\n at global code(/ti.main.js:9716:10)"; [ERROR] : toJSON = "<KrollCallback: 0x1d426d300>"; [ERROR] : } [WARN] : Cannot serialize object, trying to repair ... [WARN] : Found invalid attribute "toJSON" that cannot be serialized, skipping it ... Notes: Works fine on 8.0.2 GA and happens only on master and 8.1_x rerunning the same app on 2 times or 3 times throws error
| 5 |
3,676 |
TIMOB-27203
|
07/02/2019 14:56:59
|
iOS: no apiversion validation performed on application build
|
h5.Description When building for iOS there is no module apiversion validation being performed, this is because the apiversion in the SDK is stored as {{iphone}}, and node-appc is looking for {{ios}}. h5.Steps to reproduce 1. Add the following module to your tiapp modules section {{<module platform="iphone" version="1.1.0">com.appcelerator.aca</module>}} 2. Open the manifest file (probably at {{/Users/eharris/Library/Application Support/Titanium/modules/iphone/com.appcelerator.aca/1.1.0/manifest}}) 3. Change the apiversion to anything other than 2 4. Build with {{ti build -p ios --build-only}} h5.Actual Build carries on past the module verification stage h5.Expected Build should error that module is incompatible
| 3 |
3,677 |
TIMOB-27204
|
07/02/2019 15:22:58
|
CLI: apiversion validation always fails for native modules installed via npm
|
h5.Description When installing a module from npm and building, the apiversion fails even if the apiversion is correct. This is because the apiversion passed in from the SDK is a string, whereas the version from the version we get from the module is a number. We should parseInt both of these before using them. h5.Steps to reproduce 1. In the root of your titanium project {{alongside tiapp.xml}}, run {{npm init -y}} and then {{npm i @titanium/imagefactory}} 2. Add {{<module>ti.imagefactory</module>}} to your modules section in the tiapp 3. Build for Android or iOS (iOS will require TIMOB-27203 to be fixed first) h5.Actual Build errors with {{\[ERROR\] Found incompatible Titanium Modules:}} h5.Expected No error as everything is valid
| 3 |
3,678 |
TIMOB-27209
|
07/07/2019 16:45:55
|
iOS: Be able to determine dark / light mode, as well as changes on it
|
A developer should be able to check the current userInterfaceStyle, e.g. dark mode vs light mode.
| 5 |
3,679 |
TIMOB-27210
|
07/08/2019 09:45:39
|
iOS: Cannot find iOS 13 simulators in Xcode 11 Beta 3
|
We cannot find iOS simulators in Xcode 11 Beta 3 and up. After an investigation, we found out that the "CoreSimulator" directory path moved, so ioslib could not find it. Pull: https://github.com/appcelerator/ioslib/pull/90
| 5 |
3,680 |
TIMOB-27234
|
07/09/2019 16:23:13
|
iOS: VideoPlayer natural size
|
Since 7.0.0 VideoPlayers property {{naturalSize}} and event {{naturalSizeAvailable}} of are broken on iOS. They return video layer size instead of "movie" size. {code:javascript} // URL from https://jira.appcelerator.org/browse/TIMOB-25566 const win = Ti.UI.createWindow({ backgroundColor: '#fff' }); const player = Ti.Media.createVideoPlayer({ url: 'http://techslides.com/demos/sample-videos/small.mp4', // 560x320 showsControls: false, autoplay: true, height: 200 }); win.add(player); function onNaturalSizeAvailable(e) { console.log(e.type, 'e.naturalSize', JSON.stringify(e.naturalSize)); console.log('player.naturalSize', e.source.naturalSize); } player.addEventListener('naturalsizeavailable', onNaturalSizeAvailable); win.open(); {code} output (will differ on different devices/simulators): {noformat} {"width": 320, "height": 183} {noformat} expected output (must be the same for one video): {noformat} {"width": 560, "height": 320} {noformat}
| 5 |
3,681 |
TIMOB-27230
|
07/09/2019 19:55:50
|
iOS: CLI prefers Xcode 11/iOS 13 even though Xcode 10.2.1 is selected
|
I have Xcode 11 beta2 and 10.2.1 installed. Xcode 10.2.1 is selected. If I run {{ti build -p ios}} it will bomb out saying no Xcode's supporting iOS 13.0. Ultimately, it looks the code to auto-select the iOS SDK version when unspecified is not always sorting the Xcode's to prefer to selected one. Specifically if a 2 member array, the custom sort only checks the second Xcode to see if it's selected, not the first. This can result in it not getting "priority" and Xcode's get sorted by version instead (preferring Xcode 11 and iOS 13)
| 5 |
3,682 |
TIMOB-27232
|
07/10/2019 10:21:48
|
Android: Setting Window "barColor" while using a theme without an ActionBar/TitleBar will cause a crash as of 8.1.0
|
*Summary:* Setting {{Ti.UI.Window}} property "barColor" if it's using a theme without an {{ActionBar}} will cause a crash as of Titanium 8.1.0. Note that this bug was never in a release version. It was caught before release. *Steps to reproduce:* # Set up a Classic project to build with Titanium 8.1.0. # Copy the below code to your "app.js". # Build and run on Android. {code:javascript} var window = Ti.UI.createWindow({ barColor: "blue", theme: "Theme.AppCompat.NoTitleBar", }); window.add(Ti.UI.createLabel({ text: "Window Title Test" })); window.open(); {code} *Result:* App crashes on startup and the following exception gets logged... {code} [ERROR] : TiExceptionHandler: (main) [1,6371] Attempt to invoke virtual method 'void android.support.v7.app.ActionBar.setBackgroundDrawable(android.graphics.drawable.Drawable)' on a null object reference [ERROR] : TiExceptionHandler: [ERROR] : TiExceptionHandler: ti.modules.titanium.ui.WindowProxy.windowCreated(WindowProxy.java:313) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiActivityWindows.windowCreated(TiActivityWindows.java:57) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.windowCreated(TiBaseActivity.java:578) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:726) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiActivity.onCreate(TiActivity.java:47) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:6975){code} ---- *Use-case:* This issue is more likely to happen in apps that use theme/style XML file applied globally to the app. Like the one below supplied by [~andreas.pingas]. {code:xml} <style name="FullScreen" parent="@style/Theme.AppCompat.Light"> <item name="android:soundEffectsEnabled">false</item> <item name="colorPrimaryDark">#000000</item> <item name="colorPrimary">#EF4938</item> <item name="colorAccent">#FFFFFF</item> <item name="colorControlNormal">#EF4938</item> <item name="colorControlActivated">#2EA1FC</item> <item name="colorControlHighlight">#F26D60</item> <item name="colorSwitchThumbNormal">#FFFFFF</item> <item name="android:colorButtonNormal">#00BCFF</item> <item name="android:colorEdgeEffect">#EF4938</item> <item name="android:navigationBarColor">#000000</item> <item name="windowNoTitle">true</item> <item name="windowActionBar">false</item> </style> {code} {code:javascript} var win = Titanium.UI.createWindow({ barColor:’#FFF’ theme:'FullScreen' }); win.open(); {code}
| 3 |
3,683 |
TIMOB-27233
|
07/10/2019 18:00:37
|
Titanium CLI v5 deprecation notices
|
Titanium has 3 essential CLI's: Appc CLI, Titanium CLI, and Alloy CLI. The Appc CLI and Alloy CLI will be deprecated. The Titanium CLI will be re-imagined to include the platform specific functionality in Appc CLI as an add-on and Alloy CLI as a Titanium CLI command. As apart of this effort, the following CLI's and compabilities will be deprecated: h4. Titanium CLI * End of support for Node 8 and older ** TIMOB-27250 ** Effective Titanium SDK 9 ** Node 12 being the recommended ** Node 10.13.0 being the minimum supported (though the actual technical minimum is 10.2.0) ** Notice added to Titanium CLI v5 and displayed only if Node version < 10.2 * End of support for non-build,clean Titanium CLI (v5.x or older) plugins ** Effective Titanium SDK 10 ** Plugins must be ported to Appc Daemon plugins and new hook system * End of support for ALL Titanium CLI (v5.x or older) ** Effective Titanium SDK 11 ** Notice added to Titanium CLI for specific commands when output is text (not JSON) ** NON-BUILD plugins must be ported to Appc Daemon plugins ** Note: build-related plugins must be continue to be written as Titanium CLI v5 plugins * End of support for {{ti setup}}, {{ti module}}, and {{ti plugin}} commands? ** Effective Titanium SDK 10 ** Notice added to Titanium CLI v5 for these commands when output is text (not JSON) ** Command will not likely be replaced in Titanium CLI v6 h4. Appc CLI * End of Life for Appc CLI ** Effective Appc CLI 9 ** End of Support sometime in 2020, possibly around Titanium SDK 10... notify to switch to Titanium CLI v6 ** Notice added to Appc CLI for specific commands when output is text (not JSON) ** Users must switch to Titanium CLI v6 h4. Alloy CLI * End of Life for the Alloy CLI ** Effective Titanium SDK 10? ** Notice added to Alloy CLI ** Users must switch to {{ti alloy}} to create models, etc
| 3 |
3,684 |
TIMOB-27240
|
07/12/2019 19:31:32
|
Android: Add Intl.NumberFormat support
|
We use the {{Intl.NumberFormat}} class to format currencies, e.g.: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat {code:js} const value = new Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD', minimumFractionDigits: 2 }).format(10.12); console.log(value); // output: $10.12 {code} It works fine on iOS but throws an error "{{Intl is not defined}}", although the web docs indicate it [should work on V8|https://v8.dev/blog/intl]. Workaround until then is writing another native module: {code:java} @Kroll.module(name="TiCurrency", id="ti.currency") public class TiCurrencyModule extends KrollModule { private static final String LCAT = "TiCurrencyModule"; private static final boolean DBG = TiConfig.LOGD; @Kroll.method public String format(KrollDict params) { double value = params.getDouble("value"); String currency = params.getString("currency"); NumberFormat format = NumberFormat.getCurrencyInstance(Locale.getDefault()); format.setCurrency(Currency.getInstance(currency)); return format.format(value); } } {code}
| 8 |
3,685 |
TIMOB-27242
|
07/12/2019 22:27:53
|
Android: Improve getter and setter warnings
|
Improve Titanium proxy getter and setter warnings: - Show method and line number to aid in moving over from getter/setter methods
| 2 |
3,686 |
TIMOB-27246
|
07/16/2019 08:33:12
|
Windows: Implement Ti.Calendar.Attendee
|
https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Calendar.Attendee https://docs.microsoft.com/en-us/uwp/api/windows.applicationmodel.appointments.appointmentinvitee
| 13 |
3,687 |
TIMOB-27247
|
07/16/2019 19:09:04
|
Android 7: Content URL's are returned as MediaStore columns
|
On Android 7, different to Android 9 for example, content URL's are returned like the following: {code} content://com.google.android.apps.docs.fetcher.FileProvider/vRHOEWuB7jY0n9y_26GoQn-5crFYq2Ljl6VgSX23hUA%3D?_display_name=pdf.pdf&mime_type=application%2Fpdf&_size=433994 {code} Note {{_display_name}} for example, which is the raw column of the MediaStore class.
| 0 |
3,688 |
TIMOB-27248
|
07/16/2019 22:58:48
|
Android: Further improve launch time utilizing snapshots
|
- Futher improve launch time by including {{ti.main.js}} in our V8 snapshot
| 8 |
3,689 |
TIMOB-27249
|
07/17/2019 04:29:58
|
Android: OptionDialog without radio buttons should not auto-set "selectedIndex" property after clicking option
|
*Summary:* As of Titanium 8.1.0, Android now supports displaying an {{OptionDialog}} without radio buttons if its "selectedIndex" property is not set (or set to {{-1}}). See: [TIMOB-26793] But one usability issue with the current implementation is that tapping on an {{OptionDialog}} button causes the "selectedIndex" to be set to the index of the tapped button. The issue with this is if the {{OptionDialog}} is re-shown, it'll show radio buttons instead of plain buttons which is not desired. This happens because the "selectedIndex" was set. *Proposed Solution:* If the {{OptionDialog}} is not showing radio buttons, then it should not automatically set the "selectedIndex" property when tapping a button. The "click" event already provides the index of the button that was tapped on and this is enough. Besides, iOS does not support the "selectedIndex" property anyways, making this behavior portable. However, if the developer does set "selectedIndex" via code to show radio buttons, then the {{OptionDialog}} should maintain the old behavior and update the "selectedIndex" property with the clicked button index. *Steps to reproduce:* # Build and run the below code on Android. # Tap on the "Show Dialog" button. # Tap on the dialog's "Option 1" button. # Tap on the "Show Dialog" button again to re-show it. # Notice the dialog shows radio buttons in front of every option button. _(This is the usability issue.)_ {code:javascript} var dialog = Ti.UI.createOptionDialog({ title: "Option Dialog", options: ["Option 1", "Option 2", "Cancel"], cancel: 2, }); dialog.addEventListener("click", function(e) { Ti.API.info("@@@ Dialog 'click' index: " + e.index + ", button: " + e.button + ", cancel: " + e.cancel); }); dialog.addEventListener("cancel", function(e) { Ti.API.info("@@@ Dialog 'cancel'"); }); var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Show Dialog" }); button.addEventListener("click", function(e) { dialog.show(); }); window.add(button); window.open(); {code} *Work-around:* Set "selectedIndex" to {{-1}} before re-showing the dialog. {code:javascript} dialog.selectedIndex = -1; dialog.show(); {code}
| 5 |
3,690 |
TIMOB-27250
|
07/17/2019 17:27:47
|
Add Node 8 deprecation warning for SDK 9.0 release
|
Node 8 will not be supported in SDK 9.0. Please add a deprecation warning to the CLI in the next release.
| 2 |
3,691 |
TIMOB-27261
|
07/18/2019 00:57:59
|
iOS Unsupported Architecture [x86_64, i386]
|
Hello. Good afternoon. I created an adhoc build with the specs mentioned on the section of environment, so after that, I use the application loader to upload the build, but I am getting the issues attached in the image. Specs: Titanium SDK : 8.0.2.GA CLI: 7.0.12 Node : 8.9.1 Axway Appcelerator Studio, build: 5.1.2.201903111843 Xcode : 10.2 {code:java} ERROR ITMS-90087: "Unsupported Architecture. The executable for tony.app/Frameworks/TitaniumKit.framework contains unsupported architecture '[x86_64, i386]'." ERROR ITMS-90209: "Invalid segment Alignment. The App Binary at tony.app/Frameworks/TitaniumKit.framework/TitaniumKit does not have proper segment alignment. Try rebuilding the app with the latest xcode version." ERROR ITMS-90125: "The Binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's Linker." WARNING ITMS-90080: "The Executable Payload/tony.app/Frameworks/TitaniumKit.framework" is not a Position Independent Executable. Please ensure that ur build settings are configured to create PIE executables." {code} Note: If use the following specs, I will not get any complaint of apple in the application loader. Ti SDK : 7.5.1.GA CLI: 6.2.2 Node Version : 8.9.1 Xcode: 10.2 I do not have a reproduce project for the issue, since the project which I am using is very extensive like to put it in this jira ticket. Please let me know whether you have any doubt or question. Thanks, and best, Antonio Duran.
| 5 |
3,692 |
TIMOB-27253
|
07/18/2019 11:54:43
|
[iOS] Titanium APIs are able to be used for remote webviews
|
When using a remote webview I am still able to log messages to the console (on Android I am unable to log messages when using a webview). *app.js* {code:java} var window = Ti.UI.createWindow({ }); var webview = Ti.UI.createWebView({ top: 0, width: '100%', height: 150 }); var loadButton = Ti.UI.createButton({ title: "load html", left: 0, top: 160, width: 150, height: 100 }); var logButton = Ti.UI.createButton({ title: "Log Message", right: 0, top: 160, width: 150, height: 100 }); var reloadButton = Ti.UI.createButton({ title: "reload webview", left: 0, top: 270, width: 150, height: 100 }); var remoteButton = Ti.UI.createButton({ title: "remote load webview", right: 0, top: 270, width: 150, height: 100 }); remoteButton.addEventListener("click", function() { webview.url = "http://www.google.com"; }); loadButton.addEventListener("click", function() { webview.url = "Wv.html"; }); logButton.addEventListener("click", function() { webview.evalJS("Ti.API.info(\"-------------------------------hello\")"); }); reloadButton.addEventListener("click", function() { webview.reload(); }); window.add(webview); window.add(remoteButton); window.add(loadButton); window.add(logButton); window.add(reloadButton); window.open() {code} *Wv.html* {code:java} <html> <body> <table> <tr> <td id="test">test0</td> </tr> </table> </body> </html> {code} *Test Steps* # Create an app with the above test files # Click on the {{load html button}} # Should display {{test0}} at the top # Press {{Log Message}} # Should log a message # Press {{Reload Webview}} # Press {{Log Message}} # Should log a message # Press {{remote load webview}} # Should see google homepage # Press {{Log Message}} *Expected result* Log message should not be logged when using a remote webview. *Actual result* Log message is still logged when using a remote webview.
| 5 |
3,693 |
TIMOB-27369
|
07/19/2019 09:29:14
|
Android: Border Radius once set on a view cannot be reset( i.e. set to 0)
|
{code:java} var win = Ti.UI.createWindow({ backgroundColor: 'black', }); var vw_main = Ti.UI.createView({ left: 0, top: 0, width: '100%', height: '100%', layout: 'vertical', }); win.add(vw_main); var vw_rect1 = Ti.UI.createView({ top: 20, width: 200, height: 300, borderRadius: 20, backgroundColor: 'red', }); vw_main.add(vw_rect1); var checkBox = Ti.UI.createSwitch({ top: 10, value: true, style: Titanium.UI.Android.SWITCH_STYLE_CHECKBOX, title: 'Border Radius is enabled', }); vw_main.add(checkBox); checkBox.addEventListener('change', function (e) { if (e.value) { vw_rect1.borderRadius = 20; checkBox.title = "Border Radius is enabled"; } else { vw_rect1.borderRadius = 0; //vw_rect1.borderRadius = 0.1; //Current Workaround checkBox.title = "Border Radius is not enabled"; } }); win.open(); {code} Currently as a workaround I am setting the borderRadius to 0.1 instead of 0.
| 1 |
3,694 |
TIMOB-27257
|
07/19/2019 13:40:03
|
[Windows] Error is shown when packaging a windows module
|
When packaging a windows module an error is shown is Studio and the CLI. The CLI error is shown below: {code:java} Command C:\Users\APPC\AppData\Roaming\nvm\v8.9.1\node.exe C:\Users\APPC\.appcelerator\install\7.1.0-master.24\package\node_modules\titanium\lib\titanium.js build --config-file C:\Users\APPC\AppData\Local\Temp\build-1563539776329.json --log-level info --no-banner --project-dir C:\Users\APPC\Documents\Appcelerator_Studio_Workspace\eight\windows 2019-07-19T12:36:20.844Z | ERROR | An uncaught exception was thrown! Assignment to constant variable. 2019-07-19T12:36:20.846Z | ERROR | Assignment to constant variable. {code} Test Steps (CLI): # Create a new Windows module # {{cd}} into the Windows directory # run {{appc run}} *Expected result* Module should package successfully *Actual result* Above error is shown
| 1 |
3,695 |
TIMOB-27260
|
07/19/2019 22:24:44
|
Android: Minor memory leak occurs in runtime every time app relaunches
|
There is a minor string memory leak in our "V8Runtime.cpp" file that happens every time we launch an app. It happens in our JNI {{nativeAddExternalCommonJsModule()}} function below... [V8Runtime.cpp#L379|https://github.com/appcelerator/titanium_mobile/blob/a263a54c3a6b2afa2b909c995eb0c6fb210012d3/android/runtime/v8/src/native/V8Runtime.cpp#L379] We're calling {{GetStringUTFChar()}} to create a {{char*}} string, but we're missing a call to {{ReleaseStringUTFChar()}} to delete it. This is the leak.
| 3 |
3,696 |
TIMOB-27263
|
07/20/2019 23:07:59
|
iOS 13: Modal windows with large titles do not honor barColor
|
On iOS 13, modal windows with large titles do not honor their {{barColor}} property. Natively, it seems like iOS 13 receives it's modal bar color from the background (see native app attached), but doing the same in Titanium also doesn't work. Here is what I tried (both with backgroundColor and barColor): {code:js} var win = Ti.UI.createWindow(); var btn = Ti.UI.createButton({ title: 'Open VC' }); btn.addEventListener('click', function() { var win2 = Ti.UI.createWindow({ backgroundColor: 'red', title: 'Hello', largeTitleEnabled: true }); var nav = Ti.UI.createNavigationWindow({ window: win2 }); nav.open({ modal: true }) }); win.add(btn); win.open(); {code} In addition, it seems like Titanium applies the default bar tint color different to native iOS, which should be investigated in a different ticket!
| 5 |
3,697 |
TIMOB-27266
|
07/21/2019 00:10:26
|
Titanium "Failed to encrypt JavaScript files" error on >=8.0.1.GA on Windows when using 32 bit java
|
There is a bug on Titanium 8.0.1.GA & 8.0.2.GA, where when running a simple compile: {code} ti run -p android -T device {code} Gives the error: {code} [INFO] Encrypting JavaScript files: C:\ProgramData\Titanium\mobilesdk\win32\8.0.1.GA\android\titanium_prep.win32.exe "com.example.sandbox" "C:\path\to\project\build\android\assets" "--file-listing" "C:\path\to\project\build\android\titanium_prep_listing.txt" [ERROR] Failed to encrypt JavaScript files [ERROR] {code} I narrowed down the issue to changes made to *titanium_prep.win32.exe*. Looking at the history: https://github.com/appcelerator/titanium_mobile/commits/master/support/android/titanium_prep.win32.exe It seems that one of the 2 commits to be blamed are: https://github.com/appcelerator/titanium_mobile/commit/3eaf55c596402078321632c682549428b7c57371#diff-81660f9ac67f928cddca3a1e35855580 or https://github.com/appcelerator/titanium_mobile/commit/86b3fc01230a0ec09c0b2577a3e68c1e488e48b1#diff-81660f9ac67f928cddca3a1e35855580 A temp workaround is to copy the *titanium_prep.win32.exe* and *titanium_prep.win64.exe* from 8.0.0.GA and replace the ones in the newer 8.0.1.GA or 8.0.2.GA.
| 5 |
3,698 |
TIMOB-27264
|
07/21/2019 00:31:13
|
Windows: Jenkins tests regularly crashing
|
Jenkins unit tests seems to be regularly crashing on Windows. Ended up skipping some tests in following suites. - -ti.filesystem.file.test.js- - -ti.media.videoplayer.test.js- - -ti.filesystem.filestream.test.js- - -ti.ui.tabgroup.test.js- - -ti.map.test.js-
| 8 |
3,699 |
TIMOB-27269
|
07/22/2019 23:46:26
|
Android: Do not retry sending events if no connectivity
|
- Do not attempt to retry sending events if no connection is established
| 3 |
3,700 |
TIMOB-27270
|
07/22/2019 23:51:08
|
iOS: Allow capture of signal exceptions
|
- Allow ability to capture and handle signal exceptions
| 8 |
3,701 |
TIMOB-27271
|
07/23/2019 02:40:33
|
Android: Resuming with intent using "FLAG_ACTIVITY_MULTIPLE_TASK" can hang the app
|
*Summary:* Resuming an app with an intent having {{FLAG_ACTIVITY_MULTIPLE_TASK}} set causes it to hang in Titanium 8.0.0 if the app does not immediately open a window via its "newintent" event. Titanium 7.x.x and older isn't much better. It won't hang on startup, but will instead create a new splash screen activity instance and do nothing. *Note:* The Android OS will automatically add the {{FLAG_ACTIVITY_MULTIPLE_TASK}} to intents assigned the {{ACTION_SEND}} action. So, apps whose intent-filter do not handle "intent-filter" {{ACTION_SEND}} typically don't have to worry about this issue. *Steps to reproduce:* # Create a classic Titanium app. # Set project name to "IntentTest". _(This is {{<name/>}} in "tiapp.xml".)_ # Set project's "Application Id" to "com.appc.intent.test". _(This is {{<id/>}} in "tiapp.xml".)_ # Set up the "app.js" with the below code. # Build and run on Android. # Open the Mac "Terminal". # CD (change directory) to: {{~/Library/Android/sdk/platform-tools}} # In the terminal, enter the following... {code} ./adb shell am start -n com.appc.intent.test/.IntenttestActivity -a android.intent.action.VIEW -d https://www.appcelerator.com -f 0x08000000 {code} app.js {code:javascript} Ti.Android.rootActivity.addEventListener("newintent", function(e) { label.text = "New Intent:\n" + JSON.stringify(e.intent, null, 4); Ti.API.info("@@@ newintent: " + JSON.stringify(e.intent)); }); var window = Ti.UI.createWindow(); var scrollView = Ti.UI.createScrollView({ scrollType: "vertical", width: Ti.UI.FILL, height: Ti.UI.FILL, }); var label = Ti.UI.createLabel({ text: "Launch Intent:\n" + JSON.stringify(Ti.Android.rootActivity.intent, null, 4), width: Ti.UI.FILL, height: Ti.UI.SIZE, }); scrollView.add(label); window.add(scrollView); window.open(); {code} *Result:* In Titanium 8.0.0 and higher, the app hangs. Also notice in the log that the "newintent" is being logged non-stop, meaning the "newintent" event is being fired repeatedly when it should only be fired once. In Titanium versions older than 8.0.0, a new splash screen activity window is displayed, but nothing happens. Note that the app is not hung and you can back-out of the splash window, but this is still not good behavior. *Expected Result:* The "newintent" event should only be fired once and not hang the app. *Work-around:* Immediately open a window when a "newintent" is received set with this flag. If you don't want to open a window immediately, then you can instead quickly open/close a temporary window when this flag is set. Note that closing a window immediately as shown below prevents it from ever being shown, because Titanium destroys it via the activity's {{onCreate()}} method. {code:javascript} Ti.Android.rootActivity.addEventListener("newintent", function(e) { // This works-around the issue. if (e.intent.flags & Ti.Android.FLAG_ACTIVITY_MULTIPLE_TASK) { var window = Ti.UI.createWindow(); window.open(); window.close(); } }); {code} _(I've tested the below on Android Q while target API Level 29. It works fine.)_
| 8 |
3,702 |
TIMOB-27277
|
07/24/2019 16:08:38
|
iOS: Invalid analytics platform
|
- Analytics payload {{os.name}} was set to the wrong field
| 1 |
3,703 |
TIMOB-27279
|
07/26/2019 12:49:24
|
iOS: App rejected when using Swift module
|
We have received multiple reports that using Swift based modules will result in an App Store rejection with the following reason: Invalid bundle - A nested bundle contains simulator platform listed in CFBundleSupportedPlatforms Info.plist key Also see https://github.com/appcelerator-modules/titanium-onboarding/issues/6
| 5 |
3,704 |
TIMOB-27283
|
07/26/2019 16:51:00
|
Android: Add "contentSize" property to Ti.UI.ScrollView "scroll" event
|
Parity for contentSize inside the scroll event of a ScrollView. iOS has this since 5.2.0. *Example:* {code:java} var win = Ti.UI.createWindow({backgroundColor: '#fff'}); var view1 = Ti.UI.createView({width:20,height:1020,backgroundColor:"#f00",top:0}); var scrollView = Ti.UI.createScrollView({height:Ti.UI.FILL,width:Ti.UI.FILL}); var ldi = Ti.Platform.displayCaps.logicalDensityFactor; scrollView.addEventListener("scroll",function(e){ console.log("contentSize", e.contentSize); }) win.add(scrollView); scrollView.add(view1); win.open(); {code} Will output height: 1020 (height of the red view) and your screen width.
| 5 |
3,705 |
TIMOB-27286
|
07/29/2019 15:28:37
|
TiAPI: Create Node-compatible String Decoder module API
|
It'd be useful to create equivalents of some of the core Node modules in Titanium so that users could port/re-use node codebases on mobile devices. Some of the more common modules could map relatively easily to devices, and would be worth investigating. https://nodejs.org/api/string_decoder.html Once Node's Buffer module is implemented it is a relatively small effort to implement the String Decoder module.
| 8 |
3,706 |
TIMOB-27296
|
07/29/2019 23:43:16
|
Android: Unnecessary conversion from UTF-8 to UTF-16 loading JS assets
|
- Prevent an unnecessary conversion from UTF-8 to UTF-16 and back when loading Javascript assets
| 8 |
3,707 |
TIMOB-27297
|
07/30/2019 02:04:34
|
Android: Allow Hyperloop to access Titanium's core Java classes
|
*Summary:* Hyperloop is unable to access the Titanium SDK's core Java classes. Hyperloop is also unable to access the Java classes of the JAR/AAR libraries included with the SDK such as the "java_websocket.jar" (except for the Google support libraries). We should modify Hyperloop to reference the Titanium SDK's JARs/AARs as well and not just the project's "modules" directory. *Test:* # Create a Classic Titanium project. # Add "hyperloop" module to "tiapp.xml". # Copy the below code to the "app.js". # Build and run on Android. # Verify the following gets logged every second: {{### Is app in foreground: true}} {code:javascript} var tiApplicationClass = require("org.appcelerator.titanium.TiApplication"); setInterval(function() { var isInForeground = tiApplicationClass.isCurrentActivityInForeground(); Ti.API.info("### Is app in foreground: " + isInForeground); }, 1000); {code}
| 5 |
3,708 |
TIMOB-27298
|
07/30/2019 02:46:51
|
Android: Hyperloop should allow access to a Java inner class within an inner class
|
*Summary:* Hyperloop can currently access the 1st level of inner classes under a Java class, but cannot access an inner class belonging to an inner class (ie: 2 inner classes deep). This makes using certain Android classes such as {{MediaStore}}'s 2 level deep nested classes impossible. https://developer.android.com/reference/android/provider/MediaStore *Test:* # Create a Classic Titanium project. # Add "hyperloop" module to "tiapp.xml". # Copy the below code to your "app.js". # Build and run on Android. # Notice that an exception happens for the last line of code below. {code:javascript} var mediaStore = require("android.provider.MediaStore"); // This works. Ti.API.info("### MediaStore.ACTION_IMAGE_CAPTURE: " + mediaStore.ACTION_IMAGE_CAPTURE); // This works. Ti.API.info("### MediaStore.MediaColumns.DISPLAY_NAME: " + mediaStore.MediaColumns.DISPLAY_NAME); // This fails. Ti.API.info("### MediaStore.Images.Media.EXTERNAL_CONTENT_URI: " + mediaStore.Images.Media.EXTERNAL_CONTENT_URI); {code}
| 5 |
3,709 |
TIMOB-27300
|
07/30/2019 23:28:47
|
Android: AssetCryptImpl buffer overflow for large JS assets
|
*Summary:* A buffer overflow or out-of-memory exception can occur for device builds (ie: encrypted assets) if the total byte size of all JavaScript source code exceeds the max heap size. This is more likely to happen when transpiled and source-maps are enabled. *Steps to reproduce:* # Create a Classic Titanium app project using current *8_1_X* # Unzip the attached [^TIMOB-27300.zip] to the project's "Resources" directory. # Build and run on a physical Android device. (Alternatively, build with deployment type {{-D test}}.) # When the app launches, note that an exception occurs in the log. *Result:* - An "BufferOverflowException" gets logged. *Expected Result:* - App should have successfully started and display a green window. *Notes* - If you receive an "OutOfMemory" exception, test on a different device that has enough RAM to load the test case. *Recommended Solution:* Refactor {{titanium_prep}} to prevent {{BufferOverflowException}} for large Javascript files.
| 8 |
3,710 |
TIMOB-27303
|
08/02/2019 14:48:28
|
Windows: Issue with TableView scrollend event (Windows 10 uwp apps)
|
Hello! Scroll event attached in Ti.UI.createTableView. After scroll event-triggered then the user wants to refresh table view. While scrolling, the table view shows blank. This is happening in Windows 10 app (UWP) but working fine in android/iOS Teste project: TestUWP.zip *Steps to reproduce:* 1. Import attached project. 2. Build with sdk 8.0.2.GA or 7.0.2.GA on Windows 10 uwp apps on Windows Desktop 3. Scroll the table view 4. It showing blank {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.17134 Architecture = 32bit # CPUs = 4 Memory = 17091956736 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.1.1 Titanium SDK SDK Version = 8.0.2.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\8.0.2.GA Target Platform = windows {code} Thanks
| 8 |
3,711 |
TIMOB-27304
|
08/02/2019 22:18:16
|
Android: Setting <uses-feature/> required "true" in "tiapp.xml" should override "false" setting in libraries
|
*Summary:* The "AndroidManifest.xml" file's {{<uses-feature/>}} "android:required" attribute value can be set to {{true}} or {{false}}. When multiple manifests declare the same {{<uses-feature/>}}, the merge process must do a logical OR of these values. This means that if one of the manifest files sets it to {{true}}, it can be made {{false}} at the end of the XML merge. (The {{true}} setting wins.) https://developer.android.com/studio/build/manifest-merge When the Titanium build merges "timodule.xml" and "tiapp.xml" settings, it does not "OR" the "android:required" values. Instead the original "timodule.xml" value always wins. This means if the "timodule.xml" sets it {{false}}, the "tiapp.xml" is never able to set it {{true}}. (The reverse is not an issue though.) *Note:* The behavior of the XML merge has changed as of Titanium 8.0.2. Before 8.0.2, the "tiapp.xml" manifest settings used to blindly overwrite the "timodule.xml" manifest settings, which was not technically correct but did allow the "tiapp.xml" to override {{<uses-feature/>}} to {{true}} or {{false}} (it still wasn't {{OR}}ing the values though). Titanium 8.0.2 improved the merge to better follow Google's merging rules, but it is not {{OR}}ing the values which is what's needed. *Steps to reproduce:* # Create a Classic Titanium app project. # Add modules "ti.barcode" to "tiapp.xml". (Can download from [here|https://github.com/appcelerator-modules/ti.barcode].) # Add the {{<uses-feature/>}} settings in "tiapp.xml" as shown below. # Build for Android. # Open Mac's "Finder" window. (Or "Windows Explorer" on Windows.) # Go to project subdirectory: {{./build/android}} # Open file "AndroidManifest.xml". # Observe its {{<uses-feature/>}} XML elements. {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> <uses-feature android:name="android.hardware.camera" android:required="false"/> <uses-feature android:name="android.hardware.touchscreen" android:required="true"/> </manifest> </android> <modules> <module platform="android">ti.barcode</module> </modules> </ti:app> {code} *Result:* The merged "AndroidManifest.xml" file's {{<uses-feature/>}} for "android.hardware.touchscreen" is {{false}} when it should be {{true}}. *Expected Result:* The {{<uses-feature/>}} for "android.hardware.touchscreen" should be {{true}}, not {{false}}. The values need to be {{OR}}'ed together.
| 5 |
3,712 |
TIMOB-27306
|
08/05/2019 14:41:34
|
Windows: callback of tableview scroll function not getting the content size and contentoffset in UWP application
|
Hello! Callback of tableview scroll function not getting the content size and contentoffset in UWP application. It works as expected in android and iOS. I have implemented custom tableview using createTableView. I have attached scroll event to tableview. but callback of scroll function not getting the content size and contentoffset *Test Project*: TestUWP.zip Steps to reproduce: 1. Import attached project. 2. Build with sdk 8.0.2.GA or 7.0.2.GA on Windows 10 uwp apps on Windows Desktop 3. Check the log. {code} [INFO] : Click [INFO] : width = 1024 [INFO] : ************************************************ [INFO] : height = 721.5999755859375 [INFO] : ************************************************ [INFO] constructor = [object class TitaniumWindows::UI::TableView] [INFO] : ************************************************ [INFO] : headerTitleId = Sample Table View [INFO] : ************************************************ [INFO] : rowHeight = 0 [INFO] : ************************************************ [INFO] : headerTitle = [INFO] : ************************************************ [INFO] : search = null [INFO] : ************************************************ [INFO] : headerView = null [INFO] : ************************************************ [INFO] : maxRowHeight = 0 [INFO] : ************************************************ [INFO] data = [object class Titanium::UI::TableViewSection] [INFO] : ************************************************ [INFO] : separatorColor = [INFO] : ************************************************ [INFO] : sectionCount = 1 [INFO] : ************************************************ [INFO] : footerView = null [INFO] : ************************************************ [INFO] : filterAttribute = [INFO] : ************************************************ [INFO] : minRowHeight = 0 [INFO] : ************************************************ [INFO] : filterCaseInsensitive = true [INFO] : ************************************************ [INFO] : allowsSelectionDuringEditing = false [INFO] : ************************************************ [INFO] : allowsSelection = true [INFO] : ************************************************ [INFO] sections = [object class Titanium::UI::TableViewSection] [INFO] : ************************************************ [INFO] : filterAnchored = false [INFO] : ************************************************ [INFO] : footerTitle = [INFO] : ************************************************ [INFO] rect = [object CallbackObject] [INFO] : ************************************************ [INFO] : left = [INFO] : ************************************************ [INFO] backgroundGradient = [object CallbackObject] [INFO] : ************************************************ [INFO] : keepScreenOn = false [INFO] : ************************************************ [INFO] : bottom = 15dp [INFO] : ************************************************ [INFO] : pullBackgroundColor = [INFO] : ************************************************ [INFO] : accessibilityLabel = [INFO] : ************************************************ [INFO] : backgroundLeftCap = 5e-324 [INFO] : ************************************************ [INFO] : backgroundFocusedImage = [INFO] : ************************************************ [INFO] : borderWidth = 0 [INFO] : ************************************************ [INFO] : borderColor = [INFO] : ************************************************ [INFO] : backgroundFocusedColor = [INFO] : ************************************************ [INFO] : backgroundSelectedImage = [INFO] : ************************************************ [INFO] : borderRadius = 0 [INFO] : ************************************************ [INFO] : accessibilityValue = [INFO] : ************************************************ [INFO] : backgroundColor = [INFO] : ************************************************ [INFO] : horizontalWrap = true [INFO] : ************************************************ [INFO] : accessibilityHint = [INFO] : ************************************************ [INFO] : viewShadowColor = [INFO] : ************************************************ [INFO] : backgroundSelectedColor = [INFO] : ************************************************ [INFO] : viewShadowRadius = 5e-324 [INFO] : ************************************************ [INFO] size = [object CallbackObject] [INFO] : ************************************************ [INFO] : width = 100% [INFO] : ************************************************ [INFO] animatedCenter = [object CallbackObject] [INFO] : ************************************************ [INFO] anchorPoint = [object CallbackObject] [INFO] : ************************************************ [INFO] : touchEnabled = true [INFO] : ************************************************ [INFO] : backgroundDisabledColor = [INFO] : ************************************************ [INFO] : accessibilityHidden = false [INFO] : ************************************************ [INFO] : tintColor = [INFO] : ************************************************ [INFO] : backgroundDisabledImage = [INFO] : ************************************************ [INFO] : backgroundTopCap = -7.341218231282964e+125 [INFO] : ************************************************ [INFO] : transform = null [INFO] : ************************************************ [INFO] : right = [INFO] : ************************************************ [INFO] : visible = true [INFO] : ************************************************ [INFO] : opacity = 1 [INFO] : ************************************************ [INFO] : overrideCurrentAnimation = true [INFO] : ************************************************ [INFO] : softKeyboardOnFocus = 131074 [INFO] : ************************************************ [INFO] : backgroundImage = [INFO] : ************************************************ [INFO] center = [object CallbackObject] [INFO] : ************************************************ [INFO] : top = 50dp [INFO] : ************************************************ [INFO] : height = [INFO] : ************************************************ [INFO] : layout = [INFO] : ************************************************ [INFO] : focusable = true [INFO] : ************************************************ [INFO] : clipMode = 131074 [INFO] : ************************************************ [INFO] : zIndex = 2085626670 [INFO] : ************************************************ [INFO] : backgroundRepeat = true [INFO] : ************************************************ [INFO] viewShadowOffset = [object CallbackObject] [INFO] : ************************************************ [INFO] : lifecycleContainer = null [INFO] : ************************************************ [INFO] : bubbleParent = true [INFO] : ************************************************ [INFO] : apiName = Ti.UI.TableView [INFO] : ************************************************ [INFO] : 0 = s [INFO] : ************************************************ [INFO] : 1 = c [INFO] : ************************************************ [INFO] : 2 = r [INFO] : ************************************************ [INFO] : 3 = o [INFO] : ************************************************ [INFO] : 4 = l [INFO] : ************************************************ [INFO] : 5 = l [INFO] : ************************************************ [INFO] : searchedResult count 41 {code} Test Environment : {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.17134 Architecture = 32bit # CPUs = 4 Memory = 17091956736 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.1.1 Titanium SDK SDK Version = 8.0.2.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\8.0.2.GA Target Platform = windows {code} Thanks
| 8 |
3,713 |
TIMOB-27308
|
08/06/2019 05:21:53
|
Android: Determinant "ProgressIndicator" ignores "value" property before shown
|
*Summary:* The {{Ti.UI.Android.ProgressIndicator}} set up as "type" {{PROGRESS_INDICATOR_DETERMINANT}} ignores the "value" property when the {{show()}} method is called. The displayed progress is initialize to zero. Setting the "value" property only works after progress indicator is shown. *Steps to reproduce:* # Build and run the below code on Android. # Tap on the "Show Progress Dialog" button. # Observe the dialog's progress bar position. {code:javascript} var progressIndicator = Ti.UI.Android.createProgressIndicator({ message: "Progressing...", location: Ti.UI.Android.PROGRESS_INDICATOR_DIALOG, type: Ti.UI.Android.PROGRESS_INDICATOR_DETERMINANT, cancelable: true, min: 0, max: 100, value: 50, // <- This is ignored. }); var window = Ti.UI.createWindow(); var showButton = Ti.UI.createButton({ title: "Show Progress Dialog", bottom: "30dp", }); showButton.addEventListener("click", function() { progressIndicator.show(); }); window.add(showButton); window.open(); {code} *Result:* The dialog's progress bar is at {{0%}}, which is wrong. *Expected Result:* The dialog's progress bar should be {{50%}}. *Work-Around:* Set the progress value after the {{show()}} method is called. {code:javascript} progressIndicator.show(); progressIndicator.value = 50; {code}
| 5 |
3,714 |
TIMOB-27309
|
08/06/2019 05:40:00
|
Android: Cannot re-show "ProgressIndicator" dialog if auto-hidden by closed window
|
*Summary:* If a {{Ti.UI.Android.ProgressIndicator}} dialog was auto-closed by a window (ie: you did not call its {{hide()}} method yourself), then you will not be able to re-show the dialog ever again. The {{ProgressIndicator}} object becomes unusable. *Note:* This is more likely to happen if Android developer option "Don't keep activities" is enabled. *Steps to reproduce:* # Build and run the below code on Android. # Tap on the "Show Progress Dialog" button. # A new window displaying a progress dialog will be shown. # Wait 2 second for the window and dialog to auto-close. # Tap on the "Show Progress Dialog" button again. # Notice that the child window is empty. The progress dialog was not shown. (This is the bug.) {code:javascript} var progressIndicator = Ti.UI.Android.createProgressIndicator({ message: "Progressing...", location: Ti.UI.Android.PROGRESS_INDICATOR_DIALOG, type: Ti.UI.Android.PROGRESS_INDICATOR_INDETERMINANT, }); var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Show Progress Dialog" }); button.addEventListener("click", function(e) { var childWindow = Ti.UI.createWindow({ title: "Child Window" }); childWindow.addEventListener("open", function() { progressIndicator.show(); setTimeout(function() { childWindow.close(); }, 2000); }); childWindow.open(); }); window.add(button); window.open(); {code} *Work-Around:* Hide the progress dialog when via its window's "close" event. {code:javascript} window.addEventListener("close", function() { progressIndicator.hide(); }); {code}
| 5 |
3,715 |
TIMOB-27310
|
08/06/2019 17:52:15
|
iOS 13: Support new type of UIBlurEffectStyle constants
|
In iOS 13, couple of new UIBlurEffectStyle constants are given. We need to expose these constants to developers.
| 5 |
3,716 |
TIMOB-27313
|
08/07/2019 05:19:21
|
IOS:Regression-Console.log does not concatenate and log if it has multiple arguments with space
|
Steps to Reproduce: 1.Create a classic app 2.Run on IOS *Expected:* should log movie size *Actual:* displays only the first argument notes: if using concatenation like "console.log(e.type + ' e.naturalSize ' + JSON.stringify(e.naturalSize))" then logging correctly. console.log is working fine on 8.0.2 GA and below.not working on 8.1.0 App.js: {code} const win = Ti.UI.createWindow({ backgroundColor: '#fff' }); const player = Ti.Media.createVideoPlayer({ url: 'http://techslides.com/demos/sample-videos/small.mp4', // 560x320 showsControls: false, autoplay: true, height: 200 }); win.add(player); function onNaturalSizeAvailable(e) { console.log(e.type, 'e.naturalSize', JSON.stringify(e.naturalSize)); console.log('player.naturalSize', e.source.naturalSize); //comment out the above 2 lines and uncomment the below 2 lines //console.log(e.type + ' e.naturalSize ' + JSON.stringify(e.naturalSize)); // console.log('player.naturalSize ' + JSON.stringify(e.source.naturalSize)); } player.addEventListener('naturalsizeavailable', onNaturalSizeAvailable); win.open(); {code}
| 5 |
3,717 |
TIMOB-27318
|
08/08/2019 00:25:38
|
iOS: Use swift 5 for apple watch template
|
Currently we are using swift 3.1 for Apple Watch template. Need to update to swift 5. For module templates we have already done in TIMOB-26770.
| 5 |
3,718 |
TIMOB-27319
|
08/08/2019 03:26:53
|
Windows: Jenkins TabGroup default style test regularly crashing
|
The Jenkins tests for TabGroup {{icon-only tabs - default style}} regularly crashing.
| 5 |
3,719 |
TIMOB-27324
|
08/08/2019 19:19:24
|
Windows: Error on app launch when Liveview is enabled
|
Error is shown in the app during the app launch on windows device when the liveview is enabled. The issue consistently reproduces on windows device however on windows emulator it does work few times. Steps to Reproduce: 1. Create a default Alloy/Classic project 2. Enable liveview and build to a windows device Actual Result: After the splash screen an error is shown as the app launches. Following are the error logs {code} [INFO] : Finished launching the application [INFO] : Connected to app -- Start application log ----------------------------------------------------- [INFO] : testClass 1.0.0.1 (Powered by Titanium 8.1.0.v20190807134709.1c267e9be8bcd3f3e28703154f69c4fe615d5b7e) [ERROR] : Message: Uncaught Error: Runtime Exception: In /app.js require: Could not load module localeStrings [ERROR] require@[native code] [INFO] : require@/ti.main.js:9319:25 [INFO] : _compile@/app.js:720:43 [INFO] : require@/app.js:586:25 [INFO] : patch@/app.js:424:45 [INFO] : /app.js:763:15 [INFO] : /app.js:768:3 [INFO] : global code@/app.js:782:8 [INFO] : require@[native code] [INFO] : require@/ti.main.js:9319:25 [INFO] : /ti.main.js:9576:10 [INFO] : loadAsync@/ti.main.js:9502:13 [INFO] : /ti.main.js:9573:10 [INFO] : global code@/ti.main.js:9596:8 [INFO] : require@[native code] [INFO] : global code [ERROR] : 1 JSExportClass<class Titanium::GlobalObject>::require [ERROR] : 2 JSExportClass<class Titanium::GlobalObject>::require [ERROR] : 3 JSExportClass<class Titanium::GlobalObject>::require [ERROR] : 4 JSExportClass<class Titanium::GlobalObject>::require {code} Expected Result: The liveview should work on win device
| 8 |
3,720 |
TIMOB-27325
|
08/09/2019 03:56:59
|
Android: Adding <uses-library/> within "tiapp.xml" file's <manifest/> block creates invalid entry in "AndroidManifest.xml"
|
*Summary:* Adding a {{<uses-library/>}} element within the "tiapp.xml" file's {{<manifest/>}} block will create an invalid entry within the generated "AndroidManifest.xml" when doing a build. *Note:* The {{<uses-library/>}} entry is supposed to go within the {{<application/>}} block, not the {{<manifest/>}} block. So, doing this would have been invalid anyways. This makes this bug a very minor issue. https://developer.android.com/guide/topics/manifest/uses-library-element *Steps to reproduce:* # Setting a project's "tiapp.xml" with the {{<uses-library/>}} entry below. # Build the project. # Open Finder or Window Explorer. # Go to project's subdirectory: {{./build/android}} # Open the "AndroidManifest.xml" file. {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> <uses-library android:name="com.google.android.maps"/> </manifest> </android> </ti:app> {code} *Result:* The following invalid XML element can be found within the "AndroidManifest.xml" file. This doesn't prevent the app from running, but it's still not good that this is there. {code:xml} <uses-library>[object Object]</uses-library> {code} *Expected Result:* Build system should either omit the {{<uses-library/>}} entry or add it as-is. *Solution:* As noted above, the {{<uses-library/>}} is supposed to go within the {{<application/>}} block. So, all Titanium app devs should be doing the following instead. The build system will correctly inject this into the "AndroidManifest.xml" file. {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> <application> <uses-library android:name="com.google.android.maps"/> </application> </manifest> </android> </ti:app> {code}
| 3 |
3,721 |
TIMOB-27328
|
08/10/2019 03:56:16
|
Android: Splash screen open animation sometimes stutters on cold start
|
*Summary:* As of Android Q beta 4, the OS displays activity windows via a zoom-in animation on some devices such as the Pixel 3. Because of this new open animation, Titanium's splash screen might stutter during a cold start (but not subsequent startups) as shown by the attached "AndroidQ-Launch.gif" below. !AndroidQ-Launch.gif! This issue can happen on older Android OS versions as well, but is less likely to happen and difficult to reproduce. The attached "AndroidP-Launch.gif" shows this happening on Android P with a slide-up transition. !AndroidP-Launch.gif! *Notes:* * This does not happen with Android Q on a Pixel 2 device. (Does not do zoom-in animations.) * This stutter only happens when opening a window while the splash screen is still doing its open animation. (Can work-around by delaying opening the first window.) * This appears to be a bug on Google's end, but we should attempt to work-around it. *Steps to reproduce:* # Acquire a Pixel 3 device/emulator with Android Q beta 4 or newer. # Download kitchensink-v2 project. (Can be found [here|https://github.com/appcelerator/kitchensink-v2].) # Build and run on the Pixel 3. # Notice that the splash screen stutters while opening as shown in GIF above. # To re-test, "force-quit" the app and relaunch the app. *Work-Around:* In your "app.js" or "alloy.js", delay opening the first window by about {{100ms}}. Waiting for the splash screen open animation to end works-around the issue.
| 5 |
3,722 |
TIMOB-27330
|
08/12/2019 07:45:45
|
Xcode 11: Cannot build to device
|
When using Xcode 11 B5, I cannot build for device anymore. Production builds work fine. The following error is shown, indicating certificate issues, which is not true since all certs are valid and can be used with Xcode 10: {code} [TRACE] error: Signing certificate is invalid. Signing certificate "Apple Development: ORG_NAME (TEAM_ID)", serial number "SERIAL_NO", is not valid for code signing. It may have been revoked or expired. (in target 'test_app' from project 'test_app') {code} To reproduce, build a simple app for device in Xcode 10 and then Xcode 11.
| 0 |
3,723 |
TIMOB-27331
|
08/12/2019 14:18:43
|
Xcode 11: No logs shown on recurring builds
|
Using the latest Xcode 11 B5, application logs are no longer visible. Logs: {code} [TRACE] ** BUILD SUCCEEDED ** [INFO] Finished building the application in 41s 82ms [INFO] Launching iOS Simulator [TRACE] [ioslib] Selected iOS Simulator: iPhone Xʀ [TRACE] [ioslib] UDID = DF1A2054-2C4C-4C7F-9E4A-C1BA5338D43E [TRACE] [ioslib] iOS = 13.0 [TRACE] [ioslib] Autoselected Xcode: 11.0 [TRACE] [ioslib] Checking if the simulator /Applications/Xcode-beta.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator is already running [TRACE] [ioslib] Simulator is running (pid 30875) [TRACE] [ioslib] Waiting for simulator to boot... [TRACE] [ioslib] Simulator is booted! [TRACE] [ioslib] iPhone Xʀ Simulator already running with the correct UDID [TRACE] [ioslib] Tailing iPhone Xʀ Simulator system log: /Users/user/Library/Logs/CoreSimulator/DF1A2054-2C4C-4C7F-9E4A-C1BA5338D43E/system.log [TRACE] [ioslib] Running: osascript "/Users/user/Library/Application Support/Titanium/mobilesdk/osx/8.2.0/node_modules/ioslib/lib/sim_focus.scpt" "Simulator" [TRACE] [ioslib] iPhone Xʀ Simulator successfully focused [TRACE] [ioslib] Installing the app [TRACE] [ioslib] App launched [TRACE] [ioslib] Trying to connect to log server port 50092... {code}
| 13 |
3,724 |
TIMOB-27335
|
08/14/2019 02:48:00
|
Windows: TableView constantly fires scrollend during mouse drag
|
TableView constantly fires {{scrollend}} event during dragging scroll bar with PC mouse. !drag.png|thumbnail! {code} var win = Ti.UI.createWindow(); var tableData = []; for (var i = 0; i < 40; i++) { tableData.push({title: 'Apple ' + i}); } var table = Ti.UI.createTableView({ data: tableData }); table.addEventListener('scrollend', function() { Ti.API.info('scrollend'); }); win.add(table); win.open(); {code} Expected: {{scrollend}} happens only when you finish scrolling bar with mouse drag.
| 8 |
3,725 |
TIMOB-27336
|
08/14/2019 19:29:25
|
Android: Pre-cache common JS assets
|
- Common Javascript assets such as {{app.js}} or {{alloy.js}} etc.. could be pre-loaded and cached until they are used, speeding up {{require()}} calls. - A {{cache.json}} could list the assets to be loaded upon launch and can be generated at build time.
| 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.