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,226 |
TIMOB-25911
|
03/28/2018 15:24:55
|
Android : Return event of TextField with Ti.UI.RETURNKEY_SEARCH returnKeyType is not working 7.1.0.GA
|
Hi, We are having issues with return event of TextField in SDK 7.1.0.GA in Android. If the returnKeyType of the TextField is "Ti.UI.RETURNKEY_SEARCH", return even is not being triggered. Whereas if the returnKeyType is removed, it is working as expected. This was working in SDK 6.2.2.GA but not in 7.1.0.GA. Steps to reproduce: 1. Run the attached project - TestTextField in Android. 2. Click on the TextField in the screen and keyboard will appear. 3. Tap on the search button in the keyboard. Log message in its 'return' event will not be printed in console. 4. Repeat the above steps after removing "returnType" of the TextField. Log message('return clicked') will be printed in console PFA the environment details - tiInfo.rtf Please let us know if any additional information is required. Thanks,
| 0 |
3,227 |
TIMOB-25913
|
03/29/2018 00:12:57
|
Android: Build fails for android with java.time.DateTimeException with java 9.0.4 & crittercism
|
h5.Steps to reproduce: 1. Build an android app with SDK having fix for java 9 support. h5.Actual results: 1. The build will fail with error: {code} [ERROR] Failed to compile Java source files: [ERROR] [ERROR] An exception has occurred in the compiler (9.0.4). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com) after checking the Bug Database (http://bugs.java.com) for duplicates. Include your program and the following diagnostic in your report. Thank you. [ERROR] java.time.DateTimeException: Invalid value for MonthOfYear (valid values 1 - 12): 0 [ERROR] at java.base/java.time.temporal.ValueRange.checkValidValue(ValueRange.java:311) [ERROR] at java.base/java.time.temporal.ChronoField.checkValidValue(ChronoField.java:714) [ERROR] at java.base/java.time.LocalDate.of(LocalDate.java:269) [ERROR] at java.base/java.time.LocalDateTime.of(LocalDateTime.java:336) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipUtils.dosToJavaTime(ZipUtils.java:109) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem$Entry.cen(ZipFileSystem.java:1950) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem$Entry.readCEN(ZipFileSystem.java:1937) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.getEntry(ZipFileSystem.java:1324) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.getFileAttributes(ZipFileSystem.java:312) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipPath.getAttributes(ZipPath.java:721) [ERROR] at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.readAttributes(ZipFileSystemProvider.java:293) [ERROR] at java.base/java.nio.file.Files.readAttributes(Files.java:1755) [ERROR] at java.base/java.nio.file.FileTreeWalker.getAttributes(FileTreeWalker.java:219) [ERROR] at java.base/java.nio.file.FileTreeWalker.visit(FileTreeWalker.java:276) [ERROR] at java.base/java.nio.file.FileTreeWalker.next(FileTreeWalker.java:373) [ERROR] at java.base/java.nio.file.Files.walkFileTree(Files.java:2749) [ERROR] at jdk.compiler/com.sun.tools.javac.file.JavacFileManager$ArchiveContainer.<init>(JavacFileManager.java:523) [ERROR] at jdk.compiler/com.sun.tools.javac.file.JavacFileManager.getContainer(JavacFileManager.java:319) [ERROR] at jdk.compiler/com.sun.tools.javac.file.JavacFileManager.list(JavacFileManager.java:715) [ERROR] at jdk.compiler/com.sun.tools.javac.code.ClassFinder.list(ClassFinder.java:722) [ERROR] at jdk.compiler/com.sun.tools.javac.code.ClassFinder.scanPlatformPath(ClassFinder.java:673) [ERROR] at jdk.compiler/com.sun.tools.javac.code.ClassFinder.fillIn(ClassFinder.java:525) [ERROR] at jdk.compiler/com.sun.tools.javac.code.ClassFinder.complete(ClassFinder.java:293) [ERROR] at jdk.compiler/com.sun.tools.javac.code.Symbol.complete(Symbol.java:633) [ERROR] at jdk.compiler/com.sun.tools.javac.code.Symbol$PackageSymbol.members(Symbol.java:1120) [ERROR] at jdk.compiler/com.sun.tools.javac.code.Symtab.listPackageModules(Symtab.java:810) [ERROR] at jdk.compiler/com.sun.tools.javac.comp.Enter.visitTopLevel(Enter.java:344) [ERROR] at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:529) [ERROR] at jdk.compiler/com.sun.tools.javac.comp.Enter.classEnter(Enter.java:285) [ERROR] at jdk.compiler/com.sun.tools.javac.comp.Enter.classEnter(Enter.java:300) [ERROR] at jdk.compiler/com.sun.tools.javac.comp.Enter.complete(Enter.java:570) [ERROR] at jdk.compiler/com.sun.tools.javac.comp.Enter.main(Enter.java:554) [ERROR] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:1052) [ERROR] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:923) [ERROR] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:302) [ERROR] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:162) [ERROR] at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:57) [ERROR] at jdk.compiler/com.sun.tools.javac.Main.main(Main.java:43) {code} h5.Expected result: 1. The build should be successful.
| 5 |
3,228 |
TIMOB-25914
|
03/29/2018 15:10:06
|
Windows: ReferenceError: __ is not defined when building a module where the apiversion does not match
|
h5.Description When there is an apiversion mismatch between the SDK and a module then the CLI will error with the below {code} C:\ProgramData\Titanium\mobilesdk\win32\7.1.1.v20180327164201\windows\cli\commands\_buildModule.js:51 logger.error(__('The module manifest apiversion is currently set to %s', manifest.apiversion)); ^ ReferenceError: __ is not defined at WindowsModuleBuilder.validate (C:\ProgramData\Titanium\mobilesdk\win32\7.1.1.v20180327164201\windows\cli\commands\_buildModule.js:51:10) at Object.exports.validatePlatformOptions (C:\ProgramData\Titanium\mobilesdk\win32\7.1.1.v20180327164201\node_modules\node-titanium-sdk\lib\titanium.js:673:69) {code} h5.Steps to reproduce 1. Create a windows module or download an existing one like ti.paint 2. Change the apiversion in the manifest file 3. Build the module using {{ti build -p windows --build-only}} h5.Actual Build errors with the above h5.Expected Build should not error
| 1 |
3,229 |
TIMOB-25917
|
03/30/2018 14:15:35
|
Android: Allow picker minDate/maxDate properties to be set dynamically
|
On iOS it is possible to change the minDate/maxDate on runtime, on Android this is not possible due to TiSDK constraint in the code. Test code {code:js} var win = Ti.UI.createWindow({ title: 'Form', }); /* // working var dp = Ti.UI.createPicker({ type: Ti.UI.PICKER_TYPE_DATE, minDate: new Date(2018,1,1) }); */ var dp = Ti.UI.createPicker({ type: Ti.UI.PICKER_TYPE_DATE }); // not working dp.setMinDate(new Date(2018,1,1)); win.add(dp); dp.showDatePickerDialog(); win.open(); {code} *Observed Behaviour:* Setting minDate on creation works, adjusting it after doesn't *Expected behaviour*: On Android setting minDate/maxDate on runtime (after creation) should work as it does on iOS. *Community Credit*: Joren Vos for finding the issue, Michael Gangolf for helping locating the problem/creating test code.
| 3 |
3,230 |
TIMOB-25919
|
03/30/2018 19:36:09
|
Android: OptionDialog not firing "click" event for cancel button like iOS
|
h5. Issue: Customer is having and issue with the ClickEvent of a Ti.UI.OptionDialog in Android. If 'cancel' property is set to an index, clicking that cancel option or clicking outside the dialog doesn't fire the dialog's 'click' event. This is the behavior in SDK 7.1.0.GA whereas it is working fine in SDK 6.2.2.GA. h5: App: [^TestInputDialog.zip] h5. Steps to reproduce: 1. Run the attached project - TestInputDialog in Android. 2. Click on 'Hello World' text. OptionDialog will be displayed. 3. Click on 'Cancel' option in the dialog. Log statement in the dialog's corresponding click event handler will not be displayed in console. 4. Dismiss dialog by clicking outside the dialog. Click event of the dialog will not be triggered 4. Remove 'cancel' property in the dialog options while creating it(line 8 in index.js) and repeat the above steps. 5. Clicking the 'Cancel' option or anywhere outside the dialog will print the log statement.
| 2 |
3,231 |
TIMOB-25920
|
03/30/2018 20:00:50
|
Android: Build fails if SDK with JDK 9/10 fix is not selected in CLI & tiapp.xml (only if ran from CLI)
|
I am not sure if this is an issue or its just to be like this due to the architecture of CLI & SDK. What I am seeing is if I do not have an SDK with the new JDK 9/10 detection fix in both the CLI & tiapp.xml the build fails. h5.Steps to reproduce: *A. SDK with jdk 9/10 fix selected in the CLI & 7.1.0.GA in tiapp.xml:* 1. Make sure you have CLI core 7.0.3-master.24 installed which has the jdk 9/10 fix. 2. Create an app with SDK 7.1.0.GA (this will have sdk 7.1.0.GA in the tiapp.xml). 3. Make sure you have the SDK with the jdk 9/10 selected in the CLI. 4. Build for android. 5. Build fails with: {code} [INFO] tiapp.xml <sdk-version> set to 7.1.0.GA, but current Titanium SDK set to 7.2.0.v20180328162916 [INFO] Forking correct SDK command: "/usr/local/bin/node" "/Users/lchoudhary/.appcelerator/install/7.0.3-master.24/package/node_modules/titanium/lib/titanium.js" "build" "--sdk" "7.1.0.GA" "--no-banner" "--config-file" "/var/folders/pk/k370szc955l_9w7hsb9nfvg00000gq/T/build-1522435392553.json" "--platform" "android" "--project-dir" "/Users/lchoudhary/Desktop/lokitest" "--log-level" "trace" "--android-sdk" "/Users/lchoudhary/Desktop/android-sdk-macosx" "--target" "emulator" [ERROR] JDK (Java Development Kit) not found. [ERROR] If you already have installed the JDK, verify your JAVA_HOME environment variable is correctly set. [ERROR] The JDK can be downloaded and installed from http://appcelerator.com/jdk. {code} *B. 7.1.0.GA in selected in CLI & SDK with jdk 9/10 fix in the tiapp.xml:* 1. Make sure you have CLI core 7.0.3-master.24 installed which has the jdk 9/10 fix. 2. Select 7.1.0.GA in CLI & have sdk with jdk9/10 fix in tiapp.xml. 3. Build for android. 4. Build fails with: {code} [ERROR] JDK (Java Development Kit) not found. [ERROR] If you already have installed the JDK, verify your JAVA_HOME environment variable is correctly set. [ERROR] The JDK can be downloaded and installed from http://appcelerator.com/jdk. {code} Expected result: For A : Probably fail For B : Probably should not fail with JDK not found error.
| 2 |
3,232 |
TIMOB-25923
|
04/02/2018 09:13:30
|
Windows: More options for Logo / Splash Screen
|
The package manifest's [VisualElements|https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/appxmanifestschema2013/element-visualelements] supports more options for visual elements such as wide asset in {{DefaultTile}} with scales. Titanium supports few of them. Titanium should be able to provide more flexible way to specify them in any way. See also [tile and icon assets|https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/app-assets#asset-size-tables].
| 13 |
3,233 |
TIMOB-25928
|
04/04/2018 10:38:16
|
iOS: Closing a window with "tabBarHidden" property while modal window is open hides TabGroup bar
|
In a certain flow it is possible to permanently hide the tabbar even though it is not according to spec. It can be recreated using the following flow: - open window with {{tabbarhidden}} property on true in tab - open modal window on top of this - close window with {{tabbarhidden}} property - close modal window Now, while the tabbar should be visible again, the tabbar is actually hidden. Only way to re-enable it is to open another window in the tabgroup with the {{tabbarhidden}} property and then manually close it again without the modal present. This seems to trigger a refresh. Below code to reproduce {code:js} Ti.UI.backgroundColor = 'white'; var tabGroup = Ti.UI.createTabGroup(); var window1 = Ti.UI.createWindow({ title: 'Window 1' }); var tab1 = Ti.UI.createTab({ title: 'Tab 1', window: window1 }); var window2 = Ti.UI.createWindow({ title: 'Window 2' }); var tab2 = Ti.UI.createTab({ title: 'Tab 2', window: window2 }); tabGroup.addTab(tab1); tabGroup.addTab(tab2); tabGroup.addEventListener('open', doStuff); tabGroup.open(); // below is test code to reproduce the issue function doStuff() { Ti.API.info('START!'); var secondWindow = Ti.UI.createWindow({ tabBarHidden: true, title: "2nd window no tabbar" }); var modalWindow = Ti.UI.createWindow(); var nav = Ti.UI.iOS.createNavigationWindow({ window: modalWindow }); setTimeout(function() { // open tabbarhidden window in tabgroup tab1.openWindow(secondWindow); setTimeout(function() { // open modal nav.open({ modal: true }); setTimeout(function() { // close tabbarhidden window in tabgroup while modal is open secondWindow.close(); setTimeout(function() { // close modal window, now tabbar is gone nav.close(); }, 1000); }, 1000); }, 1000); }, 2500); } {code}
| 1 |
3,234 |
TIMOB-25931
|
04/04/2018 20:00:13
|
Android: Update Multi-Dex support library
|
Our current {{android-support-multidex.jar}} is from 2015. We should update it to the latest {{1.0.3}} from March 2018.
| 3 |
3,235 |
TIMOB-25932
|
04/04/2018 20:04:55
|
Android: Cannot build SDK with JDK 10 (missing javah tool)
|
*Summary:* If you attempt to build the Titanium SDK (ie: titanium_mobile) with JDK 10 installed, the build will fail due to a missing "javah" tool. This tool has been removed in JDK 10. *Steps to reproduce:* # Instal JDK 10 if not done already. # Open the terminal. # {{cd}} to the {{titanium_mobile/build}} directory. # Enter: {{node scons.js build android}} *Result:* Build fails due to missing "javah" tool. *Work-Around:* Build with JDK 8 or 9. *Recommended Solution:* Remove Titanium's usage of the "javah" tool and the {{#include}}'s to the generated headers files. They're not needed. The generated header files and function prototypes are useless by themselves. We have to create the function implementation ourselves, which we've already done and they're already publicly exported via {{JNIEXPORT}} in their respective C++ files. Since the implementation side already exports the functions, the function prototypes are not needed. https://github.com/appcelerator/titanium_mobile/blob/master/android/runtime/v8/src/native/JSDebugger.cpp https://github.com/appcelerator/titanium_mobile/blob/master/android/runtime/v8/src/native/V8Object.cpp https://github.com/appcelerator/titanium_mobile/blob/master/android/runtime/v8/src/native/V8Runtime.cpp ---- *Original Description:* JDK 10 has dropped the {{javah}} tool (http://openjdk.java.net/jeps/313) which is required by our tooling when building the Android platform. We need to use {{javac}}'s {{-h}} flag instead. {{javah}} generated the header files from the compiled {{.class}} files in the jars, however {{javac -h}} used the original {{.java}} files. We'll likely have to move the header generation out of the native compile step and into the Java compile step. We can do this by specifying the {{nativeheaderdir}} attribute in the {{javac}} task in the {{common.xml}} file. However, the {{nativeheaderdir}} attribute is only supported in ant 1.9.8+ (https://ant.apache.org/manual/Tasks/javac.html) and we ship {{ant}} 1.8.0 with Titanium. The Android build also depends on {{ant-contrib}} and {{ant-nodeps}} which may not be compatible with ant 1.9.8 or newer. In the meantime, we'll have to use JDK 9 to build the Titanium SDK.
| 3 |
3,236 |
TIMOB-25933
|
04/05/2018 07:07:32
|
Windows: Implement Ti.UI.TextField.padding
|
[Ti.UI.TextField.padding|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.TextField-property-padding] property is not implemented on Windows.
| 8 |
3,237 |
TIMOB-25935
|
04/05/2018 09:00:00
|
Windows: Ti.Utils.base64decode should ignore line breaks
|
{{Ti.Utils.base64decode}} should trim trailing line breaks to keep parity with other platforms. {code} var str = 'RGVjb2Rpbmcgc3VjY2Vzc2Z1bCE=\n'; var blob = Ti.Utils.base64decode(str); Ti.API.info(blob.getText()); {code} Expected: This should print "Decoding successful!"
| 5 |
3,238 |
TIMOB-25936
|
04/05/2018 19:20:53
|
iOS: TableView: Appending row immediately after a section appends them before the section
|
In a TableView, when appending a row immediately after appending a section, the elements appear in the reverse order (row and then section). *Steps to reproduce issue*: 1. Create a classic app with the below code 2. Run the app *Expected Results*: Each section has 3 rows under it *Actual Results*: All of the rows appear first, then the sections *Notes*: In the example, you can click on the window to add another section and row that also appear in reverse order. {code} var win = Ti.UI.createWindow({ backgroundColor: "#f00" }); var table = Ti.UI.createTableView(); for (var i = 0; i < 2; ++i) { table.appendSection(Ti.UI.createTableViewSection({ headerTitle: "Header " + i, className: "Header" })); for (var j = 0; j < 3; j++) { table.appendRow(Ti.UI.createTableViewRow({ title: "Row " + j, className: "Row" })); } } win.addEventListener("click", function() { table.appendSection(Ti.UI.createTableViewSection({ headerTitle: "Title", className: "Header" })); table.appendRow(Ti.UI.createTableViewRow({ title: "Row ", className: "Row" })); }); win.add(table); win.open(); {code}
| 1 |
3,239 |
TIMOB-25937
|
04/05/2018 22:16:21
|
Android: Horizontal TextField scrolling should not be canceled by scrollable parent view
|
*Summary:* When a TextField is within a vertical ListView, ScrollView, or TableView... horizontal TextField scrolling will be canceled if you drag your finger too far up/down and the vertically scrolling parent view will steal/intercept all touch events from there. This makes scrolling a TextField difficult. *Expected Behavior:* Once horizontal scrolling has started in a TextField, the parent view should no longer be able to scroll vertically until your finger has been released. *Steps to Reproduce:* # Build/run the below code on Android. # Start dragging a TextField horizontally. # As you drag it horizontally, drag up or down. # Notice that the TextField no longer scrolls horizontally and you're now vertically scrolling the parent ScrollView instead. {code:javascript} var window = Ti.UI.createWindow(); var scrollView = Ti.UI.createScrollView( { showVerticalScrollIndicator: true, layout: "vertical", }); for (var index = 1; index <= 20; index++) { var row = Ti.UI.createView( { layout: "horizontal", width: Ti.UI.FILL, height: Ti.UI.SIZE, }); row.add(Ti.UI.createLabel( { text: "Row " + index.toString(), left: "5dp", })); row.add(Ti.UI.createTextField( { value: "Welcome to the Appcelerator Platform! The Appcelerator Platform helps you develop cross-platform mobile applications using the Titanium SDK, Alloy, Appcelerator Studio and the Appcelerator CLI, then lets you manage the entire lifecycle of the application with debugging, testing, deploying, crash monitoring and analytic data collection.", left: "5dp", right: "5dp", width: Ti.UI.FILL, height: Ti.UI.SIZE, })); scrollView.add(row); } window.add(scrollView); window.open(); {code} *Notes:* * A vertical scrolling TextArea does not have this problem since it supports "nested" scrolling. * iOS does not allow horizontal scrolling of a TextField at all while in a vertically scrolling parent, but I don't think we should match this behavior on Android since it makes it less convenient to use.
| 3 |
3,240 |
TIMOB-25939
|
04/05/2018 22:53:34
|
Android: Improve horizontal ScrollView scrolling that is set up with a RefreshControl
|
*Summary:* When a horizontal {{ScrollView}} has been assigned a {{RefreshControl}}, it is difficult to scroll it horizontally. While scrolling it horizontally, if you slightly drag your finger up/down, the {{RefreshControl}} will then cancel horizontal scrolling and then steal/intercept all touch events. *Steps to Reproduce:* # Build and run the below code on Android. # Start dragging the {{ScrollView}} horizontally. # As you drag it horizontally, drag down without lifting your finger from the screen. # Notice that the {{RefreshControl}} progress circle is being pulled down by your finger. # As you drag down, attempt to drag horizontally without lifting your finger from the screen. # Notice that you can no longer scroll the {{ScrollView}} horizontally anymore. {code:javascript} var window = Ti.UI.createWindow( { fullscreen: true, layout: "vertical", backgroundColor: "white", }); var refreshControl = Ti.UI.createRefreshControl( { title: Ti.UI.createAttributedString({ text: "Refreshing" }), tintColor: "red", }); refreshControl.addEventListener("refreshstart", function(e) { Ti.API.info("@@@ 'refreshstart' event received."); setTimeout(function() { if (!scrollView.refreshCount) { scrollView.refreshCount = 1; } else { scrollView.refreshCount++; } scrollView.add(Ti.UI.createLabel( { text: "Refresh " + scrollView.refreshCount.toString(), textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER, color: "white", backgroundColor: "gray", left: "5dp", })); refreshControl.endRefreshing(); }, 2000); }); var scrollView = Ti.UI.createScrollView( { refreshControl: refreshControl, layout: "horizontal", scrollType: "horizontal", showVerticalScrollIndicator: false, showHorizontalScrollIndicator: true, width: Ti.UI.FILL, height: "90%", }); scrollView.add(Ti.UI.createLabel( { text: "Pull\nDown\nto\nRefresh", textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER, color: "white", backgroundColor: "black", height: Ti.UI.FILL, })); for (var index = 1; index <= 10; index++) { scrollView.add(Ti.UI.createLabel( { text: "Label " + index.toString(), textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER, color: "white", backgroundColor: "gray", left: "5dp", })); } window.add(scrollView); window.add(Ti.UI.createLabel( { text: "Horizontal ScrollView", textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER, color: "white", backgroundColor: "blue", width: Ti.UI.FILL, height: Ti.UI.FILL, })); window.open(); {code} *Expected Result:* Once you start scrolling horizontally, you should not be able to pull down the {{RefreshControl}} progress circle. It should only allow horizontally scrolling. And if you start dragging vertically, it should only pull down the {{RefreshControl}} and not allow horizontal scrolling of the {{ScrollView}}. It should only be one or the other since it's too difficult for a person to drag perfectly horizontally or vertically. *Cause:* This happens because Google's Java {{HorizontalScrollView}} class does not support nested scrolling. Google's {{SwipeRefreshLayout}} ignores a {{requestDisallowInterceptTouchEvent()}} method calls from child views that do not support nested scrolling, which causes it to intercept all touch events once you drag vertically. [SwipeRefreshLayout.java#L735|https://github.com/aosp-mirror/platform_frameworks_support/blob/master/core-ui/src/main/java/android/support/v4/widget/SwipeRefreshLayout.java#L735] *Note:* This is not an issue with a vertical {{ScrollView}} using a {{RefreshControl}}. This is only an issue with a horizontal {{ScrollView}}.
| 3 |
3,241 |
TIMOB-25942
|
04/06/2018 14:32:59
|
iOS 11: Screen orientation not working in navigation window
|
Hello, We are seeing a screen orientation problem as windows are being open from a root navigation modal window. *Steps to reproduce:* 1. Open the sample application in [link|https://drive.google.com/file/d/1n6lNK6bDwtQBDekMOAQE4mjoqjZeKpgk/view?usp=sharing] or use the below-provided code. 2. Run the application in an iOS simulator using below code Or 3. Run the sample application in the simulator. 4. Switch the simulator's device orientation to "UPSIDE DOWN" 5. Click on the link on the main app screen labeled "Launch Nav Root Window" 6. Once the window titled "Modal 1" window is opened, then click the "Next" nav button 7. The window titled "Modal 2" should not have the correct orientation. *Test Code:* index.xml {code} <Alloy> <Window class="container" backgroundColor="#666600"> <Button onClick="launchNavRoot">Launch Nav Root Window</Button> </Window> </Alloy> {code} *Modal1.xml, Modal3.xml, Modal3.xml, Modal4.xml, Modal5.xml* {code} //Modal1.xml <Alloy> <NavigationWindow> <Window backgroundColor="#808000"> <RightNavButton> <Button title="Next" onClick="onNext"/> </RightNavButton> <View layout="vertical"> <Label text="MODAL 1"></Label> <Label text="MODAL 1"></Label> <Label text="MODAL 1"></Label> <Label text="MODAL 1"></Label> </View> </Window> </NavigationWindow> </Alloy> //Modal2.xml <Alloy> <Window backgroundColor="#999900"> <RightNavButton> <Button title="Next" onClick="onNext"/> </RightNavButton> <View layout="vertical"> <Label text="MODAL 2"></Label> <Label text="MODAL 2"></Label> <Label text="MODAL 2"></Label> <Label text="MODAL 2"></Label> </View> </Window> </Alloy> //Modal3.xml <Alloy> <Window backgroundColor="#b3b300"> <RightNavButton> <Button title="Next" onClick="onNext"/> </RightNavButton> <View layout="vertical"> <Label text="MODAL 3"></Label> <Label text="MODAL 3"></Label> <Label text="MODAL 3"></Label> <Label text="MODAL 3"></Label> </View> </Window> </Alloy> //Modal4.xml <Alloy> <Window backgroundColor="#cccc00"> <RightNavButton> <Button title="Next" onClick="onNext"/> </RightNavButton> <View layout="vertical"> <Label text="MODAL 4"></Label> <Label text="MODAL 4"></Label> <Label text="MODAL 4"></Label> <Label text="MODAL 4"></Label> </View> </Window> </Alloy> //Modal5.xml <Alloy> <Window backgroundColor="#e6e600"> <View layout="vertical"> <Label text="MODAL 5"></Label> <Label text="MODAL 5"></Label> <Label text="MODAL 5"></Label> <Label text="MODAL 5"></Label> </View> </Window> </Alloy> {code} *Modal1.js, Modal3.js, Modal3.js, Modal4.js, Modal5.js* {code} //Modal1.js var args = $.args; function onNext() { var modal2 = Alloy.createController("Modal2").getView(); Alloy.Globals.navRoot.openWindow(modal2); } //Modal2.js var args = $.args; function onNext() { var modal2 = Alloy.createController("Modal2").getView(); Alloy.Globals.navRoot.openWindow(modal2); } //Modal3.js var args = $.args; function onNext() { var modal3 = Alloy.createController("Modal3").getView(); Alloy.Globals.navRoot.openWindow(modal3); } //Modal4.js var args = $.args; function onNext() { var modal4 = Alloy.createController("Modal4").getView(); Alloy.Globals.navRoot.openWindow(modal4); } //Modal5.js var args = $.args; function onNext() { var modal5 = Alloy.createController("Modal5").getView(); Alloy.Globals.navRoot.openWindow(modal5); } {code} tiapp.xml {code} <ios> <enable-launch-screen-storyboard>true</enable-launch-screen-storyboard> <use-app-thinning>true</use-app-thinning> <plist> <dict> <key>UISupportedInterfaceOrientations~iphone</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array> <key>UISupportedInterfaceOrientations~ipad</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array> <key>UIRequiresPersistentWiFi</key> <false/> <key>UIPrerenderedIcon</key> <false/> <key>UIStatusBarHidden</key> <false/> <key>UIStatusBarStyle</key> <string>UIStatusBarStyleDefault</string> </dict> </plist> </ios> {code} *Test Environment:* Using latest SDK 7.1.0.GA, 7.0.1.GA Latest CLI 7.0.2 The Screen orientation not working in navigation window on iPhone. Thanks
| 13 |
3,242 |
TIMOB-25943
|
04/06/2018 19:20:43
|
Windows: Unable to install to device with JDK 9
|
I am unable to install to a device with JDK 9 this is due to [package.json|https://github.com/appcelerator/titanium_mobile_windows/blob/master/package.json#L32]. When I change the package.json to allow JDK 9 it installs to the device but the application crashes immediately with no error log. h4. Actual {noformat} [ERROR] : JDK version 9.0.4 detected, but only version <=1.8.x is supported {noformat} h4. Expected No error is thrown.
| 5 |
3,243 |
TIMOB-25944
|
04/06/2018 19:56:39
|
CLI: Block-scoped declaration error when using Node 4
|
h5.Description When performing any Titanium CLI action (build, clean etc.) when using Node 4, the CLI will throw an error like the below {code} Titanium Command-Line Interface, CLI version 5.1.0, Titanium SDK version 7.1.1.v20180405080421 Copyright (c) 2012-2017, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ [ERROR] Failed to load command "clean" [ERROR] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode Error at Object.<anonymous> (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/exception.js:33:27) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.defineProperty.get (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/appc.js:63:11) at Object.<anonymous> (/usr/local/lib/node_modules/titanium/lib/context.js:30:22) at Module._compile (module.js:409:26) {code} h5.Steps to reproduce 1. Execute a command like {{ti clean}} using node 4 h5.Actual Error above h5.Expected CLI should function as we should break supported versions in a non-major release. Although Node 4 does go end-of-life at the end of the month, so we should not promote using it
| 1 |
3,244 |
TIMOB-25946
|
04/09/2018 06:57:44
|
Windows: Implement Ti.UI.TextArea.padding
|
[Ti.UI.TextArea.padding|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.TextArea-property-padding] property is not implemented on Windows.
| 5 |
3,245 |
TIMOB-25949
|
04/10/2018 08:30:30
|
Windows: Wrong layout with bottom/right and center
|
{{bottom}} property is not calculated property when it is used with {{center}} property. {code:javascript} var view1 = Ti.UI.createView({ width: 400, height: 400, backgroundColor: 'white' }), view2 = Ti.UI.createView({ backgroundColor: 'blue', center: { x: 200, y: 200 }, width: 100, bottom: 100 }), view3 = Ti.UI.createView({ backgroundColor: 'red', width: Ti.UI.FILL, height: 1, bottom: 100 }); var win = Ti.UI.createWindow({ backgroundColor: 'green' }); view1.add(view2); view1.add(view3); win.add(view1); win.open(); {code} Actual: The blue box ({{view2}}) and ed line ({{view3}}) are not aligned !b.png|thumbnail! Expected: The blue box ({{view2}}) should be aligned with red line ({{view3}}). !a.png|thumbnail! More test cases: {code:javascript} var view = Ti.UI.createView({ height: 200, width: 200, backgroundColor: 'gray' }), viewChild = Ti.UI.createView({ backgroundColor: 'blue', center: { x: 100 }, right: 50 }), line = Ti.UI.createView({ backgroundColor: 'red', width: 1, height: Ti.UI.FILL, right: 50, top: 0 }); var win = Ti.UI.createWindow(); viewChild.addEventListener('postlayout', function () { Ti.API.info(viewChild.size.width + ' should eql(100)'); }); view.add(viewChild); view.add(line); win.add(view); win.open(); {code} {code:javascript} var view = Ti.UI.createView({ height: 200, width: 200, backgroundColor: 'gray' }), viewChild = Ti.UI.createView({ backgroundColor: 'blue', center: { y: 100 }, bottom: 50 }), line = Ti.UI.createView({ backgroundColor: 'red', width: Ti.UI.FILL, height: 1, bottom: 50, left: 0 }); var win = Ti.UI.createWindow(); viewChild.addEventListener('postlayout', function () { Ti.API.info(viewChild.size.width + ' should eql(200)'); }); view.add(viewChild); view.add(line); win.add(view); win.open(); {code}
| 8 |
3,246 |
TIMOB-25950
|
04/10/2018 09:03:15
|
iOS: setUnselectedItemTintColor is unrecognized in iOS9
|
The Ti.UI.TabGroup property "unselectedItemTintColor" is only available on iOS 10+ and should be guarded. PR: https://github.com/appcelerator/titanium_mobile/pull/9991
| 1 |
3,247 |
TIMOB-25952
|
04/10/2018 15:00:34
|
iOS: Listview setHeaderView with search is not working
|
Hello ! We have an issue with Listview setHeaderView with search. HeaderView is not displayed on iOS with search bar but its working on android. Test code: {code} var popularSearchList = [], searchList = [], popularSearchListData = [], searchListData = []; for (var i = 0; i < 5; i++) { popularSearchList.push({ id : i, name : "Bhuvan " + i }); } searchList.push({ id : 0, name : "ListView" }, { id : 1, name : "TextField" }, { id : 2, name : "EditText" }, { id : 3, name : "Spinner" }, { id : 4, name : "Button" }, { id : 5, name : "ImageView" }, { id : 6, name : "ImageButton" }, { id : 7, name : "RecyclerView" }, { id : 8, name : "CardView" }); showRecentSearchList(popularSearchList); showSearchList(searchList); function showRecentSearchList(popularSearchList) { _.each(popularSearchList, function(popularSearchDataObj) { var listRowObj = { lblRecentSearchItem : { text : popularSearchDataObj.name }, rowName : popularSearchDataObj.name, template : "recentSearchListTemplate", }; popularSearchListData.push(listRowObj); }); $.lvSearchList.sections[0].setHeaderView(addRecentSectionHeader()); $.lvSearchList.sections[0].setItems(popularSearchListData); } function showSearchList(searchList) { _.each(searchList, function(searchListObj) { var listRowObj = { lblSearchItem : { text : searchListObj.name }, rowName : searchListObj.name, properties : { searchableText : searchListObj.name, }, template : "searchListTemplate" }; searchListData.push(listRowObj); }); //$.lvSearchList.sections[0].setHeaderView(addSearchSectionHeader()); //$.lvSearchList.sections[0].setItems(searchListData); } function searchAction(e) { $.lvSearchList.searchText = e.value; if (e.value.length > 0) { showListView(true); } else { showListView(false); } } function showListView(isSearchData) { //$.lvSearchList.sections[0].setHeaderView(addSearchSectionHeader()); if (isSearchData) { $.lvSearchList.sections[0].setHeaderView(addSearchSectionHeader()); $.lvSearchList.sections[0].setItems(searchListData); } else { $.lvSearchList.sections[0].setHeaderView(addRecentSectionHeader()); $.lvSearchList.sections[0].setItems(popularSearchListData); } } function addRecentSectionHeader() { var headerView = Ti.UI.createView({ width : Titanium.UI.FILL, height : 40, backgroundColor : 'white', layout : 'horizontal' }); var leftImage = Ti.UI.createImageView({ width : Titanium.UI.SIZE, height : Titanium.UI.SIZE, image : '/images/customer.png', left : 20, }); headerView.add(leftImage); var title = "RECENT"; var lblTitle = Titanium.UI.createLabel({ width : Titanium.UI.FILL, text : title, height : Titanium.UI.FILL, color : 'red', left : 20, font : { fontSize : 16, fontWeight : 'bold' } }); headerView.add(lblTitle); return headerView; } function addSearchSectionHeader() { var headerView = Ti.UI.createView({ width : Titanium.UI.FILL, height : 40, backgroundColor : 'white', layout : 'horizontal' }); var leftImage = Ti.UI.createImageView({ width : Titanium.UI.SIZE, height : Titanium.UI.SIZE, image : '/images/chassis.png', left : 20, }); headerView.add(leftImage); var title = "RESULTS"; var lblTitle = Titanium.UI.createLabel({ width : Titanium.UI.FILL, text : title, height : Titanium.UI.FILL, color : 'red', left : 20, font : { fontSize : 16, fontWeight : 'bold' } }); headerView.add(lblTitle); return headerView; } function cancelSearchAction(e) { } $.index.open(); {code} {code:xml} <Alloy> <Window class="container"> <View width="Titanium.UI.FILL" height="Titanium.UI.FILL" layout="vertical" top="25"> <View width="Titanium.UI.FILL" height="40" borderColor="green" borderWidth="2" left="10" right="10"> <SearchBar id="tfSearchField" onChange="searchAction" onCancel="cancelSearchAction" /> <!--<TextField id="tfSearchField" platform="ios" onChange="searchAction" onCancel="cancelSearchAction" />--> </View> <ListView id="lvSearchList" defaultItemTemplate="searchListItem"> <Templates> <ItemTemplate id="recentSearchListTemplate" name="recentSearchListTemplate"> <View id="viewRecentSearchList"> <Label id="lblRecentSearchItem" bindId="lblRecentSearchItem"/> <ImageView id="imgRightArrow"/> </View> </ItemTemplate> <ItemTemplate id="searchListTemplate" name="searchListTemplate"> <View id="viewSearchList"> <Label id="lblSearchItem" bindId="lblSearchItem"/> <ImageView id="imgRightArrow"/> </View> </ItemTemplate> </Templates> <ListSection/> </ListView> </View> </Window> </Alloy> {code} Full project ListviewSearch.zip Please take a look on attached screenshot for android and iOS. Teste Environment : {code} Operating System Name = Mac OS X Version = 10.13 Architecture = 64bit # CPUs = 4 Memory = 8589934592 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.0.14 Titanium SDK SDK Version = 7.1.0.GA {code} Thanks
| 1 |
3,248 |
TIMOB-25961
|
04/13/2018 04:10:50
|
iOS: e.orientation always returns 5 for landscape to FACE_UP and portrait to FACE_UP.
|
Basically, need to maintain the onset of UI when we in portrait and move up & down. Also another set of UI when are in landscape and move up&down. Eg: if( e.orientation === Ti.UI.PORTRAIT && e.orientation === Titanium.UI.FACE_UP){ updateUI(); } Also, if( (e.orientation === Ti.UI.LANDSCAPE_LEFT || e.orientation === Ti.UI.LANDSCAPE_RIGHT) && e.orientation === Titanium.UI.FACE_UP){ updateUI() } But it does not work. *Test Code:* {code:java} Ti.Gesture.addEventListener('orientationchange', function(e) { if (e.orientation == Titanium.UI.FACE_DOWN) { Ti.API.info("ORientation_FACE_DOWN:" + e.orientation); } else if (e.orientation == Titanium.UI.FACE_UP) { Ti.API.info("ORientation_FACE_UP:" + e.orientation); } else if (e.orientation == Titanium.UI.PORTRAIT) { Ti.API.info("ORientation_PORTRAIT:" + e.orientation); } else if (e.orientation == Titanium.UI.UPSIDE_PORTRAIT) { Ti.API.info("ORientation_UPSIDE_PORTRAIT:" + e.orientation); } else if (e.orientation == Titanium.UI.LANDSCAPE_LEFT) { Ti.API.info("ORientation_LANDSCAPE_LEFT:" + e.orientation); } else if (e.orientation == Titanium.UI.LANDSCAPE_RIGHT) { Ti.API.info("ORientation_LANDSCAPE_RIGHT:" + e.orientation); } else { Ti.API.info("ORientation_UNKNOWN:" + e.orientation); } if (e.orientation == Titanium.UI.PORTRAIT && e.orientation == Titanium.UI.FACE_UP) { //issue is here: cannot detect this position Ti.API.info("ORientation_PORTRAIT_FACE_UP:" + e.orientation); } if ((e.orientation == Ti.UI.LANDSCAPE_LEFT || e.orientation == Ti.UI.LANDSCAPE_RIGHT) && e.orientation == Titanium.UI.FACE_UP) { //issue is here: cannot detect this position Ti.API.info("ORientation_LANDSCAPE_:FACE_UP" + e.orientation); } }); {code} Thanks.
| 0 |
3,249 |
TIMOB-25963
|
04/13/2018 18:11:34
|
Android: Implement method to obtain current stack trace from V8
|
Currently, there it is not possible to obtain the current stack trace from V8 on the Java side of Titanium Android. - Implement a V8Runtime method to obtain the current stack trace - Report the stack trace upon runtime exceptions
| 5 |
3,250 |
TIMOB-25964
|
04/13/2018 21:44:40
|
Android: Merge manifest of Android Libraries
|
The AndroidManifest.xml of an Android Library (.aar) needs to be merged into the final app manifest.
| 2 |
3,251 |
TIMOB-25965
|
04/13/2018 23:50:59
|
Android: Update old exception dialog
|
The current exception dialog is ugly and provides little debugging information. We should update the dialog to a cleaner and clearer output that also provides a stack trace.
| 3 |
3,252 |
TIMOB-25968
|
04/16/2018 10:59:24
|
Liveview: Write more information to pidfile, such as port and ip data
|
h5.Description Currently when liveview writes its pidfile (at ~/.titanium), it only contains the path of the project, we should write more data to this (ip, fport, eport etc.) so that commands like stop/restart can function if the user defines a custom ip or port. It would probably make sense to turn this file into a json object like below {code} { "projectPath": "<path to project>", "ip": "127.0.0.1", "eport": "1234", "fport": "1235", "alloy: true, "platform": "android" } {code}
| 3 |
3,253 |
TIMOB-25971
|
04/17/2018 02:44:39
|
iOS: minimumFontSize property in Ti.UI.label lowers text baseline as it decreases
|
We've observed this problem for quite a while (I think it might also be in SDK 5.5) but it was one of those "am I seeing things or is this really happening?" bugs. I finally sat down and ran some test cases and it is really happening. As the attached test code shows, set the original font size such that the string does not fit the width of the label. Then steadily decrease minimumFontSize until the string fits. The string eventually fits into the label but the baseline of the text drops a little bit every time minimumFontSize is decreased. We set borderWidth to 2 so that you can see the text move relative to the boundaries of the label. We have several apps that require this functionality - it used to work properly somewhere in the SDK 5 generation. The same code runs correctly on Android 7.1 (see screenshot)
| 0 |
3,254 |
TIMOB-25975
|
04/17/2018 08:26:16
|
Android: Embedded youtube video is not playing due to Chrome bug
|
Hi, I am trying to display the youtube video with embedded URL. Here I am trying to assign the embedded URL to URL property of Webview. This is running fine on iOS but on Android, we are having some issues. Please find the log we are getting while doing this. [INFO] : I/TiWebChromeClient.console: (main) [456,456] Error parsing header X-XSS-Protection: 1; mode=block; report=https://www.google.com/appserve/security-bugs/log/youtube: insecure reporting URL for secure page at character position 22. The default protections will be applied. (0:https://www.youtube.com/embed/xyz?list=xyz-l) Can you please try on your end and let me know if this is valid.
| 0 |
3,255 |
TIMOB-25977
|
04/19/2018 15:31:26
|
Android: AlertDialog not firing "click" event when canceled
|
The alert dialog doesn't fire a cancel event if you press outside of the alertDialog box in 7.1.0. The event listener actually doesn't console anything if done this way. If you switch it back to 6.2.2 it works correctly and fires the eventlistener when the user touches outside of the alert dialog. Make a sample AppSellHerHater project and paste the index.js below. Then build to android on 7.1.0 and watch it not work. Then build with 6.2.2 and watch it work correctly. {code:java} //Replace the index.js code with this function doClick(e) { myAlert.show(); } $.index.open(); var myAlert = Ti.UI.createAlertDialog({ cancel: 1, buttonNames: ['Ok', 'Cancel'], message: "Event listener doesn't fire if you press outside of alert on android...", title: 'Confirm Ok' }); myAlert.addEventListener('click', function(e) { console.info('e.index: ' + e.index); $.label.text = (e.index == 0) ? "You pressed 'Ok'..." : "You cancelled the alert..."; alert('e.index: ' + e.index); }); {code}
| 2 |
3,256 |
TIMOB-25979
|
04/20/2018 17:21:43
|
Android: Changing index break events on TableViewRow
|
When we populate TableView with TableViewRows and then change their order with updateRow method it will prevent firing events on the TableViewRow with lowest index. This includes click and touchstart events. Code to reproduce: {code} var window = Ti.UI.createWindow(); window.open(); var container = Ti.UI.createView({ backgroundColor: '#333' }); var tableView = Ti.UI.createTableView({ backgroundColor: 'white' }); var row1 = Ti.UI.createTableViewRow({ height: 50, backgroundColor: 'red', className: 'scheduled' }); var row2 = Ti.UI.createTableViewRow({ height: 50, backgroundColor: 'green', className: 'scheduled' }); var row3 = Ti.UI.createTableViewRow({ height: 50, backgroundColor: 'yellow', className: 'scheduled' }); tableView.appendRow(row1); tableView.appendRow(row2); tableView.appendRow(row3); tableView.updateRow(0, row3); //this row will stop to react on events tableView.updateRow(1, row2); tableView.updateRow(2, row1); container.add(tableView); window.add(container); tableView.addEventListener('click', function() {alert('clickFromTableView');}); container.addEventListener('click', function() {alert('clickFromContainer');}); {code}
| 3 |
3,257 |
TIMOB-25981
|
04/23/2018 06:10:28
|
Windows: nuget support for Hyperloop
|
Investigate {{nuget}} support for hyperloop, similar to how iOS has support for cocoapods.
| 13 |
3,258 |
TIMOB-25983
|
04/23/2018 18:54:17
|
Windows : Ti.UI.TextArea is not wrapped when there is long text, it just show in single line
|
Hello ! Ti.UI.createTextArea is not wrapped when there is long text, it just show in single line in windows phone. But it wrapped in android. Teste code : {code} Ti.UI.setBackgroundColor('white'); var controlsHeight = 38 * Ti.App.MultiplyFactor; var win = Ti.UI.createWindow({ backgroundColor : 'white', exitOnClose : true, fullscreen : false }); var textArea = Ti.UI.createTextArea({ width : Ti.UI.FILL, backgroundColor : 'white', color : 'black', left : 40, right : 40, hintText : 'this is a long hint that is not wrapping in windows version. Not sure what is the problem. All text show in single line instead of multi line. please check' }); textArea.value = 'this is a long hint that is not wrapping in windows version. Not sure what is the problem. All text show in single line instead of multi line. please check'; win.add(textArea); win.open(); {code} Test Environment: {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 Architecture = 32bit # CPUs = 4 Memory = 17091956736 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.0.14 Titanium SDK SDK Version = 7.1.0.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\7.1.0.GA Target Platform = windows {code} Please take a look on attached screenshot.
| 8 |
3,259 |
TIMOB-25986
|
04/24/2018 15:36:01
|
Windows: Physical pixel as a unit in views and fonts is not working
|
Hi ! Using the current Ti SDK GA 7.1.0 Windows applications do not recognize widths nor heights set as pixels. Also the fonts seem to be hardcoded to DIP since they don't change when specifying "18px" as a value. See attached app folder of an alloy application that has 4 boxes, each with a different unit (px, dip, dp and pt) *Test Project*: [^app.zip] Our application requires us to have a 1920x1400 canvas to display all the elements needed. However if the user has a screen with 2736x1824 @ 200%, the actual dip that we can use are 1368x912 The device is a surface 4 pro.
| 13 |
3,260 |
TIMOB-25989
|
04/25/2018 05:04:32
|
Windows: Unit specifier is ignored for font size
|
Changing unit specifier for font size does not change font size. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green', }); var view1 = Ti.UI.createView({ backgroundColor: 'red', top: 10, left: 10, width: '50', height: '50' }); var label1 = Ti.UI.createLabel({ text: 'DEF', font: { fontSize: '18' } }); view1.add(label1); var view2 = Ti.UI.createView({ backgroundColor: 'red', top: 70, left: 10, width: '50px', height: '50px' }); var label2 = Ti.UI.createLabel({ text: 'PX', font: { fontSize: '18px' } }); view2.add(label2); var view3 = Ti.UI.createView({ backgroundColor: 'red', top: 130, left: 10, width: '50dp', height: '50dp' }); var label3 = Ti.UI.createLabel({ text: 'DP', font: { fontSize: '18dp' } }); view3.add(label3); var view4 = Ti.UI.createView({ backgroundColor: 'red', top: 200, left: 10, width: '50dip', height: '50dip' }); var label4 = Ti.UI.createLabel({ text: 'DIP', font: { fontSize: '18dip' } }); view4.add(label4); var view5 = Ti.UI.createView({ backgroundColor: 'red', top: 270, left: 10, width: '50pt', height: '50pt' }); var label5= Ti.UI.createLabel({ text: 'PT', font: { fontSize: '18pt' } }); view5.add(label5); win.add(view1); win.add(view2); win.add(view3); win.add(view4); win.add(view5); win.open(); {code}
| 5 |
3,261 |
TIMOB-25990
|
04/25/2018 19:42:18
|
Android apps crash when trying to add views to Titanium.Media.VideoPlayer objects if fullscreen property is set to true.
|
Android apps crash when trying to add views to Titanium.Media.VideoPlayer objects if fullscreen property is set to true. The sample code in the documentation exhibits the crash (see snippet under Android Fullscreen Video Player here, https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Media.VideoPlayer). See attached for example project. When the block that adds the closeButton is removed there is no crash. {code} [INFO] : APSAnalyticsService: Stopping Analytics Service [WARN] : MediaPlayer: Couldn't open file on client side; trying server side: java.io.FileNotFoundException: No content provider: http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4 [INFO] : MediaPlayer: It's not a proxy project. [ERROR] : TiApplication: (main) [109667,109667] Sending event: exception on thread: main msg:java.lang.ClassCastException: ti.modules.titanium.media.TiVideoActivity cannot be cast to org.appcelerator.titanium.TiBaseActivity; Titanium 7.1.0,2018/03/14 13:40,undefined [ERROR] : TiApplication: java.lang.ClassCastException: ti.modules.titanium.media.TiVideoActivity cannot be cast to org.appcelerator.titanium.TiBaseActivity [ERROR] : TiApplication: at org.appcelerator.titanium.proxy.TiViewProxy.handleGetView(TiViewProxy.java:562) [ERROR] : TiApplication: at org.appcelerator.titanium.proxy.TiViewProxy.getOrCreateView(TiViewProxy.java:549) [ERROR] : TiApplication: at org.appcelerator.titanium.proxy.TiViewProxy.realizeViews(TiViewProxy.java:593) [ERROR] : TiApplication: at ti.modules.titanium.media.VideoPlayerProxy.setVideoViewFromActivity(VideoPlayerProxy.java:136) [ERROR] : TiApplication: at ti.modules.titanium.media.VideoPlayerProxy.access$200(VideoPlayerProxy.java:51) [ERROR] : TiApplication: at ti.modules.titanium.media.VideoPlayerProxy$1.handleMessage(VideoPlayerProxy.java:224) [ERROR] : TiApplication: at android.os.Handler.dispatchMessage(Handler.java:98) [ERROR] : TiApplication: at android.os.Looper.loop(Looper.java:168) [ERROR] : TiApplication: at android.app.ActivityThread.main(ActivityThread.java:5885) [ERROR] : TiApplication: at java.lang.reflect.Method.invoke(Native Method) [ERROR] : TiApplication: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797) [ERROR] : TiApplication: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687) {code} Environment: {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 Architecture = 32bit # CPUs = 4 Memory = 17091956736 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.0.14 Titanium SDK SDK Version = 7.1.0.GA {code}
| 5 |
3,262 |
TIMOB-25994
|
05/01/2018 11:00:22
|
Windows: JavaScriptCore for x64
|
Build JavaScriptCore for x64.
| 13 |
3,263 |
TIMOB-25995
|
05/01/2018 11:00:51
|
Windows: JavaScriptCore for ARM64
|
Build JavaScriptCore for ARM64.
| 13 |
3,264 |
TIMOB-25997
|
05/01/2018 11:07:29
|
Windows: Setup Jenkins Build with Visual Studio 2017
|
In order to support ARM64 build (TIMOB-25716), Jenkins should be building Titanium with Visual Studio 2017.
| 13 |
3,265 |
TIMOB-25998
|
05/01/2018 11:10:04
|
Windows: CLI should support --x64 and --arm64 build target
|
Support {{x64}} and {{arm64}} build target in CLI.
| 13 |
3,266 |
TIMOB-26000
|
05/01/2018 11:15:10
|
Windows: Titanium codebase to support 64bit compatibility
|
Fix build errors/warnings when building for 64 bit.
| 8 |
3,267 |
TIMOB-26001
|
05/01/2018 18:05:18
|
Android custom Module : Unable to connect WIFI of Android 8 devices
|
We are using below code to connect to Android device Wifi programatically. This code is working fine Android devices 7 and below. Same code is not working in Android 8. We have developed sample app in Android studio where we are able to connect to WIFI using wifiManager manager class. Due to this we are suspecting this issue might exists only if we using Appcelerator module. Details are mentioned after the code. Code used to connect : {code} List scanResultList = getScanningResults(); int res =0; for (ScanResult result : scanResultList) { if (result.SSID.equals(networkSSID)) { try { WifiConfiguration wifiConfiguration = createAPConfiguration( networkSSID, networkPasskey, securityMode); this.wifiManager.setWifiEnabled(true); if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.LOLLIPOP) { wifiConfiguration.SSID = networkSSID; // int pri = 99; //wifiConfiguration.priority = wifiConfiguration.priority + 1; } else { wifiConfiguration.SSID = "\"" + networkSSID + "\""; wifiConfiguration.priority = 40; } while(!this.wifiManager.pingSupplicant()) { Thread.sleep(1000); } res = this.wifiManager.addNetwork(wifiConfiguration); Log.i("WIFI_Connect", "# addNetwork returned " + res); if (res == -1) { // Get existed network id if it is already added to WiFi network this.wifiManager.updateNetwork(wifiConfiguration); res = getExistingNetworkId(networkSSID); Log.d("WIFI_Connect", "getExistingNetworkId: " + res); } this.wifiManager.disconnect(); this.wifiManager.enableNetwork(res, true); //this.wifiManager.saveConfiguration(); this.wifiManager.reconnect(); return res; }catch(Exception ex) { Log.i("", "AddDynamicWifi--savewifi--Exception--" + ex); return 1; } } } return -1; private WifiConfiguration createAPConfiguration(String networkSSID, String networkPass, String capabilities) { this.wifiConfig.allowedKeyManagement.clear(); WifiConfiguration wifiConfiguration = new WifiConfiguration(); wifiConfiguration.allowedKeyManagement.clear(); wifiConfiguration.status = WifiConfiguration.Status.ENABLED; //wifiConfiguration.priority = 40; wifiConfiguration.SSID = String.format("\"%s\"", new Object[] { networkSSID }); Log.i("networkSSID", "=======" + wifiConfiguration.SSID); if (capabilities.toUpperCase().contains("WEP")) { Log.i("rht", "Configuring WEP"); wifiConfiguration.allowedKeyManagement.set(WifiConfiguration.KeyMgmt.WPA_PSK); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.RSN); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.WPA); wifiConfiguration.allowedAuthAlgorithms .set(WifiConfiguration.AuthAlgorithm.OPEN); wifiConfiguration.allowedAuthAlgorithms .set(WifiConfiguration.AuthAlgorithm.SHARED); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.CCMP); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.TKIP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP40); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP104); /* if (networkPass.matches("^[0-9a-fA-F]+$")) { wifiConfiguration.wepKeys[0] = networkPass; } else { wifiConfiguration.wepKeys[0] = "\"".concat(networkPass).concat( "\""); }*/ wifiConfiguration.wepKeys[0] = String.format("\"%s\"", new Object[] { networkPass }); Log.i("networkSSID", "=======" + wifiConfiguration.wepKeys[0]); wifiConfiguration.wepTxKeyIndex = 0; } else if (capabilities.toUpperCase().contains("WPA")) { Log.i("rht", "Configuring WPA"); wifiConfiguration.allowedKeyManagement.set(WifiConfiguration.KeyMgmt.WPA_PSK); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.WPA); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.WPA); wifiConfiguration.allowedAuthAlgorithms .set(WifiConfiguration.AuthAlgorithm.OPEN); wifiConfiguration.allowedKeyManagement .set(WifiConfiguration.KeyMgmt.WPA_PSK); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.CCMP); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.TKIP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP40); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP104); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.CCMP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.TKIP); wifiConfiguration.preSharedKey = String.format("\"%s\"", new Object[] { networkPass }); Log.i("network password WPA", "=======" + wifiConfiguration.preSharedKey); //wifiConfiguration.preSharedKey = "\"" + networkPass + "\""; } else if (capabilities.toUpperCase().contains("PSK")) { Log.i("rht", "Configuring PSK"); wifiConfiguration.allowedKeyManagement.set(WifiConfiguration.KeyMgmt.WPA_PSK); wifiConfiguration.preSharedKey = String.format("\"%s\"", new Object[] { networkPass }); Log.i("network password PSK", "=======" + wifiConfiguration.preSharedKey); wifiConfiguration.hiddenSSID = true; wifiConfiguration.status = WifiConfiguration.Status.ENABLED; wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.TKIP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.CCMP); wifiConfiguration.allowedKeyManagement .set(WifiConfiguration.KeyMgmt.WPA_PSK); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.TKIP); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.CCMP); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.RSN); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.WPA); } else { Log.i("rht", "Configuring OPEN network"); wifiConfiguration.allowedKeyManagement .set(WifiConfiguration.KeyMgmt.NONE); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.RSN); wifiConfiguration.allowedProtocols .set(WifiConfiguration.Protocol.WPA); wifiConfiguration.allowedAuthAlgorithms.clear(); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.CCMP); wifiConfiguration.allowedPairwiseCiphers .set(WifiConfiguration.PairwiseCipher.TKIP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP40); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.WEP104); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.CCMP); wifiConfiguration.allowedGroupCiphers .set(WifiConfiguration.GroupCipher.TKIP); } return wifiConfiguration; } {code} Please take a look on attached zip file. Note Our App which is consuming this module is targeted for Titanium SDK 5.5.1.GA. Let me know if you need more information.
| 8 |
3,268 |
TIMOB-26010
|
05/01/2018 18:57:26
|
Android: TiHTTPClient getResponseHeader throws a NullPointerException
|
Calling {code}http.getResponseHeader(){code} throws an exception: {code} [WARN] W/System.err: java.lang.NullPointerException: Attempt to invoke interface method 'boolean java.util.Map.isEmpty()' on a null object reference [WARN] W/System.err: at ti.modules.titanium.network.TiHTTPClient.getResponseHeader(TiHTTPClient.java:716) [WARN] W/System.err: at ti.modules.titanium.network.HTTPClientProxy.getResponseHeader(HTTPClientProxy.java:135) [WARN] W/System.err: at org.appcelerator.kroll.runtime.v8.V8Object.nativeCallProperty(Native Method) [WARN] W/System.err: at org.appcelerator.kroll.runtime.v8.V8Object.callProperty(V8Object.java:75) [WARN] W/System.err: at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1200) [WARN] W/System.err: at android.os.Handler.dispatchMessage(Handler.java:98) [WARN] W/System.err: at android.os.Looper.loop(Looper.java:154) [WARN] W/System.err: at android.app.ActivityThread.main(ActivityThread.java:6186) [WARN] W/System.err: at java.lang.reflect.Method.invoke(Native Method) [WARN] W/System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889) [WARN] W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779) {code} I was trying to send some data to sentry.io, maybe inside the response there were no headers.
| 3 |
3,269 |
TIMOB-26006
|
05/01/2018 22:41:01
|
Android: Reduce V8 library size
|
- The size of {{libkroll-v8}} for each architecture we support is quite large in size. We should see what optimizations we can make to reduce the size of the library.
| 5 |
3,270 |
TIMOB-26007
|
05/03/2018 02:08:39
|
iOS: Refactor RSOD
|
- Refactor the red-screen of death (crash dialog) to match the updated Android implementation
| 13 |
3,271 |
TIMOB-26008
|
05/03/2018 09:16:00
|
The new update 7.1.1 does not work on Android (Gradle bug)
|
The new update 7.1.1 does not work on Android. At the creation of the SDK, stops and i get the following message: {code:java} [ERROR] Application Installer abnormal process termination. Process exit value was 1 [ERROR] : Failed to run dexer: [ERROR] : [ERROR] : Exception in thread "main" java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file [ERROR] : at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:78) [ERROR] : at org.gradle.wrapper.Install.createDist(Install.java:47) [ERROR] : at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129) [ERROR] : at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:48) [ERROR] : Caused by: java.util.zip.ZipException: error in opening zip file [ERROR] : at java.util.zip.ZipFile.open(Native Method) [ERROR] : at java.util.zip.ZipFile.<init>(ZipFile.java:219) [ERROR] : at java.util.zip.ZipFile.<init>(ZipFile.java:149) [ERROR] : at java.util.zip.ZipFile.<init>(ZipFile.java:163) [ERROR] : at org.gradle.wrapper.Install.unzip(Install.java:160) [ERROR] : at org.gradle.wrapper.Install.access$400(Install.java:29) [ERROR] : at org.gradle.wrapper.Install$1.call(Install.java:70) [ERROR] : at org.gradle.wrapper.Install$1.call(Install.java:47) [ERROR] : at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65) [ERROR] : ... 3 more public String getFoo() { return foo; } {code}
| 2 |
3,272 |
TIMOB-26009
|
05/03/2018 09:19:36
|
Update Ti.Map modules (iOS 3.1.0, Android 4.2.0)
|
We need to update the Ti.Map module references on the SDK. Includes the following changes: * [MOD-2145] iOS: Added image overlay support. * [MOD-2416] Android: Added image overlay support. * [MOD-2345] Android/iOS: Added "padding" support. * [MOD-2417] Android: Fixed map animation crash that sometimes happens.
| 1 |
3,273 |
TIMOB-26012
|
05/04/2018 10:54:02
|
iOS: Textfield AutoCaps is not working on specific keyboardType.
|
Issue: Textfield "autocapitalization" property is not working with specific keyboardType named keyboardType :Titanium.UI.KEYBOARD_TYPE_NAMEPHONE_PAD, Steps To Reproduce: 1. Run the following test code on an iOS device 2. Then click on textfield and check autocapitalization is not showing. If you change the keyboardType it works. Test Code: {code:title=app.js} var window = Ti.UI.createWindow({ backgroundColor: 'white' }); var textField = Ti.UI.createTextField({ borderStyle: Ti.UI.INPUT_BORDERSTYLE_ROUNDED, keyboardType :Titanium.UI.KEYBOARD_TYPE_NAMEPHONE_PAD, autocapitalization :Titanium.UI.TEXT_AUTOCAPITALIZATION_ALL, color: '#336699', width: 250, height: 60 }); textField.addEventListener('click', function() { Ti.API.info('in text field click'); }); window.add(textField); window.open(); {code} Thanks!
| 0 |
3,274 |
TIMOB-26013
|
05/04/2018 12:07:36
|
TextArea: Cursor should go to beginning of the text when editable is false
|
For now, if we set value to textArea by coding, the cursor will go to the end of the text value. But if the content is more than the height of the text area, you will have to scroll up to read the top content. This is very inconvenience. Specially, when customer just want to make the textArea as a read only area. We should consider with the following improvement. Like if editable property is false, then the curser should go to the beginning of content. If editable property is true, we keep the current behaviour.
| 0 |
3,275 |
TIMOB-26014
|
05/04/2018 18:46:06
|
Windows: Titanium.Media.MEDIA_TYPE_VIDEO not working.
|
Hello ! I am having problem to take video from Appcelerator windows 10 app Surface Pro . Titanium.Media.MEDIA_TYPE_VIDEO not working now. {code} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var btnTakeMovie = Ti.UI.createButton({ title: 'title_take_video', top: 10, left: 5 }); win.add(btnTakeMovie) btnTakeMovie.addEventListener('click', function (e) { Titanium.Media.showCamera({ success: function (event) { Ti.API.info('success'); }, cancel: function () { Ti.API.info('cancel'); }, error: function (error) { Ti.API.info(JSON.stringify(error)); }, mediaTypes: [Titanium.Media.MEDIA_TYPE_VIDEO], videoMaximumDuration: 1000000, videoQuality: Titanium.Media.QUALITY_HIGH }); }); win.open(); {code} Above code doesn't give me option for video. Test Environment: SDK 7.1.0 windows 10 Surface Pro Thanks
| 13 |
3,276 |
TIMOB-26017
|
05/08/2018 12:02:52
|
Titanium.UI.iOS.MenuPopup: Ability to change background color and text color
|
Customer is looking for way to change background color and text color for controller Titanium.UI.iOS.MenuPopup. For now, there is no properties to change those. So create this as new feature. Please also advice any workaround to change them.
| 1 |
3,277 |
TIMOB-26021
|
05/09/2018 11:33:34
|
iOS: Search results table-view background color change
|
I have a window with backgroundImage and a tableView with backgroundColor transparent and labels of all item white. When I click on searchBar and start typing the backgroundColor of tableView became white and the results are unreadable because item's labels have the same color of background. Android work fine with the same component Ti.UI.createSearchBar
| 2 |
3,278 |
TIMOB-26023
|
05/09/2018 11:40:59
|
TiAPI: Add Ti.Blob parity across platforms
|
Currently, there are differences in behavior when using the Ti.Blob API across iOS and Android. Those should be resolved.
| 13 |
3,279 |
TIMOB-26025
|
05/09/2018 11:42:15
|
TiAPI: Add Ti.Filesystem.File parity across platforms
|
Currently, there are differences in behavior when using the Ti.Filesystem.File API across iOS and Android. Those should be resolved.
| 13 |
3,280 |
TIMOB-26026
|
05/09/2018 11:45:33
|
TiAPI: Improve parity on Core-SDK
|
Currently, there are differences in behavior when using several core-API's across iOS and Android. Those should be resolved.
| 0 |
3,281 |
TIMOB-26027
|
05/09/2018 16:26:24
|
Android: Analytics can cause a crash on Android 8 if app is backgrounded
|
When using Analytics (enabled by default via the tiapp.xml property {{<analytics>true</analytics}}, an Android app can randomly crash: {code} java.lang.IllegalStateException: at android.app.ContextImpl.startServiceCommon (ContextImpl.java:1538) at android.app.ContextImpl.startService (ContextImpl.java:1484) at android.content.ContextWrapper.startService (ContextWrapper.java:663) at com.appcelerator.aps.APSAnalyticsHelper$AnalyticsCallback.handleMessage (APSAnalyticsHelper.java:540) at android.os.Handler.dispatchMessage (Handler.java:101) at android.os.Looper.loop (Looper.java:164) at android.app.ActivityThread.main (ActivityThread.java:6938) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374) {code} The crash happens in the "handleMessage" method of the "APSAnalyticsHelper.java" and indicates an issue with the main thread. We removed the class recently, as part of [this PR|https://github.com/appcelerator/aps_sdk/pull/312], so it might not be an issue in future versions of the SDK. [~iwhitfield] to confirm
| 3 |
3,282 |
TIMOB-26028
|
05/10/2018 00:04:10
|
Windows: Add Ti.Filesystem.File parity across platforms
|
Fix some parity issues we're looking at deprecating Ti.Filesystem.File #createTimestamp() and #modificationTimestamp() to be replaced by new #createdAt() and #modifiedAt() methods that return a Date. Basically the timestamp methods return a Date on iOS and Number on the rest. There's not a nice non-breaking way to fix that, so we'd like to deprecate the existing methods and add new variants that return Date on all platforms (since it's pretty easy to turn that into a timestamp if necessary).
| 13 |
3,283 |
TIMOB-26029
|
05/10/2018 17:12:06
|
Android : Titanium.Android.ACTION_HEADSET_PLUG Not working as expected.
|
We want to detect the current state of headphones connected (true) or disconnected (false). We have an API for that but no example code in documents. http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Android-property-ACTION_HEADSET_PLUG I create an example code but not working. {code} function doClick() { Ti.Android.unregisterBroadcastReceiver(bc); } $.index.open(); var onReceived = function(e) { Ti.API.info("received!"); Ti.API.info('Handling broadcast. >> ' + JSON.stringify(e)); alert('Handling broadcast. >> ' + JSON.stringify(e)); }; var bc = Ti.Android.createBroadcastReceiver({ onReceived : onReceived }); Ti.Android.registerBroadcastReceiver(bc,["Titanium.Android.ACTION_HEADSET_PLUG"]); {code} Index.xml {code:xml} <Alloy> <Window class="container" onClose="doClose" /> </Alloy> {code} Test Environment: {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 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.0 Titanium SDK SDK Version = 7.1.0.GA {code} Thanks
| 2 |
3,284 |
TIMOB-26033
|
05/11/2018 16:45:10
|
iOS: Ti.Media.VideoPlayer shows an error on Window Close on SDK 7.1.1.GA
|
Hello, The following error occurs when closing a window with a video player control with SDK 7.1.1.GA on iOS. On Android, it works just fine. *Test Environment:* Appcelerator Command-Line Interface, version 7.0.3 SDK: 7.1.1.GA *Test code:* index.xml {code} <Alloy> <Window class="container"> <Label id="label" onClick="doClick">Open Video Error Page</Label> </Window> </Alloy> {code} video.xml {code} <Alloy> <Window id="winVideo" backgroundColor="#cccccc"> <Label id="videoLocalClose"></Label> <Label id="videoAdd" top="100" color="blue">Add Video First</Label> <Label id="videoPlay" top="200" color="purple">Then Play Video</Label> <Label id="videoWindowClose" bottom="0" height="80" color="red">Close Window With Error</Label> </Window> </Alloy> {code} index.js {code} function doClick(e) { Alloy.createController('video', {}).getView().open(); } $.index.open(); {code} video.js {code} var activeMovie = null; var videoMedia = null; $.videoAdd.addEventListener('click', function(e) { Ti.Media.showCamera({ mediaTypes: [Ti.Media.MEDIA_TYPE_VIDEO], videoMaximumDuration: 300000, videoQuality: Titanium.Media.QUALITY_MEDIUM, saveToPhotoGallery: true, allowEditing: false, success:function(e){ saveVideoLocal(e.media); } }); }); function saveVideoLocal(media) { videoMedia = media; } $.videoPlay.addEventListener('click', function(e) { activeMovie = Titanium.Media.createVideoPlayer({ top : 0, width : '100%', bottom:100, visible:true, zIndex:999999, mediaControlStyle : Titanium.Media.VIDEO_CONTROL_DEFAULT, scalingMode : Titanium.Media.VIDEO_SCALING_ASPECT_FILL, autoplay : true, media: videoMedia }); // Now if I use url instead of media then the video will not play. ( Same of android and iOS) // If I put a fake url like (url: 'http://fakeMovie.com' and still set media property the video will not play but error will not be thrown) // You can even put both media and url key above to same videoMedia and it will throw the error. // Looks like you have to set the url key at the creation of the control to not throw the error. // But url does not seem to be working for local media where the media key should be used. // Also when I get the script error the app will not crash but it will also not recognize //any future clicks on the listview control on the page that opened the video page. $.winVideo.add(activeMovie); }); $.videoWindowClose.addEventListener('click', function(e) { $.winVideo.close(); }); $.winVideo.addEventListener('close', function(e) { if (activeMovie != null) { activeMovie.release(); $.winVideo.remove(activeMovie); } activeMovie = null; $.destroy(); $.off(); $.winVideo = null; }); {code} index.tss {code} ".container": { backgroundColor:"white" } "Label": { width: Ti.UI.SIZE, height: Ti.UI.SIZE, color: "#000" } "#label": { font: { fontSize: 12 } } {code} alloy.js {code}Attach in the text file{code} Note: Also I have added the full project on the attachment file. *Error:* {code} [ERROR] : Script Error { [ERROR] : column = 24; [ERROR] : line = 119; [ERROR] : message = "Cannot remove an observer <TiMediaVideoPlayerProxy 0x11808d000> for the key path \"url\" from <TiMediaVideoPlayerProxy 0x11808d000> because it is not registered as an observer."; [ERROR] : } {code} In this test code customer used *media* in the create command to play a video stored on the local device. If they put a fake url in the create it won't throw the error but even though they set the media later then it will not play the video. Again, this only happens on iOS. Thanks
| 8 |
3,285 |
TIMOB-26034
|
05/11/2018 22:37:55
|
Android: Warning: "PickerProxy: the useSpinner property is deprecated"
|
Received this email through JIRA admin account: _In Android when using the Picker element we are receiving the following warning:"PickerProxy: the useSpinner property is deprecated, see the documentation for more information". At any time we are establishing this property and it is causing the application to freeze_ I reached out to the app developer for more details, and will update the ticket after information is available.
| 0 |
3,286 |
TIMOB-26036
|
05/13/2018 16:54:10
|
Windows: Disabling Ti.View does not disable its children
|
We have having issues related to disabling the children of Ti.View. If we make touchEnabled false for a View, it does not make its children uneditable. Where as if we use Ti.ScrollView instead, everything is working as expected. As mentioned in the ticket [TIMOB-25306|https://jira.appcelerator.org/browse/TIMOB-25306], since we can not make the picker disabled by setting its touchEnabled property as false, we are trying to use it as a workaround to disable its Parent view which would in turn disable all its children. Steps to reproduce: 1. Run the attached Alloy project TestPickerDisabled 2. You can see two Pickers and two TextFields. Picker and TextField whose background color is yellow are children of Ti.View where as the other Picker and TextField whose background color is Red are children of Ti.ScrollView. 3. We have touch enabled property set to false for both Ti.View and Ti.ScrollView. You can observe that the Picker and the TextField that are children of Ti.View are editable where as the children of Ti.ScrollView are not editable. Test Project : *TestPickerDisable.zip* Test Environment : {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 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.0 Titanium SDK SDK Version = 7.1.1.GA {code} Thanks
| 8 |
3,287 |
TIMOB-26045
|
05/16/2018 03:08:59
|
Windows: 2DMatrix rotation scales view
|
Animation transform using {{2DMatrix}} with {{rotate}} property should just rotate the view but it actually scales view. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green' }); var view = Ti.UI.createView({ backgroundColor: 'red', width: 100, height: 100 }), matrix = Ti.UI.create2DMatrix({ rotate: 90 }), animation = Ti.UI.createAnimation({ transform: matrix, duration: 3000 }); win.addEventListener('click', function () { view.animate(animation); }); win.add(view); win.open(); {code} Expexted: View should rotate at the center position of the view. This should not change view size.
| 8 |
3,288 |
TIMOB-26048
|
05/16/2018 23:32:17
|
Windows: Refactor RSOD
|
- Refactor the red-screen of death (crash dialog) with stack traces to match the iOS/Android look and feel. - Add "nativeStack" property to show the native stack trace Unit-test (iOS and Android so far): https://github.com/garymathews/titanium_mobile/pull/2/files#diff-3dc400bf7f83b2691685b65f5a5066d1R13
| 13 |
3,289 |
TIMOB-26049
|
05/17/2018 07:19:56
|
iOS : Replace NSURLConnection with NSURLSession used in Ti.UI.WebView
|
Apple has deprecated NSURLConnection and NSURLSession should be used instead of same. In Ti.UI.WebView, we are still using NSURLConnection. We should replace NSURLConnection with NSURLSession.
| 3 |
3,290 |
TIMOB-26051
|
05/18/2018 00:50:11
|
Android: Ti.UI.createRefreshControl.beginRefreshing() does not fire 'refreshstart'
|
- {{beginRefreshing()}} does not fire the {{refreshstart}} event *TEST CASE* {code:js} var window, control, listView; window = Ti.UI.createWindow(); window.addEventListener('open', function () { control.beginRefreshing(); }); control = Ti.UI.createRefreshControl(); listView = Ti.UI.createListView({ refreshControl: control }); control.addEventListener('refreshstart', function () { Ti.API.info('refreshstart'); setTimeout(function () { Ti.API.info('ending...'); control.endRefreshing(); }, 2000); }); control.addEventListener('refreshend', function () { Ti.API.info('refreshend'); alert('DONE!'); }); window.add(listView); window.open(); {code}
| 2 |
3,291 |
TIMOB-26054
|
05/18/2018 18:02:03
|
Android: Webview with HTML having GIF images not loaded on all android devices.
|
Hi, I am facing a wired issue in android. I have Web-view with HTML having GIF images. GIF images is loading in some android device and doesn't load in some android device. 1.html {code:HTML} <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=no"/> </head> <body style="background-color:transparent; margin: 0; height: 100%; overflow: hidden"> <div style="text-align: right"> <img src="gifImg.gif" style="width: 40px; height: 40px" /> </div> </body> </html> {code} index.xml {code:xml} <Alloy> <Window class="container"> <WebView id="previewWebView" url = '/gifTest/1.html'/> </Window> </Alloy> {code} Places your gif image and HTML file to the "assets/gifTest/" location Note: We have tested on Android 6 (HTC one m8), Android 7 (Huawei), and Android 8 Huwawei y9 2018 is working as expected. Problem with the following devices and Chrome browser version: 66.0.3359.158 OnePlus 5T(8.1.1), Moto G4 plus(v7.0.0), onePlus 3(v8.0.0) and Moto G5 (v7.0.0) *Steps To Reproduce:* 1. Run the provided test code with those specific devices. 2. Make sure the Chrome browser of those devices is up to date. 3. Test on the actual device, not on emulator. *Test environment :* {code} Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 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.0 Titanium SDK SDK Version = 7.1.1.GA {code} Thanks
| 0 |
3,292 |
TIMOB-26055
|
05/18/2018 18:22:28
|
Android: Build fails due to invalid character '$' in android manifest with facebook & liveview with 7.3.0 SDK
|
This can be called as a regression. Works with 7.1.1.GA h5.Steps to reproduce: 1. Create a default app for android. 2. Add the facebook module to the tiapp.xml. 3. Build the app with SDK 7.3.0 (I used 7.3.0.v20180518082133). h5.Actual result: 1. Build fails to package with error: {code} [ERROR] : Failed to package application: [ERROR] : [ERROR] : (skipping file '.liveviewapp.js' due to ANDROID_AAPT_IGNORE pattern '.*') [ERROR] : /Users/lchoudhary/Desktop/workspaces/workspace_2018/zdummy/build/android/AndroidManifest.xml:24: Tag <provider> attribute authorities has invalid character '$'. [ERROR] Application Installer abnormal process termination. Process exit value was 1 {code} 2. In the android manifest this line gets added: {code} <provider android:name="com.facebook.internal.FacebookInitProvider" android:authorities="${applicationId}.FacebookInitProvider" android:exported="false"/> {code} 3. Build fails due to the {{$}} symbol. Expected result: 1. Build should not fail when facebook & liveview are used in the app.
| 3 |
3,293 |
TIMOB-26059
|
05/21/2018 04:29:50
|
Windows: Support x64 build target for Hyperloop
|
Support x64 build target support for Hyperloop.
| 13 |
3,294 |
TIMOB-26076
|
05/23/2018 07:47:01
|
Android : WebView Html5 Audio / Video Not playing from External Storage
|
[ERROR] : MediaResourceGetter: Invalid url: java.lang.RuntimeException: setDataSource failed: status = 0x80000000 [ERROR] : MediaPlayer: error (262, 0) [ERROR] : MediaPlayer: Unable to create media player ================ The audio / video file from *external storage* not playing under webview. Note: please check the attached code (app.js) on my android deice I have copied both audio file into the directory where created index.html file is present
| 0 |
3,295 |
TIMOB-26063
|
05/23/2018 18:38:01
|
iOS: Implement WebView.onlink callback
|
h5. description Costumer is attempting to load a pdf for android using intents with webview. in the mobile app they are using webview control for displaying the remote web site by binding a URL. The web pages in the web site contains few pdf links. On click of normal hyperlinks, respective web page is being shown in the web view. Whereas, on tapping a pdf links, a blank window is getting opened in Android devices. In iOS it’s working fine and a PDF is showing. Per Jira WebView cannot disply PDF documents on Android. So they are using intents as a workaround to open the PDF link. The issue is that on click of the pdf link in the web view, they are unable to get the exact PDF url with any of Titanium WebView API methods or events The customer was able to do it natively and open the PDF's with intents. h5. Request The customer wants to know how to get the exact PDF link using the webview API or if there is a workaround they could use. h5. additional information attached are two apps. One is a titanium app and one is an android native application. [titanium app|https://axwaysoftware-my.sharepoint.com/personal/vvazquezmontero_axway_com/_layouts/15/guestaccess.aspx?guestaccesstoken=rsxSxfm51VH5t8MRm7YpDX1bHDfJfDfaycmtpKrlAEE%3d&docid=2_11a957eab95234b6ab84003e12f7b0b41&rev=1]
| 3 |
3,296 |
TIMOB-26065
|
05/24/2018 14:34:55
|
Android: Investigate NDK r17 support
|
We currently support the Android NDK r16b with SDK 7.x. As of May 2018, NDK r17 is available ([Changelog|https://developer.android.com/ndk/downloads/revision_history]). We should validate if our tooling already supports it and if not, what it takes to update it.
| 1 |
3,297 |
TIMOB-26066
|
05/24/2018 19:59:04
|
node-ios-device: Support Xcode 9 and Node.js 10
|
Apparently newer versions of Xcode prohibit the linking to private frameworks. In the case of node-ios-device, it needs to link with MobileDevice.framework and can't with Xcode 9.2 and 9.3. node-pre-gyp is pretty out-of-date. The build scripts need to be updated for Node.js 10 (and Node.js 9).
| 8 |
3,298 |
TIMOB-26067
|
05/24/2018 22:01:17
|
Windows: Update APSAnalytics to support opt-out
|
Update [aps_sdk|https://github.com/appcelerator/aps_sdk] to support opt-out for Windows. I believe it is not a requirement of 7.2.0 because Axway doesn't officially support native sdk for Windows, but it is good to have it updated.
| 8 |
3,299 |
TIMOB-26075
|
05/30/2018 04:33:56
|
Android: Refactor app resume and "newintent" handling
|
*Summary:* Titanium's app resume handling from notification, shortcuts, intent-filters, etc. is problematic. It does not always resume and instead displays a new splash-screen instance which never runs the "app.js" (appears to hang) or a dialog stating that the app needs to be restarted (which can get stuck in an infinite loop). The following is a list of issues that have been reported. Some are flagged closed, but they're not completely resolved: * [TIMOB-1559] * [TIMOB-4941] * [TIMOB-9285] * [TIMOB-15253] * [TIMOB-24427] * [TIMOB-24747] * [TIMOB-25776] *Recommended Solution:* Get rid of *+all+* of the activity "restarting" code. No one likes this behavior. * [TiRootActivity.onCreate()|https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/src/java/org/appcelerator/titanium/TiRootActivity.java#L75] * [TiLaunchActivity.onCreate()|https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/src/java/org/appcelerator/titanium/TiLaunchActivity.java#L142] * [TiBaseActivity.onCreate()|https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/src/java/org/appcelerator/titanium/TiBaseActivity.java#L578] Drop support for Android bug 2373/5277 related "tiapp.xml" properties: * [link|https://docs.appcelerator.com/platform/latest/#!/guide/tiapp.xml_and_timodule.xml_Reference-section-src-29004921_tiapp.xmlandtimodule.xmlReference-PropertiestoworkaroundAndroidbugs2373and5277] In the main activity's {{onCreate()}}, we should do the following: # Check if {{TiApplication.getRootActivity()}} is not null. This tells us if a pre-existing activity window is already in the background and needs to be resumed. If it doesn't exist, then go ahead and create the activity (we're done). # Fetch the pre-existing root activity's intent. If we call {{Context.startActivity()}} with this intent, then it'll resume it with all of its child activity windows intact. _(This is what we're missing.)_ # Call {{finish()}} for the new activity since we don't want to spawn a new instance. Attempt to disable the activity window's animation if possible via {{Activity.overridePendingTransition()}}. # Have the pre-existing root activity fire a "newintent" event with the intent received by the new activity that we just finished/closed. (We must wait for the old activity task to resume first though.) *Issues to Investigate:* * The {{Activity.getIntent()}} can return {{null}} in rare cases ([link|https://stackoverflow.com/questions/37856407/can-activity-getintent-ever-return-null]). We need to figure out how to resume the app's activity in this case. * We need to double check the necessity of {{TiBaseActivity.isUnsupportedReLaunch()}}. I suspect it's handling the case where a new Java runtime and {{Application}} instance is being re-created for a pre-existing app process (the C/C++ side's static variables still remember previous application info). * Check how this works with launchMode "singleTop". (It is being used by some community users. Although with this change, we shouldn't need it anymore.) * Re-test with Titanium's "Live-View" feature and {{Ti.App._restart()}} method to make sure they don't break. *Limitations:* * Titanium only supports running one V8 JavaScript runtime at a time. So, multiple activity tasks cannot be supported due to this limitation. This is partly why we need to refactor the app resume behavior. _(This may be fine from a portability standpoint anyways since iOS does not support this.)_ * We should avoid launchMode "singleTask" support. While it does what we want and makes an Android app work more like iOS, it comes with a huge limitation. A "singleTask" activity's child activity windows are all torn down by the Android OS after homing-out of the app and then resuming it. "singleTask" is only a viable solution if we re-architected Titanium to only support one activity and and all {{Ti.UI.Window}} objects spawned fragments instead, but this would be a major MAJOR breaking-change that is best avoided for now.
| 13 |
3,300 |
TIMOB-26077
|
05/30/2018 15:09:14
|
iOS: Ti.UI.convertUnits returns incorrect values for 3x resolution devices
|
Calls to Ti.UI.convertUnits return invalid values for 3x iOS devices. It appears to be multiplying by 2x instead under the hood.
| 5 |
3,301 |
TIMOB-26078
|
05/30/2018 21:33:41
|
Windows: Remove Ti.UI.currentWindow
|
Remove {{Ti.UI.currentWindow}} as it has been removed on the other platforms. Related to https://github.com/appcelerator/titanium_mobile/pull/10080#discussion_r191809153
| 3 |
3,302 |
TIMOB-26079
|
05/31/2018 02:29:57
|
App does not run if included module have multiple .aar file.
|
I am trying to build an Android module that includes .aar files. The module currently doesn't do much at all but when I include various .aar files then the module is created but when it gets to running the test app of the module it fails. It creates the unsigned apk and then processes the dex files and then the src files when it throws the following error. (__('Valid ABIs for this project: %s', this.abis(', '))); : this.abis is not a function Failed to run ti /Users/jasonwogan/.appcelerator/install/7.0.3/package/node_modules/titanium/lib/titanium.js The Module: https://github.com/jwogan5/sampleApp/blob/master/android.zip *Steps To Reproduce* 1. Just build that module 2. Then run it with any sample test App.
| 0 |
3,303 |
TIMOB-26080
|
05/31/2018 10:38:54
|
Android: ERR_INVALID_CALLBACK error when building a app/module on Node 10
|
h5.Description Building an app or module with Node 10 throws the following error {code} TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at maybeCallback (fs.js:157:9) at Object.fs.exists (fs.js:235:3) at SimpleFileCache.persist (/Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/android/cli/hooks/aar-transform.js:484:11) at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/android/cli/hooks/aar-transform.js:379:9 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/async/dist/async.js:460:16 at replenish (/Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/async/dist/async.js:977:25) at iterateeCallback (/Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/async/dist/async.js:967:17) at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/async/dist/async.js:944:16 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/android/cli/hooks/aar-transform.js:356:12 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/async/dist/async.js:460:16 --------------------------------------------- at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/extract-zip-fork/index.js:26:15 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/yauzl/index.js:32:7 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/yauzl/index.js:123:16 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/yauzl/index.js:473:5 at /Users/eharris/Library/Application Support/Titanium/mobilesdk/osx/7.2.0.v20180528150435/node_modules/fd-slicer/index.js:32:7 {code} h5.Steps to reproduce 1. Download Node 10 2. Build a module or an app h5.Actual Above error h5.Expected No error should occur
| 5 |
3,304 |
TIMOB-26081
|
05/31/2018 10:56:36
|
CLI: Fix new Buffer deprecation warnings in build scripts
|
h5.Description Node 10 produces a deprecation warning when the {{new Buffer}} constructor is used. See https://nodesource.com/blog/understanding-the-buffer-deprecation-in-node-js-10/ if you're curious In most cases I believe the most appropriate swap for us to do is turn {{new Buffer}} into {{Buffer.from}} In titanium_mobile there are two instances https://github.com/appcelerator/titanium_mobile/search?l=JavaScript&q=%22new+Buffer%22 , however checking all modules (*lib, node-appc, node-titanium-sdk etc.) would also be good as there deprecation warning will not be shown for code that resides under {{node_modules}} I believe. We might also wish to update eslint-config-axway to include the {{no-buffer-constructor}} rule Steps to reproduce to be added as replacement happens
| 5 |
3,305 |
TIMOB-26085
|
06/04/2018 07:46:53
|
Windows: 2DMatrix should scale from center
|
View scale with {{2DMatrix}} should scale the view from center position of the view. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green' }); var view = Ti.UI.createView({ backgroundColor: 'red', width: 100, height: 200, id: 'view' }), matrix = Ti.UI.create2DMatrix({ scale: 0.5 }), view2 = Ti.UI.createWindow({ width: 50, height: 50, backgroundColor: 'blue', id: 'view2' }); view.add(view2); var animation = Ti.UI.createAnimation({ transform: matrix, duration: 3000 }); win.addEventListener('open', function () { view.animate(animation); }); win.add(view); win.open(); {code} Expected: View should scale from center of the view.
| 5 |
3,306 |
TIMOB-26086
|
06/04/2018 07:59:16
|
Windows: Wrong event source after scaling with 2DMatrix
|
Wrong {{source.id}} is returned after scaling the view with {{2DMatrix}}. {code} var win = Ti.UI.createWindow({ backgroundColor: 'green', width: 800, height: 400 }); var view = Ti.UI.createView({ backgroundColor: 'red', width: '80%', height: '80%', id: 'view' }), matrix = Ti.UI.create2DMatrix({ scale: 0.5, anchorPoint: {x:0, y:0} }), view2 = Ti.UI.createView({ width: '70%', height: '70%', backgroundColor: 'blue', id: 'view2' }); view.add(view2); view.addEventListener('click', function (e) { alert(e.source.id); }); var animation = Ti.UI.createAnimation({ transform: matrix, duration: 3000 }); win.addEventListener('open', function () { view.animate(animation); }); win.add(view); win.open(); {code} Expected: When clicking on the blue view, it should prompt {{"view2"}}.
| 13 |
3,307 |
TIMOB-26089
|
06/05/2018 00:17:24
|
iOS 12: Update simulator mappings for Xcode 10
|
We need to do a slight adjustment on the simulator mappings of ioslib in order to run on Xcode 10 properly.
| 8 |
3,308 |
TIMOB-26090
|
06/05/2018 01:02:00
|
iOS 12: Make iOS development-project compatible with Xcode 10
|
This ticket describes some minor changes to our Xcode template project in order to start active development on it.
| 1 |
3,309 |
TIMOB-26097
|
06/05/2018 20:58:10
|
Hyperloop: iOS 12 - Using CocoaPods in Hyperloop does not work with Xcode 10
|
When using Xcode 10, Hyperloop errors if the app includes CocoaPods dependencies: {code} [INFO] Starting Hyperloop assembly Error: ENOENT: no such file or directory, stat '/Users/hknoechel/Documents/Apps/hyperloop-examples/build/iphone/build/Products/Debug-iphonesimulator/GLCalendarView/GLCalendarView.framework/Headers/GLCalendarView-umbrella.h' at Object.fs.statSync (fs.js:948:11) at Object.statSync (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/node_modules/graceful-fs/polyfills.js:297:22) at ModuleMetadata.getHeaders (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/module_metadata.js:227:20) at Object.generateFrameworkMetabase (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/metabase.js:50:29) at ModuleMetadata.generateMetabase (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/module_metadata.js:197:22) at ModuleMetadata.getDependencies (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/module_metadata.js:210:15) at Promise.all.toGet.map.name (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/metabase.js:176:20) at Array.map (<anonymous>) at getDependencies (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/metabase.js:173:27) at Object.unifiedMetabase (/Users/hknoechel/Documents/Apps/hyperloop-examples/modules/iphone/hyperloop/3.2.0/hooks/node_modules/hyperloop-metabase/lib/metabase.js:203:9) --------------------------------------------- {code} Before, there was also an issue with cleaning the build directory, which is addressed via [this PR|https://github.com/appcelerator/titanium_mobile/pull/10123] already.
| 3 |
3,310 |
TIMOB-26099
|
06/05/2018 23:28:13
|
Android: CLI "appc run" should launch app with intent action MAIN category LAUNCHER
|
*Summary:* {{appc run}} launches the app on Android with an intent that is missing action "android.intent.action.MAIN" and category "android.intent.category.LAUNCHER", which is how an app is normally launched on Android via the app list screen. The consequence of this is that if you press the HOME button to suspend the app and then tap on the app from the home screen, then a new activity instance will be created and Titanium will be stuck on the splash screen since Titanium only supports running 1 JavaScript runtime at a time. *Steps to reproduce:* # Build and run the below code on Android either via Appcelerator Studio or via {{appc run}} at the terminal. # Wait for the app to be displayed on the Android device. # Press the "Home" button to suspend the app. (Do *NOT* press the "Back" key.) # From the home screen, go to the app list screen. # Tap on the installed app to attempt to resume it. # After doing this, notice that the app is stuck displaying the splash screen. It does not resume the app. It has created a new activity instance without a JavaScript runtime. {code:javascript} var window = Ti.UI.createWindow(); window.add(Ti.UI.createLabel({ text: 'Test' })); window.open(); {code} *Cause:* On Android, an existing activity window stack can be resumed when using the same an intent that originally launched it. If given different intent settings for the same activity (such as the case here), then Android will create a new activity instance by default. *Recommended Solution:* We need to modify the CLI on how it starts the app via Android "adb" command line tool here... https://github.com/appcelerator/node-titanium-sdk/blob/master/lib/adb.js#L655 We need to add intent parameters {{-a}} to set the action, {{-c}} to set the category, and {{-f}} to set the flags via adb similar to the following. {code} ./adb shell am start -n <PackageName>/.<ActivityName> -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 {code} The {{-f 0x10200000}} part adds intent flags {{FLAG_ACTIVITY_NEW_TASK}} and {{FLAG_ACTIVITY_RESET_TASK_IF_NEEDED}}. The {{FLAG_ACTIVITY_NEW_TASK}} is set by all Android OS versions when launching an app from the home screen. The {{FLAG_ACTIVITY_RESET_TASK_IF_NEEDED}} is set by newer Android OS versions (such as Android 8) but works fine on older OS versions such Android 4.1. *Note:* We also need this change to resolve a regression mentioned here: [TIMOB-25867]
| 3 |
3,311 |
TIMOB-26102
|
06/06/2018 02:42:36
|
Android: Push notifications should create default channel if not assigned when targeting Android 8
|
*Summary:* Our APS library (which implements Android push notifications) correctly uses Google's {{DEFAULT_CHANNEL_ID}} on Android 8 when targeting API Level 25 or lower. [APSCloudPush.java#L409|https://github.com/appcelerator/aps_sdk/blob/897b735961c10ce1b6e74f9fd48b48edb4eec83e/android/cloudpush/APSCloudPush/src/main/java/com/appcelerator/aps/APSCloudPush.java#L409] However, when targeting API Level 26 or higher, you cannot use Google's {{DEFAULT_CHANNEL_ID}} which means notifications will fail to be posted to the status bar. So, the APS library must be changed to create its own default notification channel if one was not supplied from the payload... and it should only do so when targeting API Level 26 or higher. *Recommended Solution:* We should use a similar solution used by Titanium's local notifications as shown here... https://github.com/appcelerator/titanium_mobile/pull/9945 It probably should use a separate notification channel name than what Titanium uses. This may be needed to avoid collision with how Titanium configures its channel.
| 5 |
3,312 |
TIMOB-26141
|
06/06/2018 04:54:59
|
Android: Accessing Titanium.App.Android.R logs GC errors
|
When building an Alloy app with Ti SDK 7.1.1 accessing `Titanium.App.Android.R` causes the logs to trow errors: {code:java} [ERROR] JavaObject: !!! OH NO! We tried to grab a Java Object back out of the reference table, but it must have been GC'd, because it's null! Key: 0 [ERROR] JavaObject: !!! OH NO! We tried to grab a Java Object back out of the reference table, but it must have been GC'd, because it's null! Key: 0 {code} How to reproduce: 1. Create new Alloy app 2. Add the following code below in alloy.js: 3. Build 4. See errors in logs. {code:java} Ti.API.info("Hyper Hello"); Ti.API.info(Titanium.App.Android.R); {code} Logs: {code:java} [INFO] Hyper Hello [ERROR] JavaObject: !!! OH NO! We tried to grab a Java Object back out of the reference table, but it must have been GC'd, because it's null! Key: 0 [ERROR] JavaObject: !!! OH NO! We tried to grab a Java Object back out of the reference table, but it must have been GC'd, because it's null! Key: 0 [INFO] [object R] {code}
| 3 |
3,313 |
TIMOB-26106
|
06/07/2018 05:30:07
|
Windows: Update module apiversion to 6
|
Update module apiversion because there's module binary incompatibility in upcoming 7.3.0. All Windows module needs re-compiled to make it work with 7.3.0.
| 3 |
3,314 |
TIMOB-26108
|
06/07/2018 15:47:20
|
CLI: "clean" command builds the project instead
|
*Steps to reproduce* # Create a project {{appc new}} # Run the project once # {{ti clean}} *Expected* The app is cleaned *Actual* The app is built
| 1 |
3,315 |
TIMOB-26109
|
06/07/2018 18:11:10
|
Xcode 10: Cannot build modules with the new (default) build system
|
When using Xcode 10 and the new build system, which is now default, the linked core-classes (TiProxy.h, TiBase.h, ..) cannot be found anymore. I opened a [Radar|https://openradar.appspot.com/radar?id=5621620265713664] for this.
| 3 |
3,316 |
TIMOB-26110
|
06/08/2018 01:27:47
|
Xcode 10: Cannot build application with new (default) build system
|
When using Xcode 10 and the new build system, the app build fails because the <project>/build/iphone/build directory is generated by our CLI instead of the actual xcodebuild command. While this was okay in the past, the new build system complains about that. I filed a radar at https://openradar.appspot.com/40906897 and talked to the Apple engineers during WWDC. They assume it to be an issue in the new build system, but we can actually fix it on our end by now pre-creating the directory and let xcodebuild create it. I tested it as a local change and it works with both Xcode 10 and 9. Error: {code} [INFO] Cleaning Xcode derived data [DEBUG] Invoking: DEVELOPER_DIR=/Applications/Xcode-beta.app/Contents/Developer /Applications/Xcode-beta.app/Contents/Developer/usr/bin/xcodebuild clean [ERROR] note: Using new build system [ERROR] error: Could not delete `/Users/hknoechel/Documents/Apps/myapp/build/iphone/build` because it was not created by the build system and it is not a subfolder of derived data. [ERROR] ** CLEAN FAILED ** {code}
| 0 |
3,317 |
TIMOB-26113
|
06/08/2018 15:34:40
|
iOS: Ti.UI.convertUnits does not consult ti.ui.defaultunit property
|
Looks like iOS does not consult ti.ui.defaultunit property for converting when input units aren't specified. It assumes "dp", which is the default value placed in tiapp.xml.
| 3 |
3,318 |
TIMOB-26115
|
06/08/2018 15:53:01
|
TiAPI: Add support for console.timeLog
|
it would be very useful to have the ability to output timing to the log for testing and debugging. We have already added console.time and console.timeEnd. Due to some ambiguities around calling timeEnd multiple times for the same label, they introduced console.timeLog to handle printing intermediate timings without removing the timer/label. We should expand to support this as well. https://github.com/whatwg/console/pull/138
| 5 |
3,319 |
TIMOB-26116
|
06/08/2018 20:35:53
|
iOS: Images are skewed on iOS 8
|
*Summary:* The default splash image (and other images) appears skewed when running on iOS 8. This is not an issue on iOS 9 and newer OS versions. This issue happens in Titanium 6.1.1 and 7.3.0. *Steps to reproduce:* # Create a new "Classic App" project. # Builds and run it in the iOS 8 simulator. # Observe the default splash when displayed onscreen. (It appears skewed.) # Observe the tab icons at the bottom of the app. (They appear skewed.) *Result:* On iOS 8, it looks like the following... !iOS8Splash.bad.png|thumbnail! !iOS8Tabs.bad.png|thumbnail! On iOS 9 and 10, it works correctly. !iOS10Splash.good.png|thumbnail! !iOS10Tabs.good.png|thumbnail!
| 0 |
3,320 |
TIMOB-26117
|
06/08/2018 23:35:51
|
iOS: ES6 promises not supported on iOS 9. (Works on iOS 8 and 10.)
|
*Summary:* JavaScript ES6 "promises" are not supported on iOS 9 when setting "tiapp.xml" setting {{<transpile>true</transpile>}}. However, promises are supported on iOS 8 and iOS 10. *Steps to reproduce:* # Set up a project's "tiapp.xml" with the below "transpile" setting. # Build and run the below code on iOS 9. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> <transpile>true</transpile> </ti:app> {code} {code:javascript} Ti.API.info("@@@ typeof Promise: " + (typeof Promise)); var promise = new Promise(function(resolve, reject) { Ti.API.info("@@@ Promise execution started."); setTimeout(function() { Ti.API.info("@@@ Promise execution ended."); resolve(); // reject(); }, 1000); }).then(function() { Ti.API.info("@@@ Promise.then() called."); }).catch(function(e) { Ti.API.info("@@@ Promise.catch() called."); }); {code} *Result:* An exception dialog is displayed stating "Can't find variable: Promise". *Notes:* * This issue does not happen in iOS 8.1 and 8.4 simulators. * This issue does not happen in iOS 10.3.1 simulator. * I verified that this issue happens in iOS 9.0 and 9.3 simulator. * I've tried setting "tiapp.xml" {{<transpile>}} setting true and false. No difference. Always fails on iOS 9.x Setting {{<transpile>}} to false surprisingly works on iOS 8.
| 5 |
3,321 |
TIMOB-26127
|
06/10/2018 11:28:59
|
Android: Video Quality undefined
|
Can't changer the quality of media camera because Titanium media video qualities is undefined {quote} Ti.API.info("Titanium.Media.QUALITY_HIGH " + Titanium.Media.QUALITY_HIGH); Ti.API.info("Titanium.Media.QUALITY_MEDIUM " + Titanium.Media.QUALITY_MEDIUM); Ti.API.info("Titanium.Media.QUALITY_LOW " + Titanium.Media.QUALITY_LOW); Ti.API.info("Titanium.Media.QUALITY_640x480 " + Titanium.Media.QUALITY_640x480); Ti.API.info("Titanium.Media.QUALITY_IFRAME_960x540 " + Titanium.Media.QUALITY_IFRAME_960x540); Ti.API.info("Titanium.Media.QUALITY_IFRAME_1280x720 " + Titanium.Media.QUALITY_IFRAME_1280x720);{quote} Logs ==> 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_HIGH undefined 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_MEDIUM undefined 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_LOW undefined 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_640x480 undefined 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_IFRAME_960x540 undefined 06-10 10:20:45.406 30754 30754 I TiAPI : Titanium.Media.QUALITY_IFRAME_1280x720 undefined
| 5 |
3,322 |
TIMOB-26120
|
06/11/2018 19:00:30
|
Update npm package dependencies and reduce security vulnerabilities listed
|
We have a number of security vulnerabilities now listed by default on npm installs (as of npm 6 this is built into the process). We should try to update all of our npm package dependencies as much as possible, as well as attempt to drive down the security vulnerabilities listed as low as possible (ideally none). This has knock-on effects on all of the npm packages we generate and dependencies upon in the SDK, so this will include fixes for things like node-appc, ioslib, windowslib, appc-aar-tools, etc.
| 13 |
3,323 |
TIMOB-26121
|
06/12/2018 00:08:19
|
iOS: Default simulator should be compatible with selected xcode
|
*TEST CASE* - Install xcode-beta (10.0) along with xcode (9.x) - Use xcode-select to select 9.x - Build a project without specifying a simulator - An iOS 12.0 simulator will be selected which is only compatible with xcode 10.0
| 5 |
3,324 |
TIMOB-26124
|
06/12/2018 19:17:11
|
Android: "Ti.buildHash" property always returns null
|
*Summary:* The {{Ti.buildHash}} property always returns {{null}} on Android. This has been happening since Titanium 6.0.0. _(This is not an issue on iOS.)_ *Steps to reproduce:* * Build and run the below code on Android. * On app startup, an alert displays the {{buildHash}}. * Note that it displays it as "undefined". _(This is the bug.)_ {code:javascript} alert("Ti.buildHash = " + Ti.buildHash); {code} *Cause:* Our "android.js" build script expects to receive {{option.gitHash}} with a capital 'H' here... https://github.com/appcelerator/titanium_mobile/blob/master/build/android.js#L22 But our "scons-build.js" and "scons-cleanbuild.js" scripts are passing in a lowercase {{githash}}. https://github.com/appcelerator/titanium_mobile/blob/master/build/scons-build.js https://github.com/appcelerator/titanium_mobile/blob/master/build/scons-cleanbuild.js *Note:* The {{buildHash}} is mostly needed to distinguish between an RC and GA version of Titanium. We log the Titanium version on app startup and this is helpful to better provide tech-support for the community.
| 1 |
3,325 |
TIMOB-26126
|
06/12/2018 22:56:01
|
Android: Update emulator tooling path
|
- The current {{tools/emulator}} path is now obsolete - Update the path to the newer {{emulator/emulator}} path *TEST CASE* - Build and run a project using an x86 emulator - {{appc run -p android}} *EXPECTED* - Emulator runs correctly *ACTUAL* {code} [ERROR] Emulator exited with error: 1 [ERROR] PANIC: Missing emulator engine program for 'x86' CPU. {code}
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.