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,826 |
TIMOB-27742
|
01/28/2020 18:51:38
|
Android: Minor camera focus issues
|
- Camera should not crash with {{E/TiExceptionHandler: (main) [55,37938] autoFocus failed}} - Camera should continue to auto focus after taking a picture *TEST CASE* {code:js} const overlay = Ti.UI.createView({}); const takePicture = Ti.UI.createButton({ title: 'Take Picture' }); takePicture.addEventListener('click', _ => { Ti.Media.takePicture(); }); overlay.add(takePicture); Ti.Media.requestCameraPermissions(e => { if (e.success) { Ti.Media.showCamera({ success: e => { if (e.success) { console.log('Taken picture successfully!'); } else { console.error(JSON.stringify(e, null, 2)); } }, saveToPhotoGallery: true, autohide: false, overlay: overlay, mediaTypes: [ Ti.Media.MEDIA_TYPE_PHOTO ] }); } }); {code}
| 3 |
3,827 |
TIMOB-27745
|
02/04/2020 04:38:42
|
Android: Add "google-services.json" support for Firebase
|
*Summary:* Google documents that you should configure your app for Firebase via a "google-services.json" file. Titanium does not currently support this JSON file and requires app developers to call Google's Java APIs to configure the app for Firebase instead. Add JSON file support will make this much simpler and would follow their docs. *Note:* Google documents how to set this up here... https://firebase.google.com/docs/android/setup *Recommended Solution:* The file should be added to the following Titanium project folder... {code} ./platform/android/google-services.json {code} If the file is found, we need to copy it to the following build folder location... {code} ./build/android/app {code} We'll need to add the following to the [root.build.gradle|https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/build/root.build.gradle] file. {code:groovy} buildscript { dependencies { classpath 'com.google.gms:google-services:4.3.3' } } {code} We'll need to add the following to the [app.build.gradle|https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/build/app.build.gradle] file. {code:groovy} apply plugin: 'com.google.gms.google-services' {code}
| 5 |
3,828 |
TIMOB-27748
|
02/04/2020 05:49:21
|
Windows app issues with 8.3.1.GA
|
Hi, I have upgraded the titanium SDK 7.2.0.GA to 8.3.1.GA, but after upgrading Windows app having the following issues: 1) Small Fonts Size 2) Splash Screen 3) Random Crashes 1) Small Font Size issues got resolved in 8.3.1.GA but got another issue with UI alignment. All UI alignment is changed and it's not proper 2) Got workaround 3) Not able to fixed The third point is resolved in 9.0.0.v20181031080737. And as per the earlier discussion the 9.0.0.GA is going to release in the end of Jan 2020. Please provide the estimated date of release 9.0.0.GA. Find the attachment for earlier communication of release date of titanium SDK
| 5 |
3,829 |
TIMOB-27750
|
02/06/2020 15:01:00
|
Android: CLI fails to recognize avd emulator is booted when it starts it
|
We're seeing native modules builds (like this one for ti.map: https://jenkins.appcelerator.org/blue/organizations/jenkins/modules%2Fti.map/detail/PR-285/9/pipeline/) failing to run our test suite because once it generates a project and launches, it never seems to think the emulator is fully booted. I can reproduce locally. If I pre-boot an emulator and launch, it recognizes the emulator has booted and works. If I don't have one up and running, it fails to recognize when the emulator has booted.
| 8 |
3,830 |
TIMOB-27752
|
02/07/2020 02:45:18
|
Android: Exclude x86 and x86_64 architectures in "production" builds by default
|
*Summary:* When doing a "production" build, the {{x86}} and {{x86_64}} architectures should be excluded from the built Android app by default. That is, only ARM architectures should be included. *Note 1:* We have been excluding {{x86}} from "production" builds since Titanium 7.0.0. We want to maintain this behavior in Titanium 9.0.0's gradle builds and exclude {{x86_64}} as well. These architectures are mostly needed for testing purposes in the Android emulator. Removing these architectures can reduce the APK size by a significant amount. Also, physical Android device that support {{x86}} are extremely rare. *Note 2:* Modules built with Titanium 8.x.x and older do not support the {{x86_64}} architecture. Only modules built with Titanium 9.0.0 and higher support {{x86_64}}. When you include a module that does *+NOT+* support {{x86_64}} into a Titanium 9.0.0 or newer app, then the build system will strip out all {{x86_64}} architectures from the app. It's all or nothing, otherwise a crash will occur on an {{x84_64}} device/emulator. This means if you want your app to support {{x86_64}}, then all modules must be built with Titanium 9.0.0 or higher. *How to Override:* You can override this behavior and specify which architectures you want to include in the build by adding the following {{<abi/>}} entry in the "tiapp.xml" file. {code:xml} <ti:app xmlns:ti="http://ti.appcelerator.org"> <android> <abi>armeabi-v7a,arm64-v8a,x86,x86_64</abi> </android> </ti:app> {code}
| 3 |
3,831 |
TIMOB-27754
|
02/08/2020 07:12:50
|
SearchBar text color and hinTextColor does not work properly.
|
We have tested this issue using the attached sample code with ti SDK 8.3.1.GA iPhone 11 Pro Max(ios 13.3) simulator. I assigned a red color to the color attribute and also a red color for hintTextColor. Neither the hintTextColor nor color changes the color of the text. *Code:* *index.js* {code} $.index.open(); {code} *index.xml* {code} <Alloy> <Window class="container"> <SearchBar id="search" color="red" barColor="gray" showCancel="true" height="43" top="100" hintText= "Enter value ..." hintTextColor= "red" /> </Window> </Alloy> {code} *Test steps*: 1. Open Studio and create a new alloy project. 2. Copy index.xml and index.js code and paste your project. 3. Run the project on iPhone or simulator. 4. Then observe the search bar. *Test Output*: Please check the attachment section. Thanks.
| 3 |
3,832 |
TIMOB-27756
|
02/10/2020 20:35:18
|
watchOS: Including watchOS framework causing build error
|
When including a watchOS framework to our watchOS target, the build fails because the CLI tries to parse a compiled (binary) plist which shouldn't be checked. The easy but powerful fix is to not check plist files inside frameworks but still copy them.
| 3 |
3,833 |
TIMOB-27758
|
02/11/2020 05:10:34
|
Android: Modules with AARs in "lib" directory should trigger a build failure in 9.0.0
|
*Summary:* The Android gradle build system allows a library project to reference a local AAR for compilation, but it won't merge the local AAR's classes, "AndroidManifest.xml", assets, or "res" files into the library project's built AAR. This is intentional on Google's end. The build system will only merge all of the AAR files' content into an app project. Because of the above, a native module referencing local AAR files will crash at runtime when built with Titanium 9.0.0 and gradle. It will compile fine, but the classes in the AARs will not be included in the module; nor the app. *Solution:* When building a native Android module with Titanium, the CLI should trigger a build failure if the module's "lib" directory contains any AAR files and should tell the developer to reference AAR libraries via the "build.gradle" file instead. *Note:* This is a breaking-change. But by doing this, we force module developers to reference dependencies the gradle/maven way, which will solve library version conflict issues between modules.
| 5 |
3,834 |
TIMOB-27768
|
02/14/2020 16:50:07
|
iOS: TypeError: Cannot read property 'logger' of undefined
|
h5.Description Building a project with extensions, where one of the extensions does not contain a build phase will error with the below, easy fix to just convert to an arrow function {code} (node:96371) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'logger' of undefined at /Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/iphone/cli/commands/_build.js:3450:12 at Array.forEach (<anonymous>) at iOSBuilder.<anonymous> (/Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/iphone/cli/commands/_build.js:3439:51) at Array.forEach (<anonymous>) at iOSBuilder.<anonymous> (/Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/iphone/cli/commands/_build.js:3345:26) at Array.forEach (<anonymous>) at iOSBuilder.createXcodeProject (/Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/iphone/cli/commands/_build.js:3325:19) at /Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/node_modules/async/dist/async.js:3880:24 at replenish (/Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/node_modules/async/dist/async.js:1011:17) at iterateeCallback (/Users/awam/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA/node_modules/async/dist/async.js:995:17) {code} h5.Steps to reproduce 1. Build Hans' app h5.Actual Above error h5.Expected No error
| 1 |
3,835 |
TIMOB-27769
|
02/18/2020 20:04:19
|
Android: Textfield inputs not setting in focused textfield and Keyboard not showing (sometimes) on a textfields which is focused
|
In Tableview when they clicks on any text fields are not pop-up up keyboards but it is focusing (showing cursor) on the textfields. In their case, the issue is sometimes the keyboard is not opening for the text fields 'Middle name' and 'Last Name' and also once they enter value in 'Middle Name' fields clicks on next button should go to 'Last name' field. But the issue is, It's focusing on 'Last name' field but the text typing in the 'Middle name' field. Sometimes when they click on text field it is focusing, but it's not opening keyboard They have tested it with Ti-SDK 8.3.1.GA and above. *Sample project:* https://drive.google.com/open?id=1HaUmYK-KjbPerkw72feUtmlgwAFEjwbI *Recorded Video:* https://drive.google.com/open?id=1X1MYW_NtYafzLCovchGjKWUarrB4J-gW
| 8 |
3,836 |
TIMOB-27770
|
02/19/2020 00:15:23
|
Android: Module build should add empty "build.gradle" if missing
|
*Summary:* When building an existing module for 9.0.0, the build system's migration code should add an empty "build.gradle" file to the project folder if missing. *Reasons:* # This will help compel developers to use this file to reference libraries instead of using the "lib" directory. # Appcelerator Studio needs a "clue" in the directory that indicates it is an Android project or else it won't be able to build/package it. This will resolve [TISTUD-9204]. *Note:* Titanium 9.0.0's module template has already been updated to provide an empty "build.gradle" file. The migration code should use this same file.
| 3 |
3,837 |
TIMOB-27771
|
02/19/2020 16:51:34
|
Android: Hyperloop builds fail if NDK not installed as of 9.0.0
|
_(This issue was caught before 9.0.0.GA.)_ h5.Description When building a hyperloop application without an NDK installed the build errors with the below, we just need to do a defensive check when we're looking up the ndk path {code} [ERROR] TypeError: Cannot read property 'path' of null at HyperloopAndroidBuilder.build (/Users/awam/Library/Application Support/Titanium/modules/android/hyperloop/5.0.0/hooks/hyperloop.js:127:106) {code} h5.Steps to reproduce 1. Move your NDK away from the usual location (~/Library/Android/sdk/ndk/) so the CLI doesn't autodetect and remove it from the config with {{appc ti config --remove android.ndkPath 2. Build the hyperloop-examples app h5.Actual Above error h5.Expected No error
| 1 |
3,838 |
TIMOB-27774
|
02/19/2020 21:09:27
|
Android: Ti.Blob.imageAsResized() not working for JPEG with exif rotation as of 8.1.0
|
There were some changes in the imageAsResized function in https://jira.appcelerator.org/browse/TIMOB-26456 It looks they broke some stuff! Taking a camera image and resizing it to random values leads to strange results: {noformat} w=50, h=60 original size: [INFO] 4032 2268 resized size: [INFO] 71 126 w=500, h=600 original size: [INFO] 4032 2268 resized size: [INFO] 1134 2016 w=300, h=300 original size: [INFO] 4032 2268 resized size: [INFO] 169 300 w=169, h=300 original size: [INFO] 4032 2268 resized size: [INFO] 567 1008 {noformat} It looks like it is keeping the aspect ration even if I don't want it to. {code} _.delay(function() { Titanium.Media.showCamera({ success: function(e) { var start = new Date().getTime(); var blob = e.media; var w = e.media.width; var h = e.media.height; var r = h / w; w = 300; h = 300; blob = blob.imageAsResized(w, h); $.img.image = blob; var end = new Date().getTime(); console.log(end - start); console.log(e.media.width, e.media.height); console.log(blob.width, blob.height); }, cancel: function() {}, error: function(error) {}, mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO] }); }, 4000); $.index.open(); {code} {code} <Alloy> <Window class="container"> <ImageView id="img"></ImageView> </Window> </Alloy> {code} Note: Allow camera permissions! *Tested versions:* SDK 8.3.0.GA, 8.3.1.GA, 9.0.0.RC *Device* Pixel 4, Android 10
| 3 |
3,839 |
TIMOB-27776
|
02/24/2020 19:37:33
|
Android: NDK version 21 outputs "Bad file descriptor"
|
- Latest NDK {{21.0.6113669}} outputs: {code} fcntl(): Bad file descriptor {code} Although builds do complete successfully, the log seems to increase build times significantly.
| 8 |
3,840 |
TIMOB-27777
|
02/24/2020 23:52:26
|
Android: Obtain holder for module references
|
- It is not possible to indirectly reference a module method or property. *TEST CASE* {code:js} const permissions = Ti.Filesystem.requestStoragePermissions; // Attempt to call 'requestStoragePermissions'. permissions(e => { if (e.success) { console.log('Storage permissions granted.'); return; } console.warn('Storage permissions denied.'); }); {code} - Should see a console log regarding storage permissions. - Should not see {code}Couldn't obtain argument holder{code}
| 5 |
3,841 |
TIMOB-27778
|
02/25/2020 00:00:28
|
Android: Update gradle build tools to 3.6.x
|
*Summary:* As of Titanium 9.0.0, we're using Android gradle build tool 3.4.2 to build the SDK, apps, and modules. {code} 'com.android.tools.build:gradle:3.4.2' {code} We should update the tools to version 3.6.x. https://developer.android.com/studio/releases/gradle-plugin#3-6-0 The newest build tools are supposed to improve APK build times. https://developer.android.com/studio/releases/gradle-plugin#zipflinger *Note:* We should also update our gradle template to 6.0.x which has full support for JDK 13. https://developer.android.com/studio/releases/gradle-plugin#updating-gradle https://docs.gradle.org/6.0/release-notes.html *To-Do:* We must update the version in the following files... https://github.com/appcelerator/titanium_mobile/blob/master/android/build.gradle https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/build/root.build.gradle Upgrading will cause the SDK and module builds to fail. The reason is because Google's build tool will now compile C/C++ before Java, which is an issue since our {{kroll-apt}} Java annotation processor generates C++ source files. We can solve this by adding the below to the library project's "build.gradle" file. {code:groovy} project.afterEvaluate { externalNativeBuildDebug.dependsOn compileDebugJavaWithJavac externalNativeBuildRelease.dependsOn compileReleaseJavaWithJavac } {code} https://github.com/appcelerator/titanium_mobile/blob/master/android/titanium/build.gradle https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/module/generated/build.gradle We will also need to update our gradlew and gradle library folder to the newest version. https://github.com/appcelerator/titanium_mobile/tree/master/android
| 3 |
3,842 |
TIMOB-27780
|
02/26/2020 04:28:28
|
Android: Hyperloop builds fail if JDK 12 or higher is installed
|
*Summary:* If you have JDK 12 or higher installed on your machine, then Titanium apps using the Hyperloop module will fail to build. *Steps to reproduce:* # Install JDK 12 or higher on your machine. # Build [hyperloop-example|https://github.com/appcelerator/hyperloop-examples] for Android. # Notice the build *fails* with the following error message. {code} [ERROR] hyperloop:generateMetabase: Failed to generated metabase: warning: [options] bootstrap class path not set in conjunction with -source 6 error: Source option 6 is no longer supported. Use 7 or later. error: Target option 6 is no longer supported. Use 7 or later. {code} *Cause:* As of JDK 12, Oracle has dropped support for the Java 6 language. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8028563 Hyperloop currently hardcodes its usage of the {{javac}} command line tool during the build to Java 1.6, which is why it fails when using the newest JDK. [android/hooks/metabase/metabase.js#L41|https://github.com/appcelerator/hyperloop.next/blob/24feb99f719da5e3df279452526638d46fa0043a/android/hooks/metabase/metabase.js#L41] *Solution:* Update {{javac}} usage to use Java 1.8 instead. *Note:* For JDK 13 support, we'll likely need to update Titanium's gradle template to 6.x.x as well, which means updating our Android build tools to 3.6.x via [TIMOB-27778].
| 3 |
3,843 |
TIMOB-27781
|
02/26/2020 19:38:11
|
Android: App/Module builds fail with JDK 13 as of 9.0.0
|
*Summary:* When building an app or module with Titanium 9.0.0, the build will fail if JDK 13 is installed. Titanium 8.3.x builds fine with JDK 13... except for Hyperloop builds: [TIMOB-27780] *Steps to reproduce:* # Install JDK 13. # Create a Titanium app project. # Build with Titanium 9.0.0 for Android. *Result:* {code} [ERROR] [GRADLE] FAILURE: Build failed with an exception. [ERROR] [GRADLE] [ERROR] [GRADLE] * Where: [ERROR] [GRADLE] Settings file '/Users/jquick2/Documents/Appcelerator_Studio_Workspace/kitchensink-v2/build/android/settings.gradle' [ERROR] [GRADLE] [ERROR] [GRADLE] * What went wrong: [ERROR] [GRADLE] Could not compile settings file '/Users/jquick2/Documents/Appcelerator_Studio_Workspace/kitchensink-v2/build/android/settings.gradle'. [ERROR] [GRADLE] > startup failed: [ERROR] [GRADLE] General error during semantic analysis: Unsupported class file major version 57 [ERROR] [GRADLE] [ERROR] [GRADLE] java.lang.IllegalArgumentException: Unsupported class file major version 57 [ERROR] [GRADLE] at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:184) [ERROR] [GRADLE] at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:166) [ERROR] [GRADLE] at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:152) [ERROR] [GRADLE] at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:273) {code} *Cause:* As of Titanium 9.0.0, we now build with gradle. We're currently using gradle v5.4.1 which does not support JDK 13. We'll need to upgrade to gradle v6.0.x (released January 2020) which supports JDK 13. https://docs.gradle.org/6.0/release-notes.html#java-13 *Note:* You can have multiple JDK installations on Mac. You can list the JDK versions installed by entering the following at the command line. {code} /usr/libexec/java_home -V {code} You can select which installed JDK version to use by entering the following at the command line. You'll need to set the {{<JavaVersion>}} to what's installed, which the above command line will list. The below can be set in your {{.bash_profile}} file. {code} export JAVA_HOME=$(/usr/libexec/java_home -v <JavaVersion>) {code} *Work-Around:* Downgrade to JDK 12 or lower. (JDK 8 is the min version needed.)
| 5 |
3,844 |
TIMOB-27782
|
02/28/2020 16:41:38
|
Ignoring a file in babel config causes an error during compile
|
If a file is ignored through a babel config file, an error will occur because it is trying to access properties of a transformation that didn't occur. Sample app to recreate issue: https://github.com/brentonhouse/timob-27782 Simply run "ti build -p ios --build-only" to see compiler error.
| 3 |
3,845 |
TIMOB-27784
|
02/29/2020 03:14:06
|
Android: Running "clean" on a module will error if "libs" folder does not exist
|
*Summary:* When developing a module, running the {{appc ti clean}} command on a module directory that is missing a "libs" folder will throw an error. This is a minor issue that you can safely ignore. The clean command will successfully delete the "build" and "dist" folders first if they exist, which is what's most important. *Steps to reproduce:* # Download a zip of the [ti.imagefactory|https://github.com/appcelerator-modules/ti.imagefactory] repo source. # Unzip the above. # Open the Terminal. # {{CD}} to folder: {{./ti.imagefactory/android}} # Enter: {{appc ti clean}} # Notice it errors with below message. # Enter: {{appc run -p android --build-only}} # Wait for the build to finish. # Enter: {{appc ti clean}} # Notice it errors with below message. *Result:* {code} [ERROR] :Failed to run command "clean" [ERROR] :Error: ENOENT: no such file or directory, scandir '/Users/<UserName>/Development/modules/ti.imagefactory/android/libs' {code} *Reason:* We're missing a "libs" directory existence check below. [titanium_mobile/android/cli/commands/_cleanModule.js|https://github.com/appcelerator/titanium_mobile/blob/73c73b6d352ada5918ec30e008c95bf12d7ed633/android/cli/commands/_cleanModule.js#L38]
| 1 |
3,846 |
TIMOB-27785
|
03/02/2020 14:48:42
|
Buffer: Proxy object's 'set' trap returned falsy value for property '0'
|
*Steps to reproduce the behavior* {code:js} (function () { 'use strict'; const b = Buffer.alloc(1); b[0] = 0; })(); {code} *Expected behavior* The value will be set. *Actual behavior* Setting the value fails with the following error message: {{Proxy object's 'set' trap returned falsy value for property '0'}}
| 3 |
3,847 |
TIMOB-27788
|
03/03/2020 10:01:33
|
Android: Unable to view UI.Switch when it is turned off.
|
h6.Reproduce 1. Create a sample classic app. 2. Replace app.js content with the attached app.js content. 3. Run the app on an Android device. h6.Problem Observed an issue that we are not able to view switch properly if it is turned off in Android devices. Please find the attached screenshot for reference.
| 1 |
3,848 |
TIMOB-27792
|
03/06/2020 07:03:00
|
iOS: Remove python dependency from SDK build
|
h5.Description When building the iOS portion of the SDK, we use [a python script|https://github.com/appcelerator/titanium_mobile/blob/cc1b0554a72c271ed2050b3e7ee4ce27627804e3/support/dev/localecompiler.py] to do some handling of i18n files. We should rewrite this in the same timeframe as the Android changes (TIMOB-27719) to allow us to remove the python dependency at the same time
| 5 |
3,849 |
TIMOB-27794
|
03/07/2020 02:55:52
|
Android: Improve kroll-apt incremental build times with SDK
|
*Summary:* The Titanium SDK incremental build times should be improved. Every time we make a Java code change in the Titanium SDK library, our "kroll-apt" Java annotation processor always re-generates C++ files for all Java proxies in our library, even if the proxy classes haven't changed. *Note:* On my machine, the build system recognizes that the re-generated C++ files haven't changed since the last build and does an incremental C++ build. On [~gmathews]' machine, the C++ incremental build does not work at all and recompiles all C++ files. Incremental build times after making a Java code changes takes {{20s}} for me and {{~1}} minute for Gary. *To-Do:* When our "kroll-apt" Java annotation processor reads all {{@Kroll}} annotations, it should read the last written JSON bindings file to see if the bindings have changed since the last build. If not, do not re-generate the proxy C++ files... unless the files are missing.
| 5 |
3,850 |
TIMOB-27797
|
03/10/2020 15:35:20
|
Android: Unable to see "error" event in remote images
|
Using the test case below the "error" event in remote images is not fired unlike on iOS. *Test Steps:* # Create a new Titanium application # Add the test case below in to the {{app.js}} # Run the application *Test Case:* {code:java} Ti.UI.setBackgroundColor('#000'); var tabGroup = Ti.UI.createTabGroup(); var win1 = Ti.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff', }); var img = Ti.UI.createImageView({ image:'http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg' }); win1.add(img); img.addEventListener('error', function(){ Ti.API.info('--------------fired error event----------'); }); tabGroup.addTab(Ti.UI.createTab({ title:'Tab 1', window:win1 })); tabGroup.open(); {code} *Actual result* Following Error is shown {code:java} [ERROR] TiDownloadManager: (pool-4-thread-1) [174,616] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [200,816] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [104,920] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [118,1038] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [105,1143] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [103,1246] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg [ERROR] TiDownloadManager: (pool-5-thread-1) [105,1351] Failed to download from: http://files.daddyhunt.com/sites/default/files/imagecache/mangrid-212/photos/z/z/z/277606/Photo_on_2010-09-14_at_13.14_3.jpg {code} *Expected Result* Following should be seen in the console {code:java} [INFO] --------------fired error event---------- {code}
| 5 |
3,851 |
TIMOB-27846
|
03/10/2020 17:37:42
|
iOS: Calling Ti.Platform.openURL without all parameters causes the app to crash (regression)
|
When I use Ti.Platform.openURL, and the app goes to background, the app crashes with this error: [ERROR] Script Error { [ERROR] toJSON = "<KrollCallback: 0x600001e12380>"; [ERROR] }
| 5 |
3,852 |
TIMOB-27798
|
03/10/2020 18:42:35
|
Android: Module build should auto-download NDK if not installed
|
*Summary:* Google's gradle tool supports downloading the Android NDK for C/C++ builds. Titanium's module build system should automatically download the NDK in case it's not already installed. This will help reduce tech-support issues. *Recommended Solution:* When we upgrade the Android gradle plugin to v3.6.0 or higher, we can specify the exact NDK version we want to download in the {{build.gradle}} as follows. https://developer.android.com/studio/projects/install-ndk#apply-specific-version {code:groovy} android { ndkVersion "major.minor.build" } {code} We should do the above if the CLI fails to find the Android NDK path in our [_buildModule.js|https://github.com/appcelerator/titanium_mobile/blob/master/android/cli/commands/_buildModule.js] script. In this case, we should also omit the NDK path from the gradle {{local.properties}} file [here|https://github.com/appcelerator/titanium_mobile/blob/master/android/cli/commands/_buildModule.js#L517]. *Research Results:* Using {{android.ndkVersion}} to download a specific version (as noted above) appears to be unreliable. https://issuetracker.google.com/issues/132876707 https://stackoverflow.com/questions/60404457/android-no-version-of-ndk-matched-the-requested-version Attempting to set this to NDK version {{19.2.5345600}} causes the following build error. {code} No version of NDK matched the requested version 19.2.5345600. Versions available locally: 20.1.5948944 {code} Attempting to set this to NDK version {{20.0.5594570}} causes the following build error. This appears to be a recent issue. {code} No version of NDK matched the requested version 20.0.5594570. Versions available locally: 20.1.5948944 {code} It seems like when new NDK versions get released, older NDK versions appear to stop downloading via gradle (this is speculation). Because of this, we should avoid this feature at the moment. If we don't set the NDK version in gradle, then the gradle build system will download the newest NDK version which has a minor issue noted in [TIMOB-27776] but it still works.
| 3 |
3,853 |
TIMOB-27808
|
03/13/2020 17:32:46
|
Node: console.trace is not a function.
|
*Steps to reproduce the behavior* {code:js} console.trace('test'); {code} *Actual behavior* The following error is thrown: {code} console.trace is not a function. (In 'console.trace('test')', 'console.trace' is undefined) {code} *Expected behavior* The message gets printed to the logs with {{trace}} log level.
| 3 |
3,854 |
TIMOB-27822
|
03/18/2020 04:27:47
|
Ti.UI.iPad.Popover including arrow in content view on iOS 13
|
As of iOS 13, Ti.UI.iPad.Popover's "arrow" is included as part of the content area. This was not the case in previous versions of iOS, and is causing content to be pushed outside the bounds of what is visible in the Popover on iOS 13 devices. It's probably an issue with safe area implementation in iOS 13. See !popover_ios13_issue.png|thumbnail! for the difference between how it is working on iOS 13 and iOS 12. Reproduction code: {code:java} var win = Ti.UI.createWindow({backgroundColor: 'white'}); var button = Ti.UI.createButton({title: 'Open Popover Up', top: 100}); var button2 = Ti.UI.createButton({title: 'Open Popover Left', top: 200}); button.addEventListener('click', function(e){ popover.show({ view: button }); }) button2.addEventListener('click', function(e){ popover2.show({ view: button2 }); }) win.add(button); win.add(button2); var contentWindow = Ti.UI.createWindow({ title: 'Window title' }); contentWindow.add(Ti.UI.createLabel({text: "Example text."})); var popover = Ti.UI.iPad.createPopover({ backgroundColor: 'black', arrowDirection: Titanium.UI.iPad.POPOVER_ARROW_DIRECTION_UP, contentView: Ti.UI.createNavigationWindow({ width: 450, height: 300, window: contentWindow, }) }); var popover2 = Ti.UI.iPad.createPopover({ backgroundColor: 'black', arrowDirection: Titanium.UI.iPad.POPOVER_ARROW_DIRECTION_LEFT, contentView: Ti.UI.createNavigationWindow({ width: 450, height: 300, window: contentWindow, }) }); win.open(); {code}
| 5 |
3,855 |
TIMOB-27823
|
03/25/2020 17:31:19
|
Android: javascript files/content assumed to be binary for Ti.Blob on apilevel 29+
|
This was caught by our test suite on android emulator. It seems Android changed the underlying mime type mapping result for javascript files to report {{'application/javascript'}} (whereas before it reported {{'text/javascript'}}) Our TiBlob code assumes most {{'application/'}} mime types are binary, and as a result thinks JS files hold binary content.
| 5 |
3,856 |
TIMOB-27825
|
03/25/2020 21:10:31
|
Android: High CPU usage in Android Studio
|
Opening titanium_mobile/android with Android Studio 3.6+ causes high CPU usage when viewing *.java files. This is an Android Studio pre-processor issue that can be worked around by disabling specific _Java Inspections_. This bug has been reported and can be tracked: https://issuetracker.google.com/issues/152430526
| 5 |
3,857 |
TIMOB-27834
|
03/27/2020 08:49:25
|
Android: NavigationWindow doesnt trigger open and close events
|
As per the docs the [open|http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.NavigationWindow-event-open] and [close|http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.NavigationWindow-event-open] events must be triggered when the NavigationWindow opens and closes respectively. This only works on iOS. Here is a sample: _controller.xml_ {code:xml} <Alloy> <NavigationWindow onOpen="onNavigationWindowOpen" onClose="onNavigationWindowClose"> <Window> <Label>Main</Label> </Window> </NavigationWindow> </Alloy> {code} _controller.js_ {code:javascript} // Arguments passed into this controller can be accessed via the `$.args` object directly or: var args = $.args; function onNavigationWindowOpen() { Ti.API.info('Opened'); } function onNavigationWindowClose() { Ti.API.info('Closed'); } {code} Nor _Opened_ neither _Closed_ events were shown inside the console.
| 3 |
3,858 |
TIMOB-27830
|
04/02/2020 22:25:08
|
Android: TabGroup.titleColor has no effect
|
Attempting to specify a {{titleColor}} or {{activeTitleColor}} does not work, the TabGroup defaults to standard system colors. *TEST CASE* {code:js} const tabGroup = Ti.UI.createTabGroup(); const tabWin_home = Ti.UI.createWindow({ title: 'Home', backgroundColor: 'white' }); const tab_home = Ti.UI.createTab({ icon: 'home.png', title: 'Home', titleColor: 'red', activeTitleColor: 'blue', window: tabWin_home }); const tabWin_chat = Ti.UI.createWindow({ title: 'Chat', backgroundColor: 'white' }); const tab_chat = Ti.UI.createTab({ icon: 'chat.png', title: 'Chat', titleColor: 'red', activeTitleColor: 'blue', window: tabWin_chat }); tabGroup.addTab(tab_home); tabGroup.addTab(tab_chat); tabGroup.open(); {code}
| 3 |
3,859 |
TIMOB-27831
|
04/02/2020 22:47:20
|
Android: Implement TabGroup.tintColor
|
Implement ability to specify a {{tintColor}} or {{activeTintColor}} for tab icons. *TEST CASE* {code:js} const tabGroup = Ti.UI.createTabGroup({ // style: Ti.UI.Android.TABS_STYLE_BOTTOM_NAVIGATION }); const tabWin_home = Ti.UI.createWindow({ title: 'Home', backgroundColor: 'white' }); const tab_home = Ti.UI.createTab({ icon: 'home.png', title: 'Home', titleColor: 'red', activeTitleColor: 'blue', tintColor: 'red', activeTintColor: 'blue', window: tabWin_home }); const tabWin_chat = Ti.UI.createWindow({ title: 'Chat', backgroundColor: 'white' }); const tab_chat = Ti.UI.createTab({ icon: 'chat.png', title: 'Chat', titleColor: 'red', activeTitleColor: 'blue', tintColor: 'red', activeTintColor: 'blue', window: tabWin_chat }); tabGroup.addTab(tab_home); tabGroup.addTab(tab_chat); tabGroup.open(); {code}
| 3 |
3,860 |
TIMOB-27835
|
04/07/2020 13:37:06
|
Android: Repository specified in modules build.gradle is not able to be resolved when building an application
|
h5.Description When providing an extra maven repository that provides a dependency in a modules build.gradle file, when building an application that uses that dependency cannot be resolved. *Workaround*: In your application, add a build.gradle to {{platform/android}} (classic) or {{app/platform/android}} (alloy) that contains the repository definition. h5.Steps to reproduce 1. Copy the below to a build.gradle file in a module {code} allprojects { repositories { maven { url 'https://dl.bintray.com/radiusnetworks/flybuy-sdk'} } } dependencies { implementation "com.radiusnetworks.flybuy:sdk:1.1.1" implementation "com.radiusnetworks.flybuy:api:1.1.1" } {code} 2. Build the module using {{appc run -p android}} (so the app creation/building happens) h5.Actual During the *application build* the following error occurs {code} [ERROR] [GRADLE] [ERROR] [GRADLE] FAILURE: Build failed with an exception. [ERROR] [GRADLE] [ERROR] [GRADLE] * What went wrong: [ERROR] [GRADLE] Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. [ERROR] [GRADLE] > Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'. [ERROR] [GRADLE] > Could not find com.radiusnetworks.flybuy:api:1.1.1. [ERROR] [GRADLE] Required by: [ERROR] [GRADLE] project :app > com.awam:foo:1.0.0 [ERROR] [GRADLE] [ERROR] [GRADLE] * Try: [ERROR] [GRADLE] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. [ERROR] [GRADLE] [ERROR] [GRADLE] * Get more help at https://help.gradle.org [ERROR] [GRADLE] [ERROR] [GRADLE] BUILD FAILED in 2s [ERROR] "gradlew" tool returned exit code: 1 [ERROR] Failed to run ti /Users/awam/.nvm/versions/node/v10.16.3/bin/ti {code} h5.Expected My expectation is that the repository definition shouldn't be required in app and module (but I could be wrong)
| 0 |
3,861 |
TIMOB-27837
|
04/08/2020 01:51:37
|
Android: Custom theme ignored by modal/translucent windows as of 9.0.0
|
*Summary:* As of Titanium 9.0.0, a custom Android theme/style defined in XML is ignored by windows: * With "modal" property set to {{true}}. * With "opacity" property set less than {{1.0}}. (ie: translucent windows) *Steps to reproduce:* # Create a Classic app project with below files. # Build and run on Android. # Notice modal window's title bar is dark gray, but theme sets it to red. # Notice button's text is in all caps, but theme sets it to use lowercase letters. app.js {code:javascript} var window = Ti.UI.createWindow({ title: "Modal Window", modal: true, }); var closeButton = Ti.UI.createButton({ title: "Close", }); closeButton.addEventListener("click", function() { window.close(); }); window.add(closeButton); window.open(); {code} tiapp.xml {code:xml} <?xml version="1.0" encoding="UTF-8"?> <ti:app> <android> <manifest> <application android:theme="@style/MyTheme"/> </manifest> </android> </ti:app> {code} ./platform/android/res/values/my_theme.xml {code:xml} <?xml version="1.0" encoding="UTF-8"?> <resources> <style name="MyTheme" parent="@style/Theme.AppCompat"> <item name="buttonStyle">@style/MyButtonStyle</item> <item name="colorPrimary">#FF0000</item> </style> <style name="MyButtonStyle" parent="@style/Widget.AppCompat.Button"> <item name="android:textAllCaps">false</item> </style> </resources> {code}
| 5 |
3,862 |
TIMOB-27850
|
04/16/2020 02:04:57
|
Android: App/Module builds fail with JDK 14 as of 9.0.0
|
*Summary:* When building an app or module with Titanium 9.0.0, the build will fail if JDK 14 is installed. Titanium 8.3.x builds fine with JDK 14... except for Hyperloop builds: [TIMOB-27780] *Steps to reproduce:* # Install JDK 14. # Create a Titanium app project. # Build with Titanium 9.0.1 for Android. (9.0.1 supports JDK 13.) *Result:* {code} [ERROR] [GRADLE] [ERROR] [GRADLE] FAILURE: Build failed with an exception. [ERROR] [GRADLE] [ERROR] [GRADLE] * What went wrong: [ERROR] [GRADLE] Could not initialize class org.codehaus.groovy.runtime.InvokerHelper [ERROR] [GRADLE] [ERROR] [GRADLE] * Try: [ERROR] [GRADLE] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. [ERROR] [GRADLE] [ERROR] [GRADLE] * Get more help at https://help.gradle.org [ERROR] [GRADLE] [ERROR] [GRADLE] BUILD FAILED in 597ms [ERROR] "gradlew" tool returned exit code: 1 {code} *Cause:* As of Titanium 9.0.0, we now build with gradle. We need to upgrade gradle to v6.3.0 which recently added JDK 14 support. https://docs.gradle.org/6.3/release-notes.html *To-Do:* In folder {{titanium_mobile/android}}, execute below command line to upgrade gradle wrapper files. {code} ./gradlew wrapper --distribution-type all --gradle-version 6.3 {code} We should also update our {{com.android.tools.build:gradle}} tool to version {{3.6.2}} for files... https://github.com/appcelerator/titanium_mobile/blob/master/android/build.gradle https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/build/root.build.gradle *Note:* You can have multiple JDK installations on Mac. You can list the JDK versions installed by entering the following at the command line. {code} /usr/libexec/java_home -V {code} You can select which installed JDK version to use by entering the following at the command line. You'll need to set the {{<JavaVersion>}} to what's installed, which the above command line will list. The below can be set in your {{.bash_profile}} file. {code} export JAVA_HOME=$(/usr/libexec/java_home -v <JavaVersion>) {code} *Work-Around:* Downgrade to JDK 13 for Titanium 9.0.1. Downgrade to JDK 12 for Titanium 9.0.0. (See [TIMOB-27781]) (JDK 8 is the min version needed.)
| 5 |
3,863 |
TIMOB-27852
|
04/17/2020 17:35:22
|
Android: Production builds no longer copy AAB to distribution folder as of 9.0.1
|
*Summary:* As of Titanium 9.0.1, a "production" build no longer outputs an AAB (Android App Bundle) file to the distribution directory. The build does create the AAB file under the "build" directory, but not to the desired location. *Steps to reproduce:* # Delete the last built APK and AAB files from the distribution folder. # Set up a project to build with 9.0.1. # Build for "production". # Go to the selected "Distribution" folder. # Notice the AAB file is missing. Only the APK file is there. *Work-Around:* The AAB file can be found under the following folder instead... {code} ./build/android/app/build/outputs/bundle/release/aap-release.aab {code}
| 3 |
3,864 |
TIMOB-27855
|
04/19/2020 14:27:01
|
Android: Animate elevation value
|
Currently it is not possible to animate the elevation value. Other values can be animated. {code} var win = Ti.UI.createWindow({ layout: "vertical", backgroundColor: "#fff" }); var v = Ti.UI.createView({ elevation: 20, width: 200, height: 200, top: 50, backgroundColor:"#fff" }); var v2 = Ti.UI.createView({ width: 200, height: 200, top: 50, backgroundColor:"#fff" }); win.add([v,v2]); setTimeout(function(){ v.animate({ duration: 2000, elevation: 0, autoreverse:true, repeat: 10 }); v2.animate({ duration: 2000, elevation: 20, autoreverse:true, repeat: 10 }); }, 1000) win.open(); {code}
| 5 |
3,865 |
TIMOB-27862
|
04/22/2020 01:29:23
|
Android: Add callback support to Ti.Platform.openURL()
|
*Summary:* On Android, the {{Ti.Platform.openURL()}} method only supports the URL argument. The 2 optional arguments, "options" dictionary and callback, are ignored and only supported on iOS. https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Platform-method-openURL We should add support for the callback argument for consistency with iOS. {code:javascript} // Add support for the callback argument. var result = Ti.Platform.openURL("https://www.google.com", function(e) { Ti.API.info("### openURL() callback event.success: " + e.success); }); // We should still support returned boolean for backward compatibility. Ti.API.info("### openURL() returned: " + result); {code} *Note:* The "options" dictionary should continue to be ignored since it only supports iOS settings. Meaning that the below should work on Android without issue. {code:javascript} var result = Ti.Platform.openURL("https://www.google.com", {/* Ignore Me */}, function(e) { Ti.API.info("### openURL() callback event.success: " + e.success); }); {code}
| 5 |
3,866 |
TIMOB-27871
|
04/28/2020 02:19:28
|
Android: Setting TextField/TextArea "editable" to false should allow user to copy text to clipboard
|
*Summary:* When setting a {{TextField}}/{{TextArea}} object's "editable" property to {{false}}, the end-user should be able to select the text and copy it to the clipboard. Allowing this is typically the main purpose of making a field read-only. If the app developer doesn't want the text to be selectable, then disabling it via the "enabled" property would be better. *Note:* On iOS, we currently support copying text from a read-only {{TextArea}}. Unfortunately, iOS' {{TextField}} does not support this. (It should though.)
| 8 |
3,867 |
TIMOB-27872
|
04/29/2020 17:21:18
|
Android: Blob imageAsX() methods ignore EXIF orientation if not wrapping a file
|
*Summary:* When a Titanium blob references a non-file type, such as a byte buffer or "content://" URL, then the blob's {{imageAs*()}} methods will ignore a JPEG's EXIF orientation setting. This affects the following methods: * {{Blob.imageAsCropped()}} * {{Blob.imageAsResized()}} * {{Blob.imageAsThumbnail()}} * {{Blob.imageWithAlpha()}} * {{Blob.imageWithRoundedCorner()}} * {{Blob.imageWithTransparentBorder()}} *Steps to reproduce:* # Build the attached [^DownloadImageBlobTest.js] on Android. # Tap on the "Download" button. (Requires Internet access.) # Tap on "JPEG - EXIF Rotate 90" in option dialog. # Notice that the displayed resized image is not upright. (This is the bug. # Do the same with all of the other "EXIF" options in the dialog. They all have this issue.
| 5 |
3,868 |
TIMOB-27874
|
04/30/2020 06:33:30
|
TiAPI: Add Ti.Locale.parseDecimal() method
|
*Summary:* Titanium has APIs to turn numbers into localized strings, but there are no APIs to convert a localized numeric string back to a number type. *Proposed Solution:* Add the following method. {{Ti.Locale.parseDecimal(text \[, locale \]); // Returns number type.}} If the above was given an invalid string, then it will return {{NaN}} (Not-a-Number), which matches JavaScript's standard {{Number.parseFloat()}} method behavior. *Main Use-Case:* A {{TextField}} using a decimal keyboard type will be using the device's current locale for the decimal separator. This means the decimal separator will be a comma {{,}} in Europe. It will can also be a unicode decimal separator for Arabic locales. When reading the {{TextField}} string "value" property, the app developer will need an easy means of parsing the localized numeric string back to a JS number type. *Test Cases:* Converting a number to localized string and then back to a number. {code:javascript} var oldNumericValue = 123.456; var stringValue = String.formatDecimal(oldNumericValue); var newNumericValue = Ti.Locale.parseDecimal(stringValue); if (Math.abs(newNumericValue - oldNumericValue) < Number.EPSILON) { console.log('Parsed number matches original number.'); } {code} Parsing equivalent numbers from 2 different locales. {code:javascript} var number1 = Ti.Locale.parseDecimal('1,234,567.8', 'en-US'); var number2 = Ti.Locale.parseDecimal('1.234.567,8', 'de-DE'); if (Math.abs(number1 - number2) < Number.EPSILON) { console.log('Parsed numbers match.'); } {code} Strings that cannot be converted to a number will return NaN. {code:javascript} var result = Ti.Locale.parseDecimal('Invalid'); if (Number.isNaN(result)) { console.log('Invalid string returned NaN.'); } {code}
| 5 |
3,869 |
TIMOB-27879
|
05/03/2020 14:35:42
|
Android: ListView should only fire "scrolling" event when moving a min distance
|
Android's {{ListView}} can spam a "scrolling" event even when your finger is held at a single position. This is because there is currently no touch tolerance applied and 1 pixel scroll movement will fire the event. It should only fire a "scrolling" event when the scroll direction changes and for a minimum pixel distance specified by Google's [ViewConfiguration.getScaledTouchSlop()|https://developer.android.com/reference/android/view/ViewConfiguration#getScaledTouchSlop()] API. {code} var win = Ti.UI.createWindow({backgroundColor: 'gray'}); var listView = Ti.UI.createListView(); var sections = []; var fruitSection = Ti.UI.createListSection({ headerTitle: 'Fruits'}); var fruitDataSet = [ {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Apple'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, {properties: { height: 100,title: 'Banana'}}, ]; fruitSection.setItems(fruitDataSet); sections.push(fruitSection); listView.appendSection(sections); listView.addEventListener("scrolling",function(e){ console.log(e.direction); }) win.add(listView); win.open(); {code}
| 5 |
3,870 |
TIMOB-27881
|
05/05/2020 19:15:58
|
Android: ImageView tintColor has no effect
|
- {{Ti.UI.ImageView.tintColor}} fails to apply the defined color to the {{ImageView}} *TEST CASE* {code:js} const win = Ti.UI.createWindow({ backgroundColor: 'white' }); const img = Ti.UI.createImageView({ width: '80%', image: 'https://about.gitlab.com/images/press/logo/png/gitlab-icon-1-color-black-rgb.png', tintColor: 'red' }); win.add(img); win.open(); {code} *EXPECTED* - Image should tint to defined color (red). *ACTUAL* - Image does not tint to defined color and remains black.
| 3 |
3,871 |
TIMOB-27882
|
05/06/2020 16:01:33
|
Android: Unable to do a production build after switching SDK on Windows
|
When creating a production build with two different SDKs the following error can be seen: {code:java} [ERROR] : Error: EBUSY: resource busy or locked, unlink 'C:\Users\APPC\Documents\Appcelerator_Studio_Workspace\elloello\build\android\app\build\intermediates\metadata_library_dependencies_report\release\dependencies.pb' {code} *Note*: If you manually end the java-tm process you are able to build *Test Steps:* # Open Appcelerator studio # Create a new alloy application using SDK: 9.0.2.v20200505111803 # Package using the Android store option in the drop down menu # Go through the prompts and select an output destination # Wait for .APK and .AAB to be created # Change SDK in the tiapp.xml to SDK: 9.1.0.v20200505112143 # Package again using the Android store option in the drop down menu # Go through the prompts and select an output destination
| 5 |
3,872 |
TIMOB-27890
|
05/08/2020 19:35:37
|
Android: Add Intl.DateTimeFormat support
|
*Summary:* On Android, we should add support for JavaScript class {{Intl.DateTimeFormat}}. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/DateTimeFormat This is already supported on iOS. We should add it to Android for parity. *Note:* To add official {{Intl}} support to V8, we would have to {{#if}} it in, but this involves adding the ICU (International Components for Unicode) C++ library which is about 20 MB per architecture. This is too big and is not mobile friendly. Especially since Google Play has a 100 MB limit on APKs. So, the most reasonable solution is to implement this ourselves in Java. *Alternatives:* On older Titanium versions, your only option to generate localized date/time strings was via APIs: * [String.formatDate()|https://docs.appcelerator.com/platform/latest/#!/api/Global.String-method-formatDate] * [String.formatTime()|https://docs.appcelerator.com/platform/latest/#!/api/Global.String-method-formatTime]
| 8 |
3,873 |
TIMOB-27891
|
05/08/2020 19:41:55
|
Android: Add Intl.Collator support
|
*Summary:* On Android, we should add support for the JavaScript {{Intl.Collator}} class. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Collator A collator is used to do localized string comparisons. This allows an app to correct sort text for the current locale/language. This is already supported on iOS. We should add it to Android for parity. *Note:* To add official {{Intl}} support to V8, we would have to {{#if}} it in, but this involves adding the ICU (International Components for Unicode) C++ library which is about 20 MB per architecture. This is too big and is not mobile friendly. Especially since Google Play has a 100 MB limit on APKs. So, the most reasonable solution is to implement this ourselves in Java.
| 5 |
3,874 |
TIMOB-27892
|
05/08/2020 19:57:40
|
Android: Update toLocale*String() methods to support locale/options
|
*Summary:* On Android, the following methods ignore the {{locales}} and {{options}} arguments. They also ignore the current locale and always use {{"en-US"}} when formatting a string. * [Date.toLocaleString()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString] * [Date.toLocaleDateString()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleDateString] * [Date.toLocaleTimeString()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleTimeString] * [Number.toLocaleString()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toLocaleString] * [String.localeCompare()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/localeCompare] * [String.toLocaleLowerCase()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toLocaleLowerCase] * [String.toLocaleUpperCase()|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toLocaleLowerCase] On iOS, the above methods *+do+* support locale/options. We should add the same on Android for parity and to better support the standard JavaScript APIs. *Note:* To add official {{Intl}} support to V8, we would have to {{#if}} it in, but this involves adding the ICU (International Components for Unicode) C++ library which is about 20 MB per architecture. This is too big and is not mobile friendly. Especially since Google Play has a 100 MB limit on APKs. So, the most reasonable solution is to implement this ourselves in Java. *Alternatives:* On older Titanium versions, your only option to generate localized strings was via APIs: * [String.formatDecimal()|https://docs.appcelerator.com/platform/latest/#!/api/Global.String-method-formatDecimal] * [String.formatDate()|https://docs.appcelerator.com/platform/latest/#!/api/Global.String-method-formatDate] * [String.formatTime()|https://docs.appcelerator.com/platform/latest/#!/api/Global.String-method-formatTime]
| 8 |
3,875 |
TIMOB-27895
|
05/10/2020 08:48:27
|
TiAPI: Handle semantic colors (dark mode) without helper function
|
Titanium supports dark mode pretty okay, which is a great achievement! Unfortunately, there is one major issue when using it's API's right now: One has to fetch the colors via {{Ti.UI.fetchSemanticColor}} which does not work in Alloy (neither when styling in XML views nor in TSS styles). Users should create a mapping that fetches the color on the app start and write it to something more accessible like {{Alloy.CFG.styles.myColor}}. That is fine until you have 200+ colors that slow down the app launch by seconds (!) because all colors of the app need to be set before even shown *Suggestion*: Be able to pass semantic colors just like normal css colors, e.g. {code:js} '#myView': { backgroundColor: 'contentBackgroundColor' } {code} which works with just one line of code inside the color handling of iOS (WebColor.m) / Android (TiColorHelper.java). It will lead to a notable performance boost on both startup and view presentation, since we don't have to do any manual color matching anymore.
| 13 |
3,876 |
TIMOB-27977
|
05/20/2020 11:50:09
|
TiAPI: Add "isTrusted" property to Ti.UI.Slider "change" event
|
Component: Ti.UI.Slider Platform: Android At the moment it is not possible to differentiate between a "user slide" and a "change of the value by code" inside the change event. There is already a `fromUser` parameter inside the listener: https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUISlider.java#L315 Exposing that value inside the event: https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUISlider.java#L361 and changing the calls to that function to "onProgressChanged(seekBar, curPos, false);" (last parameter false) would only output true if the slider was dragged by the user. PR and Test case will follow
| 5 |
3,877 |
TIMOB-27904
|
05/21/2020 21:24:46
|
Android: Incremental build duplicates "bootstrap.json" entries as of 8.1.0
|
*Summary:* If a project contains a JS file ending with {{*.bootstrap.js}}, then every Android incremental build performed will duplicate its entry within our {{ti.internal/bootstrap.json}} file. This causes the bootstrap JS file to be executed multiple times on startup. This regression was introduced in Titanium 8.1.0. *Note:* This only negatively impacts bootstraps that have an {{execute()}} function such as [ti.playservices|https://github.com/appcelerator-modules/ti.playservices/blob/master/android/Resources/ti.playservices/ti.playservices.bootstrap.js], because that function will end up being invoked multiple times. *Steps to reproduce:* # Create a Titanium app project. # Copy the below {{test.bootstrap.js}} to the {{Resources}} directory. # Build and run on Android. # Notice a bootstrap dialog appears once. _(This is good.)_ # Build and run on Android again. # Notice *two* bootstrap dialogs appear on startup. _(This is bad.)_ # Build and run on Android again. # Notice *three* bootstrap dialogs appear on startup. _(This is bad.)_ \\ {{./Resources/test.bootstrap.js}} {code:javascript} Ti.API.info("### Bootstrap was required-in."); var wasExecuted = false; exports.execute = function(finished) { Ti.API.info("### Bootstrap execute() method was called."); var message = "This is the bootstrap dialog."; if (wasExecuted) { message = "Uh-oh!!! Bootstrap was wrongly executed again."; } var dialog = Ti.UI.createAlertDialog({ message: message, buttonNames: ['OK'], cancel: 0, persistent: true, }); dialog.addEventListener('click', finished); dialog.addEventListener('cancel', finished); dialog.show(); wasExecuted = true; }; {code} *Cause:* The incremental build changes made in Titanium 8.1.0 by [TIMOB-27043] moved bootstrap script finding code to our core [process-js-task.js|https://github.com/appcelerator/titanium_mobile/blob/master/cli/lib/tasks/process-js-task.js] file. The iOS {{_build.js}} was changed to not fetch bootstrap scripts itself anymore... but the same as not done in Android's {{_build.js}} which is why the entries are being duplicated.
| 3 |
3,878 |
TIMOB-27912
|
05/29/2020 12:46:38
|
Android: chrome devtools URL is no longer valid
|
h5.Description When debugging an Android app we log a message on how to connect to the debugger in Chrome which uses a {{chrome-devtools://}} URL. In Chrome 83 this URL has been removed and is now just {{devtools://}} h5.Steps to reproduce 1. Build an Android app with {{--debug-host /localhost:9000}} 2. Try to open the chrome-devtools URL that gets logged h5.Actual URL doesnt work h5.Expected URL should work
| 2 |
3,879 |
TIMOB-27927
|
06/02/2020 21:40:05
|
Android: Changing currently selected row's color in picker does not update shown color
|
Setting the color of a picker row dynamically does not show up the changed color. To show up the changed color we need to select another option and reselect the first one. *Steps to reproduce:* # Create a project using the app.js as below. Run on android device # Select an option in the picker. The selected option should change text color but it does not show up the color change. # Click on the picker again. The last selected option shows changed color in the drop down. # Select another option and again the option selected in step 2. The changed color is shown now. Note: On iOS calling the picker.reloadColumn() method reloads the picker and shows the changed color of the selected option. {code:javascript} var window = Ti.UI.createWindow({ backgroundColor: "gray" }); var picker = Ti.UI.createPicker({ width: "50%" }); picker.add([ Ti.UI.createPickerRow({ title: "Red", color: "red" }), Ti.UI.createPickerRow({ title: "Green", color: "green" }), Ti.UI.createPickerRow({ title: "Blue", color: "blue" }), ]); picker.addEventListener("change", function(e) { Ti.API.info("### Selected row: " + e.rowIndex); picker.getSelectedRow(0).color = "purple"; }); window.add(picker); window.open(); {code} *Expected Result:* On android the color change of the option should show on the first time it is selected. *Work-Around:* Set the row's title text after setting the color. This force picker's text field to update. {code:javascript} picker.addEventListener("change", function(e) { Ti.API.info("### Selected row: " + e.rowIndex); var row = picker.getSelectedRow(0); row.color = "purple"; row.title = row.title; // <- This updates the picker's TextField. }); {code}
| 3 |
3,880 |
TIMOB-27930
|
06/03/2020 14:31:16
|
iOS: iPad crashing intermittently during unit test suite
|
When the test suite runs on iPad, it tends to crash around the Ti.UI.iOS.WebViewConfiguration tests (not one specific test, though). i.e. Please see the attached crash logs. Looks like perhaps TiViewController's underlying _proxy pointer is null? {code} [2020-06-03T13:01:33.689Z] [INFO] : !TEST_START: #createWebViewProcessPool() [2020-06-03T13:01:33.689Z] [INFO] : !TEST_END: {"state":"passed","duration":16,"suite":"Titanium.UI.iOS","title":"#createWebViewProcessPool()","message":""} [2020-06-03T13:01:33.689Z] [INFO] : !TEST_START: #createWebViewConfiguration() [2020-06-03T13:01:33.689Z] [INFO] : !TEST_END: {"state":"passed","duration":0,"suite":"Titanium.UI.iOS","title":"#createWebViewConfiguration()","message":""} [2020-06-03T13:01:33.689Z] [INFO] : !TEST_START: allowsPictureInPictureMediaPlayback [2020-06-03T13:01:33.689Z] [INFO] : !TEST_END: {"state":"passed","duration":337,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"allowsPictureInPictureMediaPlayback","message":""} [2020-06-03T13:01:33.689Z] [INFO] : !TEST_START: suppressesIncrementalRendering [2020-06-03T13:01:33.689Z] [INFO] : !TEST_END: {"state":"passed","duration":6,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"suppressesIncrementalRendering","message":""} [2020-06-03T13:01:33.689Z] [INFO] : !TEST_START: allowsAirPlayMediaPlayback [2020-06-03T13:01:33.690Z] [INFO] : !TEST_END: {"state":"passed","duration":5,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"allowsAirPlayMediaPlayback","message":""} [2020-06-03T13:01:33.690Z] [INFO] : !TEST_START: allowsInlineMediaPlayback [2020-06-03T13:01:33.690Z] [INFO] : !TEST_END: {"state":"passed","duration":8,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"allowsInlineMediaPlayback","message":""} [2020-06-03T13:01:33.690Z] [INFO] : !TEST_START: selectionGranularity [2020-06-03T13:01:33.690Z] [INFO] : !TEST_END: {"state":"passed","duration":4,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"selectionGranularity","message":""} [2020-06-03T13:01:33.690Z] [INFO] : !TEST_START: mediaTypesRequiringUserActionForPlayback [2020-06-03T13:01:33.690Z] [INFO] : !TEST_END: {"state":"passed","duration":7,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"mediaTypesRequiringUserActionForPlayback","message":""} [2020-06-03T13:01:33.690Z] [INFO] : !TEST_START: preferences [2020-06-03T13:01:33.690Z] [INFO] : !TEST_END: {"state":"passed","duration":7,"suite":"Titanium.UI.iOS.WebViewConfiguration","title":"preferences","message":""} [2020-06-03T13:01:33.690Z] [INFO] : !TEST_START: Should pass [2020-06-03T13:01:33.690Z] [WARN] : Ti.UI.iOS.NavigationWindow DEPRECATED in 8.0.0, in favor of Ti.UI.NavigationWindow [2020-06-03T13:01:33.690Z] [WARN] : 3DTouch is not available on this device. [2020-06-03T13:01:33.690Z] [WARN] : Ti.UI.iOS.StatusBar.GRAY DEPRECATED in 9.1.0, in favor of Ti.UI.iOS.StatusBar.DEFAULT [2020-06-03T13:01:33.690Z] [WARN] : Ti.UI.iOS.StatusBar.GREY DEPRECATED in 9.1.0, in favor of Ti.UI.iOS.StatusBar.DEFAULT [2020-06-03T13:01:33.690Z] [ERROR] : Application received error: signal error code: 11 [2020-06-03T13:01:33.690Z] [ERROR] : (null) {code}
| 5 |
3,881 |
TIMOB-27933
|
06/03/2020 20:05:35
|
LiveView: Do not report disconnect errors to ACA
|
h5.Description Currently when the liveview app code can't connect to the server it will spam errors (this will be improved in 9.1.0), however we should make sure that these errors also are not reported to ACA. LiveView currently has a shim that overrides the old APM module that would make the functions a no-op, although I think that is too brute forcey. I think we are best to maybe try to suppress these errors somehow (probably by just handling them better), and then lastly trying to detect the error somehow in liveview and suppress if it is a liveview. (maybe we could prefix all errors with LIVEVIEW and check for that before sending onto ACA)
| 2 |
3,882 |
TIMOB-27935
|
06/04/2020 14:23:58
|
iOS: TableViewRow does not return getRect methods
|
When trying to get the {{rect.height}} the value does not change even through the tableViewRow height is increasing/changing. On the Android side this is working fine and the value is returned. *Test Case:* {code:java} win = Ti.UI.createWindow({ backgroundColor: '#AAAAFF', layout: 'vertical' }); var top = Ti.UI.createView({ backgroundColor: '#FFAAAA', layout: 'horizontal', height: Ti.UI.SIZE, width: Ti.UI.FILL }); var btnPlus = Ti.UI.createButton({title: '+', top: 50, color: 'white', borderWidth:2 }); btnPlus.addEventListener('click', function() { console.log('plus click'); view.height += 50; }); var btnMinus = Ti.UI.createButton({title: '-', top: 50, color: 'white', borderWidth:2 }); btnMinus.addEventListener('click', function() { console.log('minus click'); view.height -= 50; }); var label = Ti.UI.createLabel(); var tableView = Ti.UI.createTableView(); var row = Ti.UI.createTableViewRow({ height: Ti.UI.SIZE, width: Ti.UI.FILL }); var view = Ti.UI.createView({ height: 150, backgroundColor: 'blue' }); row.add(view); tableView.setData([ row ]); tableView.addEventListener('postlayout', function onPostLayout() { console.log('postlayout', row.rect.height, view.rect.height); label.text = [row.rect.height, view.rect.height].join(' \| '); }); top.add(btnPlus); top.add(btnMinus); top.add(label); win.add(top); win.add(tableView); win.open(); {code} *Test Steps:* # Create a new application with the code above # Run the application # Click on the {{Minus}} and {{Plus}} buttons # Notice label does not change with the correct the values (even though height of the tableViewRow changes)
| 3 |
3,883 |
TIMOB-27938
|
06/04/2020 23:52:27
|
Android: Update gradle build tools to 4.0.x
|
*Summary:* Titanium currently builds with "com.android.tools.build:gradle" tool version {{3.6.2}}. We should update it to {{4.0.0}}. https://developer.android.com/studio/releases/gradle-plugin?buildsystem=ndk-build#4-0-0 *To-Do:* We must update the following files... https://github.com/appcelerator/titanium_mobile/blob/master/android/build.gradle https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/build/root.build.gradle *Note:* You must use Android Studio 4.x to build a project using Android gradle tools 4.0.0 or higher.
| 3 |
3,884 |
TIMOB-27939
|
06/05/2020 00:05:57
|
Android: Module builds should auto-download NDK r21c by default if needed
|
*Summary:* When doing a module build, Titanium will auto-download NDK r20b (aka: 20.1.5948944) by default if NDK installations were found on the system. The default should be updated to NDK r21c (aka: 21.2.6472646). https://github.com/android/ndk/wiki/Changelog-r21#r21c *Reason:* The macOS distribution of the Android NDK r21c tools have been "notarized" by Google. This means module builds will no longer display several security popups on macOS Catalina. *To-Do:* Update the {{android.ndkVersion}} here... https://github.com/appcelerator/titanium_mobile/blob/master/android/templates/module/generated/build.gradle
| 3 |
3,885 |
TIMOB-27946
|
06/08/2020 18:08:25
|
Android: Implement Ti.View.borderRadius multiple values for custom edge radii
|
A developer should be able to configure custom border radii, e.g. bottom-left, bottom-right, top-left and top-right. The size of the radius can and should be reused from the existing border-radius property. Example: {code:js} var win = Ti.UI.createWindow({ backgroundColor: '#333' }); var view = Ti.UI.createView({ backgroundColor: '#fff', height: 350, bottom: 0, borderRadius: '20px 20 20dp 15px', }); win.add(view); win.open(); {code}
| 5 |
3,886 |
TIMOB-27950
|
06/08/2020 20:14:03
|
Android: "tiapp.xml" setting <navbar-hidden> is ignored if <fullscreen> or <statusbar-hidden> is also not set as of 9.0.0
|
In tiapp.xml there is the property <navbar-hidden>. I set it to false and in 9.0.2.GA it doesn't worky anymore and I have to use (and I'm happy with it): {code:tss} "TabGroup": { theme: "Theme.AppCompat.NoTitleBar" } {code} I just want to notice you of this thing.
| 3 |
3,887 |
TIMOB-27963
|
06/17/2020 00:08:49
|
Android: Always specify default Tab.tintColor
|
- Always specify default {{tintColor}} for tabs *TEST CASE* {code:js} const tabGroup = Ti.UI.createTabGroup({ // style: Ti.UI.Android.TABS_STYLE_BOTTOM_NAVIGATION, // tintColor: '#bbb' // NOTE: Workaround for 9.0.3 }); const tabWin_home = Ti.UI.createWindow({ title: 'Home', backgroundColor: 'white' }); const tab_home = Ti.UI.createTab({ title: 'Home', window: tabWin_home }); const tabWin_chat = Ti.UI.createWindow({ title: 'Chat', backgroundColor: 'white' }); const tab_chat = Ti.UI.createTab({ title: 'Chat', window: tabWin_chat }); tabGroup.addTab(tab_home); tabGroup.addTab(tab_chat); tabGroup.open(); {code} - Unselected tab text and icon should be dimmer than selected tab.
| 3 |
3,888 |
TIMOB-27964
|
06/17/2020 18:45:42
|
iOS: Support iOS 14 and Xcode 12
|
This epic will track all the items required to enable support for iOS 14 and Xcode 12.
| 0 |
3,889 |
TIMOB-27976
|
06/23/2020 19:36:24
|
iOS 14: Expose API to use Core Location AccuracyAuthorization
|
Apple has exposed new APIs CoreLocation framework e.g. https://developer.apple.com/documentation/corelocation/claccuracyauthorization?changes=latest_major https://developer.apple.com/documentation/corelocation/cllocationmanager/3600217-requesttemporaryfullaccuracyauth?changes=latest_major https://developer.apple.com/documentation/corelocation/cllocationmanager/3600216-requesttemporaryfullaccuracyauth?changes=latest_major. Expose new APIs in SDK to use . New APIs- Constants - {code:java} Ti.Geolocation.ACCURACY_AUTHORIZATION_FULL Ti.Geolocation.ACCURACY_AUTHORIZATION_REDUCED {code} Property (read-only)- {code:java} Ti.Geolocation.locationAccuracyAuthorization {code} function - {code:java} Ti.Geolocation.requestTemporaryFullAccuracyAuthorization('purposekey1', callback); {code}
| 8 |
3,890 |
TIMOB-27985
|
06/25/2020 18:46:11
|
iOS 14: Ensure widgets are working as expected in titanium apps via extension
|
Apple has introduced Widgets in iOS 14 https://developer.apple.com/documentation/widgetkit. Titanium developers can use it via creating extensions and use extension in their project. Try to create a widget extension and use it in sample app, run it and see if everything works as expected. For creating extension see guide [here|https://wiki.appcelerator.org/display/guides2/Creating+iOS+Extensions+-+Siri+Intents]
| 5 |
3,891 |
TIMOB-27987
|
06/25/2020 20:11:14
|
iOS 14: Expose new APIs given in WKWebView
|
In WKWebView Apple has given new APIs. e.g. 1. [pageZoom|https://developer.apple.com/documentation/webkit/wkwebview/3516411-pagezoom?changes=latest_minor&language=objc] 2. [createPDF|https://developer.apple.com/documentation/webkit/wkwebview/3516407-createpdfwithconfiguration?changes=latest_minor&language=objc] 3. [createWebArchivedData|https://developer.apple.com/documentation/webkit/wkwebview/3516408-createwebarchivedatawithcompleti?changes=latest_minor&language=objc] 4. [findString|https://developer.apple.com/documentation/webkit/wkwebview/3516409-findstring?changes=latest_minor&language=objc] Expose these APIs in titanium. Corresponding Titanium APIs - 1. Property {code:java} Ti.UI.WebView.zoomLevel {code} It already exists. Internal implementation, native side, will be changed. 2. Function {code:java} Ti.UI.WebView.createPDF(callback); {code} 3. Function {code:java} Ti.UI.WebView.createWebArchive(callback); {code} 4. Function {code:java} Ti.UI.WebView.findString(string, Options, callback); {code}
| 5 |
3,892 |
TIMOB-27994
|
07/01/2020 14:25:45
|
iOS: itemclick event its firing instead of a move event when ordering items in a list (iOS 13+)
|
When using iOS13 or 14 the itemclick event is fired when moving items in a listView instead of a Move event listener. *Test Case:* {code:java} var win = Ti.UI.createWindow({ backgroundColor : 'white' }); var data = []; var listSections = []; var fruitsData; var vegData; var plainTemplate = { childTemplates : [{ type : 'Ti.UI.Label', // Use a label bindId : 'rowtitle', // Bind ID for this label properties : {// Sets the Label.left property left : '10dp', // backgroundColor : 'blue', } }, { type : 'Ti.UI.Label', // Use a button bindId : 'label', // Bind ID for this button properties : {// Sets several button properties width : '80dp', height : '40dp', right : '10dp', text : 'press me', touchEnabled : false } }], }; function report(e) { Ti.API.info(e.type); } var listView = Ti.UI.createListView({ templates : { 'plain' : plainTemplate }, defaultItemTemplate : 'plain', editing : true, pruneSectionsOnEdit : true }); var listArray = [{ id : "1001", title : "Apple", moduleId : "Fruits" },{ id : "1002", title : "carrot", moduleId : "Vegetables" }, { id : "1003", title : "Banana", moduleId : "Fruits" }, { id : "1004", title : "Capsicum", moduleId : "Vegetables" }, { id : "1005", title : "Brinjal", moduleId : "Vegetables" }, { id : "1006", title : "Papaya", moduleId : "Fruits" }, { id : "1007", title : "PineApple", moduleId : "Fruits" }, { id : "1008", title : "LadiesFinger", moduleId : "Vegetables" } ]; function getIndex(array, itemId){ var actualIndex; array.findIndex(function(arrayObj,index){ if(arrayObj.id.toString() === itemId.toString()){ actualIndex = index; } }); return actualIndex; } var sourceItemId; var targetItemId; var insertBefore = false; listView.addEventListener('itemclick', function(e){ alert('Item click fired::::::::'); }); listView.addEventListener('move', function(e) { Ti.API.info('Move event listener::::::::' + JSON.stringify(e)); Ti.API.info('e.itemId:::::' + JSON.stringify(e.itemId)); sourceItemId = e.itemId; }); function setModuleItems(moduleData){ var listItems = []; moduleData.forEach(function(listArrayItem){ listItems.push({ rowtitle : { text : listArrayItem.title }, label :{ text : "Press Me" }, properties : { itemId : listArrayItem.id, canEdit : true, canMove : true } }); }); return listItems; } if(listArray.length > 0){ fruitsData = listArray.filter(listArrayObj => listArrayObj.moduleId === "Fruits"); vegData = listArray.filter(listArrayObj => listArrayObj.moduleId === "Vegetables"); if(fruitsData.length !== 0){ var fruitsSection = Ti.UI.createListSection({ headerTitle :"Fruits" }); listSections.push(fruitsSection); fruitsSection.setItems(setModuleItems(fruitsData)); } if(vegData.length !== 0){ var vegSection = Ti.UI.createListSection({ headerTitle :"Vegetables" }); listSections.push(vegSection); vegSection.setItems(setModuleItems(vegData)); } } listView.sections = listSections; win.add(listView); win.open(); {code} *Test Steps* # Create a Titanium application # Copy the code above into the {{app.js}} # Run the app on a iOS 13/14 device # Move one of the items in the listView around # Notice a click event is fired # Rerun application on a device/sim < iOS13 # Move one of the items in the listView around # Notice Move event listener is fired and logged *Expected result* Following should be logged: {code:java} [INFO] Move event listener::::::::{"itemId":"1001","itemIndex":0,"targetItemIndex":3,"section":{},"targetSectionIndex":0,"sectionIndex":0,"targetSection":{},"bubbles":false,"type":"move","source":{"canScroll":true,"caseInsensitiveSearch":true,"horizontalWrap":true,"visible":true,"touchEnabled":true,"dictTemplates":{"plain":{}},"defaultItemTemplate":"plain","editing":true,"pruneSectionsOnEdit":true},"cancelBubble":false} {code}
| 5 |
3,893 |
TIMOB-27997
|
07/02/2020 21:35:42
|
iOS: Ti.Blob images from device (via Ti.UI.View#toImage()) would report dimensions in points, not pixels
|
On Android, if we generate a Ti/Blob image from calling Ti.UI.View#toImage(), it reports width/height/size properly. On iOS, it will report width and height in points, not pixels. size is therefore also incorrect. Say we have a 10px x 10px view rendered to image on a 3x scale device. The blob will report width of 3, height of 3 and size of 9. The device will report density factor of 3. So naively multiple by that still gives us wrong values (of 9, 9, 81 respectively instead of 10, 10, 100). UIImage holds a scale value for cases like this and we should multiply width/height by that on iOS to get true pixel values. (Doing so in this case we actually do end up with 10, 10, 100 because presumably the image scale is recorded as something like 3.3333?)
| 5 |
3,894 |
TIMOB-28012
|
07/10/2020 20:12:10
|
iOS 14: Expose new APIs in Ti.UI.ScrollableView to customize indicator
|
In iOS 14, Apple has introduced new APIs to customize indicator image in UIPageControl. https://developer.apple.com/documentation/uikit/uipagecontrol/3577679-preferredindicatorimage?language=objc https://developer.apple.com/documentation/uikit/uipagecontrol/3577680-setindicatorimage?language=objc Expose these APIs in titanium sdk . New APIs- Property - {code:java} Ti.ScrollableView.preferredIndicatorImage = image; {code} Function - {code:java} Ti.ScrollableView.setIndicatorImageForPage(image, pageNo); {code}
| 5 |
3,895 |
TIMOB-28016
|
07/14/2020 01:56:16
|
Android: Build fails with ACA 2.0.1 and SDK 9.0.0-9.0.2
|
h5.Steps to reproduce: 1. Create & build an app with ACA 2.0.1 module and SDK 9.0.0.GA, 9.0.1.GA, or 9.0.2.GA on android device/emulator. h5.Actual results: 1. The build fails in gradle with: {code} [ERROR] : [GRADLE] [ERROR] : [GRADLE] FAILURE: Build failed with an exception. [ERROR] : [GRADLE] [ERROR] : [GRADLE] * What went wrong: [ERROR] : [GRADLE] Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. [ERROR] : [GRADLE] > Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'. [ERROR] : [GRADLE] > Could not find org.appcelerator:titanium:9.0.3. [ERROR] : [GRADLE] Required by: [ERROR] : [GRADLE] project :app [ERROR] : [GRADLE] project :app > ti:cloudpush:7.1.0 [ERROR] : [GRADLE] > Could not find org.appcelerator:titanium:9.0.3. [ERROR] : [GRADLE] Required by: [ERROR] : [GRADLE] project :app > hyperloop:hyperloop:5.0.3 [ERROR] : [GRADLE] project :app > ti:playservices:17.1.1 [ERROR] : [GRADLE] > Could not find org.appcelerator:titanium:9.0.3. [ERROR] : [GRADLE] Required by: [ERROR] : [GRADLE] project :app > com.appcelerator:aca:2.0.1 [ERROR] : [GRADLE] [ERROR] : [GRADLE] * Try: [ERROR] : [GRADLE] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. [ERROR] : [GRADLE] [ERROR] : [GRADLE] * Get more help at https://help.gradle.org [ERROR] : [GRADLE] [ERROR] : [GRADLE] BUILD FAILED in 1s [ERROR] : "gradlew" tool returned exit code: 1 [ERROR] Application Installer abnormal process termination. Process exit value was 1 {code} h5.Actual results: 1. The build should be successful. *Work-Around 1:* Build with Titanium 9.0.3.GA or higher. *Work-Around 2:* Use ACA module v2.0.0 instead by setting the following in "tiapp.xml"... {code:xml} <ti:app> <modules> <module platform="android" version="2.0.0">com.appcelerator.aca</module> </modules> </ti:app> {code}
| 3 |
3,896 |
TIMOB-28020
|
07/15/2020 23:01:22
|
Android: Parity with iOS Shortcut click event payload
|
- Amend {{Ti.UI.Shortcut}} click event to include {{item}} as Shortcut item instead *TEST CASE* {code:js} const window = Ti.UI.createWindow({ backgroundColor: 'grey', layout: 'vertical' }); const shortcut = Ti.UI.createShortcut(); let lastShortcutItem; function test(title, callback) { const button = Ti.UI.createButton({ title, top: 50 }); button.addEventListener('click', callback); window.add(button); } test('ADD RANDOM SHORTCUT', _ => { const rand = Math.floor(Math.random() * (999 - 1)) + 1; const item = Ti.UI.createShortcutItem({ id: `test_shortcut_${rand}`, title: `SHORTCUT_${rand}`, description: `DESCRIPTION_${rand}` }); lastShortcutId = item; shortcut.add(item); }); test('REMOVE LAST SHORTCUT', _ => { try { shortcut.remove(lastShortcutItem); } catch { } }); test('REMOVE ALL SHORTCUTS', _ => { shortcut.removeAll(); }); test('NUMBER OF SHORTCUTS', _ => { alert(`staticItems: ${shortcut.staticItems.length}`); alert(`items: ${shortcut.items.length}`); }); Ti.UI.Shortcut.addEventListener('click', e => { // e should contain 'item' console.log('shortcut: ' + JSON.stringify(e, null, 1)); }); window.open(); {code}
| 3 |
3,897 |
TIMOB-28025
|
07/16/2020 15:40:05
|
Install Xcode 12 betas to build nodes
|
In order to support building/testing on Xcode 12 and iOS 14, we will need at least one build node running the latest Xcode 14 beta.
| 8 |
3,898 |
TIMOB-28030
|
07/17/2020 16:08:02
|
TiAPI: Deprecate WebView "blacklistedURLs" property in favour of "blockedURLs"
|
*I am not intending to open a debate with this ticket, there has been plenty of discussion within tech as to this term and others like it. We want to create a space that is inclusive to everyone, so if there are any issue that can cause people to feel unwelcome then we will strive to fix those issues* h5.Description Deprecate property {{blacklistedURLs}} and replace with {{blockedURLs}}. https://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.WebView-property-blacklistedURLs Deprecate event {{blacklisturl}} and replace with {{blockedurl}}. https://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.WebView-event-blacklisturl We should deprecate at the earliest convenience and look to remove in the next semver major release.
| 3 |
3,899 |
TIMOB-28031
|
07/17/2020 19:39:18
|
CLI: Unable to find an iOS Simulator running iOS 14.0.
|
I'm seeing this locally, m as well s on the build node with Xcode 12 beta 2 installed. trying to build an iOS app the CLI shows: {code} 2020-07-16T18:13:57.547Z] Command [2020-07-16T18:13:57.547Z] /Users/build/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node_10.17.0/bin/node /Users/build/jenkins/workspace/ium-sdk_titanium_mobile_PR-11049/titanium-mobile-mocha-suite/node_modules/titanium/lib/titanium.js build --project-dir /Users/build/jenkins/workspace/ium-sdk_titanium_mobile_PR-11049/titanium-mobile-mocha-suite/scripts/mocha --platform ios --target simulator --log-level info --deploy-type test --hide-error-controller --device-family iphone --no-prompt --color [2020-07-16T18:13:57.547Z] [2020-07-16T18:13:57.547Z] [ERROR] : Unable to find an iOS Simulator running iOS 14.0. [2020-07-16T18:13:57.547Z] [2020-07-16T18:13:57.547Z] Error: Exited unexpectedly with exit code: 1 [2020-07-16T18:13:57.547Z] at ChildProcess.prc.on.code (/Users/build/jenkins/workspace/ium-sdk_titanium_mobile_PR-11049/titanium-mobile-mocha-suite/scripts/test.js:506:19) [2020-07-16T18:13:57.547Z] at ChildProcess.emit (events.js:198:13) [2020-07-16T18:13:57.547Z] at maybeClose (internal/child_process.js:982:16) [2020-07-16T18:13:57.547Z] at Socket.stream.socket.on (internal/child_process.js:389:11) [2020-07-16T18:13:57.547Z] at Socket.emit (events.js:198:13) [2020-07-16T18:13:57.547Z] at Pipe._handle.close (net.js:607:12) {code}
| 3 |
3,900 |
TIMOB-28041
|
07/23/2020 18:17:04
|
Merge titanium-mobile-mocha-suite into titanium_mobile
|
We split out the test suite so that it could be used between iOS/Android (titanium_mobile) and Windows (titanium_mobile_windows). Given that Windows is dead, we should consider making our lives much easier and folding the test suite and tooling directly into the SDK repo (titanium_mobile). We would avoid the need to migrate tests back and forth and maintain branches/fixes on both repos.
| 13 |
3,901 |
TIMOB-28049
|
07/25/2020 02:20:26
|
Android: Investigate "ACCESS_BACKGROUND_LOCATION" handling on Android 11
|
*Summary:* Supposedly, Android 11 will no longer show a permission request dialog for the {{ACCESS_BACKGROUND_LOCATION}} permission. We need to confirm this. https://developer.android.com/preview/privacy/location#background-location-permission-dialog-changes If true, then the only way to enable permission is to go to the app's "Location Permissions" activity under system settings. This very well maybe true because according to Google's developer blog below, they will be removing apps using this permission from Google Play unless they provide a valid reason and pass Google's review process. https://android-developers.googleblog.com/2020/02/safer-location-access.html *Note 1:* We might be able to reach the app's "Location Permission" activity under system settings via the following intent action. {{ACTION_LOCATION_SOURCE_SETTINGS}} *Note 2:* We may need to expose Android's [shouldShowRequestPermissionRationale ()|https://developer.android.com/reference/android/app/Activity.html#shouldShowRequestPermissionRationale(java.lang.String)] API. Normally, this method would return {{true}} if the end-user tapped on "Disallow" in the permission request dialog. On Android 11, this might always return {{true}} for the {{ACCESS_BACKGROUND_LOCATION}} where you would have to tell the end-user how to enable it under system settings.
| 3 |
3,902 |
TIMOB-28061
|
08/01/2020 04:33:55
|
TiAPI: Add OS version major/minor integer constants
|
*Summary:* Currently, you can only fetch the OS version as a string via the [Ti.Platform.version|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Platform-property-version] property. This is not convenient to use when you only want to call APIs on higher OS versions. For example, we've seen a lot of code that looks like the below. {code:javascript} if (OS_IOS && parseInt(Ti.Platform.version.split('.')[0]) >= 13) { // Do something on iOS 13 or higher... } {code} *Feature Proposal:* Add the following properties to {{Ti.Platform}}... * {{Ti.Platform.versionMajor}} // Returns an integer. * {{Ti.Platform.versionMinor}} // Returns an integer. Also add the following global constants. _(These will pair well with [OS_ANDROID|https://docs.appcelerator.com/platform/latest/#!/api/Global-property-OS_ANDROID] and [OS_IOS|https://docs.appcelerator.com/platform/latest/#!/api/Global-property-OS_IOS].)_ * {{OS_VERSION_MAJOR}} * {{OS_VERSION_MINOR}} This will make the above code example look simpler like this... {code:javascript} if (OS_IOS && (OS_VERSION_MAJOR >= 13)) { // Do something on iOS 13 or higher... } {code} *Note:* On Android, we have a [Ti.Platform.Android.API_LEVEL|https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Platform.Android-property-API_LEVEL] constant which is a single integer used to represent all Android OS versions. It's best to use this if you can, but note that no other platform has a similar concept... while all operating system support a {{<major>.<minor>}} version that we can use for parity. https://developer.android.com/guide/topics/manifest/uses-sdk-element#ApiLevels
| 5 |
3,903 |
TIMOB-28062
|
08/02/2020 13:08:36
|
iOS: Titanium not compatible with new Facebook SDK versions due to missing Swift files
|
Since Facebook SDK 7.0.0, their iOS SDK requires the project to contain at least one ".swift" file. Otherwise the build fails due to missing Swift standard libraries. And although Titanium already enables Swift for module compatibility, it does not seem to be enough so far. The same issue is happening for other app frameworks like React Native and they workaround it by adding it to the Xcode project (which is not generated their but stable, an option Titanium has not). Importance of the Facebook SDK 7+ upgrade: They fixed an issue with random server errors crashing the whole app that uses it, therefore it's a critical update developers should perform.
| 5 |
3,904 |
TIMOB-28064
|
08/03/2020 22:08:12
|
Android: Setting border fills view when backgroundColor is not specified
|
- Setting a border will fill the view with {{borderColor}} if a {{backgroundColor}} is not specified *TEST CASE* {code:js} const window = Ti.UI.createWindow({ backgroundColor: 'white' }); const border = Ti.UI.createView({ width: 200, height: 200, borderRadius: 5, borderColor: 'gray', borderWidth: 3 }); window.add(border); window.open(); {code}
| 3 |
3,905 |
TIMOB-28147
|
08/04/2020 03:50:25
|
iOS 14 App Clips extension for titanium
|
App Clips may be the entry point for retail that have never jumped the App service to cater to on-premise , proximity temporary apps. https://developer.apple.com/app-clips/ They are small (10 mb apps) that doesn’t need to be downloaded from the App Store and can be used instantly. Even though Android has thé équivalant Instant Apps, such features would enhance greatly and bring up to speed a feature that will be ubiquitous. Even more so than regular full on apps (which are still required even for an App Clip to be attached to it). If it is possible to do so in Ti, an Example on Axway’s Developer blog would spread it faster among us developers.
| 5 |
3,906 |
TIMOB-28070
|
08/05/2020 23:13:25
|
TiAPI: Add vscode json files to app templates
|
*Summary:* We should add {{.vscode/}} JSON configuration files to our Titanium app templates which hide the generated folders (like the "build" folder) and suggest VS Code users to use our extension. *Classic App Folder Exclusion:* For Classic apps, we only need to hide the {{./build}} folder from the editor and exclude it from file monitoring/search. {{.vscode/settings.json}} {code:json} { "files.exclude": { "build/": true }, "search.exclude": { "build/": true }, "files.watcherExclude": { "build/": true }, } {code} *Alloy/Angular App Folder Exclusion:* For all other app templates, the project's root {{./i18n}}, {{./platform}}, and {{./Resources}} folders are generated from the project's {{./app}} folder. So, these folders need to be excluded as well. {{.vscode/settings.json}} {code:json} { "files.exclude": { "build/": true, "i18n/": true, "platform/": true, "Resources/": true }, "search.exclude": { "build/": true, "i18n/": true, "platform/": true, "Resources/": true }, "files.watcherExclude": { "build/": true, "i18n/": true, "platform/": true, "Resources/": true } } {code} *Promoting Titanium's Extension:* When opening the app project folder in VS Code, we can have the editor recommend the end-user to use our Titanium extension by adding the following JSON file. {{.vscode/extensions.json}} {code:json} { "recommendations": [ "axway.vscode-titanium" ] } {code}
| 1 |
3,907 |
TIMOB-28073
|
08/07/2020 04:06:24
|
Android: DateTimeFormat mishandles some combinations of settings on Android 8
|
*Summary:* If you set up {{Intl.DateTimeFormat}} to use 12-hour time and fractional digits on Android 8.x, then it will log an error and output a different format. This is not an issue on older or new Android OS versions. *Steps to reproduce:* # Build and run the below code on Android 8. # Notice an error gets logged: {{Failed to generate 'best' date pattern.}} # Notice displayed date is {{"3/31/20 8:15 PM"}} which doesn't match format settings. {code:javascript} var date = new Date(Date.UTC(2020, 2, 31, 20, 15, 30, 123)); var formatter = new Intl.DateTimeFormat('en-US', { year: 'numeric', month: '2-digit', day: '2-digit', hour: 'numeric', minute: '2-digit', second: '2-digit', fractionalSecondDigits: 3, hour12: true, timeZone: 'UTC' }); var window = Ti.UI.createWindow(); window.add(Ti.UI.createLabel({ text: formatter.format(date) })); window.open(); {code} *Result:* The following error gets logged... {code} [ERROR] DateTimeFormatProxy: (main) [37,37] Failed to generate 'best' date pattern. [ERROR] DateTimeFormatProxy: java.lang.IllegalArgumentException: Illegal pattern character 'b' [ERROR] DateTimeFormatProxy: at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:870) [ERROR] DateTimeFormatProxy: at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:684) [ERROR] DateTimeFormatProxy: at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:623) {code} *Expected Result:* No error should be logged. The displayed date should be... {code} 03/31/2020, 8:15:30.123 PM {code} *Cause:* This is a bug on Google's end. It is adding invalid format character {{'b'}} for the AM/PM component when it should be using format character {{'a'}} instead. This used to be a bug in Oracle's JDK as well... https://bugs.openjdk.java.net/browse/JDK-8209047 Titanium was correctly catching the exception and falling-back to use a basic date/time format, but unfortunately that means it won't match the given format settings. (Having the fallback is still a good thing.)
| 3 |
3,908 |
TIMOB-28077
|
08/11/2020 20:39:28
|
iOS14: Expose new error type in Bonjure Service and update doc to align with Local n/w privacy restrictions
|
In iOS 14, Apple has put restriction on accessing local network. It requires user permission. To show the prompt developer need to add key [NSLocalNetworkUsageDescription|https://developer.apple.com/documentation/bundleresources/information_property_list/nslocalnetworkusagedescription?language=objc] in tiapp.xml and if using Bonjure Service, that need to be added in info.plist using key [NSBonjourServices |https://developer.apple.com/documentation/bundleresources/information_property_list/nsbonjourservices] . More detail can be found in WWDC video https://developer.apple.com/videos/play/wwdc2020/10110/. In iOS 14, new error [constant|https://developer.apple.com/documentation/foundation/nsnetserviceserror/nsnetservicesmissingrequiredconfigurationerror?language=objc] is given. In titanium, it need to added in Ti.Network.BonjureService and expose as error string.
| 3 |
3,909 |
TIMOB-28078
|
08/11/2020 20:53:47
|
iOS14: Expose new APIs Titanium.Network.HTTPClient which will require while accessing local http server
|
In iOS 14, Due to local network access prompt it may be that request get failed while waiting for user's permission. See more detail in WWDC video https://developer.apple.com/videos/play/wwdc2020/10110/. In titanium, we need to provide APIs corresponding to [waitsForConnectivity|https://developer.apple.com/documentation/foundation/urlsessionconfiguration/2908812-waitsforconnectivity] and [timeoutIntervalForResource |https://developer.apple.com/documentation/foundation/urlsessionconfiguration/1408153-timeoutintervalforresource]
| 5 |
3,910 |
TIMOB-28092
|
08/20/2020 17:25:40
|
Android: Native modules pinned to build Titanium SDK version
|
Building a Titanium Android native module with SDK 9.0.0+ will pin the module to require the SDK the module was built with or newer. For example, building {{titanium-identity}} with {{9.0.3.GA}} will cause a build failure for any project builds that include the module and use a older Titanium SDK. This is because the *.pom file generated depends on {{org.appcelerator.titanium}}: {code:xml} <dependency> <groupId>org.appcelerator</groupId> <artifactId>titanium</artifactId> <version>9.0.3</version> </dependency> {code} *TEST CASE* 1. Build a native Android module using {{9.0.3.GA}} (i.e: https://github.com/appcelerator-modules/titanium-identity) 2. Include module in project that uses an older Titanium SDK (9.0.0, 9.0.2, ...) 3. Build will fail {code} [ERROR] : [GRADLE] Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. [ERROR] : [GRADLE] > Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'. [ERROR] : [GRADLE] > Could not find org.appcelerator:titanium:9.0.3. {code}
| 5 |
3,911 |
TIMOB-28093
|
08/20/2020 22:41:13
|
TiAPI: Add properties "uprightWidth" and "uprightHeight" to Ti.Blob
|
*Summary:* When a Titanium {{Blob}} wraps an image, its "width" and "height" properties provide the "decoded" image's dimensions. Unfortunately, Android's native image loading APIs ignore a JPEG's EXIF orientation, meaning the image is loaded as-is (no rotation applied). While our {{ImageView}} and other APIs will correctly handle the EXIF orientation, the blob's "width" and "height" is for the unrotated image which makes it difficult to do manual layouts (ex: calculate letterbox scaling). *Proposed Solution:* Add the following properties to Titanium {{Blob}}: * uprightWidth * uprightHeight The above properties will return what the image width and height should be when a JPEG's EXIF orientation is applied onscreen. If the image is not a JPEG or the JPEG has no EXIF orientation, then these properties will return the same values as "width" and "height". And since iOS loads images in the upright positions, the above properties will always return the same values as "width" and "height". *Use-Case:* Developers need the image's actual width and height to do things like letterbox scaling. For example... {code:javascript} var scale = Math.min( Ti.UI.convertUnits(window.size.width, Ti.UI.UNIT_PX) / imageBlob.width, Ti.UI.convertUnits(window.size.height, Ti.UI.UNIT_PX) / imageBlob.height); imageView.image = imageBlob; imageView.width = imageBlob.width * scale; imageView.height = imageBlob.height * scale; {code} If the JPEG is loaded sideways (ie: its EXIF orientation is ignored), then the above will scale the image wrong. *Note:* This is an interim solution. A better solution would be to completely refactor Titanium's image loading code and decode the image in the upright position (pre-rotated). This will be a huge undertaking that is best done in a major Titanium release version. But when we do this, Android's "uprightWidth" and "uprightHeight" properties will match "width" and "height" just like iOS.
| 3 |
3,912 |
TIMOB-28098
|
08/26/2020 15:38:47
|
TiAPI: Add OS version patch integer constants
|
*Feature Proposal:* Add the following properties to {{Ti.Platform}}... * {{Ti.Platform.versionPatch}} // Returns an integer. Also add the following global constants. _(These will pair well with [OS_ANDROID|https://docs.appcelerator.com/platform/latest/#!/api/Global-property-OS_ANDROID] and [OS_IOS|https://docs.appcelerator.com/platform/latest/#!/api/Global-property-OS_IOS].)_ * {{OS_VERSION_PATCH}}
| 5 |
3,913 |
TIMOB-28099
|
08/26/2020 16:29:45
|
iOS: Unable to build Hyperloop Example app on iOS 14 using Xcode 12 Command line tools
|
When running the Hyperloop examples app on Xcode 12 command line tools and then running to 14.0 beta sim/device the following errors can be seen. *Test Steps:* # Download Hyperloop examples app # Download the latest Xcode 12 beta # Download the latest iOS 14 beta for device # Run Hyperloop examples app *Simulator error:* {code:java} [ERROR] ** BUILD FAILED ** [ERROR] The following build commands failed: [ERROR] CompileC /Users/samir/Desktop/Appc/Repos/hyperloop-examples/build/iphone/build/Intermediates/Hyperloop_Sample.build/Debug-iphonesimulator/Hyperloop_Sample.build/Objects-normal/x86_64/uikit.o /Users/samir/Desktop/Appc/Repos/hyperloop-examples/build/hyperloop/ios/js/uikit/uikit.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler [ERROR] (1 failure) Build failed. Process exited with code 1. {code} *Device error:* {code:java} [ERROR] ** BUILD FAILED ** [ERROR] The following build commands failed: [ERROR] CompileC /Users/samir/Desktop/Appc/Repos/hyperloop-examples/build/iphone/build/Intermediates/Hyperloop_Sample.build/Debug-iphonesimulator/Hyperloop_Sample.build/Objects-normal/x86_64/uikit.o /Users/samir/Desktop/Appc/Repos/hyperloop-examples/build/hyperloop/ios/js/uikit/uikit.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler [ERROR] (1 failure) Build failed. Process exited with code 1. {code} *Expected result:* App should be able to build and run without any issues. *Actual result:* Above errors are shown.
| 5 |
3,914 |
TIMOB-28104
|
08/28/2020 13:51:36
|
iOS: Support new date picker styles from iOS 13.4 and iOS 14
|
iOS 13.4 and 14 are introducing new date picker styles (automatic, wheels, compact and inline). Titanium does not support those so far. Example: {code:js} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var picker = Ti.UI.createPicker({ type: Ti.UI.PICKER_TYPE_DATE, datePickerStyle: Ti.UI.iOS.DATE_PICKER_STYLE_INLINE }); win.add(picker); win.open(); {code} See the attachment for details!
| 8 |
0 |
TISTUD-1
|
03/01/2011 11:50:44
|
Update JS metadata to include items from ECMA-262, 5th Edition
|
At the very least, we need to verify that these items exist in our metadata: # JSON.parse, .stringify # Date.prototype.toISOString, .toJSON # Object.create, .defineProperty, .defineProperties, .freeze, .getOwnPropertyDescription, .getOwnPropertyNames, .getPrototypeOf, .isExtensible, .isFrozen, .isSealed, .keys, .preventExtensions, .seal # Array.isArray, Array.prototype.every, filter, .forEach, .indexOf, .lastIndexOf, .map, .reduce, .reduceRight, .some # String.prototype.trim # Function.prototype.bind
| 0 |
1 |
TISTUD-68
|
03/01/2011 11:58:08
|
Add pings to Blackberry Events
|
{html}<div><p>Mobile Distribute App event: Use sendDistributeEvent() from MobileUsageUtils</p> <p>Mobile Install on Device event: use sendInstallEvent() from MobileUsageUtils</p> <p>Blackberry does not have devName / sdk fields for those methods. Those fields should have null passed in.</p></div>{html}
| 1 |
2 |
TISTUD-121
|
03/09/2011 17:30:17
|
Allow users to download older versions of Mobile SDK
|
Change "Install Titanium SDK From URL..." to "Install Specific Titanium SDK..." Add radio button: * Install from URL: Top text box will stay as before, allowing people to paste in. Add browse button to surf to local location on disk * Install from Update stream: Cascading drop-downs ** Contributed via extension point. Two default streams contributed ** "release" stream: https://api.appcelerator.net/p/v2/release-list?name=mobilesdk (filter on OS) ** "continuous integration master" stream: http://builds.appcelerator.com.s3.amazonaws.com/mobile/master/index.json (we may need to work with platform to either a) regularize the format or b) allow for the extension point to apply some regex/xpath to the JSON to grab build info)
| 13 |
3 |
TISTUD-127
|
03/10/2011 10:53:37
|
Hook up language modules to be exported in timanifest file during Desktop packaging
|
The code for dealing with modules was commented out by me in porting over the Ti Dev 1 packager for Desktop, since we didn't have this in our metadata or anything. We need to re-implement this now that we are keeping track of this.
| 1 |
4 |
TISTUD-138
|
03/11/2011 07:58:45
|
Add Portal Dispatcher to Launch Specific Wizard
|
Could be done through a link. Suggestion is to allow the user to pass in a specific ID, i.e. com.appcelerator.titanium.ui.import.wizard
| 1 |
5 |
TISTUD-176
|
03/21/2011 13:36:51
|
Update the verified publisher in Windows installer to Appcelerator
|
It currently shows Aptana, Inc when hovering over the installer image. Would be 5 points if it is already in correct format.
| 8 |
6 |
TISTUD-200
|
03/28/2011 16:19:55
|
Tiapp: surface errors/warnings in Overview Editor to Problem view and as project file decorators
|
Steps to Reproduce: 1. Create a new project from tiDev 2. Import the project to tiStudio 3. open tiapp.xml Actual: there are errors that the user need to resolve, but they do not see that indication until file is open Expected: To indicate to the user that there is an error on the project when they import
| 20 |
7 |
TISTUD-273
|
04/06/2011 11:42:00
|
Allow selection by CamelCase
|
In another I-can't-name-it Eclipse based IDE, there's a feature where you can select things based on CamelCase, instead of by word, which is very handy. Example: If I have code like this: /pintley/ui/components/MoreRow.js On OS X, if I put my cursor between "Row" and ".js", hold down option-shift, and hit the left arrow, it would highlight "Row" instead of "MoreRow". It's a huge timesaver, but I can see that not everyone would like it. I just want the option.
| 8 |
8 |
TISTUD-525
|
04/15/2011 03:27:36
|
Replace colons in project names with underscore characters
|
I tried creating a mobile project through developer with a colon in the name and got the following in the console. Just create a project with a colon in the name to reproduce. We should instead replace the colon with an underscore. {panel} <p><a href="/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> Compiling JavaScript...one moment <a href="/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> Simulator is exiting <a href= "/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> No JavaScript errors detected. <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> executing command: /usr/bin/killall iPhone Simulator <a href="/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> One moment, building ... <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copy resources from /Users/kevin/Name: Lite/Resources to /Users/kevin/Name: Lite/build/iphone/tmp <a href="/projects/32238/changesets/DEBUG" title="Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/about.html to /Users/kevin/Name: Lite/build/iphone/tmp/about.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.css to /Users/kevin/Name: Lite/build/iphone/tmp/index.css <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.html to /Users/kevin/Name: Lite/build/iphone/tmp/index.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.js to /Users/kevin/Name: Lite/build/iphone/tmp/index.js <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/about.html to /Users/kevin/Name: Lite/build/iphone/tmp/about.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.css to /Users/kevin/Name: Lite/build/iphone/tmp/index.css <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.html to /Users/kevin/Name: Lite/build/iphone/tmp/index.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.js to /Users/kevin/Name: Lite/build/iphone/tmp/index.js <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/about.html to /Users/kevin/Name: Lite/build/iphone/tmp/about.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.css to /Users/kevin/Name: Lite/build/iphone/tmp/index.css <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.html to /Users/kevin/Name: Lite/build/iphone/tmp/index.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.js to /Users/kevin/Name: Lite/build/iphone/tmp/index.js <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/about.html to /Users/kevin/Name: Lite/build/iphone/tmp/about.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.css to /Users/kevin/Name: Lite/build/iphone/tmp/index.css <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.html to /Users/kevin/Name: Lite/build/iphone/tmp/index.html <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/index.js to /Users/kevin/Name: Lite/build/iphone/tmp/index.js <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/default.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/default.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/default.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/android/default.png to /Users/kevin/Name: Lite/build/iphone/tmp/android/default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/iphone/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copy resources from /Users/kevin/Name: Lite/Resources/iphone to /Users/kevin/Name: Lite/build/iphone/tmp <a href="/projects/32238/changesets/DEBUG" title="Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/appicon.png to /Users/kevin/Name: Lite/build/iphone/tmp/appicon.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/closebox.png to /Users/kevin/Name: Lite/build/iphone/tmp/closebox.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> copying: /Users/kevin/Name: Lite/Resources/iphone/Default.png to /Users/kevin/Name: Lite/build/iphone/tmp/Default.png <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.App <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.API <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.Network <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.Platform <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.Analytics <a href="/projects/32238/changesets/DEBUG" title="Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.Media <a href="/projects/32238/changesets/DEBUG" title="Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.Gesture <a href= "/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> module library dependency detected Titanium.UI <a href="/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> Executing XCode build... <a href= "/projects/32238/changesets/INFO" title= "Changeset [INFO]">[INFO]</a> Executing XCode Compiler [toggle output] <a href="/projects/32238/changesets/DEBUG" title= "Changeset [DEBUG]">[DEBUG]</a> executing command: xcodebuild -configuration Debug -sdk iphonesimulator3.1.2 WEB_SRC_ROOT=/Users/kevin/Name: Lite/build/iphone/tmp GCC_PREPROCESSOR_DEFINITIONS=<strong>LOG</strong>ID<strong>=d7b66483-2558-4df7-9701-dfe81c20550d DEPLOYTYPE=development DEBUG=1 Traceback (most recent call last):<br> File "/Library/Application Support/Titanium/mobilesdk/osx/0.8.1/iphone/builder.py", line 544, in<br> main(sys.argv)<br> File "/Library/Application Support/Titanium/mobilesdk/osx/0.8.1/iphone/builder.py", line 359, in main<br> "GCC_PREPROCESSOR_DEFINITIONS=</strong>LOG<strong>ID</strong>=%s DEPLOYTYPE=development DEBUG=1" % log_id File "/Library/Application Support/Titanium/mobilesdk/osx/0.8.1/iphone/run.py", line 7, in run<br> (so,se) = subprocess.Popen(args, stderr=subprocess.PIPE, stdout=subprocess.PIPE).communicate() File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/subprocess.py", line 667, in communicate<br> return self.<em>communicate(input)<br> File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/subprocess.py", line 1138, in</em> communicate<br> rlist, wlist, xlist = select.select(read_set, write_set, [])<br> KeyboardInterrupt</p></div> {panel}
| 5 |
9 |
TISTUD-302
|
04/18/2011 15:22:26
|
Build error when using external module
|
When I try to include an external module (SMSDialog Module from https://github.com/omorandi/TiSMSDialog/tree/) and compile my app to run on the iPhone simulator I get the following error: [ERROR] Error: Traceback (most recent call last): File "/Library/Application Support/Titanium/mobilesdk/osx/1.6.1/iphone/builder.py", line 1091, in main execute_xcode("iphonesimulator%s" % link_version,["GCC_PREPROCESSOR_DEFINITIONS=__LOG__ID__=%s DEPLOYTYPE=development TI_DEVELOPMENT=1 DEBUG=1 TI_VERSION=%s" % (log_id,sdk_version)],False) File "/Library/Application Support/Titanium/mobilesdk/osx/1.6.1/iphone/builder.py", line 1012, in execute_xcode output = run.run(args,False,False,o) File "/Library/Application Support/Titanium/mobilesdk/osx/1.6.1/iphone/run.py", line 39, in run sys.exit(rc) SystemExit: 65 This same code compiles correctly using Titanium Developer version 1.2.2.
| 1 |
10 |
TISTUD-317
|
04/26/2011 07:13:11
|
Confirm BlackBerry Tooling can install on top of Titanium Studio
|
Confirm that the BlackBerry tooling here can be installed on top of Titanium Studio: http://na.blackberry.com/eng/developers/javaappdev/javaplugin.jsp If it cannot, we need to figure out what packaging changes to make to Titanium Studio in order for it to be able to work. If it turns out that it requires a whole bunch of things, like the Java editor, then we may want to consider requiring those who wish to do BlackBerry development to install Eclipse and use TiStudio as a plugin.
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.