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,426 |
TIMOB-26388
|
09/13/2018 07:09:33
|
iOS 12: Support iPhone Xs Max & iPhone XR launch-screen images
|
Pretty much the same as TIMOB-25269, but now for another device. We need to figure out the names for the iPhone Xs launch-screen image names and handle those for the launch-screen image. This is required to incorporate the new image dimensions (and notch changes) that the new model includes. *Important note: This can be easily workarounded by using launch-screen storyboards as documented [here|https://wiki.appcelerator.org/display/guides2/iOS+Launch+Files].
| 8 |
3,427 |
TIMOB-26389
|
09/13/2018 15:02:36
|
iOS: Application throws an error if there is no Ti.UI.Window reference
|
When building a blank application or with just console.log/console.time. The following error is shown: {code:java} [ERROR] : ** BUILD FAILED ** [ERROR] : The following build commands failed: [ERROR] : CompileC /Users/Samir/Desktop/newWS/T5/build/iphone/build/Intermediates/T5.build/Debug-iphoneos/T5.build/Objects-normal/armv7/TiViewProxy.o /Users/Samir/Desktop/newWS/T5/build/iphone/Classes/TiViewProxy.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler [ERROR] : (1 failure) {code} *Steps to reproduce:* # Create a titanium application # Run the app blank or with something similar to: {code:java} console.time('mytimer'); // Start timer console.timeLog('mytimer'); // Log time taken so far console.timeLog('mytimer', 'with', 'some', 'extra', 'info'); // Log time taken with extra logging console.timeLog('mytimer', [ 'a', 'b', 'c' ], { objects: true }); // Should handle Arrays and Objects console.timeEnd('mytimer'); {code} *Expected result* Application should still build and the console should output something similar to (if the code above is used): {code:java} [INFO] mytimer: 1ms [INFO] mytimer: 2ms with some extra info [INFO] mytimer: 3ms ["a","b","c"] {"objects":true} [INFO] mytimer: 3ms {code} *Actual result* Build fails and above error is shown.
| 2 |
3,428 |
TIMOB-26402
|
09/20/2018 13:36:20
|
Android: Maintain native module compatibility with Titanium 7.0.0
|
- Updating V8 to 7.0 breaks native module compatibility with Titanium SDK {{7.0.0}} - Make necessary changes to V8 to maintain backwards compatibility with Titanium SDK {{7.0.0}}
| 8 |
3,429 |
TIMOB-26403
|
09/20/2018 14:26:14
|
kitchensink-v2 broken on latest SDK build on master
|
On the latest version of the SDK in master (7.5.0.v20180920040518) kitchensink-v2 is broken and displays the following error on iOS (Looks like it broke in SDK Version 7.5.0.v20180919143608): {code:java} [ERROR] : Script Error { [ERROR] : column = 18; [ERROR] : line = 6; [ERROR] : message = "Can't find variable: _"; [ERROR] : sourceURL = "file:///Users/Samir/Library/Developer/CoreSimulator/Devices/2BA65AF9-7B80-486E-9A20-005A318A4424/data/Containers/Bundle/Application/5A64DDEB-EA50-4721-81B9-15B9BBC5D6DE/KitchenSink.app/logger.js"; [ERROR] : stack = " at Logger(/logger.js:6:18)\n at (/logger.js:33:41)\n at global code(/logger.js:35:70)\n at require@[native code]\n at (/alloy/controllers/index.js:5:22)\n at global code(/alloy/controllers/index.js:108:70)\n at require@[native code]\n at createController(/alloy.js:339:21)\n at (/app.js:34:23)\n at global code(/app.js:36:70)\n at require@[native code]\n at (/ti.main.js:27:10)\n at loadAsync(/ti.internal/bootstrap.loader.js:106:11)\n at global code(/ti.main.js:24:52)"; [ERROR] : toJSON = "<KrollCallback: 0x604000265e00>"; [ERROR] : } [ERROR] : Script Error Module "logger.js" failed to leave a valid exports object [ERROR] : Script Error Module "alloy/controllers/index.js" failed to leave a valid exports object [ERROR] : Script Error Module "app.js" failed to leave a valid exports object {code} *Android Error* {code:java} [ERROR] : TiExceptionHandler: (main) [213,213] /logger.js:6 [ERROR] : TiExceptionHandler: this.logger = _.extend({}, Backbone.Events); [ERROR] : TiExceptionHandler: ^ [ERROR] : TiExceptionHandler: ReferenceError: _ is not defined [ERROR] : TiExceptionHandler: at new Logger (/logger.js:6:17) [ERROR] : TiExceptionHandler: at /logger.js:33:33 [ERROR] : TiExceptionHandler: at Module._runScript (ti:/module.js:613:9) [ERROR] : TiExceptionHandler: at Module.load (ti:/module.js:105:7) [ERROR] : TiExceptionHandler: at Module.loadJavascriptText (ti:/module.js:457:9) [ERROR] : TiExceptionHandler: at Module.loadAsFile (ti:/module.js:512:15) [ERROR] : TiExceptionHandler: at Module.loadAsFileOrDirectory (ti:/module.js:429:20) [ERROR] : TiExceptionHandler: at Module.require (ti:/module.js:296:17) [ERROR] : TiExceptionHandler: at require (ti:/module.js:570:15) [ERROR] : TiExceptionHandler: at /alloy/controllers/index.js:5:15 [ERROR] : TiExceptionHandler: [ERROR] : TiExceptionHandler: org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(Native Method) [ERROR] : TiExceptionHandler: org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModule(V8Runtime.java:180) [ERROR] : TiExceptionHandler: org.appcelerator.kroll.KrollRuntime.runModule(KrollRuntime.java:247) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiLaunchActivity.loadActivityScript(TiLaunchActivity.java:135) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiLaunchActivity.windowCreated(TiLaunchActivity.java:190) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiRootActivity.windowCreated(TiRootActivity.java:174) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:675) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiLaunchActivity.onCreate(TiLaunchActivity.java:176) [ERROR] : TiExceptionHandler: org.appcelerator.titanium.TiRootActivity.onCreate(TiRootActivity.java:163) [ERROR] : TiExceptionHandler: android.app.Activity.performCreate(Activity.java:6237) [DEBUG] : OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true [ERROR] : GraphResponse: {HttpStatus: 400, errorCode: -1, subErrorCode: -1, errorType: null, errorMessage: null} [DEBUG] : D/com.facebook.FacebookSdk: getGraphApiVersion: v3.0 [ERROR] : V8Exception: Exception occurred at /logger.js:6: Uncaught ReferenceError: _ is not defined {code} *Test Steps* # Download the latest SDK version from master {{appc ti sdk install -b master -d}} # Download the kitchensink-v2 app from https://github.com/appcelerator/kitchensink-v2 # Run the kitchensink-v2 using the latest master build *Expected result* Application should run without any issues *Actual result* Above error is shown *Note:* kitchensink-v2 works as expected in SDK version 7.5.0.v20180919120117
| 13 |
3,430 |
TIMOB-26406
|
09/20/2018 16:14:59
|
iOS 12 Random crashes.
|
We're noticing various seemingly random crashes in our apps on iOS 12. See attached device logs. Issues only occur on physical devices. I don't have any code to present, it happens "randomly". I've seen various other tickets that are potentially related, but I'm creating this ticket anyway to hopefully create awareness for this issue, our clients starting to notice this which is a big issue for us. Link with similar issue on SO: https://stackoverflow.com/questions/52120879/appcelerator-app-crashing-on-iphone-x-with-ios-12-beta-11 Titanium SDK we're using: 7.1.0.GA, but also tested with 7.2.0, 7.4.0. Same result. Xcode 9 / 10, no difference.
| 0 |
3,431 |
TIMOB-26444
|
09/25/2018 13:36:28
|
Calling Titanium.App.iOS.UserNotificationCenter.getDeliveredNotifications causes 'NSInvalidArgumentException'
|
Calling Titanium.App.iOS.UserNotificationCenter.getDeliveredNotifications causes 'NSInvalidArgumentException'. The first line of the stacktrace ` -[UNNotification content]: unrecognized selector sent to instance` points to a type mismatch. The code attempts to get the 'content' property on UNNotification instead of UNNotificationRequest. Code should be modified to look like this. I can provide a PR {code:java} [[UNUserNotificationCenter currentNotificationCenter] getDeliveredNotificationsWithCompletionHandler:^(NSArray<UNNotification *> *notifications) { NSMutableArray *result = [NSMutableArray arrayWithCapacity:[notifications count]]; for (UNNotification *notification in notifications) { [result addObject:[self dictionaryWithUserNotificationRequest:[notification request]]]; } {code}
| 3 |
3,432 |
TIMOB-26411
|
09/25/2018 19:59:50
|
API: Support async variants of Ti.IOStream methods
|
We currently have synchronous read/write calls for Ti.IOStreams. This has been our historical API, but having I/O done in a blocking synchronous way is a big performance no-no, and is especially bad when running on the main thread. We should support passing in callback functions as optional final arguments to these functions, and consider deprecating the block/sync versions.
| 13 |
3,433 |
TIMOB-26454
|
09/27/2018 11:35:42
|
Reverse geocoding freeze the app when manualMode is true
|
I was implementing the Titanium reverse geocoding in my app, on iOS I have had no problems so I also do it on android, suddenly app freeze. But I think I found the problem: When Ti.Geolocation.Android.manualMode = true; Titanium.Geolocation.reverseGeocoder not works and freeze the app. I attach my index file where you can see the //commented line for manual mode, decomment it and see after first location event everything freeze
| 3 |
3,434 |
TIMOB-26433
|
09/27/2018 22:27:48
|
same error with sdk 7.4.0 GA --> TIMOB-26109 Xcode 10: Cannot build modules with the new (default) build system
|
I have reproduced the error again. I don´t know the reason, this is my log. Its seems all its ok. Any ideas? Thanks in advance. 2018-9-27 22:48:21 Operating System Name = Mac OS X Version = 10.13.6 Architecture = 64bit CPUs = 8 Memory = 8589934592 Node.js Node.js Version = 9.2.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.1.1 Titanium SDK SDK Version = 7.4.0.GA SDK Path = /Users/user1/Library/Application Support/Titanium/mobilesdk/osx/7.4.0.GA Target Platform = iphone Command /Users/user1/.nvm/versions/node/v9.2.1/bin/node /Users/user1/.appcelerator/install/7.0.6/package/node_modules/titanium/lib/titanium.js build --platform ios --log-level trace --sdk 7.4.0.GA --project-dir /Users/user1/Documents/app --target simulator --ios-version 12.0 --device-family universal --deploy-type development --device-id 53FAF1A3-224E-4BE5-8315-7D04DA01E8BE --skip-js-minify --no-colors --no-progress-bars --no-prompt --prompt-type socket-bundle --prompt-port 49199 --config-file /var/folders/jq/rlqcc3v10_9_y__l4fsmjvkh0000gn/T/build-1538081291744.json --no-banner --project-dir /Users/user1/Documents/app [TRACE] [ioslib] Validating iOS Simulator UDID 53FAF1A3-........ [TRACE] [ioslib] Found iOS Simulator UDID 53FAF1A3......... [TRACE] [ioslib] Selected iOS Simulator: iPhone 6 [TRACE] [ioslib] UDID = 53FAF1A3-........... [TRACE] [ioslib] iOS = 12.0 error: [INFO] : Cleaning Xcode derived data [ERROR] : note: Using new build system [ERROR] : error: Could not delete `/Users/user1/Documents/app/build/iphone/build` because it was not created by the build system and it is not a subfolder of derived data. [ERROR] : ** CLEAN FAILED **
| 3 |
3,435 |
TIMOB-26436
|
10/01/2018 12:48:50
|
iOS: VIdeoPlayer time in seconds
|
Since 7.0.0 VideoPlayer on iOS treats time in seconds instead of milliseconds. Affected properties: "currentPlaybackTime", "duration" (probably also "playableDuration" and "endPlaybackTime"), events: "durationavailable".
| 5 |
3,436 |
TIMOB-26423
|
10/01/2018 17:41:30
|
[Android] Application crashes when using debugger
|
When using the debugger (Windows - Android in this instance) the application crashes after a certain period of time. *Test Steps* # Create and Alloy application # Set some debug points in the {{index.js}} # Set studio to {{debug}} # Debug the app # Once the debugging view is shown use the Step into/over/return buttons # After a period of time the following error is shown in studio (see screenshot) and the application crashes *Actual result* Studio shows the error shown in the screenshot and the emulator/device crash. *Expected result* Debugging should work without any issues.
| 1 |
3,437 |
TIMOB-26424
|
10/01/2018 18:23:01
|
Android: Added Ti.App "pause" and "resume" lifecycle events
|
- {{Ti.App}} lifecycle events are not fired {code:js} Ti.App.addEventListener('resume', () => { Ti.API.info('RESUME'); }); Ti.App.addEventListener('pause', () => { Ti.API.info('PAUSE'); }); {code}
| 5 |
3,438 |
TIMOB-26427
|
10/02/2018 02:55:53
|
Android: Add "safeAreaPadding" property to Ti.UI.Window
|
*Summary:* On Android, we'd like to add support for Window property "extendSafeArea" so that the window's root view can extend under the Android 9 notch or under an Android 4.4 translucent StatusBar/NavigationBar (see: [TIMOB-26246]). However, this feature is useless since these insets can be of various sizes and on any side of the screen. An app developer needs to know what region of the screen they can place content so that it won't be covered up by the device's insets. *Proposal:* Add read-only property "safeAreaPadding" to {{Ti.UI.Window}}. This property will return a Titanium [ViewPadding|https://docs.appcelerator.com/platform/latest/#!/api/ViewPadding] dictionary providing the left, top, right, and bottom padding needed to show content safely within the window without overlap. If there are no insets or if "extendSafeArea" is set {{false}}, then this property is expected to return all zeros for the padding. The idea is that the app developer will then be able to set up their own safe area view and use it as a container as shown below. {code:javascript} var FLAG_TRANSLUCENT_NAVIGATION = 134217728; var FLAG_TRANSLUCENT_STATUS = 67108864; var window = Ti.UI.createWindow({ extendSafeArea: true, theme: "Theme.AppCompat.NoTitleBar", windowFlags: FLAG_TRANSLUCENT_STATUS | FLAG_TRANSLUCENT_NAVIGATION, }); var safeAreaView = Ti.UI.createView({ backgroundColor: "green", borderWidth: "4dp", borderColor: "blue", }); window.add(safeAreaView); window.addEventListener("postlayout", function() { // Padding's left/top/right/bottom can be used as pin positions for the view. safeAreaView.applyProperties(window.safeAreaPadding); }); window.open(); {code} *Note:* We should do the same on iOS to handle the following: * iPhone X top notch and bottom home indicator. * Translucent status bar on all other iOS devices. (Safe area should be beneath status bar.) *Safe-Area Container Example:* Test code [^ExtendSafeAreaContainerTest.js] shows how to create a safe-area view container for other child views, guaranteed to always make child content tappable without overlap. The green rectangle with the blue border is the safe-area view within the root white window using an orange border. !ExtendSafeAreaContainerPortrait.jpeg|thumbnail! !ExtendSafeAreaContainerLandscapeLeft.jpeg|thumbnail! !ExtendSafeAreaContainerLandscapeRight.jpeg|thumbnail! *Safe-Area ScrollView Example:* Test code [^ExtendSafeAreaScrollViewTest.js] shows how to pad a ScrollView. It allows its contents to scroll beneath a translucent status bar and navigation bar, but pads the top and bottom so that the top-most view and bottom-most view can be scrolled within the safe-area, making them tappable. !ExtendSafeAreaScrollPortraitTop.jpeg|thumbnail! !ExtendSafeAreaScrollPortraitBottom.jpeg|thumbnail! !ExtendSafeAreaScrollLandscapeRightTop.jpeg|thumbnail! !ExtendSafeAreaScrollLandscapeLeftBottom.jpeg|thumbnail! !ExtendSafeAreaScrollLandscapeLeftTop.jpeg|thumbnail! *Safe-Area TabGroup Example:* Test code [^ExtendSafeAreaTabsTest.js] shows how to extend tabs to beneath the notches, translucent status bar, and translucent navigation bar. You would *not* normally use a translucent top status bar with an opaque top tab bar, but this is for testing purposes. Note that the top tab bar hovers over the content and each individual tab completely fills the window. The safe-area padding reported lies within the TabGroup container where content is normally displayed when "extendSafeArea" is set to {{false}}. !ExtendSafeAreaTab1Portrait.jpeg|thumbnail! !ExtendSafeAreaTab2Portrait.jpeg|thumbnail! !ExtendSafeAreaTabTransitionPortrait.jpeg|thumbnail! !ExtendSafeAreaTab1LandscapeRight.jpeg|thumbnail! !ExtendSafeAreaTab1LandscapeLeft.jpeg|thumbnail! *Safe-Area DrawerLayout Example:* Test code [^ExtendSafeAreaDrawerTest.js] shows that a {{Ti.UI.Toolbar}} with "extendBackground" to {{true}} will automatically handle the safe-area when docked to the top of the screen. The toolbar will extend into the unsafe area of the screen inset while leaving its text and button content within the safe-area. This test code uses a toolbar in the root view and in a drawer side panel. !ExtendSafeAreaDrawerMainPortrait.jpg|thumbnail! !ExtendSafeAreaDrawerMainLandscape.jpg|thumbnail! !ExtendSafeAreaDrawerPanelPortrait.jpg|thumbnail! !ExtendSafeAreaDrawerPanelLandscape.jpg|thumbnail!
| 13 |
3,439 |
TIMOB-26431
|
10/02/2018 20:56:40
|
iOS: Password Keyboard Toolbar showing on non password fields
|
iOS app is crashing when using Titanium.UI.AUTOFILL_TYPE_PASSWORD as they getting this 2 issues: # 1. Since a password text field exists then various text fields within the app will show the password toolbar even though they have no autofill type. This becomes very confusing like when you are entering text into a field called stock number and the password toolbar shows. # 2. Even if I remove autoFill type password from the password field since it has a password mask set to true it will show the password toolbar. If I remove password mask it will not show the password toolbar but it will also not mask the text. *App Link with recorded video* # [Video of the issue happening|https://github.com/jwogan5/sampleApp/blob/master/My%20Movie%201.mp4] # [The app code for the issue|https://github.com/jwogan5/sampleApp/blob/master/hypertest.zip] *Steps to Reproduce:* # 1. Using autofillType:Titanium.UI.AUTOFILL_TYPE_PASSWORD, from the above video, you can get icloud keychain opens up for a password when it got clicked. The issue occurred by going to the next page even though those fields neither an autofill nor password fields but they also show the password toolbar when click on them. # 2. To show password toolbar in simulator, go to Settings > Accounts and Password > AutoFill Password turn on. You will get the issue.
| 3 |
3,440 |
TIMOB-26434
|
10/03/2018 13:38:18
|
Android: Support building "app bundles"
|
*Summary:* Google Play allows you to upload your app as an "app bundle" (aka: an {{*.aab}} file) instead of an APK. How this works is that Google will generate multiple APKs from the app bundle, split by architecture and image density, and digitally sign each APK with a keystore you've uploaded for you. This is a similar feature to what Apple provides on iOS and allows for smaller apps to be downloaded to the Android device. https://developer.android.com/guide/app-bundle *Note:* You cannot install/run an app bundle on an Android devices. That is, Android devices still only support APKs. An app bundle is only a Google Play publishing feature. This is why a Titanium "test" or "development" build should not build an app bundle, because it's useless for local testing purposes. It only makes sense for "production" builds for publishing. *Recommended Solution:* When doing a "production" build, Titanium should generate both an APK and app-bundle to the destination directory. No configuration required. Note that building a "production" APK is still useful. Some features such as push notifications, in-app billing, Google LVL licensing, etc. can't be tested with a "debug.keystore" signed APK. Also, app bundles do not support Google expansion files. Nor are app bundles supported on other Android app stores such as Amazon (ie: only supported on Google Play). We can implement app bundle support once we've adopted gradle build support. https://developer.android.com/studio/build/building-cmdline The {{gradlew}} command line would be something like this... {code} ./gradlew :app:bundleRelease {code}
| 3 |
3,441 |
TIMOB-26443
|
10/03/2018 13:38:44
|
iOS: App crashing while playing Youtube Video in WebView
|
App is crashing when working with youtube videos. Please check out the video attached. index.xml <Alloy> <Window class="container"> <WebView url='https://www.youtube.com/watch?v=MYREllHPSbU&list=PL9MeVsU0uG64RMlPf71OHsRyJWyAXnZ-l'></WebView> </Window> </Alloy> Index.js $.index.open();
| 3 |
3,442 |
TIMOB-26441
|
10/05/2018 23:43:11
|
Android: Implement Titanium.UI.NavigationWindow
|
- Android implementation of {{Titanium.UI.NavigationWindow}}
| 13 |
3,443 |
TIMOB-26447
|
10/09/2018 10:19:59
|
Android 8: Unable open PDF on some devices
|
h6.Problem Customer is trying to download the pdf from remote server using URL, save them to external or application directory and then open them in external pdf viewer using intent. Like example in post https://www.appcelerator.com/blog/2015/08/appcelerator-pdf-viewer-demo/. But throwing following error on Android 8. {code} [ERROR] : TiFileProxy: (KrollRuntimeThread) [9574,75852] IOException encountered [ERROR] : TiFileProxy: java.io.FileNotFoundException: /storage/emulated/0/com.edf.mobile/EDF Bill 10 August 2018.pdf (Permission denied) [ERROR] : TiFileProxy: at java.io.FileOutputStream.open0(Native Method) [ERROR] : TiFileProxy: at java.io.FileOutputStream.open(FileOutputStream.java:287) [ERROR] : TiFileProxy: at java.io.FileOutputStream.<init>(FileOutputStream.java:223) [ERROR] : TiFileProxy: at org.appcelerator.titanium.io.TiFile.getOutputStream(TiFile.java:304) [ERROR] : TiFileProxy: at org.appcelerator.titanium.io.TiFile.open(TiFile.java:368) [ERROR] : TiFileProxy: at org.appcelerator.titanium.io.TiFile.write(TiFile.java:414) [ERROR] : TiFileProxy: at org.appcelerator.titanium.TiFileProxy.write(TiFileProxy.java:331) [ERROR] : TiFileProxy: at org.appcelerator.kroll.runtime.v8.V8Object.nativeCallProperty(Native Method) [ERROR] : TiFileProxy: at org.appcelerator.kroll.runtime.v8.V8Object.callProperty(V8Object.java:75) [ERROR] : TiFileProxy: at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1208) [ERROR] : TiFileProxy: at android.os.Handler.dispatchMessage(Handler.java:101) [ERROR] : TiFileProxy: at android.os.Looper.loop(Looper.java:164) [ERROR] : TiFileProxy: at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:117) {code} h6.Note The strange problem is not happening to all model of devices. For example On Android 7 Seems all devices work well. At least, all the test devices are working well. On Android 8 Moto G device which is on android 8 worked fine. but others, like Google Pixel or Samsung Note 8, will get above error. h6.Example code {code} function testPDF() { var tempFile = Titanium.Filesystem.getFile(Titanium.Filesystem.isExternalStoragePresent() ? Titanium.Filesystem.externalStorageDirectory : Titanium.Filesystem.applicationDataDirectory, '/' + 'EDF Bill ' + e.source.text + '.pdf'); var appfilepath = tempFile.nativePath; var url = "http://www.mbta.com/uploadedfiles/Documents/Schedules_and_Maps/Rapid%20Transit%20w%20Key%20Bus.pdf"; var xhr = Ti.Network.createHTTPClient(); xhr.onload = function() { tempFile.write(this.responseData); try{ Ti.Android.currentActivity.startActivity(Ti.Android.createIntent({ action: Ti.Android.ACTION_VIEW, type: 'application/pdf', data: appfilepath })); } catch(e) { Ti.API.info('error trying to launch activity, e = '+e); alert('No PDF apps installed!'); } }; xhr.onerror = function() { alert("Cannot retrieve PDF from web site") ; }; xhr.timeout = 10000; xhr.open("GET", url); xhr.send(); } {code} Please check this asap, very important function for customer's app.
| 2 |
3,444 |
TIMOB-26495
|
10/10/2018 01:59:13
|
Cannot load iOS 12.0 simulator after upgrading to Xcode 10 and Ti SDK 7.4.0.GA
|
h3. Steps to Reproduce create a new project tap on run and watch it fail Error message in the console: [ERROR] : Simulator is not available h3. Actual Result [DEBUG] : Removing empty directories [INFO] : Invoking xcodebuild [DEBUG] : Invoking: DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild build -target 'Contractor WorkZone' -configuration Debug -scheme Contractor_WorkZone -derivedDataPath /Volumes/BOX/Projects/Titanium/WorkZone/build/iphone/DerivedData -UseNewBuildSystem=YES OBJROOT=/Volumes/BOX/Projects/Titanium/WorkZone/build/iphone/build/Intermediates SHARED_PRECOMPS_DIR=/Volumes/BOX/Projects/Titanium/WorkZone/build/iphone/build/Intermediates/PrecompiledHeaders SYMROOT=/Volumes/BOX/Projects/Titanium/WorkZone/build/iphone/build/Products -destination 'platform=iOS Simulator,id=DD7ADA2D-8D55-4275-A373-37FDE844367C,OS=12.0' ONLY_ACTIVE_ARCH=1 [INFO] : Finished building the application in 12s 747ms [INFO] : Launching iOS Simulator [ERROR] : Simulator is not available h3. Expected Result Simulator should boot up
| 1 |
3,445 |
TIMOB-26451
|
10/12/2018 01:56:43
|
Android: Hyperloop does not generate meta data for synchronized classes
|
- Metabase generator does not generate meta data for synchronized classes *TEST CASE* - Include https://www.dropbox.com/s/rax8o5m3mrgypns/libwebrtc_19324.aar?dl=1 into {{<project>/platforms/android}} directory {code:js} const EglBase14 = require('org.webrtc.EglBase14'); console.log(EglBase14); {code}
| 8 |
3,446 |
TIMOB-26477
|
10/12/2018 10:30:58
|
Ti.Locale.setLanguage is not applying the locale effects properly on Android & iOS
|
In Arabic mode, the locale should change the layout correctly like window-title to the right, home-up button on right as well. All RTL effects should be applied. However, using Ti.Locale the Arabic or RTL changes do not take place. If we use below code to apply Arabic language using Ti.Locale, the only changes that are taking place the Alert Dialog buttons are switched, but title, home-up button position, pickers are still unaffected, and it's incorrect behaviour as opposed to native Android app. *Full titanium code using Ti.Locale(not-working) and Hyperloop(working)* {code:java} var ios_nav; var indexWindow = Ti.UI.createWindow({ backgroundColor : 'white', title : 'Language Changes', layout : 'vertical' }); var btn1 = Ti.UI.createButton({ title : 'Set English using Ti.Locale', top : 10, width : Ti.UI.SIZE }); btn1.addEventListener('click', function () { Ti.Locale.setLanguage('en'); showAlert(); }); var btn2 = Ti.UI.createButton({ title : 'Set Arabic using Ti.Locale', top : 10, width : Ti.UI.SIZE }); btn2.addEventListener('click', function () { Ti.Locale.setLanguage('ar'); showAlert(); }); var btn3 = Ti.UI.createButton({ title : 'Set English using Hyperloop', top : 40, width : Ti.UI.SIZE }); btn3.addEventListener('click', function () { changeByHyperloop('en') }); var btn4 = Ti.UI.createButton({ title : 'Set Arabic using Hyperloop', top : 10, width : Ti.UI.SIZE }); btn4.addEventListener('click', function () {changeByHyperloop('ar') }); var btn5 = Ti.UI.createButton({ title : 'Open new Window to see changes', top : 50, width : Ti.UI.SIZE }); btn5.addEventListener('click', openNewWindow); indexWindow.add(btn1); indexWindow.add(btn2); indexWindow.add(btn3); indexWindow.add(btn4); indexWindow.add(btn5); if (OS_IOS) { ios_nav = Ti.UI.iOS.createNavigationWindow({ window : indexWindow }); ios_nav.open(); } else { indexWindow.open(); } function showAlert(e){ Ti.UI.createAlertDialog({ cancel : 1, buttonNames: ['RIGHT', 'LEFT'], message: 'App language is ' + (Ti.Locale.currentLanguage == 'en' ? 'English' : 'Arabic'), title: 'Dialog Title' }).show(); } function changeByHyperloop(language) { if (OS_ANDROID) { var Activity = require('android.app.Activity'); var Configuration = require('android.content.res.Configuration'); var Locale = require('java.util.Locale'); var activity = new Activity(Ti.Android.currentActivity); var myLocale = new Locale(language); Locale.setDefault(myLocale); var config = new Configuration(); config.locale = myLocale; // this doesn't work completely like moving scroll-bars and titles to right-edge. // seems Ti.Locale.setLanguage() also using Application-Context which doesn't work properly on layout-direction // var ctx = activity.getApplicationContext(); // this is working fine by applying all layout and directional changes properly var ctx = activity.getBaseContext(); ctx.getResources().updateConfiguration(config, ctx.getResources().getDisplayMetrics()); showAlert(); } else { alert('Hyperloop code not available on iOS. Please use Ti.Locale buttons to test language changes'); } } function openNewWindow() { var win = Ti.UI.createWindow({ backgroundColor : 'white', title : Ti.Locale.currentLanguage == 'en' ? 'English Language' : 'Arabic Language', layout : 'vertical' }); if (OS_IOS) { win.backButtonTitle = ''; win.add(Ti.UI.createLabel({ top : 20, left : 20, right : 20, textAlign : Ti.UI.TEXT_ALIGNMENT_CENTER, color : 'black', text : "New window opening transition animation is from right-to-left in English language.\n\nBut it should be left-to-right in Arabic language which it is not.\n\nAlso the back-arrow icon should be on different sides in both language.\n\nSo it's a bug on iOS also." })); } else { var picker = Ti.UI.createPicker({ left : 20, right : 20, top : 20 }); var data = []; data[0]=Ti.UI.createPickerRow({title:'Bananas'}); data[1]=Ti.UI.createPickerRow({title:'Strawberries'}); data[2]=Ti.UI.createPickerRow({title:'Mangos'}); data[3]=Ti.UI.createPickerRow({title:'Grapes'}); picker.add(data); win.add(picker); win.add(Ti.UI.createLabel({ top : 20, left : 20, right : 20, textAlign : Ti.UI.TEXT_ALIGNMENT_CENTER, color : 'black', text : 'Picker caret icon should be on right-side in English language and on left-side in Arabic language' })); win.addEventListener('open', function () { var actionBar = win.activity.actionBar; actionBar.displayHomeAsUp = true; actionBar.title = "Language Demo"; actionBar.onHomeIconItemSelected = function() { win.close(); }; }); } OS_IOS ? ios_nav.openWindow(win) : win.open(); } {code} The layout changes works all correctly ONLY using Hyperloop which replicates the native Android code. In this full sample code, using Ti.Locale, the alert-buttons are changing their positions, but title stays on left-edge in both Arabic and English language. But through Hyperloop or native Android, alert-title move to right-edge and so does the picker which is correct behaviour. After reviewing the Ti.Locale.setLanguage() method code, I was able to get only one hint that Ti SDK code is using application-context and my native Android or Hyperloop code works when using Activity's base-context. I do not know how to do this in iOS using Hyperloop, but I hope you get the issue.
| 3 |
3,447 |
TIMOB-26456
|
10/16/2018 20:27:11
|
Android: Optimize TiBlob.imageAsResized
|
I had a look at the implementation of TiBlob.imagesAsResized on Android and it could be optimized according to this stackoverflow article: https://stackoverflow.com/a/32121059/5193915 Rather than opening the image using {{getImage()}} and then creating a new Bitmap with {{createScaledBitmap()}} to resize it the rescaled image could be opened right away (with inTargetDensity + inDensity). In my test patch I've returned the {{getImage()}} Bitmap right away when rotation is 0. According to !ti_memory.png|thumbnail! it will save some memory. But I'm not 100% sure what {{mMemoryCache}} will do so I need some help/guidance if that is still needed. It was added in https://jira.appcelerator.org/browse/TIMOB-16450 to solve some memory leak. *Test code:* {code:java} _.delay(function() { Titanium.Media.showCamera({ success: function(e) { var start = new Date().getTime(); var blob = e.media; var w = e.media.width; var h = e.media.height; var r = h / w; w = 300; h = r * w; blob = blob.imageAsResized(w, h); $.img.image = blob; var end = new Date().getTime(); console.log(end - start); }, cancel: function() {}, error: function(error) {}, mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO] }); }, 4000); $.index.open(); {code} {code:java} <Alloy> <Window class="container"> <ImageView id="img"></ImageView> </Window> </Alloy> {code}
| 3 |
3,448 |
TIMOB-26455
|
10/16/2018 21:32:56
|
Android: Hyperloop should sanitize numeric names
|
- Hyperloop generator should sanitize numeric method names {code:js} var 1PackageInfoProxy = function() {...} {code}
| 3 |
3,449 |
TIMOB-26457
|
10/17/2018 02:02:10
|
Windows: Window.exitOnClose doesn't work when only one Window is opened
|
{{Window.exitOnClose}} works only when there are multiple Windows opened. It exits the app when there's only one Window opened. {code} var win = Ti.UI.createWindow({ exitOnClose: false, backgroundColor: 'green' }); win.addEventListener('open', function () { win.close(); }); win.open(); {code} Expected: It should not exit the app.
| 5 |
3,450 |
TIMOB-26459
|
10/18/2018 01:52:15
|
Android: Add support for translucent status bar and navigation bar
|
*Summary:* Add support for a translucent top status bar and translucent bottom navigation bar by adding the following constants that can be used by the {{Ti.UI.Window}} "windowFlags" property. * {{Ti.UI.Android.FLAG_TRANSLUCENT_NAVIGATION}} * {{Ti.UI.Android.FLAG_TRANSLUCENT_STATUS}} The above correspond to the following Android 4.4 Java constants... https://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#FLAG_TRANSLUCENT_NAVIGATION https://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#FLAG_TRANSLUCENT_STATUS *Example Usage:* {code:javascript} var window = Ti.UI.createWindow({ extendSafeArea: true, theme: "Theme.AppCompat.NoTitleBar", windowFlags: Ti.UI.Android.FLAG_TRANSLUCENT_STATUS | Ti.UI.Android.FLAG_TRANSLUCENT_NAVIGATION, backgroundColor: "white", borderWidth: "8dp", borderColor: "green", }); window.open(); {code} !AndroidTranslucentBars.png|thumbnail! *Note 1:* Internally, Titanium needs to support/apply these flags to allow *Android P* notches to overlap a fullscreen window. Otherwise the app window will be letterboxed between the notches. So, we might as well as expose the window flags constants for convenience... and they can be used on older Android OS versions (4.4 and higher). *Note 2:* Android 4.4 only supports a translucent navigation bar when the app is shown in portrait form. It is opaque when landscape. This is a limitation on Google's end. Android 5.0 and newer OS versions support a translucent nav bar for all orientations.
| 5 |
3,451 |
TIMOB-26460
|
10/18/2018 02:23:25
|
Android: Toolbar height set to Ti.UI.SIZE won't resize when changing orientation
|
*Summary:* Android Toolbars (and ActionBars) are supposed to use a height of {{56dp}} for portrait orientation and {{48dp}} for landscape. If a Toolbar's "height" is set to {{Ti.UI.SIZE}} (the default), then the height and its font size should automatically change when the orientation changes. It currently does *not*. *Steps to reproduce:* # Position an Android device in portrait. # Build and run the below code on that Android device. # Note the height of the top toolbar. # Rotate the device to landscape. # Notice that toolbar height does not shrink. _(This is the bug.)_ # Keep holding the device at landscape and back out of the app. # Launch the app in landscape form. # Notice that the toolbar height is smaller upon launch. # Rotate the device to portrait. # Notice that the toolbar height has not increased. _(This is the bug.)_ {code:javascript} var window = Ti.UI.createWindow({ theme: "Theme.AppCompat.NoTitleBar", }); var toolbar = Ti.UI.createToolbar({ title: "My Toolbar", top: 0, width: Ti.UI.FILL, height: Ti.UI.SIZE, }); window.activity.supportToolbar = toolbar; window.add(toolbar); window.open(); {code} *Cause:* The height is not changing because Titanium override the activity's "configChanges" for orientation in the "AndroidManifest.xml". This is needed to prevent the UI from being torn down upon orientation change. Google designed it to reload UI from XML, but since Titanium's UI is generated dynamically via code, this is not an option. We have to resize the height ourselves.
| 13 |
3,452 |
TIMOB-26479
|
10/18/2018 14:23:12
|
TiUtils.m missing check for iPhone XR and iPhone XS Max images
|
TiUtils.m missing check for iPhone XR and iPhone XS Max images So these devices will display the [email protected]/jpg instead of [email protected]/jpg [email protected]/jpg
| 3 |
3,453 |
TIMOB-26464
|
10/19/2018 00:56:08
|
Windows: Add Ti.UI.Window property "safeAreaPadding"
|
*Summary:* On Android and iOS, we're adding a new "safeAreaPadding" property to {{Ti.UI.Window}} which returns a Titanium [ViewPadding|https://docs.appcelerator.com/platform/latest/#!/api/ViewPadding] dictionary. This is really only relevant on Android and iOS because it's needed on devices which have camera notches which overlap the screen or when using a translucent StatusBar/NavigationBar. It reports the distance on each edge of the window where the insets/notches overlap the contents of the window. Please see: [TIMOB-26427] and [TIMOB-26461] On Windows, we should probably hard-code the padding to all zeros.
| 5 |
3,454 |
TIMOB-26466
|
10/19/2018 01:16:10
|
Make Alloy app runnable
|
Make default Alloy app runnable with crash.
| 8 |
3,455 |
TIMOB-26472
|
10/19/2018 09:29:04
|
Android: Replace support libraries with AndroidX
|
The Android "Support Libraries" have been deprecated by Google in favor of the AndroidX libraries. Google will no longer be making updates to the Support Libraries (v28 is their last version). New features will be going to AndroidX instead. https://developer.android.com/jetpack/androidx The Titanium SDK and its modules needs to migrate to the AndroidX libraries. Titanium's app builds will also need to leverage Google's "jetifier" tool which replaces prebuilt Android libraries, replaces their references from the Support libraries to AndroidX by hacking the binary (this is a Google sanctioned feature) so that 3rd party modules will be backward compatible. https://developer.android.com/jetpack/androidx/migrate AndroidX is best implemented in the app "build.gradle" file via... {code:groovy} android { useAndroidX true enableJetifier true } {code}
| 13 |
3,456 |
TIMOB-26481
|
10/23/2018 19:56:26
|
Android: Target API Level 28 (Android P) by default
|
*Summary:* When building for Android, Titanium should target API Level 28 (aka: Android 9.0) by default if installed under the Android SDK. Titanium currently targets up to API Level 27 (aka: Android 8.1). *Note:* Titanium currently does not target API Level 28 by default. This is a safety precaution until Titanium addresses all Android P breaking changes. But a developer can opt-in to targeting the newest API Level (at their own risk) by adding the following to their "tiapp.xml" file. {code:javascript} <ti:app> <android xmlns:android="http://schemas.android.com/apk/res/android"> <manifest> <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="28"/> </manifest> </android> </ti:app> {code}
| 1 |
3,457 |
TIMOB-26484
|
10/25/2018 02:49:10
|
Android: Add "sound" support to NotificationChannel
|
*Summary:* Android 8.0 and newer OS versions ignore the "sound" property assigned to individual notifications. The only way to play custom notification sounds is to assign the sound to a {{NotificationChannel}} instead. See sample code [^NotificationSoundTest.js] for an example on how this would work. Note that you must assign the custom sound to both the {{Notification}} (for Android 7.1 and below) and the {{NotificationChannel}} (for Android 8.0 and above). It's a bummer that you have to assign it to both, but that's the only solution if you want to support customer sound on OS versions older than Android 8.0.
| 5 |
3,458 |
TIMOB-26485
|
10/25/2018 08:21:46
|
Android: Local database provides error in Alloy
|
Trying to install a local database(dumped form SQlite Manager) on Android using *Titanium.Database.Install()* and it provides error. *Testing Environment:* Appcelerator Command-Line Interface, version 7.0.6,Operating System Mac OS X 10.13.6, Node.js Version 8.9.1 SDK Version 7.4.1.GA,Device: Huawei GR3 (Android 7) *Test Steps:* 1. Create an alloy app 2.Paste the sample code to app directory and sample database to app->lib directory(sample db file is attached) 2. Run the project , click the label and check console *Test Code:* *index.js* {code} function doClick(e) { var db = Ti.Database.install('/lib/db', 'db'); var db = Ti.Database.open('db'); var importName='def'; var imporCaptured='567'; db.execute('INSERT INTO info (name,captured) VALUES (?,?)', importName, imporCaptured); var cityWeatherRS = db.execute('SELECT id,name,captured FROM info'); while (cityWeatherRS.isValidRow()) { var cityId = cityWeatherRS.fieldByName('id'); var cityName = cityWeatherRS.fieldByName('name'); var citycaptured = cityWeatherRS.fieldByName('captured'); Ti.API.info(cityId + ' ' + cityName + ' ' + citycaptured); cityWeatherRS.next(); } db.close(); } $.index.open(); {code} *index.xml* {code} <Alloy> <Window class="container"> <Label id="label" onClick="doClick">Hello, World</Label> </Window> </Alloy> {code} *Test output:* {code} [ERROR] : TiDB: (main) [7582,7583] Error executing sql: no such table: info (Sqlite code 1): , while compiling: INSERT INTO info (name,captured) VALUES (?,?), (OS error - 2:No such file or directory) [ERROR] : TiDB: android.database.sqlite.SQLiteException: no such table: info (Sqlite code 1): , while compiling: INSERT INTO info (name,captured) VALUES (?,?), (OS error - 2:No such file or directory) [ERROR] : TiDB: at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method) [ERROR] : TiDB: at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:910) [ERROR] : TiDB: at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:521) [ERROR] : TiDB: at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:603) [ERROR] : TiDB: at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:63) [ERROR] : TiDB: at android.database.sqlite.SQLiteStatement.<init>(SQLiteStatement.java:31) [ERROR] : TiDB: at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1965) [ERROR] : TiDB: at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1941) [ERROR] : TiDB: at ti.modules.titanium.database.TiDatabaseProxy.execute(TiDatabaseProxy.java:142) [ERROR] : TiDB: at org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method) [ERROR] : TiDB: at org.appcelerator.kroll.runtime.v8.V8Object.fireEvent(V8Object.java:63) [ERROR] : TiDB: at org.appcelerator.kroll.KrollProxy.doFireEvent(KrollProxy.java:969) [ERROR] : TiDB: at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1194) [ERROR] : TiDB: at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:394) [ERROR] : TiDB: at android.os.Handler.dispatchMessage(Handler.java:101) [ERROR] : TiDB: at android.os.Looper.loop(Looper.java:156) [ERROR] : TiDB: at android.app.ActivityThread.main(ActivityThread.java:6523) [ERROR] : TiDB: at java.lang.reflect.Method.invoke(Native Method) [ERROR] : TiDB: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:942) [ERROR] : TiDB: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:832) [ERROR] : TiExceptionHandler: (main) [4,7587] /alloy/controllers/index.js:59 [ERROR] : TiExceptionHandler: db.execute('INSERT INTO info (name,captured) VALUES (?,?)', importName, imporCaptured); [ERROR] : TiExceptionHandler: ^ [ERROR] : TiExceptionHandler: Error: no such table: info (Sqlite code 1): , while compiling: INSERT INTO info (name,captured) VALUES (?,?), (OS error - 2:No such file or directory) [ERROR] : TiExceptionHandler: at Label.doClick (/alloy/controllers/index.js:59:6) [ERROR] : TiExceptionHandler: at Label.value (ti:/events.js:49:21) [ERROR] : TiExceptionHandler: at Label.value (ti:/events.js:101:19) [ERROR] : TiExceptionHandler: [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:910) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:521) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:603) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:63) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteStatement.<init>(SQLiteStatement.java:31) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1965) [ERROR] : TiExceptionHandler: android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1941) [ERROR] : TiExceptionHandler: ti.modules.titanium.database.TiDatabaseProxy.execute(TiDatabaseProxy.java:142) [ERROR] : TiExceptionHandler: org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method) [INFO] : HwPointEventFilter: do not support AFT because of no config [ERROR] : V8Exception: Exception occurred at /alloy/controllers/index {code}
| 3 |
3,459 |
TIMOB-26496
|
10/29/2018 19:03:55
|
Android: Exception message not displaying for Java runtime exceptions
|
- Java exceptions do not display the exception message, only the stack
| 2 |
3,460 |
TIMOB-26498
|
10/30/2018 07:06:26
|
Windows: ListView item template support CommonJS modules and Alloy widgets
|
The ListView item template only supports a limited set of view classes from the Ti.UI namespace. In addition to using one of the predefined view classes, you should be able to also pass module views to your list item template. For example, use {{ImageView}} on {{AvImageview}} module in your list view: {code} <ListView id="Images" defaultItemTemplate="template"> <Templates> <ItemTemplate name="template" height="160"> <ImageView ns="AvImageview" bindId="photo" height="160" width="Ti.UI.FILL" /> </ItemTemplate> </Templates> <ListSection> <ListItem template="template" photo:image="http://www.nationalgeographic.com/content/dam/photography/photos/000/060/6018.ngsversion.1467254523217.adapt.1900.1.jpg"></ListItem> <ListItem template="template" photo:image="http://www.italiangoodnews.com/wp-content/uploads/2014/11/italy-04.jpg"></ListItem> </ListSection> </ListView> {code} where {{<ImageView ns="AvImageview">}} will be expanded into {{type: 'AvImageview.ImageView'}} in ListView ItemTemplate. In this case ListView should call {{AxImageview.createImageView}} behind the scenes eventually. We also need support for Alloy {{Widget}} tag like below. {code} <ListView id="listView" defaultItemTemplate="template"> <Templates> <ItemTemplate name="template"> <Widget src="test.widget" bindId="testWidget" id="testWidget"/> </ItemTemplate> </Templates> <ListSection headerTitle="WIDGETS"> <ListItem testWidget:backgroundColor="red" /> <ListItem testWidget:backgroundColor="blue" /> <ListItem testWidget:backgroundColor="orange" /> </ListSection> </ListView> {code} In this case {{<Widget src="test.widget">}} will be expanded into {{type: 'test.widget'}} in ListView ItemTemplate. In this case ListView should create Alloy widget {{test.widget}} behind the scenes eventually. So, ListView should search template class in following order: # If there's a class in global namespace such as {{Ti.UI.View}}, use {{\[namespace\].create\[Classname\]}} function such as {{Ti.UI.createView}}. # If there's a CommonJS module with given name, {{require}} it and then use its {{getView}} function. # If there's a Alloy widget with given name, {{require}} {{Resources/windows/alloy/widgets/WIDGET_NAME/controllers/widget.js}} and then use its {{getView}} function
| 13 |
3,461 |
TIMOB-26503
|
10/31/2018 02:25:59
|
Windows: Touch event coordinate units do not match between platforms
|
*Summary:* The (x,y) units provided by View event's "touchstart", "touchmove", "touchend", and "touchcancel" do not match between Android and iOS. Both platforms ignore the "ti.ui.defaultunit" property setting in "tiapp.xml". On Android, the touch coordinates are always in "px" (ie: pixels). On iOS, the touch coordinates are always in "dip" (aka: "dp"). *Steps to Reproduce:* # Build and run the below code on Android. # Drag your finger in the gray view. # Notice that the blue square does *not* correctly following your finger. # Build and run on iOS. # Drag your finger in the gray view. # Notice that the blue square *correctly* follows your finger. # Change "tiapp.xml" property "ti.ui.defaultunit" to "px". # Build and run on iOS. # Drag your finger in the gray view. # Notice that the blue square does *not* correctly following your finger. # Build and run on Android. # Drag your finger in the gray view. # Notice that the blue square *correctly* follows your finger. {code:javascript} function onTouch(event) { touchView.center = { x: event.x, y: event.y }; } var window = Ti.UI.createWindow( { layout: "vertical", fullscreen: true, }); window.add(Ti.UI.createLabel( { text: "Touch Drag Test", top: "20dp", })); var containerView = Ti.UI.createView( { touchEnabled: true, backgroundColor: "gray", top: "10dp", bottom: "20dp", width: "90%", }); var touchView = Ti.UI.createView( { touchEnabled: false, backgroundColor: "#008800", width: "100dp", height: "100dp", }); containerView.add(touchView); containerView.addEventListener("touchstart", onTouch); containerView.addEventListener("touchmove", onTouch); containerView.addEventListener("touchend", onTouch); containerView.addEventListener("touchcancel", onTouch); window.add(containerView); window.open(); {code} *Work-Around:* The following will work-around this issue on both Android and iOS... {code:javascript} // Fetch the default unit property set in "tiapp.xml". var defaultUnit = Ti.App.Properties.getString("ti.ui.defaultunit", "dip"); if (defaultUnit === "dp") { defaultUnit = "dip"; } else if (defaultUnit === "system") { defaultUnit = (Ti.Platform.name === "android") ? "px" : "dip"; } // Do the below when a touch event has been received. function onTouch(event) { if (Ti.Platform.name === "android") { event.x = Ti.UI.convertUnits(event.x + "px", defaultUnit); event.y = Ti.UI.convertUnits(event.y + "px", defaultUnit); } else if ((Ti.Platform.name === "iOS") || (Ti.Platform.name === "iPhone OS")) { event.x = Ti.UI.convertUnits(event.x + "dip", defaultUnit); event.y = Ti.UI.convertUnits(event.y + "dip", defaultUnit); } touchView.center = { x: event.x, y: event.y }; } {code} *Ideal Solution:* Convert native touch coordinates to use "ti.ui.defaultunit" on both Android and iOS. This way views can easily be dragged since their "x", "y", and "center" properties already respect the "ti.ui.defaultunit" property. Note that this would be a breaking change.
| 8 |
3,462 |
TIMOB-26506
|
10/31/2018 21:34:45
|
Android: Validate TiUIAbstract getWindowProxy()
|
- {{Titanium.UI.AbstractTab}} {{getWindowProxy}} does not validate if the proxy exists - Causes test failures https://jenkins.appcelerator.org/job/titanium-sdk/job/titanium_mobile/job/PR-10405/24/console
| 1 |
3,463 |
TIMOB-26507
|
11/01/2018 03:52:32
|
Windows: View.center is not respected when left & top is set.
|
{{center}} property is not respected when {{left}} and {{top}} is set. Even when these properties are already set, {{center}} should be respected and update the position of the view. Also, we should be able to use {{undefined}} to "clear" existing values according to [UNDEFINED behavior|https://docs.appcelerator.com/platform/latest/#!/guide/UI_Composite_Layout_Behavior_Spec-section-src-4196675_UICompositeLayoutBehaviorSpec-UNDEFINEDbehavior] which is taken care by TIMOB-26507. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green' }); var view1 = Ti.UI.createView({ width: 100, height: 100, top: 100, left: 100, backgroundColor: 'blue', }); win.addEventListener('click', function (e) { // view1.top = undefined; // view1.left = undefined; view1.center = { x: e.x, y:e.y }; }); win.add(view1); win.open(); {code} Expected: View should move to the position where you clicked.
| 8 |
3,464 |
TIMOB-26508
|
11/01/2018 08:52:47
|
Windows: Setting undefined should clear layout value
|
Setting {{undefined}} to layout property should "clear" layout value. For instance, Setting both {{left}} and {{top}} disables {{center}} property (TIMOB-26507) but we should be able to enable {{center}} property again by setting {{undefined}} for {{left}} and {{top}} properties. {code} var win = Ti.UI.createWindow(); var view1 = Ti.UI.createView({ width: 100, height: 100, top: 100, left: 100, backgroundColor: 'blue', }); win.addEventListener('click', function (e) { view1.top = undefined; view1.left = undefined; view1.center = { x: e.x, y:e.y }; }); win.add(view1); win.open(); {code} Expected: The blue view should move to where you click.
| 5 |
3,465 |
TIMOB-26510
|
11/01/2018 15:07:47
|
Windows: "Runtime Exception: Layout cycle detected." when launching kitchensink-v2
|
h5.Description When launching ks-v2 I'm seeing {{"Runtime Exception: Layout cycle detected." }} when the app launches. Tracking the issue down it appears to be coming from the {{$.log.setText}} call [here|https://github.com/appcelerator/kitchensink-v2/blob/27e44b5635f6ca2abf83f9e76cc9f0044a56795f/app/controllers/console/index.js#L11]. * Commenting out the setText call allows the app to open fine (/) * Placing the {{setText}} call in a setTimeout fixes the issue (/) * Replacing {{logger.history}} with 'astring' does not fix the issue (x) My best guess right now is that there's some issue around updating the label text while we're laying out the UI? h5.Steps to reproduce 1. Run kitchensink-v2 h5.Actual App will error out on launch h5.Expected App should not error out on launch
| 8 |
3,466 |
TIMOB-26513
|
11/02/2018 19:02:45
|
iOS: Push notifications crash the app when used with third-party module
|
Using third-party modules to integrate remote notifications may crash an app due to unsafe calls to {{application:didReceiveRemoteNotification:}}. This method is only available when {{Ti.Network.registerForPushNotifications}} was used.
| 3 |
3,467 |
TIMOB-26516
|
11/03/2018 10:42:59
|
Android: Ti.Platform "id" and "version" properties return null if analytics disabled as of 7.5.0.RC
|
*Summary:* Properties {{Ti.Platform.id}} and {{Ti.Platform.version}} return {{null}} if analytics have been disabled in the "tiapp.xml" file. They return the correct values if analytics is enabled. This bug was introduced as of 7.5.0.RC. *Steps to reproduce:* # Set up a Classic app with the "app.js" code shown below. # In the "tiapp.xml" file, disabled analytics as shown below. # Build and run on an Android device. # In the log, notice that "id" and "version" return {{null}}. _(This is the bug.)_ *tiapp.xml* {code:xml} <ti:app xmlns:ti="http://ti.appcelerator.org"> <analytics>false</analytics> </ti:app> {code} *app.js* {code:javascript} Ti.API.info("@@@ Ti.Platform.id: " + Ti.Platform.id); Ti.API.info("@@@ Ti.Platform.version: " + Ti.Platform.version); {code} *Note:* I suspect APIs {{Ti.Geolocation.forwardGeocoder()}} and {{Ti.Geolocation.reverseGeocoder()}} might also fail if analytics is disabled.
| 2 |
3,468 |
TIMOB-26517
|
11/05/2018 10:39:59
|
CLI: Add link to implicit global warning log
|
h5.Description The warning log had a link created to explain it, we should link to the doc.appc page (via shortlink) so that there's less confusion around the message
| 1 |
3,469 |
TIMOB-26518
|
11/05/2018 12:40:30
|
Android: Webview FireEvent not get fired in correct sequence
|
Hi team, For Android Platform, I have added "evenlistener" in webview local html file. The event is fired from app.js. The issue is, fireEvent get fired in reverse order for Android. For iOS, the sequence is right and for Android, the sequence is wrong. App.js {code} var win = Ti.UI.createWindow({ }); var webView = Ti.UI.createWebView({ visible : false, url : 'index.html' }); win.add(webView); webView = null; win.open(); setTimeout(function() { for (var i = 0; i < 5; i++) { var data = { value : i }; Ti.API.info("value passed:" + i); Ti.App.fireEvent('testevent', data); } }, 5000); {code} index.html {code:html} <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> </head> <body> <script type="text/javascript"> function passdatatoserver(e) { Ti.API.info("testevent:" + e.value); } Ti.App.addEventListener('testevent', passdatatoserver); </script> </body> </html> {code} Log for adroid: {code} [INFO] : value passed:0 [INFO] : value passed:1 [INFO] : value passed:2 [INFO] : value passed:3 [INFO] : value passed:4 [WARN] : TiVerify: (Timer-0) [4992,4993] Verifying module licenses... [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):Reading from variable values from setDefaultValuesToVariables [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):isSBSettingEnabled false [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):isShipBuild true [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):getDebugLevel 0x4f4c [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):Smart Bonding Setting is false [INFO] : I/System.out: Thread-63102(ApacheHTTPLog):SmartBonding Setting is false, SHIP_BUILD is true, log to file is false, DBG is false, DEBUG_LEVEL (1-LOW, 2-MID, 3-HIGH) is 1 [INFO] : I/System.out: Timer-0 calls detatch() [INFO] : TiVerify: (Timer-0) [838,5831] Succesfully verified module licenses [INFO] : testevent:4 [INFO] : testevent:3 [INFO] : testevent:2 [INFO] : testevent:1 [INFO] : testevent:0 {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 = 7.4.1.GA {code}
| 3 |
3,470 |
TIMOB-26521
|
11/05/2018 19:37:16
|
iOS: The popover UI has shrunk and also lines are not visible in between few rows on iPad
|
Issue :-1 * Issue description - The popover UI has shrunk and also lines are not visible in between few rows * Screen shot showing the issue – PFA Issue_1.png and Issue_1_screenshot.png * Sample app code – PFA Sample_APP.zip Issue :-2 * Issue description - On searching an item in search bar and selecting a row the, popover stays with blank white background instead of disappearing * Screen shot showing the issue – PFA Issue_2.png * Sample app code – PFA Sample_APP.zip
| 8 |
3,471 |
TIMOB-26523
|
11/06/2018 11:41:51
|
iOS 11+: Support large title style (dynamic fonts)
|
Titanium is pretty well suited regarding dynamic fonts, which becomes more and more important in larger scale applications. We need one more style which is currently missing ({{UIFontTextStyleLargeTitle}}) which will complete the dynamic font support. Note: Until the below PR is merged, the following enum raw value will allow to use it today: {code} font: { textStyle: 'UICTFontTextStyleTitle0' // Raw value of UIFontTextStyleLargeTitle } {code}
| 3 |
3,472 |
TIMOB-26524
|
11/07/2018 01:59:42
|
Windows: Can not compile folder with spaces
|
Latest [titanium-mobile-mocha-suite|https://github.com/appcelerator/titanium-mobile-mocha-suite/tree/master/Resources/folder%20with%20spaces] shows that Titanium project that contains folder with spaces does not compile. How to reproduce: * Create folder with spaces (i.e. "{{folder with spaces}}") under {{Resources}} folder. Building the project errors out with CMake Error: {code} [WARN] CMake Error at CMakeLists.txt:263 (set_property): Syntax error in cmake code at titanium/vsbuild/mocha-suite/CMakeLists.txt:263 when parsing string ${SOURCE_folder syntax error, unexpected $end, expecting } (15) [DEBUG] -- Configuring incomplete, errors occurred! {code} Expected: It should compile without errors.
| 5 |
3,473 |
TIMOB-26525
|
11/07/2018 07:07:42
|
Windows: ScrollView does not expand with Ti.UI.SIZE
|
{{ScrollView}} does not expand its size along with child content when {{Ti.UI.SIZE}} is specified. {code} var scrollView = Ti.UI.createScrollView({ height: Ti.UI.SIZE, width: Ti.UI.SIZE, scrollType: 'vertical', layout: 'vertical', backgroundColor: 'red' }); var view1 = Ti.UI.createView({ width: '100', height: '50', backgroundColor: 'pink' }); var view2 = Ti.UI.createView({ width: '200', height: '100', backgroundColor: 'green' }); scrollView.add(view1); scrollView.add(view2); var win = Ti.UI.createWindow({ backgroundColor: 'white', }); win.add(scrollView); win.open(); {code} Expected: !1.png|thumbnail!
| 5 |
3,474 |
TIMOB-26529
|
11/07/2018 17:33:21
|
Android: Amend Ti.Platform properties
|
- Amend {{Ti.Platform}} properties: {code:js} Ti.Platform.getName(); Ti.Platform.getOsname(); Ti.Platform.getVersion(); Ti.Platform.getOstype(); {code}
| 2 |
3,475 |
TIMOB-26533
|
11/08/2018 15:16:19
|
iOS: Ti.Media.Audio player without url set is crashing while registering for event listener
|
The application throws an error when using the following test case: {code:java} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var debug = Ti.API.debug; var info = Ti.API.info; Ti.Media.audioSessionMode = Ti.Media.AUDIO_SESSION_MODE_PLAYBACK; var url = Titanium.UI.createTextField({ value : 'http://users.skynet.be/fa046054/home/P22/track06.mp3', color : '#336699', returnKeyType : Titanium.UI.RETURNKEY_GO, keyboardType : Titanium.UI.KEYBOARD_URL, hintText : 'url', textAlign : 'left', height : 35, top : 10, width : 300, borderStyle : Titanium.UI.INPUT_BORDERSTYLE_ROUNDED }); var streamButton = Titanium.UI.createButton({ title : 'Start Streaming', top : 60, width : 200, height : 40 }); var pauseButton = Titanium.UI.createButton({ title : 'Pause Streaming', top : 110, width : 200, height : 40, enabled : false }); var progressLabel = Titanium.UI.createLabel({ text : 'Time Played: Not Started', top : 160, left : 10, height : 40, width : 300, color : '#555', textAlignment : 'center' }); var stateLabel = Titanium.UI.createLabel({ text : 'State: Not Started', top : 180, left : 10, width : 300, height : 40, color : '#555' }); win.add(url); win.add(streamButton); win.add(pauseButton); win.add(progressLabel); win.add(stateLabel); var streamer = Ti.Media.createAudioPlayer(); streamButton.addEventListener('click', function() { if (streamButton.title == 'Stop Stream') { progressLabel.text = 'Stopped'; streamer.stop(); pauseButton.enabled = false; pauseButton.title = 'Pause Streaming'; streamButton.title = "Start Streaming"; } else { progressLabel.text = 'Starting ...'; streamer.url = url.value; streamer.start(); pauseButton.enabled = true; pauseButton.title = 'Pause Streaming'; streamButton.title = "Stop Stream"; } }); pauseButton.addEventListener('click', function() { if (pauseButton.title == 'Pause Streaming') { streamer.pause(); pauseButton.title = 'Unpause Streaming'; } else { streamer.start(); pauseButton.title = 'Pause Streaming'; } }); streamer.addEventListener('change', function(e) { stateLabel.text = 'State: ' + e.description + ' (' + e.state + ')'; Ti.API.info('disc: ' + e.description); Ti.API.info('state: ' + e.state); }); streamer.addEventListener('progress', function(e) { progressLabel.text = 'Time Played: ' + Math.round(e.progress) + ' seconds'; }); // save off current idle timer state var idleTimer = Ti.App.idleTimerDisabled; // while we're in this window don't let the app shutdown // when the screen is idle Ti.App.idleTimerDisabled = true; win.addEventListener('close', function() { Ti.API.info("window was closed, idleTimer reset to = " + idleTimer); // restore previous idle state when closed Ti.App.idleTimerDisabled = idleTimer; }); win.open(); {code} Following error is shown: {code:java} [ERROR] : Script Error { [ERROR] : column = 26; [ERROR] : line = 97; [ERROR] : message = "Invalid URL passed to the audio-player"; [ERROR] : nativeLocation = "-[TiMediaAudioPlayerProxy player] (TiMediaAudioPlayerProxy.m:76)"; [ERROR] : nativeReason = "The \"url\" probably has not been set to a valid value."; [ERROR] : nativeStack = "3 T3 0x00000001011081e8 T3 + 508392\n4 T3 0x000000010110c000 T3 + 524288\n5 T3 0x000000010110b988 T3 + 522632\n6 T3 0x0000000101106b78 T3 + 502648\n7 CoreFoundation 0x0000000185a35630 <redacted> + 144\n8 CoreFoundation 0x0000000185913560 <redacted> + 292\n9 T3 0x00000001010ad8e8 T3 + 137448\n10 T3 0x00000001010abfcc T3 + 131020\n11 T3 0x0000000101128c1c T3 + 642076\n12 T3 0x00000001010abcec T3 + 130284\n13 JavaScriptCore 0x000000018d656b58 <redacted> + 348\n14 JavaScriptCore 0x000000018dd40f5c <redacted> + 352\n15 JavaScriptCore 0x000000018d62ddd8 <redacted> + 29992\n16 JavaScriptCore 0x000000018d62ddec <redacted> + 30012\n17 JavaScriptCore 0x000000018d6266b4 <redacted> + 308\n18 JavaScriptCore 0x000000018dc9cda0 <redacted> + 9620\n19 JavaScriptCore 0x000000018de77ecc _ZN3JSC8evaluateEPNS_9ExecStateERKNS_10SourceCodeENS_7JSValueERN3WTF8NakedPtrINS_9ExceptionEEE + 320"; [ERROR] : sourceURL = "file:///var/containers/Bundle/Application/977A5AE0-84DB-4956-B8B5-79A219E25A27/T3.app/app.js"; [ERROR] : stack = " at [native code]\n at (/app.js:97:26)\n at global code(/app.js:116:70)\n at require@[native code]\n at (/ti.main.js:27:8)\n at loadAsync(/ti.internal/bootstrap.loader.js:148:186)\n at global code(/ti.main.js:24:52)"; [ERROR] : toJSON = "<KrollCallback: 0x281918ac0>"; [ERROR] : } [ERROR] : Script Error Module "app.js" failed to leave a valid exports object {code} Note this worked on 7.4.1.GA and looks like a regression. *Expected result* Application should not crash and stream should work accordingly. (If stream is paused/played) *Actual result * Application crashes on launch
| 5 |
3,476 |
TIMOB-26534
|
11/08/2018 19:23:21
|
Android: Modify native HTTP handling to only cache "GET" responses
|
*Summary:* Titanium's custom {{TiResponseCache.java}} class currently caches all HTTP responses and ignores the HTTP method. Meaning that it'll cache "POST", "PUT", "DELET", etc. which is a problem when using REST web APIs. It should be changed to only cache HTTP "GET" responses. _(Note: iOS does not cache "HEAD" responses.)_ *Note:* This is not an issue with Titanium's {{Ti.Network.HTTPClient}} on Android since it's currently set up to *never* cache responses. The only Titanium JavaScript API which does HTTP response caching is when you load images via URLs, which are "GET" requests. The above is only an issue for app's which do HTTP requests natively in Java, such as via a 3rd party native library.
| 3 |
3,477 |
TIMOB-26535
|
11/08/2018 22:16:24
|
Android: Fix analytics session events
|
- {{ti.foreground}} and {{ti.background}} events are being sent on every Activity {{onPause}} and {{onResume}}. This means every new window is classed as a new session, which is incorrect. - The events need to be tied to the application lifecycle and not each activity lifecycle *TEST CASE* {code:js} const win = Ti.UI.createWindow({ backgroundColor: 'blue' }), btn = Ti.UI.createButton({ title: 'OPEN' }); btn.addEventListener('click', () => { // this should not create a new session (not send ti.foreground) Ti.UI.createWindow({ backgroundColor: 'red' }).open(); }); win.add(btn); win.open(); {code}
| 5 |
3,478 |
TIMOB-26539
|
11/09/2018 04:02:33
|
Android: Label's default font size should be "dp" unless explicitly set
|
*Summary:* Android's {{Ti.UI.Label}} is currently hard-coded to a font size of {{15}} using the "tiapp.xml" property's "ti.ui.defaultunit". The problem with this is if you set the default unit to pixels (ie: {{px}}), then the label will default to "15px" and be too small to read on high DPI devices. The label's default font size should be hard-coded to "dp". We don't have this issue with any of our other UI features such as {{Button}}, {{TextField}}, {{Picker}}, etc. All other UI elements use "dp" by default. Only our Android {{Label}} has this problem. iOS does not have this problem. *Steps to reproduce:* # Create a Titanium classic app. # Set up the "tiapp.xml" file's default unit to "px" (pixels) as shown below. # Use the "app.js" below. # Build and run on an Android device that is xxhdpi or higher. # Notice that the text is very tiny. _(This is the bug.)_ tiapp.xml {code:xml} <ti:app xmlns:ti="http://ti.appcelerator.org"> <property name="ti.ui.defaultunit" type="string">px</property> </ti:app> {code} app.js {code:javascript} var window = Ti.UI.createWindow(); window.add(Ti.UI.createLabel({ text: "Hello World" })); window.open(); {code} *Android Results:* !Android-dp.png|thumbnail! !Android-px.png|thumbnail! *iOS Results:* !ios-dp.png|thumbnail! !ios-px.png|thumbnail!
| 1 |
3,479 |
TIMOB-26540
|
11/09/2018 17:16:25
|
Windows: When using html in webView application closes
|
When using the following test case the application crashes on Windows without throwing an error. (Works fine on Android and works fines on windows using 7.4.1.GA): {code:java} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var webView = Titanium.UI.createWebView({ html: '<select name="selectBox"><option value="val1">Value 1</option><option value="val2">Value 2</option><option value="val3">Value 3</option></select>' }); webView.setBasicAuthentication('user', 'pass'); win.add(webView); win.open(); {code} *Expected result* Application should show a selectBox. *Actual result* Application crashes without showing an error
| 5 |
3,480 |
TIMOB-26545
|
11/10/2018 20:19:20
|
Android: Using global L() method for localization does not work if second argument is not supplied
|
If the {{L}} method does not receive a second parameter, the fallback string is not displayed if not supplied as a second argument. This works fine on iOS. Example: {code:js} // Works L('Hello world', 'Hello world'); // Does not work on Android, works on iOS L('Hello world'); {code} This triggered TIMOB-26544 and is kind of a blocker for us. *Update*: We now implemented a workaround using the ti.shell feature (in a {{L.bootstrap.js}}): {code:js} global.Lx = (value, comment) => { return L(value, comment || value); }; {code}
| 8 |
3,481 |
TIMOB-26549
|
11/13/2018 12:03:35
|
Windows: HTTPClient: Invalid Status Codes returned
|
GET request should be returning a status of "301" or "302"; instead returns a status code of "200" *Test case* {code:java} var xhr = Titanium.Network.createHTTPClient(); xhr.autoRedirect = false; xhr.allResponseHeaders = true; // what to do if it loads xhr.onload = function(e) { Ti.API.log('Status = ' + this.getStatus()); if (this.getStatus() == 301) { Ti.API.log('Redirect to ' + this.getResponseHeader('location')); } else { Ti.API.log('This should have returned a 301 not a 200'); } }; xhr.open('GET', 'http://google.co.nz'); xhr.send(); {code} *Actual result:* Following is returned: {code:java} [INFO] Status = 200 [INFO] This should have returned a 301 not a 200 {code} *Expected result:* Following should be returned: {code:java} [INFO] : Status = 301 [INFO] : Redirect to http://www.google.co.nz/ {code}
| 5 |
3,482 |
TIMOB-26550
|
11/13/2018 13:02:30
|
Windows: Add support for file property to HTTPClient
|
*Test case:* {code:java} function createButton(title, filename, url) { var b = Ti.UI.createButton({ title : title }); b.addEventListener("click", function() { var xhr = Titanium.Network.createHTTPClient(); if (filename != null) { xhr.file = filename; } xhr.onload = function() { var responseFilePath = this.responseData.nativePath; alert("responseData.nativePath = " + responseFilePath); if (responseFilePath != null) { imageView.image = responseFilePath; } else { imageView.image = this.responseData; } }; xhr.open('GET', url); xhr.send(); }); return b; } var win = Titanium.UI.createWindow({ title: "The 'file' property for HTTPClient", layout: "vertical" }); var imageView = Titanium.UI.createImageView({ top : 5, height : 200, width : 300 }); win.add(createButton("Not setting 'file' (download a small image)", null, "http://developer.appcelerator.com/blog/wp-content/themes/newapp/images/appcelerator_avatar.png?s=48")); win.add(createButton("Not setting 'file' (download a large image)", null, "http://2.bp.blogspot.com/-z-cZ7JirojQ/Tc8OMAAqbLI/AAAAAAAAAfc/slhGE764cyY/s1600/Cars+2.jpg")); win.add(createButton("'file' is in tempDirectory", Ti.Filesystem.tempDirectory + "/sky.jpg", "http://www.forestwander.com/wp-content/original/2009_01/Sky-View.JPG")); win.add(createButton("'file' is in applicationDataDirectory", Ti.Filesystem.applicationDataDirectory + "/flower.jpg", "http://flowerdeliverygo.com/wp-content/uploads/2014/05/flower-delivery.jpg")); win.add(createButton("'file' is in externalStorageDirectory", Ti.Filesystem.externalStorageDirectory + "/fruit.jpg", "http://southernbite.com/wp-content/uploads/2012/05/SouthernBiteFruitSalad-2.jpg")); win.add(imageView); win.open(); {code} Null should only be shown for the first two buttons but it shown for all buttons unlike on Android.
| 5 |
3,483 |
TIMOB-26551
|
11/13/2018 13:19:02
|
iOS: "Cannot read property 'code' of undefined" error thrown if log server connection times out
|
h5.Description When checking the log server connection in the iOS build if the check times out then the following error is thrown. I'm unsure as to the actual reasons for why I ran into this, but you can easily reproduce by reducing the logserver wait time {code} /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/8.0.0.v20181109074008/iphone/cli/commands/_build.js:2506 if (error.code === 'ENOTFOUND') { ^ TypeError: Cannot read property 'code' of undefined at Socket.die (/Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/8.0.0.v20181109074008/iphone/cli/commands/_build.js:2506:15) {code} h5.Steps to reproduce 1. Reduce the logserver wait time using {{appc ti config ios.logServerTestTimeout 1}} 2. Build an iOS app for simulator or device h5.Actual Error thrown like the above h5.Expected Error thrown should inform the user the real reason it errored
| 1 |
3,484 |
TIMOB-26558
|
11/14/2018 10:47:54
|
iOS: Ti.Media.takeScreenshot is not working
|
Ti.Media.takeScreenshot is not working working properly on iOS. On android, clicking on button its takes a screenshot, saved it to the gallery and displayed it to imageview properly. But on ios we are not getting the same behaviour. *Test Code:* {code} var win = Ti.UI.createWindow({ layout: "vertical", backgroundColor: "green" }); var button = Ti.UI.createButton({ title: "Take Pic", top: 20, width: 200, height: 200 }); win.add(button); var imageView = Ti.UI.createImageView({ width: "100", height: "100", top: 20 }); win.add(imageView); button.addEventListener('click', function(e) { Ti.Media.takeScreenshot(function(e) { Ti.API.info(e.media); imageView.image = e.media; }); }); win.open(); {code} *Test Environment:* {code} Appcelerator Command-Line Interface, version 7.0.7 Operating System Name = Mac OS X Version = 10.13.6 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 = 7.4.1.GA iOS SDK: 12.0, iOS Simulator: iPhone X {code} *Test steps:* 1. Create a classic project 2. Run the sample code on simulator 3. Click on button. We get the following: {code} [INFO] : rakhiAndroid2/1.0 (7.4.1.f47cf79a83) [INFO] : [object TiBlob] {code} *Console logs and output:* See attachment section for screenshots
| 3 |
3,485 |
TIMOB-26559
|
11/14/2018 13:21:02
|
iOS: App crash and missing events for local notifications
|
There are currently multiple issues around local notifications which either crash the app, do not trigger an event at all, or trigger the wrong event. This ticket is used to group other related tickets and fix those issues all in one go as they all interfere with each other. *Issue 1* (AC-5993) Scheduling local notification raises a "unrecognized selector sent to instance" exception when the app is in foreground when the notification triggers. This was already fixed in TIMOB-26513. However, local notifications shouldn't even try to trigger this method meaning our logic in UNNotificationCenter delegates is flawed and needs to be fixed. *Issue 2* (AC-6013 & AC-6015) Local notifications are not scheduled (or appear so because no notification will be fired).
| 5 |
3,486 |
TIMOB-26560
|
11/14/2018 22:12:34
|
Android: Remove deprecated Ti.UI.KEYBOARD_* constants in favor of TI.UI.KEYBOARD_TYPE_*
|
*Summary:* The {{Ti.UI.KEYBOARD_\*}} type constants were deprecated in Titanium 6.0.0 in favor of our new {{Ti.UI.KEYBOARD_TYPE_\*}} constants. These deprecated constants should be removed in Titanium 8.0.0. Constants to be removed... * {{Ti.UI.KEYBOARD_ASCII}} * {{Ti.UI.KEYBOARD_DECIMAL_PAD}} * {{Ti.UI.KEYBOARD_DEFAULT}} * {{Ti.UI.KEYBOARD_EMAIL}} * {{Ti.UI.KEYBOARD_NAMEPHONE_PAD}} * {{Ti.UI.KEYBOARD_NUMBERS_PUNCTUATION}} * {{Ti.UI.KEYBOARD_NUMBER_PAD}} * {{Ti.UI.KEYBOARD_PHONE_PAD}} * {{Ti.UI.KEYBOARD_WEBSEARCH}} * {{Ti.UI.KEYBOARD_TWITTER}} * {{Ti.UI.KEYBOARD_URL}} Above constants are to be replaced with... * {{Ti.UI.KEYBOARD_TYPE_ASCII}} * {{Ti.UI.KEYBOARD_TYPE_DECIMAL_PAD}} * {{Ti.UI.KEYBOARD_TYPE_DEFAULT}} * {{Ti.UI.KEYBOARD_TYPE_EMAIL}} * {{Ti.UI.KEYBOARD_TYPE_NAMEPHONE_PAD}} * {{Ti.UI.KEYBOARD_TYPE_NUMBERS_PUNCTUATION}} * {{Ti.UI.KEYBOARD_TYPE_NUMBER_PAD}} * {{Ti.UI.KEYBOARD_TYPE_PHONE_PAD}} * {{Ti.UI.KEYBOARD_TYPE_WEBSEARCH}} * {{Ti.UI.KEYBOARD_TYPE_TWITTER}} * {{Ti.UI.KEYBOARD_TYPE_URL}} *Note:* We must also remove deprecated constant {{Ti.UI.KEYBOARD_APPEARANCE_ALERT}}. While this constant is only supported on iOS, it is currently defined on Android to avoid JavaScript runtime errors.
| 3 |
3,487 |
TIMOB-26562
|
11/15/2018 00:41:47
|
Windows: Remove deprecated Ti.UI.KEYBOARD_* constants in favor of TI.UI.KEYBOARD_TYPE_*
|
*Summary:* The {{Ti.UI.KEYBOARD_\*}} type constants were deprecated in Titanium 6.0.0 in favor of our new {{Ti.UI.KEYBOARD_TYPE_\*}} constants. These deprecated constants should be removed in Titanium 8.0.0. Constants to be removed... * {{Ti.UI.KEYBOARD_ASCII}} * {{Ti.UI.KEYBOARD_DECIMAL_PAD}} * {{Ti.UI.KEYBOARD_DEFAULT}} * {{Ti.UI.KEYBOARD_EMAIL}} * {{Ti.UI.KEYBOARD_NAMEPHONE_PAD}} * {{Ti.UI.KEYBOARD_NUMBERS_PUNCTUATION}} * {{Ti.UI.KEYBOARD_NUMBER_PAD}} * {{Ti.UI.KEYBOARD_PHONE_PAD}} * {{Ti.UI.KEYBOARD_URL}} * {{Ti.UI.KEYBOARD_APPEARANCE_ALERT}} Above constants are to be replaced with... * {{Ti.UI.KEYBOARD_TYPE_ASCII}} * {{Ti.UI.KEYBOARD_TYPE_DECIMAL_PAD}} * {{Ti.UI.KEYBOARD_TYPE_DEFAULT}} * {{Ti.UI.KEYBOARD_TYPE_EMAIL}} * {{Ti.UI.KEYBOARD_TYPE_NAMEPHONE_PAD}} * {{Ti.UI.KEYBOARD_TYPE_NUMBERS_PUNCTUATION}} * {{Ti.UI.KEYBOARD_TYPE_NUMBER_PAD}} * {{Ti.UI.KEYBOARD_TYPE_PHONE_PAD}} * {{Ti.UI.KEYBOARD_TYPE_URL}}
| 3 |
3,488 |
TIMOB-26564
|
11/15/2018 13:10:35
|
Windows: Cannot find module 'babylon' error thrown on build
|
h5.Description When building for windows the following error is thrown, this is because of the changes made in TIMOB-25650. We can remove this code though as it is a backwards compat thing for hyperloop 2.x {code} Error: Cannot find module 'babylon' at Function.Module._resolveFilename (module.js:547:15) at Function.Module._load (module.js:474:25) at Module.require (module.js:596:17) at require (internal/module.js:11:18) at Object.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\8.0.0.v20181114074027\windows\cli\commands\_build\copy.js:10:12) at Module._compile (module.js:652:30) at Object.Module._extensions..js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) at Function.Module._load (module.js:497:3) --------------------------------------------- at C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\node_modules\async\dist\async.js:2135:9 at apply (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\node_modules\async\dist\async.js:21:25) at C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\node_modules\async\dist\async.js:56:12 at _insert (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\node_modules\async\dist\async.js:2248:9) at Object.push (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\node_modules\async\dist\async.js:2294:13) at Object.findExecutable (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\node-appc\lib\subprocess.js:113:8) at resolveNode (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\titanium\lib\titanium.js:97:34) at C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\titanium\lib\titanium.js:74:5 at Object.<anonymous> (C:\Jenkins\workspace\anium_mobile_windows_master-VEBTVBGZKPOIHZSZQD5XUBDGPM6Q4OEDUIMQP6TH2EZSWDMRL22Q\titanium-mobile-mocha-suite\node_modules\titanium\lib\titanium.js:80:2) {code} h5.Steps to reproduce 1. Build for Windows h5.Actual Above error thrown h5.Expected No error thrown
| 5 |
3,489 |
TIMOB-26565
|
11/15/2018 13:39:08
|
Windows: Building with hyperloop fails with "traverse is not a function"
|
h5.Description Building hyperloop-examples with SDK 8 throws the following error. This is because hyperloop-examples is using the babel packages from within the SDK and these were removed in TIMOB-25650. The hyperloop hook should be fixed up to have its own dependencies {code} TypeError: traverse is not a function at WindowsBuilder.pre (C:\ProgramData\Titanium\modules\windows\hyperloop\3.1.3\hooks\hyperloop.js:97:5) at C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\lib\hook.js:214:10 at C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:3845:9 at replenish (C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:1030:17) at C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:1034:9 at eachOfLimit (C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:1061:22) at C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:1066:16 at _parallel (C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:3844:5) at Object.series (C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\node_modules\async\dist\async.js:4663:3) at C:\Users\awam\.appcelerator\install\7.0.7\package\node_modules\titanium\lib\hook.js:211:9 [ERROR] traverse is not a function {code} h5.Steps to reproduce 1. Build hyperloop-examples h5.Actual traverse is not a function is thrown h5.Expected No error, app should build just fine
| 5 |
3,490 |
TIMOB-26566
|
11/15/2018 17:00:46
|
iOS: Add ability to remove previously added motion effects
|
I would like to expose a "clearMotionEffects()" method. We use the API exposed by this ticket but see some glitches when switching tabs. This is the natively, but requires some handling to remove the motion-effect on blur and re-add it on focus. Using this API will solve it. This is based on the existing API exposed in TIMOB-25684.
| 5 |
3,491 |
TIMOB-26567
|
11/16/2018 00:03:29
|
Windows: Upgrade to Babel 7
|
https://github.com/appcelerator/titanium_mobile_windows/blob/master/cli/commands/_build/copy.js This relies on Babel 6, we need to update this to support Babel 7. The builds are failing since we removed Babel 6 dependencies https://github.com/appcelerator/node-titanium-sdk/commit/3cfe4346ee87b67fd7da89c2d75a525c588a7c93#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
| 5 |
3,492 |
TIMOB-26571
|
11/16/2018 16:12:35
|
TiAPI: Global process object compatible with Node.js
|
Node has a top-level global {{process}} object which we should attempt to emulate to some degree. A large amount of it's API is not particularly relevant to us, but for compatibility reasons we should support/expose it and try to implement as much as we can that makes sense. https://nodejs.org/api/process.html Notable are: - process.arch - equivalent to {{Ti.Platform.architecture}} - process.cwd() - process.debugPort - process.hrtime([time]) - process.mainModule - process.memoryUsage() - process.nextTick(callback[, ...args]) - process.pid - process.platform - Probably equivalent to {{Ti.Platform.name}} - process.release - process.setUncaughtExceptionCaptureCallback(fn) - process.stderr - process.stdin - process.stdout - process.title - process.uptime() - process.version - Equivalent to {{Ti.version}} - process.versions
| 13 |
3,493 |
TIMOB-26573
|
11/16/2018 16:29:50
|
TiAPI: Make Ti.Buffer Node-compatible with Node's Buffer type
|
We have our own Ti.Buffer type. To play nice with Node, we should see if we can't have it add/use a similar API so that can be used interchangeably.
| 13 |
3,494 |
TIMOB-26574
|
11/16/2018 16:52:45
|
TiAPI: Implement set/clearImmediate
|
setImmediate and clearImmediate are *sort of* like setTimeout/clearTimeout, but are supposed to be run after current I/O event callbacks are done. https://nodejs.org/api/timers.html#timers_setimmediate_callback_args Basically this is roughly like setTimeout(callback, 0); as a first stab, but should be run **before** and timeout callbacks. In effect, immediate, timers and ticks from process.nextTick are *sort of* like 3 separate priorities of timer queues, although at a lower level they have semantic/behavioral differences. ticks are right away and can cause infinite loops. immediate come next chance after I/O events callbacks. Then timers get fired when ready.
| 13 |
3,495 |
TIMOB-26575
|
11/16/2018 19:23:50
|
Windows: Support async variants of Ti.Network.TCP #read and #write
|
We've added async variants for Android/iOS, but Windows does not yet support this - and is failing the unit test we wrote for it. The test has since been skipped on Windows.
| 8 |
3,496 |
TIMOB-26577
|
11/16/2018 19:30:25
|
Windows: ScrollView sizing incorrectly in a vertical layout
|
In our unit tests suite, the ti.ui.layout.test.js scrollViewWithSIZE test is failing on Windows with expected 24 to equal 50 https://github.com/appcelerator/titanium-mobile-mocha-suite/blob/master/Resources/ti.ui.layout.test.js#L1291 The test is now skipped on Windows. It turns out this only happens when parent view is {{vertical}} layout. As a side note, {{postlayout}} for {{ScrollView}} may be fired multiple times during layout and we should be testing latest value only. {code} var scrollView = Ti.UI.createScrollView({ height: Ti.UI.SIZE, width: Ti.UI.SIZE, backgroundColor: 'red' }); var view1 = Ti.UI.createButton({ width: '100', height: '50', title: 'Click', backgroundColor: 'pink' }); scrollView.add(view1); scrollView.addEventListener('postlayout', function () { Ti.API.info(JSON.stringify(scrollView.size)); }); var win = Ti.UI.createWindow({ backgroundColor: 'white', layout: 'vertical' }); win.add(scrollView); win.open(); {code}
| 5 |
3,497 |
TIMOB-26578
|
11/16/2018 19:37:37
|
Windows: Missing trailing separator for directory in Ti.Filesystem.File#nativePath
|
There are a number of parity issues with the implementation of Ti.Filesystem.File#getDirectoryListing() on Windows, which can be seen in the tests now skipped there: https://github.com/appcelerator/titanium-mobile-mocha-suite/blob/master/Resources/ti.filesystem.file.test.js#L726-L746 Namely that: - calling it for a file should return null - calling for a directory that does not exist should return null (returns empty array right now) The other test ("can access resource directory files") may be failing due to Windows not appending a trailing separator while other platforms do? I tried with unix and windows separators and that didn't seem to fix it, so I don't think it's a separator mismatch issue.
| 5 |
3,498 |
TIMOB-26579
|
11/16/2018 19:45:42
|
Windows: Ti.UI.ImageView's load event object has no state property
|
According to our docs and our unit test suite, the Ti.UI.ImageView {{load}} event should fire off with an object holding a {{state}} property whose values is either {{'image'}} or {{'images'}}, based on whether it's being fired after loading a single image from {{image}} property, or after loading a series of images from the {{images}} property.
| 5 |
3,499 |
TIMOB-26580
|
11/16/2018 22:42:12
|
Android: ListView templates not compatible with native modules
|
ListView templates have a bug that prevents support for native modules. {code:js} var template = { childTemplates: [ { type: '<native-module-namespace>, bindId: '', properties: { ... } } ] }; {code}
| 3 |
3,500 |
TIMOB-26582
|
11/19/2018 21:17:25
|
IOS: Build fails for simulator/device with SOASTA
|
*Steps to reproduce:* 1.Create a classic sample app 2.run against IOS device or emulator *Expected:* App should successfully built and installed on ios device *Actual:* Throws the following error [TRACE] : ld: symbol(s) not found for architecture x86_64 [TRACE] : clang: error: linker command failed with exit code 1 (use -v to see invocation) [ERROR] : ** BUILD FAILED ** [ERROR] : The following build commands failed: [ERROR] : Ld /Users/kmahalingam/Documents/Appcelerator_Studio_Workspace/Htest/build/iphone/build/Products/Debug-iphonesimulator/Htest.app/Htest normal x86_64 [ERROR] : (1 failure)
| 5 |
3,501 |
TIMOB-26586
|
11/21/2018 02:11:03
|
iOS: Animation curve ease-in/ease-out does not auto-reverse correctly
|
*Summary:* A view animation with "autoreverse" set to {{true}} and a "repeat" of {{0}} (the default) will not correctly reverse the animation when using "curve" {{Ti.UI.ANIMATION_CURVE_EASE_IN}} or {{Ti.UI.ANIMATION_CURVE_EASE_OUT}}. The animation incorrectly uses the same curve when performing the reverse animation. If "repeat" is set to {{1}} or higher, this issue will only happen on the final/last repeated reverse animation. This issue won't happen on prior repeated animations. *Expected Behavior:* When the curve is set to {{Ti.UI.ANIMATION_CURVE_EASE_IN}}, then the reverse animation curve is supposed to be {{Ti.UI.ANIMATION_CURVE_EASE_OUT}}. When the curve is set to {{Ti.UI.ANIMATION_CURVE_EASE_OUT}}, then the reverse animation curve is supposed to be {{Ti.UI.ANIMATION_CURVE_EASE_IN}}. The above is how it works in HTML5 "reverse" animation. See... https://developer.mozilla.org/en-US/docs/Web/CSS/animation-direction#Syntax *Cause:* Titanium's iOS code generates its own reverse animation to work-around an Apple bug. The issue is that the reverse animation uses the same "curve" as the forward animation. This is where the reverse curve should be applied instead. https://github.com/appcelerator/titanium_mobile/blob/master/iphone/TitaniumKit/TitaniumKit/Sources/API/TiAnimation.m#L412
| 3 |
3,502 |
TIMOB-26587
|
11/21/2018 11:11:30
|
Babel throwing an error on build
|
Babel is throwing an error on build stopping building on a device. *Error* {noformat} [ERROR] Cannot read property 'isPure' of null {noformat} *Steps to reproduce* # Create an application {{appc new}} # Build to device {{appc run -p ios -T device}}
| 3 |
3,503 |
TIMOB-26594
|
11/21/2018 14:27:45
|
iOS: Exception when canceling local notifications with removePendingNotifications
|
I'm trying to cancel local iOS notifications with Ti.App.iOS.UserNotificationCenter.removePendingNotifications(notificationsToCancel), but whenever I try to call this with an array of notifications the app crashes. I did a little bit of research and it seems the ENSURE_TYPE on line 109 in TiAppiOSUserNotificationCenterProxy.m throws an exception. But I'm getting the notifications from getPendingNotifications so they should be ok right? Example (press schedule and then cancel right afterwards to get the exception): {code:java} var window = Ti.UI.createWindow({ backgroundColor: 'white' }); var button = Ti.UI.createButton({ title: 'Schedule' }); var isScheduling = true; button.addEventListener('click', function() { if (isScheduling) { var alarmObject = { date: new Date(new Date().getTime() + 20000), alertBody: "Hello world", badge: 1, identifier: "test_id", sound: 'default' }; console.log('schedule: ' + JSON.stringify(alarmObject)); Ti.App.iOS.scheduleLocalNotification(alarmObject); button.title = "Cancel"; } else { Ti.App.iOS.UserNotificationCenter.getPendingNotifications(function(result) { if (result && result.notifications && result.notifications.length) { var notificationsToCancel = _.filter(result.notifications, function(n) { return n.identifier == "test_id"; }); console.log('cancel these: ' + JSON.stringify(notificationsToCancel)); if (notificationsToCancel) { Ti.App.iOS.UserNotificationCenter.removePendingNotifications(notificationsToCancel); } } }); button.title = "Schedule"; } isScheduling = !isScheduling; }); window.add(button); window.addEventListener('open', function() { Ti.App.iOS.registerUserNotificationSettings({ types: [ Ti.App.iOS.USER_NOTIFICATION_TYPE_ALERT, Ti.App.iOS.USER_NOTIFICATION_TYPE_SOUND, Ti.App.iOS.USER_NOTIFICATION_TYPE_BADGE ] }); }); window.open(); {code} Exception: {code:java} [ERROR] The application has crashed with an uncaught exception 'org.testproject.TiAppiOSUserNotificationCenterProxy'. [ERROR] Reason: [ERROR] Invalid type passed to function [ERROR] Stack trace: [ERROR] 0 CoreFoundation 0x000000010f8881bb __exceptionPreprocess + 331 [ERROR] 1 libobjc.A.dylib 0x000000010e683735 objc_exception_throw + 48 [ERROR] 2 TestProject 0x0000000108c65b1d TiExceptionThrowWithNameAndReason + 141 [ERROR] 3 TestProject 0x0000000108c21e7b -[TiProxy throwException:subreason:location:] + 107 [ERROR] 4 TestProject 0x0000000108bb1f4f __66-[TiAppiOSUserNotificationCenterProxy removePendingNotifications:]_block_invoke_2 + 1055 [ERROR] 5 UserNotifications 0x0000000110bc6161 __111-[UNUserNotificationServiceConnection getPendingNotificationRequestsForBundleIdentifier:withCompletionHandler:]_block_invoke_2.217 + 240 [ERROR] 6 libdispatch.dylib 0x0000000110d9c4e1 _dispatch_call_block_and_release + 12 [ERROR] 7 libdispatch.dylib 0x0000000110d9d54b _dispatch_client_callout + 8 [ERROR] 8 libdispatch.dylib 0x0000000110da401c _dispatch_lane_serial_drain + 720 [ERROR] 9 libdispatch.dylib 0x0000000110da4b95 _dispatch_lane_invoke + 455 [ERROR] 10 libdispatch.dylib 0x0000000110dad9a8 _dispatch_workloop_worker_thread + 645 [ERROR] 11 libsystem_pthread.dylib 0x0000000111182fd2 _pthread_wqthread + 980 [ERROR] 12 libsystem_pthread.dylib 0x0000000111182be9 start_wqthread + 13 {code}
| 1 |
3,504 |
TIMOB-26595
|
11/26/2018 11:02:35
|
CLI: Unable to create module using latest the build from Master
|
When creating a module the platform folders do not get created _The below is for iOS but is relevant for all platforms_ *Test steps:* # Open Appc Studio # Create a new module (File -> New -> Mobile App project) # When creating a module select the latest SDK from master (8.0.0.v20181121114345) # Open project and check if iOS folder has been created *Actual result* iOS folder can not be seen once a new module has been 'created'. *Expected result* iOS folder should be created when creating a new module.
| 3 |
3,505 |
TIMOB-26597
|
11/26/2018 13:35:25
|
CLI: Prompted for ios code base type when creating an android module
|
H5.Description When creating a module for a non-iOS platform, I'm still prompted for the code base type, this prompt should only show if the platforms includes ios h5.Steps to reproduce 1. Run {{ti create --log-level trace --name foobarmodule --force --type module --platforms android --id com.foo}} h5.Actual Prompted for the code base type h5.Expected No prompt for code base type
| 3 |
3,506 |
TIMOB-26599
|
11/26/2018 14:31:32
|
iOS: Add "allowTranscoding" option to Ti.Media.openPhotoGallery()
|
*Summary:* When selecting a video from the gallery, iOS will transcode/convert the selected video by default and return the newly formatted video instead. This can cause a very long delay if the video is large. *Solution:* Add an iOS-only "allowTranscoding" option for our {{Ti.Media.openPhotoGallery()}} method, when set {{false}}, will return the selected video as-is without transcoding it. This will solve the long delay issue. {code:javascript} Ti.Media.openPhotoGallery({ allowTranscoding: false, mediaTypes: [Ti.Media.MEDIA_TYPE_VIDEO], success: function(e) { // Got it. }, }); {code} *Note:* There is no equivalent to this on Android, which always returns a reference to the video as-is. So, this is an iOS only feature. *Native Implementation Details:* Add this code at line 1746. I can provide a PR {code:java} if ([TiUtils isIOS11OrGreater]) { BOOL disableVideoCompression = [TiUtils boolValue:@"disableVideoCompression" properties:args def:NO]; if (disableVideoCompression) { picker.videoExportPreset = AVAssetExportPresetPassthrough; } } [self displayModalPicker:picker settings:args]; {code}
| 5 |
3,507 |
TIMOB-26601
|
11/28/2018 04:06:29
|
Android: Cannot apply theme with "windowTranslucentNavigation" or "windowTranslucentStatus" to splash screen as of 7.5.0
|
*Summary:* As of Titanium 7.5.0, a custom theme set up with {{windowTranslucentNavigation}} or {{windowTranslucentStatus}} will be undone when applied to the splash screen activity. *Steps to reproduce:* # Create a Classic app named "SplashTest". # Set up a blank "app.js" as shown below. # Add the below "my_themes.xml" file under folder: {{./platform/android/res/values}} # Set up "tiapp.xml" with the below. # Build and run on Android. # On app startup, notice that top status bar and bottom navigation bar are briefly displayed semi-transparent... but then become opaque. (The bug is they're not supposed to turn opaque.) # Notice that the following warning gets logged. {{You cannot use a translucent status bar or navigation bar unless you set the window's 'extendSafeArea' property to true.}} {{app.js}} {code:javascript} // Leave the "app.js" script blank. {code} {{./platform/android/res/values/my_themes.xml}} {code:xml} <?xml version="1.0" encoding="UTF-8"?> <resources> <style name="MyTheme" parent="@style/Theme.Titanium"> <item name="android:windowTranslucentNavigation">true</item> <item name="android:windowTranslucentStatus">true</item> </style> </resources> {code} {{tiapp.xml}} {code:xml} <ti:app xmlns:ti="http://ti.appcelerator.org"> <android xmlns:android="http://schemas.android.com/apk/res/android"> <manifest> <application> <activity android:name=".SplashtestActivity" android:theme="@style/MyTheme"> <intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter> </activity> </application> </manifest> </android> </ti:app> {code}
| 5 |
3,508 |
TIMOB-26678
|
11/28/2018 22:40:21
|
Android: Unnecessary default notification channel created when using a custom one
|
When using SDK 7.5.0.GA and targeting Android SDK version 26 there is a small issue with notifications. In TIMOB-25864 forward compatibility was introduced to have a default channel in case apps target SDK version 26. This works perfect, apart from the fact that it now always creates this channel. When using the (undocumented) 'channelId' as option in the createNotification after creating a custom notification channel this yields the expected result. You see a notification that belongs to the channel just created, but on top that you still see the warning: {code} [WARN] TiNotification: (main) [234,27512] Falling back to default notification channel. [WARN] TiNotification: It is highly advised to create your own notification channel using Ti.Android.NotificationManager.createNotificationChannel() {code} This occurs with the example code of NotificationChannel when targeting SDK version 26: https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Android.NotificationChannel Expected result: No default notification channel is created, when a custom notification channel is defined.
| 3 |
3,509 |
TIMOB-26613
|
11/29/2018 17:51:41
|
node-ios-device: Add Node.js 11 support
|
node-ios-device needs to add support for module API version 64. This only affects the build scripts. The node-ios-device user code does not need to be changed. After the module API 64 has been added to the build scripts, node-ios-device must be built locally and then manually upload the binary to S3. There will be no new resulting npm package.
| 5 |
3,510 |
TIMOB-26630
|
12/05/2018 12:32:18
|
ScrollView: toImage() not taking complete screenshot of scrollview
|
Hello! I have a scrollview added on window, while taking the screenshot of scrollview, it takes toImage() of the area that is visible on the window, but not of full scrollview, how I can overcome this issue ? {code} var win = Ti.UI.createWindow({ backgroundColor : "white", }); var scrollview = Ti.UI.createScrollView({ width : "100%", height : "100%", // contentHeight:"auto", layout : "vertical" }); win.add(scrollview); scrollview.addEventListener("click", function(e) { var win2 = Ti.UI.createWindow({ backgroundColor : "white", }); var scrollVw = Ti.UI.createScrollView({ width : "100%", height : "100%", // contentHeight:"auto", layout : "vertical" }), varImageVw = Ti.UI.createImageView({ width : "100%", height : Ti.UI.SIZE, image : scrollview.toImage(), }); scrollVw.add(varImageVw); win2.add(scrollVw); win2.open(); }); var view1 = Ti.UI.createView({ top : 0, width : "100%", height : "400", backgroundColor : "red" }); scrollview.add(view1); var view2 = Ti.UI.createView({ top : 0, width : "100%", height : "400", backgroundColor : "green" }); scrollview.add(view2); var view3 = Ti.UI.createView({ top : 0, width : "100%", height : "400", backgroundColor : "blue" }); scrollview.add(view3); var view4 = Ti.UI.createView({ top : 0, width : "100%", height : "400", backgroundColor : "yellow" }); scrollview.add(view4); var view5 = Ti.UI.createView({ top : 0, width : "100%", height : "400", backgroundColor : "pink" }); scrollview.add(view5); win.open(); {code} while clicking on first window scrollview, image is displayed in next window scrollview, you will notice its not taking toImage() of complete scrollview, as its not displaying in 2 window. 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 = 7.5.0.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\7.5.0.GA Target Platform = android {code} Thanks
| 5 |
3,511 |
TIMOB-26631
|
12/05/2018 17:02:10
|
Android: image from camera gets rotated to 90 degree
|
Hello! I'm trying to take an image from the camera and then save it to the image view or post it to my server for Android. The problem is when I take the image it gets rotated to 90 degrees. Test Code: {code} var win = Ti.UI.createWindow({ backgroundColor: '#fff', title: 'Test', layout:"vertical" }); var button = Ti.UI.createButton({ title: 'Post Item' }); button.addEventListener('click', function(e) { var dialog = Ti.UI.createOptionDialog({ options: ['Take a Picture', 'Choose a Picture'], cancel: 2 }); dialog.addEventListener('click', function(e) { if(e.index == 0) { Ti.Media.showCamera({ success: function(e) { alert('media.nativePath: ' + e.media.nativePath); // create an imageView to display our photo var imageView = Ti.UI.createImageView({ image: e.media }); // add the imageView to the window win.add(imageView); }, cancel: function(e) { Ti.API.info(JSON.stringify(e)); }, error: function(e) { Ti.API.info(JSON.stringify(e)); }, animated: false, autohide: true, saveToPhotoGallery: false, showControls: true }); } else if(e.index == 1) { Ti.Media.openPhotoGallery({ success: function(e) { alert('media.nativePath: ' + e.media.nativePath); }, cancel: function(e) { Ti.API.info(JSON.stringify(e)); }, error: function(e) { Ti.API.info(JSON.stringify(e)); }, mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO] }); } }); dialog.show(); }); win.add(button); //check if we already have permissions to capture media if (!Ti.Media.hasCameraPermissions()) { // request permissions to capture media Ti.Media.requestCameraPermissions(function (e) { // success! display the camera if (e.success) { win.open(); // oops! could not obtain required permissions } else { callback(new Error('could not obtain camera permissions!'), null); } }); } else { win.open(); } {code} Tets 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 = 7.5.0.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\7.5.0.GA Target Platform = android {code} Please take a look on attached screenshot. Also note, that front and back facing cameras rotate the image different ways Thanks
| 1 |
3,512 |
TIMOB-26632
|
12/05/2018 21:33:01
|
Android: App sometimes crashes when backgrounded as of 7.5.0
|
App getting crashed, whenever app is in background. Error description: {code}java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object org.appcelerator.kroll.KrollObject.callProperty(java.lang.String, java.lang.Object[])' on a null object reference.{code} The following link will show the apm from dashboard: * https://platform.axway.com/#/app.service/apm/5af9ddd60f0e5961bf7cd0d5 or * https://app.crittercism.com/developers/crash-details/44567a3b3cfe456e8577fb10b74a469c00555300/e30ecfa1fcab9675#period=P14D&appVersion=5.6.7 The app was showing no such crashes with SDK 7.4.1.GA, Something has changed in SDK 7.5.0.GA that is making the app crash. There are like 100s of crashes which were never there with 7.4.1.GA. *Attachments:* I've added 2 screenshots of crash & appc ti setup check command log.
| 5 |
3,513 |
TIMOB-26633
|
12/06/2018 00:21:10
|
Android: Change min supported version to Android 4.4 (API Level 19)
|
In Titanium 8.0.0, we need to bump up the minimum Android OS version supported... *From:* Android 4.1 (API Level 16) *To:* Android 4.4 (API Level 19) The "minSdkVersion" in Titanium SDK's "package.json" needs to be changed here. https://github.com/appcelerator/titanium_mobile/blob/master/android/package.json Titanium's "AndroidManefest.xml" template will automatically pull the "minSdkVersion" from the above mentioned "package.json".
| 1 |
3,514 |
TIMOB-26636
|
12/08/2018 04:51:37
|
Android: Remove deprecated "newIntent" event in favor of "newintent"
|
*Summary:* The {{Ti.Android.Activity}} object currently supports events "newIntent" and "newintent". The "newIntent" event was deprecated in the past in favor of "newintent" with a lower-case 'i'. We should remove it in Titanium 8.0.0. {code:javascript} Ti.Android.currentActivity.addEventListener("newIntent", function(e) { // This event is deprecated and should no longer be supported. Ti.API.info("!!! Event 'newIntent' is deprecated. Should no longer be fired."); }); Ti.Android.currentActivity.addEventListener("newintent", function(e) { // This is the event name you should listen to. Ti.API.info("### Event 'newintent' was received"); }); {code} *Note:* Ideally, we should log a warning when JS code attempts to add a listener to the deprecated "newIntent" event to avoid confusion/tech-support issues.
| 1 |
3,515 |
TIMOB-26637
|
12/08/2018 05:39:50
|
Android: Add "rootActivity" property to Ti.Android module
|
*Summary:* The {{Ti.Android}} module supports a "currentActivity" property. used to access the top-most activity displayed by the app. We could improve the usability of the "newintent" event and intent-filter handling if we provided easy access to the app's root activity as well. This is because the root activity's is the one that's being updated when the native Java {{Activity.onNewIntent()}} method gets called. Currently, the only way to set up "newintent" handling is to do so before opening a {{Ti.UI.Window}}. *Proposed Solution:* Add a new "rootActivity" property to the {{Ti.Android}} module.
| 1 |
3,516 |
TIMOB-26638
|
12/08/2018 05:53:09
|
Android: Root Ti.Android.Activity "intent" property should be updated when "newintent" event is fired
|
*Summary:* Currently, the root {{Ti.Android.Activity}} object's "intent" property never changes when a "newintent" event gets fired. The activity's "intent" property returns the intent that originally launched/created the activity. We can improve the usability of the app's "newintent" and intent-filter handling if the root activity's "intent" property was updated to the same intent provided by the "newintent" event. Note that {{Ti.App.Android}} provides a [launchIntent|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.App.Android-property-launchIntent] property which already provides the intent used to launch/create the root activity. So, we're not losing anything by making this change. Also, it's currently possible to miss the "newintent" event on app startup, before the "app.js" has a chance to set up a listener for it. {code:javascript} var rootActivity = Ti.Android.currentActivity; rootActivity.addEventListener("newintent", function(e) { // Ideally, the 2 intents logged below should be the same. Ti.API.info("### event.intent: " + JSON.stringify(e.intent)); Ti.API.info("### rootActivity.intent: " + JSON.stringify(rootActivity.intent)); // The launch intent property must never change. Ti.API.info("### launchIntent: " + JSON.stringify(Ti.App.Android.launchIntent)); }); {code}
| 5 |
3,517 |
TIMOB-26645
|
12/12/2018 00:17:47
|
Android: Calling finish() on root splash screen activity should exit the app
|
*Summary:* Calling {{Activity.finish()}} on the root splash screen activity should automatically close all child windows/activities and exit out of the app. It should only work this way for the root activity. Finishing/closing an activity in the middle of the stack should not automatically close the child activities. *Note:* This is mostly needed for Titanium apps launched via the Java {{startActivityForResult()}} method. In this case, the Titanium developer must call the {{Activity.setResult()}} method on the root activity and exit out to respond to the other app with the result. You typically call {{Activity.finish()}} just after {{Activity.setResult()}} when following Google's examples. *Steps to reproduce:* # Build and run with the below code on Android. # Tap on the "Close" button. # Notice that the app does not exit out. {code:javascript} var rootActivity = Ti.Android.currentActivity; var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Close Root Activity" }); button.addEventListener("click", function() { rootActivity.finish(); }); window.add(button); window.open(); {code}
| 3 |
3,518 |
TIMOB-26648
|
12/13/2018 11:22:20
|
Windows: ability to override global functions
|
Relates to https://github.com/appcelerator/HAL/pull/86 , https://github.com/appcelerator/titanium-mobile-mocha-suite/blob/master/Resources/timers.test.js#L170-L176 and https://github.com/appcelerator/titanium_mobile/blob/master/common/Resources/ti.internal/extensions/binding.js We already modified this behavior on iOS to allow to override global functions like `setTimeout`, which is typical of an environment like Node and is assumed by some of the popular JS testing frameworks. I also ran into issues in overriding the standard require function in an effort to introduce cross-platform JS implementations of node-compatible "core" modules. iOS PR: appcelerator/titanium_mobile#10155 unit tests we're skipping on Windows due to this {code} var originalRequire = global.require; global.require = function (moduleId) { Ti.API.info('Overridden require'); return originalRequire(moduleId); } require('require_test'); {code} Expected: `Overridden require` should be shown before requiring files.
| 3 |
3,519 |
TIMOB-26649
|
12/13/2018 14:00:39
|
[LiveView] Unable to use LiveView with KitchenSink-v2
|
When trying to use liveView with KitchenSink the application throws the following error: {code:java} liveview:clihook Error: ENOENT: no such file or directory, open '/Users/Samir/Desktop/Appc/Repos/kitchensink-v2/i18n/de/strings.xml' --------------------------------------------- at /Users/Samir/Library/Application Support/Titanium/mobilesdk/osx/8.0.0.v20181212133855/node_modules/liveview/hook/lvhook.js:172:10 at /Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/lib/hook.js:235:13 at /Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:3845:9 at replenish (/Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:1030:17) at /Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:1034:9 at eachOfLimit (/Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:1061:22) at /Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:1066:16 at _parallel (/Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:3844:5) at Object.series (/Users/Samir/.appcelerator/install/7.0.8/package/node_modules/titanium/node_modules/async/dist/async.js:4663:3) {code} *Steps to reproduce* # Download {{KitchenSink-v2}} # Download the latest SDK version {{appc ti sdk install -b master -d}} # In the project directory run the following command {{DEBUG=liveview:* appc run -p ios --liveview}} # Above error is thrown in the console and an error can be seen in the iOS simulator *Actual result* Above error can be seen. *Expected result* Application should show no error and LiveView should work with KitchenSInk without any issues.
| 3 |
3,520 |
TIMOB-26651
|
12/13/2018 18:02:17
|
Windows: Ti.Locale.setLangauge result is delayed
|
In our unit tests, we attempt to change languages and ensure we end up pulling the correct translation strings. Windows behaves oddly in that the language does get changed immediately in our model, but it still pulls the translation strings from the old language for a little while. So ~3 tests fail in order by using the wrong language's strings, and it appears to be using the previous test's language. I'm not sure if there's some caching going on, or overriding the language is really done async - or maybe when we ask for the ResourceLoader for the current view it's outdated because it needs to load async when primary language changes?
| 5 |
3,521 |
TIMOB-26654
|
12/14/2018 12:47:59
|
Hyperloop Android: How to get access the views in the inflate layout
|
Hello! How to get access the views in the inflate layout on android hyperloop? We have a button in inflate layout and we want to set button text form our js file. Test code : {code} var window = Titanium.UI.createWindow(); var OnValueChangeListener = require('android.widget.NumberPicker.OnValueChangeListener'); var OnClickListener = require('android.view.View.OnClickListener'); var Activity = require('android.app.Activity'); var Button = require('android.widget.Button'); var Context = require('android.content.Context'); var LinearLayout = require("android.widget.LinearLayout"); var Inflater = require('android.view.LayoutInflater'); // var numberOnclickListener = // require('android.content.NumberPicker.OnClickListener'); var activity = new Activity(Ti.Android.currentActivity); var layout = new LinearLayout(activity); var viewLayout = new LinearLayout(activity); var okButton = new Button(activity); // var field = new Field(); var cancelButton = new Button(activity); var inflater = Inflater.cast(activity.getApplicationContext().getSystemService( Context.LAYOUT_INFLATER_SERVICE)); var resId = activity.getResources().getIdentifier('button', 'layout', activity.getPackageName()); var view = inflater.inflate(resId, null); // numberPicker1 = activity.getResources().getIdentifier("button", "id", // activity.getPackageName()); // numberPicker1.setMinValue(1); // numberPicker1.setMaxValue(9); var resid = Titanium.App.Android.R.id.cancelButtton; // var id = // Ti.Android.currentActivity.getIdentifier(Ti.Android.R.cancelButtton); var myButton = new Button(view.findViewById(resid)); myButton.setText("Hello!"); window.add(view); window.open(); {code} Place it to the [app]/platform/android/res/layout/ {code:xml} <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent" android:layout_height="match_parent" android:orientation="vertical" android:gravity="center_horizontal" android:id="@+id/parent_view"> <LinearLayout android:id="@+id/numberPickerViews" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_gravity="center" android:orientation="horizontal"> <NumberPicker android:id="@+id/numberPicker" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_gravity="center" android:visibility="visible" /> <NumberPicker android:id="@+id/numberPicker2" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_gravity="center" android:visibility="visible" /> <NumberPicker android:id="@+id/numberPicker3" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_gravity="center" android:visibility="visible" /> </LinearLayout> <LinearLayout android:id="@+id/timeSetView" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_gravity="center" android:orientation="horizontal"> <Button android:id="@+id/setButtton" android:layout_width="wrap_content" android:layout_height="wrap_content" android:textColor="@android:color/holo_blue_light" android:text="OK" android:textAlignment="center_horizontal" android:gravity="left" android:textStyle="bold" android:textAlignment="center" /> <Button android:id="@+id/cancelButtton" android:layout_width="wrap_content" android:layout_height="wrap_content" android:textColor="@android:color/holo_blue_light" android:textStyle="bold" android:gravity="right" android:textAlignment="center" /> </LinearLayout> </LinearLayout> {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 = 7.5.0.GA {code} Thanks
| 1 |
3,522 |
TIMOB-26662
|
12/17/2018 11:13:52
|
Android. TableViewRow bugs
|
Currently on Android TableViewRow: # always returns zeroes for {{getRect}} method (and rect {{property}}) # does not grow in height beyond original size (but can shrink) {code:javascript} win = Ti.UI.createWindow({ backgroundColor: '#AAAAFF', layout: 'vertical' }); var top = Ti.UI.createView({ backgroundColor: '#FFAAAA', layout: 'horizontal', height: Ti.UI.SIZE, width: Ti.UI.FILL }); var btnPlus = Ti.UI.createButton({title: '+'}); btnPlus.addEventListener('click', function() { console.log('plus click'); view.height += 50; }); var btnMinus = Ti.UI.createButton({title: '-'}); btnMinus.addEventListener('click', function() { console.log('minus click'); view.height -= 50; }); var label = Ti.UI.createLabel(); var tableView = Ti.UI.createTableView(); var row = Ti.UI.createTableViewRow({ height: Ti.UI.SIZE, width: Ti.UI.FILL }); var view = Ti.UI.createView({ height: 150, backgroundColor: 'blue' }); row.add(view); tableView.setData([ row ]); tableView.addEventListener('postlayout', function onPostLayout() { console.log('postlayout', row.rect.height, view.rect.height); label.text = [row.rect.height, view.rect.height].join(' | '); }); top.add(btnPlus); top.add(btnMinus); top.add(label); win.add(top); win.add(tableView); win.open(); {code}
| 5 |
3,523 |
TIMOB-26660
|
12/17/2018 15:06:36
|
Support native modules in Karma Titanium Launcher
|
[karma-titanium-launcher|https://github.com/appcelerator/karma-titanium-launcher] currently supports testing for Apps and JS modules. Covering native modules is the last missing piece for a complete unit testing environment. The workflow for unit testing of native modules should be as follows: * Build the module for the current platform we are testing * Create a temporary project serving as the test runner and integrate the built module into that project * Run the test runner and spit out results * Tests can be configured as usual with the Karma config. For example, tests for all platform can reside in {{<project-dir>/test}} with additional tests for each platform in the respective platform folder, i.e. {{<project-dir>/android/test}}.
| 5 |
3,524 |
TIMOB-26664
|
12/18/2018 01:38:58
|
Windows: Ti.Geolocation.lastGeolocation should return string
|
{{Ti.Geolocation.lastGeolocation}} should return string. On Windows, it returns object. {code:javascript} Ti.API.info(typeof Ti.Geolocation.lastGeolocation); {code} Expected: It should print {{string}}.
| 3 |
3,525 |
TIMOB-26667
|
12/19/2018 03:20:38
|
Windows: Ti.Locale.getString should ignore non-string default value
|
If the supplied "default" value is a non-string, we should now "reject" it and treat it as if no default fallback was given. If no default was given, the original key is returned when no corresponding value is found. {code} Ti.API.info(Ti.Locale.getString('this_should_not_be_found', null) + '.eql(this_should_not_be_found)'); Ti.API.info(L('this_should_not_be_found', null) + '.eql(this_should_not_be_found)'); Ti.API.info(Ti.Locale.getString('this_should_not_be_found', 123) + '.eql(this_should_not_be_found)'); Ti.API.info(L('this_should_not_be_found', 123) + '.eql(this_should_not_be_found)'); {code} Expected: key should be returned.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.