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,126 |
TIMOB-25701
|
01/24/2018 14:28:03
|
Add support for promises to Titanium and Alloy
|
As a developer, I want to be able to use libraries that depend on JavaScript Promises, So that I can have out-0f-box support for a wider range of modules. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises I have been using JavaScript promises in my code for years but the only way to use modules that depend on Promises is to add support myself. It would be great if Titanium added built-in support for Promises. I think it would be a relatively small change. Just add bluebird (http://bluebirdjs.com/docs/getting-started.html) and add a global variable "Promise". Let me know if you have any questions. Thanks!
| 0 |
3,127 |
TIMOB-25941
|
01/24/2018 16:51:45
|
Android: HTTPClient downloads are slower compared to iOS
|
Performance of HTTP Client on Android is rather sub-par when compared to how it performs on iOS. Speed and responsiveness is just not there and has never been. It also seems to be hard on resources that can really slow down the performance of the phone/app as a whole when there are multiple HTTP requests happening at once or in succession. Here is a basic bit of code that just does a download of a 100 Mb file and shows the speed of the download and time. In the image attached you can see the performance difference between a iPhone and Android phone running the same app. The android phone is more the capable of the same download speed as the iPhone is showing, when using react or when creating a web view to do the same thing I can get over 150 Mbps on the Android phone. Sample code: {code:java} var xhr = null; var win = Ti.UI.createWindow({ backgroundColor: '#fff', fullscreen: false, navBarHidden: true, exitOnClose: true, theme: "Theme.materialTheme", orientationModes: [Titanium.UI.PORTRAIT] }); var runTime = Ti.UI.createLabel({ text: 'Run Time...', top: 50, left: 10, color: '#000' }); var downloadSpeed = Ti.UI.createLabel({ text: '0.00 Mbps', top: 90, left: 10, color: '#000' }); var buttonStart = Ti.UI.createButton({ title: "START", width: 100, height: 40, top: '45%', left: '10%' }); var buttonStop = Ti.UI.createButton({ title: "STOP", width: 100, height: 40, top: '45%', right: '10%' }); buttonStart.addEventListener("click", function() { var startTime = new Date().getTime(); var totalPercent = 0; xhr = Titanium.Network.createHTTPClient({ ondatastream: function(e) { totalPercent = (e.progress).toFixed(2); var currentTime = new Date().getTime(); var timeDiff = ((currentTime-startTime)/1000).toFixed(2); var totalDownloaded = (102400 * totalPercent); var currentKBPS = (((((totalDownloaded * 1024) * 8.192) / timeDiff) / 1024 / 1024)).toFixed(2); runTime.text = timeDiff; downloadSpeed.text = currentKBPS + ' Mbps'; }, onload: function() { alert('All Finished!'); }, timeout: 10000 }); xhr.open('GET','http://mirror.lstn.net/st/test100.zip'); xhr.send(); }); buttonStop.addEventListener("click", function() { xhr.abort(); }); win.add(runTime); win.add(downloadSpeed); win.add(buttonStart); win.add(buttonStop); win.open(); {code}
| 5 |
3,128 |
TIMOB-25703
|
01/24/2018 21:40:43
|
Android: Add VideoPlayer "showsControls" property
|
*Summary:* As of Titanium 7.0.0, we've added VideoPlayer.showsControls property for iOS to show/hide the overlaid video controls. We should do the same on Android for parity. http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Media.VideoPlayer-property-showsControls *Test:* Once this feature is implemented, run the below code on Android and verify that the video player does not show any overlaid controls when the video is tapped on. {code:javascript} var window = Ti.UI.createWindow({ fullscreen: true }); var videoView = Ti.Media.createVideoPlayer( { url: "http://download.blender.org/peach/bigbuckbunny_movies/BigBuckBunny_640x360.m4v", autoplay: true, showsControls: false, scalingMode: Ti.Media.VIDEO_SCALING_ASPECT_FIT, width: Ti.UI.FILL, height: Ti.UI.FILL, }); window.add(videoView); window.open(); {code}
| 1 |
3,129 |
TIMOB-25744
|
01/25/2018 20:59:49
|
iOS: Uploaded file persists in memory when using JSCore
|
Doing a file upload with the createHTTPClient on iOS in TI SDK 7.x.x causes the file to stay in ram after the upload is completed or aborted. It does not get removed from ram as it should. When doing a large upload or multiple uploads this is a rather big problem because it can cause the app to crash or have a large ram usage as you can see from the screen shot. Example code is below, using a 100MB file will cause 400 + Mb of ram usage for 1 upload, this will then stay in ram, doing 3 uploads will cause the app to crash on a iPhone X. The file should be removed from ram when the upload is completed or aborted, it use to do this in previous version of TI. {code:java} var xhr = null; var win = Ti.UI.createWindow({ backgroundColor: '#fff', fullscreen: false, navBarHidden: true, exitOnClose: true, theme: "Theme.materialTheme", orientationModes: [Titanium.UI.PORTRAIT] }); var runTime = Ti.UI.createLabel({ text: 'Run Time...', top: 50, left: 10, color: '#000' }); var uploadSpeed = Ti.UI.createLabel({ text: '0.00 Mbps', top: 90, left: 10, color: '#000' }); var buttonStart = Ti.UI.createButton({ title: "START", width: 100, height: 40, top: '45%', left: '10%' }); var buttonStop = Ti.UI.createButton({ title: "STOP", width: 100, height: 40, top: '45%', right: '10%' }); var uploadfile = Ti.Filesystem.getFile(Ti.Filesystem.getResourcesDirectory(), "100MB.bin").read(); buttonStart.addEventListener("click", function() { console.log('Starting Upload'); var startTime = new Date().getTime(); var totalPercent = 0; xhr = Titanium.Network.createHTTPClient(); xhr.onsendstream = function(e){ console.log(e.progress); totalPercent = (e.progress).toFixed(2); var currentTime = new Date().getTime(); var timeDiff = ((currentTime-startTime)/1000).toFixed(2); var totalDownloaded = (102400 * totalPercent); var currentKBPS = (((((totalDownloaded * 1024) * 8.192) / timeDiff) / 1024 / 1024)).toFixed(2); runTime.text = timeDiff; uploadSpeed.text = currentKBPS + ' Mbps'; }; xhr.onload = function(e) { }; xhr.open('POST','http://sfo.veeapps.com/upload.php'); xhr.send({media: uploadfile }); }); buttonStop.addEventListener("click", function() { xhr.abort(); xhr = null; }); win.add(runTime); win.add(uploadSpeed); win.add(buttonStart); win.add(buttonStop); win.open(); {code}
| 8 |
3,130 |
TIMOB-25708
|
01/25/2018 22:27:53
|
iOS: Support iOS 12 and Xcode 10
|
This epic will track all the items required to enable support for iOS 12
| 0 |
3,131 |
TIMOB-25726
|
01/26/2018 02:54:53
|
Android: Ensure device's installed Google Play Services is available/updated on app startup
|
*Summary:* The Google Play Services libraries (included with "ti.playservices" module) are merely an interface to the installed Google Play Services app/apk. The app must ensure that Google Play Services is installed on the device and that its apk version is greater or equal to the version of the Google Play Services libraries that the app includes... or else the library's APIs will fail or throw an exception. Google documents the above here... https://developers.google.com/android/guides/setup#ensure_devices_have_the_google_play_services_apk *Feature Requirements:* # The Google Play Services check should be done when the Titanium splashscreen is displayed (ie: TiLaunchActivity.java) and before executing the "app.js" script. # Do not run the check if "ti.playservices" module is not included in the app. (In this case, assume app does not use Google Play Services.) # If Google Play Services is found to be too old or disabled, display an alert asking end-user to resolve it. Keep the end-user on the launcher screen in this case. # If end-user chooses to update Google Play Services, remain on the launcher screen until the download completes, then proceed on to execute the "app.js" script. # Do not display an alert if the device does not have Google Play installed and proceed to execute the "app.js" script. In this case, assume the app is not distributed via the Google Play app store (such as Amazon) or the app is running via an emulator without Google Play installed. # Add "tiapp.xml" boolean property "ti.playservices.validate.on.startup" which when set {{false}} will disable this feature. In this case, it is the app developer's responsibility to manage this. *Note:* Currently, Titanium's "ti.playservices" module purposely uses Google Play Services library versions a few revs old to avoid the failure mentioned above. Once we update a Titanium app to install the newest version of Google Play Services on startup, we no longer have to fear this issue and we can keep the module's libraries up-to-date.
| 5 |
3,132 |
TIMOB-25731
|
01/26/2018 13:18:32
|
Android: Glitch on backgroundColor animation with borderRadius
|
Background color animation in rounded-angle views changes the color to the rectangle behind the view, but the shape with rounded corners does not animate. I enclose two comparison videos on iOS and Android. Example code: {code:java} // $.win is the Window View in index.xml Alloy controller var view1 = $.UI.create('View', { width: 100, height: 100, top: 110, backgroundColor: "#FF0000", borderRadius: 50 }); $.win.add(view1); var view2 = $.UI.create('View', { width: 100, height: 100, top: 220, backgroundColor: "#FF0000", borderRadius: 50 }); $.win.add(view2); $.win.addEventListener('open', function() { var ani1up = function() { view1.animate({ backgroundColor: '#0000FF', duration: 500 }, function() { ani1down(); }); }; var ani1down = function() { view1.animate({ backgroundColor: '#FF0000', duration: 500 }, function() { ani1up(); }); }; var ani2up = function() { view2.animate({ backgroundColor: '#0000FF', duration: 2000 }, function() { ani2down(); }); }; var ani2down = function() { view2.animate({ backgroundColor: '#FF0000', duration: 2000 }, function() { ani2up(); }); }; ani1up(); ani2up(); }); $.win.open(); {code}
| 1 |
3,133 |
TIMOB-25729
|
01/26/2018 21:26:59
|
Hyperloop: iOS - Unable to load Mapbox using Hyperloop
|
h5 Issue: Using steps in Timob-23853 https://jira.appcelerator.org/browse/TIMOB-23853?focusedCommentId=429306&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-429306 customer is unable to load Mapbox and gets error: "Couldn't find module: " Attached is a screenshot of the error along with the testapp: [^HyperloopDemo.zip] !Screen_Shot_2018-01-26_at_1.29.28_PM.png|thumbnail! you can see the log we get when trying to load the module here: https://gist.github.com/exclusiveTanim/c47578c227c7e958a34d441311a5c223 Customer has reached out to express urgency for a resolution.
| 5 |
3,134 |
TIMOB-25730
|
01/26/2018 23:15:17
|
Android: Allow SearchBar "color" and "hintTextColor" properties to be set dynamically
|
*Summary:* Add the ability to set the text color and hint text color of a "Ti.UI.SearchBar" on Android The Android "Ti.UI.SearchBar" supports undocumented properties "color" and "hintTextColor" for changing its text field colors. However, these properties can only be set upon creation. We should allow these properties to be set dynamically. This is especially needed for parity since we're adding this feature on iOS via [TIMOB-10368]. *Note:* We plan on adding a similar feature to Android's "SearchView" in 7.1.0. See: [TIMOB-25668] *Test Code:* Once this feature has been implemented, verify that the SearchBar's hint text color is "blue" and the entered text is "red". {code:javascript} var window = Ti.UI.createWindow(); var searchBar = Ti.UI.createSearchBar( { barColor: "white", hintText: "Hint Text...", }); window.addEventListener("open", function(e) { var dialog = Ti.UI.createAlertDialog( { message: "Show SearchBar in...", buttonNames: ["Window", "ListView", "TableView"], }); dialog.addEventListener("click", function(e) { searchBar.color = "red"; searchBar.hintTextColor = "blue"; switch (e.index) { case 0: searchBar.top = 0; searchBar.left = 0; searchBar.width = Ti.UI.FILL; searchBar.height = "50dp"; window.add(searchBar); window.add(Ti.UI.createLabel({ text: "Window" })); break; case 1: var listView = Ti.UI.createListView( { searchView: searchBar, sections: [Ti.UI.createListSection({ headerTitle: "ListView" })], width: Ti.UI.FILL, height: Ti.UI.FILL, }); window.add(listView); break; case 2: var tableView = Ti.UI.createTableView( { search: searchBar, data: [Ti.UI.createTableViewRow({ title: "TableView" })], width: Ti.UI.FILL, height: Ti.UI.FILL, }); window.add(tableView); break; } }); dialog.show(); }); window.open(); {code}
| 1 |
3,135 |
TIMOB-25733
|
01/28/2018 22:18:52
|
Android: View with border larger than screen may fail to appear as of 7.0.2.RC
|
This warning appeared to me with SDK 7.0.2.v20180123170142 and 7.0.2.v20180125101244 only. So some views do not display, but with SDK 7.0.2.v20180123083830 and below it's working good [WARN]: View: TiBorderWrapperView not displayed because it is too large to fit into a software layer (or drawing cache), needs 14925600 bytes, only 8294400 available
| 3 |
3,136 |
TIMOB-25776
|
01/29/2018 13:31:11
|
Android: Cannot use Ti.NFC
|
Dear all, I've been playing (or trying to play) with the ti.nfc module for a while. I'm just throwing there the example TagViewer from the module examples, just a copy and paste of the module and a modification of the tiapp.xml to add the android properties in manifest. However, when trying to run the project, this warning appears in there: [WARN] : android:launchMode should not be used. Ignoring definition from .NfcActivity And the application doesn't work properly. Am I doing something wrong? Should I change something to allow android:launchMode? Thanks for your comments. PD: I've also attached the tiapp.xml the modules folder and the app folder of the project, in case you want to take a look (I tried to attach the whole project, but looks like it is too heavy).
| 8 |
3,137 |
TIMOB-25735
|
01/30/2018 18:47:31
|
Android: Replace Activity.isDestroyed() with Android 4.1 compatible alternative
|
The fix for TIMOB-25656 made use of {{Activity.isDestroyed()}} which is an Android 4.2+ method. We need to replace it with an alternative. *TEST CASE* - Titanium Application should launch on 4.1 device
| 1 |
3,138 |
TIMOB-25736
|
01/31/2018 11:48:14
|
iOS: Question about TabGroup limitations
|
We are not able to resize the tab group height, as when we provide both icon and title for tab they are getting stick to each other using circle shape icon. Also we are not able to provide the padding forth icons. *Test Environments:* Appcelerator Command-Line Interface, version 7.0.1 Operating System Mac OS X,Version 10.13.2,Architecture 64bit,CPUs 4,Memory 8.0GB Node.js Version = 8.9.1 npm Version = 5.5.1 Appcelerator CLI 4.2.11 Core Package 7.0.1 Titanium CLI 5.0.14 node-appc Version 0.2.41 Titanium SDK 7.0.1.GA iOS SDK: 11.1-Simulator iPhone X *Test Steps:* 1. Open Studio and create a clasic project 2.Paste the resource folder to newly created project 3. Run via simulator . Observe that both icon and title for tab they are getting stick to each other using circle shape icon. *Test Output:* [Snapshot| https://s9.postimg.org/3uxpv598v/Simulator_Screen_Shot_-_i_Phone_X_-_2018-01-31_at_15.29.01.png]
| 2 |
3,139 |
TIMOB-25739
|
02/01/2018 09:09:24
|
iOS 11: Location permissions do not indicate missing "WhenInUse" privacy-key
|
When asking for Location permissions in iOS 11, the following error is shown, even thought my plist already have these keys: {code:java}[ERROR] : The NSLocationAlwaysAndWhenInUseUsageDescription, NSLocationAlwaysUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription key must be defined in your tiapp.xml in order to request this permission.{code} This is the ios part of the tiapp.xml. I've also opened the generated Info.plist file and it looks good. {code:java} <ios> <enable-launch-screen-storyboard>true</enable-launch-screen-storyboard> <use-app-thinning>true</use-app-thinning> <plist> <dict> <key>NSLocationAlwaysUsageDescription</key> <string>Can we use geolocation?</string> <key>NSLocationAlwaysAndWhenInUseUsageDescription</key> <string>Can we use geolocation?</string> <key>UISupportedInterfaceOrientations~iphone</key> <array> <string>UIInterfaceOrientationPortrait</string> </array> <key>UISupportedInterfaceOrientations~ipad</key> <array> <string>UIInterfaceOrientationPortrait</string> </array> <key>UIRequiresPersistentWiFi</key> <false/> <key>UIPrerenderedIcon</key> <false/> <key>UIStatusBarHidden</key> <false/> <key>UIStatusBarStyle</key> <string>UIStatusBarStyleDefault</string> </dict> </plist> </ios> {code} In order to reproduce the issue, this is an example code, on an normal app, inside app.js (I've also attached the file) {code:java} var win = Ti.UI.createWindow({layout:'vertical'}); var label = Ti.UI.createLabel({top:30,width:'90%',height:Ti.UI.SIZE}); win.addEventListener('open',function(){ Ti.Geolocation.requestLocationPermissions(Ti.Geolocation.AUTHORIZATION_ALWAYS, function(e){ apiInfo(JSON.stringify(e)); }); }); function apiInfo(msg) { Titanium.UI.createAlertDialog({ title: "info", message:msg }).show(); }; win.add(label); win.open(); {code} Thanks for having a look
| 2 |
3,140 |
TIMOB-25740
|
02/01/2018 09:26:23
|
TiAPI: Add support for async/await
|
We added support for ES6 and later in the latest 7.1.0 changes, which is *awesome*! The only thing missing is the support for using async/await in Titanium code. Here is an example (taken from my sample-project): {code:js} someOtherMethod() { this._getUserLocation(); } async _getUserLocation() { // FIXME: Current throws, work in progress! const coordinates = await Ti.Geolocation.getCurrentPosition(event => { return new Promise(resolve => { resolve(event.coords); }); }); alert(`Found location! Latitude: ${coordinates.latitude}, Longitude: ${coordinates.longitude}`); } {code} The full sample can be found [here|https://github.com/hansemannn/titanium-es6-sample/blob/master/Resources/src/application.js#L84-L94]. It is throwing an "Cannot find regeneratorRuntime" error when calling the method, which looks like a Babel error that occurs when certain transform-plugins are missing. We use the babel-preset-env, which should already support it by having a dependency on [babel-plugin-transform-async-to-generator|https://www.npmjs.com/package/babel-plugin-transform-async-to-generator] but for some reasons it does not work. Important to say is also that I may be doing something wrong, so let me know if thats the case!
| 8 |
3,141 |
TIMOB-25741
|
02/01/2018 09:28:18
|
iOS:Tableview with custom rows becomes blank on search bar OnFocus
|
Tableview with custom rows becomes blank on search bar OnFocus *Test Environments:* Appcelerator Command-Line Interface, version 7.0.1 Operating System Mac OS X,Version 10.13.2,Architecture 64bit, CPUs 4,Memory 8.0GB Node.js Version = 8.9.1 npm Version = 5.5.1 Appcelerator CLI 4.2.11 Core Package 7.0.1 Titanium CLI 5.0.14 node-appc Version 0.2.41 Titanium SDK 7.0.1.GA iOS SDK: 11.1-Simulator iPhone X Xcode 9.1,9.2 *Test Code:* *index.js* {code} $.index.open(); {code} *index.xml* {code} <Alloy> <Window title="TableView Search Issue"> <TableView filterAttribute="customSearchProp" top="20"> <SearchBar platform="android,ios"/> <TableViewSection> <TableViewRow customSearchProp='Row 1'> <View height="40"> <Label text="Row 1"></Label> </View> </TableViewRow> <TableViewRow customSearchProp='Row 3'> <View height="40"> <Label text="Row 2" ></Label> </View> </TableViewRow> <TableViewRow customSearchProp='Row 3'> <View height="40"> <Label text="Row 3"></Label> </View> </TableViewRow> </TableViewSection> </TableView> </Window> </Alloy> {code} *Test Steps:* 1. Create an alloy project 2. Paste the sample code to app folder 3. Run Via simlator 4. Click on searchbar and observe that tableview becomes blank on search bar OnFocus *Output*:[Screenshot| https://s17.postimg.org/ouj2zhgwf/Simulator_Screen_Shot_-_i_Phone_X_-_2018-02-01_at_15.01.03.png]
| 0 |
3,142 |
TIMOB-25743
|
02/02/2018 04:12:27
|
Windows: Auto-increment version numbering
|
We might want to introduce automatic-increment for build number during build due to deployment issues (See TIMOB-25616 and TIMOB-25017). Here's some starting point to discuss: - Do we accept the difference between version numbering in tiapp.xml and actual app? Note that Developers may want to determine specific version number for the release build. - We could introduce special placeholder like {{<version>1.0.*</version>}} but this may cause breaking change and parity issue between platforms. Do we wan to do like this? Or we could just say "If you omit the build number, we just automatically increment it behind scenes, only on Windows platform". - Do we accept this breaking change regarding new version numbering spec? - Do we want to enable it by default? Otherwise do we want to introduce new property in tiapp.xml like {{<enable-auto-build-numvering/> or so}}? - Do we want to introduce this new version numbering spec for other platforms? Do we want to keep parity for it? - Do we want to make it configurable from Appc Studio? For instance ["Automatically increment" checkbox in UWP packager|https://docs.microsoft.com/en-us/windows/uwp/packaging/images/packaging-screen5.jpg]
| 5 |
3,143 |
TIMOB-25747
|
02/03/2018 22:34:36
|
iOS: Modal error dialog not shown when using main-thread
|
When running on main-thread (new default since 7.0.0), the "red screen of death" is not shown. This is due to [this commit|https://github.com/appcelerator/titanium_mobile/commit/32dd2c512b18e7cfa6655fb4b57987f45613249a] from the good old 1.x SDK days where we didn't have the ability to run UI on the main-thread. This ticket should also be used to refactor the error dialog a bit - to include the error reason and make a bit less ugly.
| 5 |
3,144 |
TIMOB-25748
|
02/04/2018 10:16:01
|
iOS: Remove TiCore
|
We deprecated TiCore in SDK 7 and fixed the last issues around using JSCore (proxies not being released, post data not being released, fix debugger). So it's time!
| 13 |
3,145 |
TIMOB-25749
|
02/04/2018 17:04:16
|
Android: Incompatible types: Class<KrollExternalModule>
|
I'm using 7.0.1, trying to switch to 7.0.2 RC I unable to run it to android and I get this error error: incompatible types: Class<KrollExternalModule> cannot be converted to Class<? extends KrollSourceCodeProvider> [ERROR] : (Class<KrollExternalModule>) Class.forName(className)); [ERROR] : ^ [ERROR] : Note: Some input files use unchecked or unsafe operations. [ERROR] : Note: Recompile with -Xlint:unchecked for details. [ERROR] : Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output [ERROR] : 1 error [ERROR] Application Installer abnormal process termination. Process exit value was 1
| 2 |
3,146 |
TIMOB-25753
|
02/05/2018 18:59:39
|
Android: ScrollView "width" ignores Ti.UI.SIZE as of 6.3.0
|
*Summary:* Setting the ScrollView "width" property to "Ti.UI.SIZE" will do a "Ti.UI.FiLL" instead as of Titanium 6.3.0. _(This is not an issue with the "height" property. Only the "width".)_ *Code to Reproduce:* {code:javascript} var window = Ti.UI.createWindow(); var scrollView = Ti.UI.createScrollView( { layout: "vertical", showHorizontalScrollIndicator: false, shorVerticalScrollIndicator: true, backgroundColor: "yellow", width: Ti.UI.SIZE, height: Ti.UI.FILL, }); scrollView.add(Ti.UI.createLabel( { text: "Hello World", color: "white", backgroundColor: "blue", width: Ti.UI.SIZE, height: Ti.UI.SIZE, })); window.add(scrollView); window.open(); {code} *Result:* The above code produces a yellow ScrollView. Note that the ScrollView does not auto-size itself to just fit the "Hello World" label as seen in "Screenshot-Bad.png". *Expected Result:* The ScrollView width should auto-size itself to fit the label as shown in "Screenshot-Good.png". This is how it worked in Titanium 6.2.2 and older versions. *Cause:* This bug happened when we added "RefreshControl" support. Google's Java "SwipeRefreshLayout" class does not support the "WRAP_CONTENT" setting. *Recommended Solution:* Modify Titanium's Java "TiSwipeRefreshLayout" onMeasure() method to handle the "WRAP_CONTENT" setting ourselves. We're already doing this in the vertical direction and we need to do the same for the horizontal. https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiSwipeRefreshLayout.java#L76
| 1 |
3,147 |
TIMOB-25757
|
02/06/2018 22:50:17
|
Android: Improve proxy getter/setter validation
|
- The parent proxy of getters and setters is not validated which can cause a crash *TEST CASE* {code:js} Ti.API.bubbleParent; // should not crash {code}
| 3 |
3,148 |
TIMOB-25760
|
02/07/2018 14:56:20
|
Windows: Titanium.Network.HTTPClient Location doesn't return the redirected URL
|
Titanium.Network.HTTPClient Location doesn't return the redirected url in windows. It works perfectly on iOS and Android. Sample Code: var _tmpURL = "any url that redirects to other url" var _tmpClient = Ti.Network.createHTTPClient({ onload: function(e) { serverAddressRedirected = _tmpClient.location; //this should return redirected url but returns the url before redirect Ti.API.info("Location:" + serverAddressRedirected); }, onerror : function(e) { alert("Error:" + e.error); }, timeout: 30000 }); _tmpClient.open("GET",_tmpURL); _tmpClient.send();
| 8 |
3,149 |
TIMOB-25769
|
02/07/2018 21:07:41
|
Android: Allow video-upload in Ti.UI.WebView
|
If you display a web form in Webview on your app with a File upload, you can't choose a video on Android. (iOS it's OK).
| 3 |
3,150 |
TIMOB-25767
|
02/09/2018 21:53:44
|
Android: Animated views should retain their initial properties
|
- Animations update the properties of the proxy after a transformation. Out documentation suggests this is not the case (http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.Animation) {quote}Note that when you animate a view's size or position, the actual layout properties (such as top, left, width, height) are not changed by the animation.{quote} *TEST CASE* {code:js} var win = Ti.UI.createWindow(); view = Ti.UI.createView({ backgroundColor:'red', width: 100, height: 100, left: 100, top: 100 }); win.addEventListener('open', function () { var animation = Ti.UI.createAnimation({ top: 150, duration: 1000 }); animation.addEventListener('complete', function () { // make sure to give it a time to layout setTimeout(function () { console.log(`X: ${view.rect.x} == 150, TOP: ${view.top} == 100`); }, 500); }); view.animate(animation); }); win.add(view); win.open(); {code}
| 3 |
3,151 |
TIMOB-25768
|
02/09/2018 22:55:49
|
Use rollup to avoid circular references with ES6 imports in JavascriptCore
|
- JavascriptCore does not have full ES6 module support, circular references with {{import}} will cause a stack overflow *TEST CASE* {code:js} // TODO {code}
| 8 |
3,152 |
TIMOB-25770
|
02/12/2018 16:39:26
|
Android: requestThumbnailImagesAtTimes() does not work with remote content
|
Requesting a thumb from a video payer that has a remote video loaded results in a crash. Test case: {code:java} var win = Ti.UI.createWindow({layout:'vertical'}), buttonCamera = Ti.UI.createButton({title: "Camera"}), buttonGallery = Ti.UI.createButton({title: "Gallery"}), buttonLocalURL = Ti.UI.createButton({title: "Local"}), buttonRemoteURL = Ti.UI.createButton({title: "Remote"}), buttonLayout = Ti.UI.createView({bottom: 20, layout:'horizontal'}), slider = Ti.UI.createSlider({top: 30, backgroundColor: 'gray', min: 0, max: 100, width: '100%', touchEnabled: false, enabled: false}), videoPlayer = Ti.Media.createVideoPlayer({top: 20, height:'30%', autoplay: false}), imageView = Ti.UI.createImageView({top: 20, height:'30%'}), updatingThumbnail = false; buttonLayout.add([buttonCamera, buttonGallery, buttonLocalURL, buttonRemoteURL]); win.add(videoPlayer); win.add(imageView); win.add(slider); win.add(buttonLayout); win.open(); slider.addEventListener('change', function(e) { if (videoPlayer && e.value > 0 && !updatingThumbnail) { updatingThumbnail = true; videoPlayer.requestThumbnailImagesAtTimes([e.value], Ti.Media.VIDEO_TIME_OPTION_NEAREST_KEYFRAME, function(response) { imageView.image = response.image; updatingThumbnail = false; }); } }); videoPlayer.addEventListener('durationavailable', function() { enableGetThumbSlider(); }); buttonCamera.addEventListener('click', recordVideo); function recordVideo() { disableGetThumbSlider(); var permissionsToRequest = []; var cameraPermission = "android.permission.CAMERA"; var hasCameraPerm = Ti.Android.hasPermission(cameraPermission); if (!hasCameraPerm) { permissionsToRequest.push(cameraPermission); } var storagePermission = "android.permission.READ_EXTERNAL_STORAGE"; var hasStoragePerm = Ti.Android.hasPermission(storagePermission); if (!hasStoragePerm) { permissionsToRequest.push(storagePermission); } if(permissionsToRequest.length > 0) { Ti.Android.requestPermissions(permissionsToRequest, function (e) { if (e.success) { showCamera(); } }); } else { showCamera(); } } function showCamera() { Ti.Media.showCamera({ autohide: false, animated: false, allowEditing: false, success:function(event) { videoPlayer.url = event.media.nativePath; }, cancel:function() { console.log("cancel"); }, error:function(error) { console.log("error"); console.log(error); }, mediaTypes: [Ti.Media.MEDIA_TYPE_VIDEO], }); } buttonLocalURL.addEventListener("click", function() { disableGetThumbSlider(); videoPlayer.url = 'BigBuckBunny_320x180.mp4'; }); buttonRemoteURL.addEventListener("click", function() { disableGetThumbSlider(); videoPlayer.url = 'http://ve-ep.ember.ltd/assets/media/qa/samplevideo-1280x720-5mb.mp4'; }); buttonGallery.addEventListener("click", function() { disableGetThumbSlider(); var intent = Ti.Android.createIntent({ action: Ti.Android.ACTION_PICK, type: "video/*" }); intent.addCategory(Ti.Android.CATEGORY_DEFAULT); win.getActivity().startActivityForResult(intent, function(e) { if (e.intent != null) { videoPlayer.url = e.intent.data; } }); }); function disableGetThumbSlider() { slider.touchEnabled = false; slider.enabled = false; } function enableGetThumbSlider() { slider.touchEnabled = true; slider.enabled = true; } {code}
| 5 |
3,153 |
TIMOB-25771
|
02/12/2018 21:20:18
|
Android: Apps fail to build as of 7.0.2 if system requires proxy to access Internet
|
*Summary:* If the developer's system uses a proxy to access the Internet, then Android apps will fail to build as of Titanium 7.0.2. *Steps to Reproduce:* # Delete the following folder on Mac, if it exists: ~/.gradle/caches # Set up the machine to access the Internet via a proxy. # Configure the proxy settings in Appcelerator Studio via its "Proxy Setup" window or via the CLI's "appc config set proxyServer". # Attempt to do an Android build. *Result:* The build fails with follow logged errors... {code} [ERROR] Failed to run dexer: [ERROR] [ERROR] FAILURE: Build failed with an exception. [ERROR] [ERROR] * What went wrong: [ERROR] A problem occurred configuring root project 'android'. [ERROR] > Could not resolve all files for configuration ':classpath'. [ERROR] > Could not resolve net.sf.proguard:proguard-gradle:5.3.3. [ERROR] Required by: [ERROR] project : [ERROR] > Could not resolve net.sf.proguard:proguard-gradle:5.3.3. [ERROR] > Could not get resource 'https://repo1.maven.org/maven2/net/sf/proguard/proguard-gradle/5.3.3/proguard-gradle-5.3.3.pom'. [ERROR] > Could not GET 'https://repo1.maven.org/maven2/net/sf/proguard/proguard-gradle/5.3.3/proguard-gradle-5.3.3.pom'. [ERROR] > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [ERROR] [ERROR] * Try: [ERROR] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. [ERROR] [ERROR] * Get more help at https://help.gradle.org [ERROR] [ERROR] BUILD FAILED in 1s {code} *Cause:* A new "gradle" build step has been added to Titanium 7.0.2 to perform ProGuard and multidexing apps. Gradle is failing to download its module(s) from maven repositories since it is not configured to work through a proxy. *Recommended Solution:* Developers currently have to configure Titanium/Appc to use a proxy according to our docs here... http://docs.appcelerator.com/platform/latest/#!/guide/Using_Studio_From_Behind_a_Proxy http://docs.appcelerator.com/platform/latest/#!/guide/Appcelerator_CLI_Getting_Started When the Titanium build system generates the "gradle-wrapper.properties" file, it should add the CLI's proxy settings to that gradle property file as well. Gradle documents these proxy settings here... https://docs.gradle.org/current/userguide/build_environment.html#sec:accessing_the_web_via_a_proxy *Work-Around:* Titanium developers can work-around this issue by configuring a global "gradle.properties" file with these proxy settings according to the docs here... https://docs.gradle.org/current/userguide/build_environment.html#sec:accessing_the_web_via_a_proxy On Mac, the global file goes here... {code}~/.gradle{code} On Windows, the global file goes here... {code}C:\Users\<UserName>\.gradle{code}
| 5 |
3,154 |
TIMOB-25774
|
02/13/2018 07:24:29
|
Windows: Contact request should not block UI thread
|
Requesting access to contact while {{ContactManager::RequestStoreAsync}} should not block UI thread because permission requesting dialog actually uses UI thread. This causes intermittent application freeze described in TIMOB-23332.
| 5 |
3,155 |
TIMOB-25775
|
02/13/2018 11:55:05
|
iOS: Cannot get gradient properties after creation
|
Triggered by TIMOB-9366, a developer might want to receive gradient properties after creating the gradient. Example: {code:js} var win = Titanium.UI.createWindow({ backgroundColor:'#fff' }); var gradient = { type: 'radial', startPoint: { x: 50, y: 50 }, colors: [ 'red', 'blue'], startRadius: '90%', endRadius: 0 }; var radialGradient = Ti.UI.createView({ width: 100, height: 100, backgroundGradient: gradient }); win.addEventListener('open', function() { console.log(radialGradient.backgroundGradient.colors.join(', ')); // CRASH! }); win.add(radialGradient); win.open(); {code} This does not only effect the "colors" key but also "startPoint", "endPoint" and "type".
| 5 |
3,156 |
TIMOB-25778
|
02/14/2018 03:44:32
|
Windows: Implement Ti.UI.Label.ellipsize
|
Implement [Ti.UI.Label.ellipsize|http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.Label-property-ellipsize]. It should return {{Number}} value but currently on Windows it returns {{bool}}.
| 8 |
3,157 |
TIMOB-25779
|
02/14/2018 08:20:36
|
Foreground Push notification cannot get received when there is "Content-Available" in payload
|
h6.Reproduce 1. Run the following app on iOS device. https://github.com/sliang0904/SimlpePushCode/blob/master/app.js 2. Click subscribe button to register to channel. And keep the app in foreground. 3. Send push notification from dashboard. But with 'Content-Available' checked. (attached screen shot) 4. Then the app can not get the push notification. 5. But if you put the app in background. Then send same push again. then app can receive the push.
| 5 |
3,158 |
TIMOB-25780
|
02/14/2018 09:58:19
|
Windows: Ti.Filesystem.File can't handle multilingual filename
|
{{Ti.Filesystem.File}} can't handle multilingual filename. {code} var msg = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory, '網上廣東話輸入法.txt'); Ti.API.info(msg.write('Appcelerator', true)); // This should return true. {code} Expected: This should write a file with given filename and given content.
| 8 |
3,159 |
TIMOB-25783
|
02/15/2018 06:05:45
|
Windows: HttpClient.clearCookies freezes app
|
{{Ti.Network.HttpClient.clearCookies}} hangs. It also doesn't clear the cache. {code:javascript} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); win.addEventListener('open', function () { var xhr = Ti.Network.createHTTPClient(), cookie_string; function second_cookie_fn() { Ti.API.info('Set-Cookie: ' + this.getResponseHeader('Set-Cookie')); var second_cookie_string = this.getResponseHeader('Set-Cookie').split(';')[0]; // New Cookie should be different. Ti.API.info('OLD: ' + cookie_string); Ti.API.info('NEW: ' + second_cookie_string); win.backgroundColor = 'green'; } xhr.setTimeout(3e4); xhr.onload = function () { Ti.API.info('Set-Cookie: ' + this.getResponseHeader('Set-Cookie')); cookie_string = this.getResponseHeader('Set-Cookie').split(';')[0]; xhr.clearCookies('https://my.appcelerator.com'); xhr.onload = second_cookie_fn; setTimeout(function () { xhr.open('GET', 'https://my.appcelerator.com/auth/login'); xhr.send(); }, 5000); }; xhr.onerror = function (e) { Ti.API.warn(e); win.backgroundColor = 'red'; }; xhr.open('GET', 'https://my.appcelerator.com/auth/login'); xhr.send(); }); win.open(); {code} Expected: App should not freeze and New cookie should be different.
| 3 |
3,160 |
TIMOB-25784
|
02/15/2018 13:31:35
|
Windows: Ti.Geolocation.getCurrentPosition location is not accurate
|
Test Code : {code} function doClick(e) { Titanium.Geolocation.preferredProvider = "gps"; Titanium.Geolocation.purpose = "user coordinates"; Titanium.Geolocation.distanceFilter = 10; Titanium.Geolocation.getCurrentPosition(function(e) { if (!e.success || e.error) { return; } var longitude = e.coords.longitude; var latitude = e.coords.latitude; var altitude = e.coords.altitude; var heading = e.coords.heading; var accuracy = e.coords.accuracy; var speed = e.coords.speed; var timestamp = e.coords.timestamp; var altitudeAccuracy = e.coords.altitudeAccuracy; Titanium.Geolocation.reverseGeocoder(latitude, longitude, function(evt) { if (evt.success) { var places = evt.places; alert('Your Current Location is : ' + places[0].address + '\n Latitude:' + latitude + '\nLongitude : ' + longitude); } else { Ti.API.info("Reverse geocoding error"); } }); }); } $.index.open(); {code} Test Environment: {code} Appcelerator Command-Line Interface, version 7.0.2 Copyright (c) 2014-2018, Appcelerator, Inc. All Rights Reserved. Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 Architecture = 32bit # CPUs = 4 Memory = 15.9GB Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.0.14 node-appc Version = 0.2.41 Titanium SDKs 7.0.2.GA Version = 7.0.2 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.0.2.GA Platforms = android, windows git Hash = 5ef0c56 git Timestamp = 2/9/2018 19:02 node-appc Version = 0.2.43 7.0.1.GA Version = 7.0.1 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.0.1.GA Platforms = android, windows git Hash = f5ae7e5 git Timestamp = 12/18/2017 18:45 node-appc Version = 0.2.43 7.0.0.GA Version = 7.0.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.0.0.GA Platforms = android, windows git Hash = f09dec4 git Timestamp = 12/5/2017 21:33 node-appc Version = 0.2.43 6.3.0.GA Version = 6.3.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\6.3.0.GA Platforms = android, mobileweb, windows git Hash = 3620088 git Timestamp = 11/1/2017 01:16 node-appc Version = 0.2.43 5.5.1.GA Version = 5.5.1 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\5.5.1.GA Platforms = android, mobileweb, windows git Hash = b18727f git Timestamp = 09/27/16 05:38 node-appc Version = 0.2.36 Intel® Hardware Accelerated Execution Manager (HAXM) Not installed Java Development Kit Version = 1.8.0_131 Java Home = C:\Program Files (x86)\Java\jdk1.8.0_131 {code} Thanks
| 3 |
3,161 |
TIMOB-25785
|
02/16/2018 12:54:35
|
iOS: Sending events that cannot be serialized fail on SDK 7.0.0+
|
Here is a code : alloy.js {code:javascript} Ti.Gesture.addEventListener('orientationchange', function (e) { Ti.App.fireEvent('_customEvent', e); }); Ti.App.addEventListener('_customEvent', function () {}); {code} This triggers an error on orientation change {noformat} [ERROR] : Script Error { [ERROR] : column = 19; [ERROR] : line = 13; [ERROR] : message = "Invalid type in JSON write (GestureModule)"; [ERROR] : sourceURL = "file:///Users/houra/Library/Developer/CoreSimulator/Devices/599E21F7-4A9F-4B60-8864-1CE1485B4360/data/Containers/Bundle/Application/F13B31FA-B6FE-4372-A3FF-AFC5B5E2F1F9/Clean.app/app.js"; [ERROR] : } {noformat}
| 5 |
3,162 |
TIMOB-25788
|
02/20/2018 00:51:40
|
Windows: Fix windowsBroken HttpClient tests
|
In {{ti.network.httpclient.tests}} on our unit tests, we've been skipping some of unit tests for Windows by marking {{windowsBroken}}. Need to make sure what's causing the actual issue and create new ticket when needed. This ticket is to keep track on it.
| 8 |
3,163 |
TIMOB-25789
|
02/20/2018 07:30:45
|
Windows: HttpClient.onreadystatechange should be called right after ondatastream/onsendstream
|
HttpClient {{callbackTestForGETMethod}} and {{callbackTestForPOSTMethod}} [unit test|https://github.com/appcelerator/titanium-mobile-mocha-suite/blob/master/Resources/ti.network.httpclient.test.js#L377] shows {{onreadystatechange}} should be called right after {{ondatastream/onsendstream}} event to keep parity with iOS/Android. {code:javascript} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); win.addEventListener('open', function () { var xhr = Ti.Network.createHTTPClient(), attempts = 3, sendStreamFinished = false, buffer; xhr.setTimeout(3e4); xhr.onreadystatechange = function () { Ti.API.info('onreadystatechange sendStreamFinished: ' + sendStreamFinished + ' DONE? ' + (this.readyState === this.DONE)); if (this.readyState === this.DONE && sendStreamFinished) { Ti.API.info('finish'); } }; xhr.onsendstream = function (e) { Ti.API.info('onsendstream'); Ti.API.info(e.progress + ' be.ok'); if (e.progress >= 0.99) { sendStreamFinished = true; } }; xhr.onerror = function (e) { if (attempts-- > 0) { Ti.API.warn('failed, attempting to retry request...'); xhr.send(); } else { Ti.API.warn(JSON.stringify(e, null, 2)); Ti.API.warn(e.error || this.responseText); } }; buffer = Ti.createBuffer({ length: 1024 * 10 }).toBlob(); xhr.open('POST', 'http://www.httpbin.org/post'); xhr.send({ data: buffer, username: 'fgsandford1000', password: 'sanford1000', message: 'check me out' }); }); win.open(); {code} Expected: {{finish}} should be printed.
| 5 |
3,164 |
TIMOB-25845
|
02/20/2018 10:18:43
|
Android: Non-production app builds with modules crash on startup if TLS 1.1 or higher is required for Internet access
|
Related to https://jira.appcelerator.org/browse/TIMOB-20579 When being connected to a hotspot network, without being logged in into the hotspot (and without having internet connection), I'm not able to open the app, I get following error log: It's just a normal Appcelerator Titanium app, containing the ti.brightness module. That's might not be the issue, as the error stack shows that it goes wrong when performing network calls. Android 7 on Samsung Galaxy S8 {code:xml} [WARN] TiVerify: (Timer-0) [4934,4998] Verifying module licenses... [INFO] I/System.out: Thread-360(ApacheHTTPLog):Reading from variable values from setDefaultValuesToVariables [INFO] I/System.out: Thread-360(ApacheHTTPLog):isSBSettingEnabled false [INFO] I/System.out: Thread-360(ApacheHTTPLog):isShipBuild true [INFO] I/System.out: Thread-360(ApacheHTTPLog):getDebugLevel 0x4f4c [INFO] I/System.out: Thread-360(ApacheHTTPLog):Smart Bonding Setting is false [INFO] I/System.out: Thread-360(ApacheHTTPLog):SmartBonding Setting is false, SHIP_BUILD is true, log to file is false, DBG is false, DEBUG_LEVEL (1-LOW, 2-MID, 3-HIGH) is 1 [INFO] I/System.out: Timer-0 calls detatch() [INFO] I/InputDispatcher( 3740): Delivering touch to : action: 0x1, toolType: 1 [ERROR] TiApplication: (Timer-0) [106,5104] Sending event: exception on thread: Timer-0 msg:java.lang.IncompatibleClassChangeError: Class 'ti.modules.titanium.network.NonValidatingSSLSocketFactory' does not implement interface 'org.apache.http.conn.scheme.SocketFactory' in call to 'java.net.Socket org.apache.http.conn.scheme.SocketFactory.createSocket()' (declaration of 'org.apache.http.impl.conn.DefaultClientConnectionOperator' appears in /system/framework/org.apache.http.legacy.boot.jar); Titanium 6.3.0,2017/10/31 18:13,undefined [ERROR] TiApplication: java.lang.IncompatibleClassChangeError: Class 'ti.modules.titanium.network.NonValidatingSSLSocketFactory' does not implement interface 'org.apache.http.conn.scheme.SocketFactory' in call to 'java.net.Socket org.apache.http.conn.scheme.SocketFactory.createSocket()' (declaration of 'org.apache.http.impl.conn.DefaultClientConnectionOperator' appears in /system/framework/org.apache.http.legacy.boot.jar) [ERROR] TiApplication: at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:189) [ERROR] TiApplication: at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:172) [ERROR] TiApplication: at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:130) [ERROR] TiApplication: at org.apache.http.impl.client.DefaultRequestDirector.executeOriginal(DefaultRequestDirector.java:1334) [ERROR] TiApplication: at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:700) [ERROR] TiApplication: at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:560) [ERROR] TiApplication: at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:514) [ERROR] TiApplication: at org.appcelerator.titanium.TiVerify.run(Unknown Source) [ERROR] TiApplication: at java.util.TimerThread.mainLoop(Timer.java:555) [ERROR] TiApplication: at java.util.TimerThread.run(Timer.java:505) [INFO] I/System.out: (HTTPLog)-Static: isSBSettingEnabled false [INFO] I/System.out: (HTTPLog)-Static: isSBSettingEnabled false [ERROR] TiHTTPClient: (TiHttpClient-1) [70,5174] HTTP Error (java.net.NoRouteToHostException): No route to host [ERROR] TiHTTPClient: java.net.NoRouteToHostException: No route to host [ERROR] TiHTTPClient: at java.net.PlainSocketImpl.socketConnect(Native Method) [ERROR] TiHTTPClient: at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:334) [ERROR] TiHTTPClient: at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:196) [ERROR] TiHTTPClient: at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) [ERROR] TiHTTPClient: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:356) [ERROR] TiHTTPClient: at java.net.Socket.connect(Socket.java:586) [ERROR] TiHTTPClient: at com.android.okhttp.internal.Platform.connectSocket(Platform.java:113) [ERROR] TiHTTPClient: at com.android.okhttp.Connection.connectSocket(Connection.java:1455) [ERROR] TiHTTPClient: at com.android.okhttp.Connection.connect(Connection.java:1413) [ERROR] TiHTTPClient: at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:1700) [ERROR] TiHTTPClient: at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:133) [ERROR] TiHTTPClient: at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:466) [ERROR] TiHTTPClient: at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:371) [ERROR] TiHTTPClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:503) [ERROR] TiHTTPClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:130) [ERROR] TiHTTPClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:261) [ERROR] TiHTTPClient: at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:218) [ERROR] TiHTTPClient: at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java) [ERROR] TiHTTPClient: at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1195) [ERROR] TiHTTPClient: at java.lang.Thread.run(Thread.java:762) {code}
| 13 |
3,165 |
TIMOB-25791
|
02/20/2018 19:43:12
|
Android: getTime issue with 7.0.2 sdk in android
|
Hi, There is an issue in the SDK 7.0.2 with the getTime() function in Android. Issue:- new Date("2018-02-20T11:30:00").getTime() has discrepancy with the old sdk's ( same function is returning different values(milliseconds) in old sdk and new sdk. 1519104600000 - new sdk (7.0.2.GA) 1519126200000 - old sdk (6.3.0.GA) steps to recreate:- 1)calculate the milliseconds using new Date("2018-02-20T11:30:00").getTime() in 7.0.2 and 6.3.0. 2)copy that in check the local time and UTC in http://currentmillis.com. 3) you should see the difference in two SDK's. Test Code: {code} var win = Ti.UI.createWindow({ backgroundColor : '#fff' }); var sf=new Date("2018-02-20T11:30:00").getTime(); Ti.API.info(sf); alert(sf); win.open(); {code}
| 2 |
3,166 |
TIMOB-25792
|
02/21/2018 02:33:59
|
Android: Scrolling horizontal ScrollView within a vertical ScrollView should disable vertical scrolling
|
*Summary:* When scrolling a "horizontal" ScrollView within a "vertical" ScrollView, it will scroll horizontally until you scroll too far up/down, then horizontal scrolling will be canceled by the parent "vertical" ScrollView and it'll only scroll vertically from then on. This is a behavior change that was introduced in Titanium 6.3.0. The old behavior would block the parent ScrollView from scrolling vertically while scrolling the child horizontal ScrollView. This behavior should be restored. _(This is also the iOS behavior.)_ *Steps to Reproduce:* # Build/run the below code for Android using Titanium 6.3.0 or higher. # Start dragging one of the horizontal ScrollViews. (It's the box containing labels.) # As you drag it horizontally, drag up or down. # Notice the parent ScrollView will scroll vertically, but you can no longer scroll the child ScrollView horizontally anymore. {code:javascript} var window = Ti.UI.createWindow({ fullscreen: true }); var verticalScrollView = Ti.UI.createScrollView( { layout: "vertical", scrollType: "vertical", showVerticalScrollIndicator: true, showHorizontalScrollIndicator: false, backgroundColor: "darkgray", width: Ti.UI.FILL, height: Ti.UI.FILL, }); for (var scrollViewIndex = 1; scrollViewIndex <= 20; scrollViewIndex++) { verticalScrollView.add(Ti.UI.createLabel( { text: "Horizontal Scroll View " + scrollViewIndex.toString(), color: "white", top: "10dp", })); var horizontalScrollView = Ti.UI.createScrollView( { layout: "horizontal", scrollType: "horizontal", showVerticalScrollIndicator: false, showHorizontalScrollIndicator: true, backgroundColor: "darkgray", borderWidth: "1dp", borderColor: "black", width: "100%", height: "100dp", }); for (var labelIndex = 1; labelIndex <= 20; labelIndex++) { horizontalScrollView.add(Ti.UI.createLabel( { text: " Label " + labelIndex.toString() + " ", color: "white", backgroundColor: "gray", top: "5dp", left: "5dp", })); } verticalScrollView.add(horizontalScrollView); } window.add(verticalScrollView); window.open(); {code} *Result:* Once you drag up or down while scrolling horizontally, the horizontal ScrollView's scrolling is canceled and only the parent vertical ScrollView can be scrolled. *Expected Result:* Parent vertical ScrollView should not be scrollable while scrolling a child horizontal ScrollView. This was the old Android behavior. It is also the iOS behavior. *Cause:* ScrollViews call the parent view's {{requestDisallowInterceptTouchEvent()}} method when scrolling has started. However, Google's {{SwipeRefreshLayout.requestDisallowInterceptTouchEvent()}} method ignores the request when made by a child view (in this case a {{HorizontalScrollView}}) that does not support nested scrolling. Since it's ignored, the parent ScrollView ends up intercepting and stealing the nested {{HorizontalScrollView}} touch events. [SwipeRefreshLayout.java#L735|https://github.com/aosp-mirror/platform_frameworks_support/blob/master/core-ui/src/main/java/android/support/v4/widget/SwipeRefreshLayout.java#L735] *Work-Around:* You can restore the old behavior by listening to the horizontal ScrollView's "dragstart" and "dragend" events. In the "dragstart" event handler, disable the parent vertical ScrollView. In the "dragend" event handler, re-enable the parent vertical ScrollView. {code:javascript} horizontalScrollView.addEventListener("dragstart", function(e) { verticalScrollView.scrollingEnabled = false; }); horizontalScrollView.addEventListener("dragend", function(e) { verticalScrollView.scrollingEnabled = true; }); {code}
| 3 |
3,167 |
TIMOB-25793
|
02/21/2018 05:38:07
|
iOS: No callback when not granting push notification permission (Apple bug)
|
Hi, I am trying to enable push notifications on IOS device and when I grab token I am being asked to provide push notification permission. If I choose not to give it, error callback is not thrown. I copied code directly from Push Notifications Reference Guide: http://docs.appcelerator.com/platform/latest/#!/guide/Subscribing_to_push_notifications Here is the code: --------------------------------------------------------------------------------------------------------------------------------------------------- {code:java} var deviceToken = null; // Check if the device is running iOS 8 or later if (Ti.Platform.name == "iPhone OS" && parseInt(Ti.Platform.version.split(".")[0]) >= 8) { // Wait for user settings to be registered before registering for push notifications Ti.App.iOS.addEventListener('usernotificationsettings', function registerForPush() { // Remove event listener once registered for push notifications Ti.App.iOS.removeEventListener('usernotificationsettings', registerForPush); Ti.Network.registerForPushNotifications({ success: deviceTokenSuccess, error: deviceTokenError, callback: receivePush }); }); // Register notification types to use Ti.App.iOS.registerUserNotificationSettings({ types: [ Ti.App.iOS.USER_NOTIFICATION_TYPE_ALERT, Ti.App.iOS.USER_NOTIFICATION_TYPE_SOUND, Ti.App.iOS.USER_NOTIFICATION_TYPE_BADGE ] }); } // For iOS 7 and earlier else { Ti.Network.registerForPushNotifications({ // Specifies which notifications to receive types: [ Ti.Network.NOTIFICATION_TYPE_BADGE, Ti.Network.NOTIFICATION_TYPE_ALERT, Ti.Network.NOTIFICATION_TYPE_SOUND ], success: deviceTokenSuccess, error: deviceTokenError, callback: receivePush }); } // Process incoming push notifications function receivePush(e) { alert('Received push: ' + JSON.stringify(e)); } // Save the device token for subsequent API calls function deviceTokenSuccess(e) { deviceToken = e.deviceToken; } function deviceTokenError(e) { alert('Failed to register for push notifications! ' + e.error); //this is the function that never gets thrown. } {code} --------------------------------------------------------------------------------------------------------------------------------------------------- Note that deviceTokenError never gets thrown once permission has been granted/revoked. *Expected Result:* error callback should be fired when not granting push notification permission. *Actual Result:* error callback never be fired. Thanks
| 5 |
3,168 |
TIMOB-25794
|
02/21/2018 18:15:36
|
Windows: Adding a hyperloop created UI element to a View crashes the app
|
h5.Description *This is a regression from 7.0.2.GA* When adding a UI element that is created using hyperloop to a Ti.UI.View the app will crash with no logs {code} var win = Ti.UI.createWindow(); var Canvas = require('Windows.UI.Xaml.Controls.Canvas'); var SolidColorBrush = require('Windows.UI.Xaml.Media.SolidColorBrush'); var Colors = require('Windows.UI.Colors'); var view = Ti.UI.createView({ backgroundColor: 'fuchsia' }); var box = new Canvas(); box.Background = new SolidColorBrush(Colors.Red); box.Width = 50; box.Height = 50; win.addEventListener('click', function() { view.add(box); }); win.add(view); win.open(); {code} h5.Steps to reproduce 1. Add the above code to an existing classic project with hyperloop setup 2. Build for any Windows target 3. Click the view when the app launches h5.Actual App crashes h5.Expected App should not crash
| 5 |
3,169 |
TIMOB-25795
|
02/21/2018 20:46:43
|
Hyperloop: Android - Expose all missing Android R resource types to Ti.Android.R
|
We support a couple of Android R resources types in Titanium [already|http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Android.R]. With having Hyperloop these days, we are able to perform powerful Android interactions like the BottomNavigationView, RecyclerView API's. It's convenient to load the views via XML and configure them via colors and strings inside the platform/android/res/ directory. For a concrete use-case, we need to load a {{menu}} resource for the bottom navigation view, which would be {{Ti.Android.R.menu.xxxx}}, but the {{menu}} namespace is not exposed. Therefore, this ticket proposes a tiny change that basically adds all (current) Android R resources types to our resource lookup map, so developers can use the official SDK API's instead of hacking it together like in the example. Missing properties: - animator - bool - fraction - interpolator - menu - mipmap - plurals - raw - transition - xml
| 8 |
3,170 |
TIMOB-25810
|
02/22/2018 10:17:47
|
Android: ActionBar height won't resize on screen rotation
|
*Summary:* The ActionBar on Android won't resize when the device rotates. [As seen in Material Design guidelines|https://material.io/guidelines/layout/structure.html#structure-app-bar], when a mobile is on landscape, ActionBar's height is 48dp, while on portrait it's 56dp. Attached is a video demonstrating the issue. *Steps to reproduce:* # Position an Android device in portrait. # Build and run a default Classic app project on that Android device. # Note the height of the top titlebar. # Rotate the device to landscape. # Notice the titlebar height does not shrink. _(This is the bug.)_ # Keep holding the device at landscape and back out of the app. # Launch the app in landscape form. # Notice that the titlebar height is smaller upon launch. # Rotate the device to portrait. # Notice that the titlebar height has not increased. _(This is the bug.)_
| 13 |
3,171 |
TIMOB-25796
|
02/22/2018 14:39:01
|
Windows: Adding a hyperloop created UI element to a View multiple times throws an error
|
h5.Description Adding a HL created view to a Titanium view multiple times throws the following error {code} [ERROR] : ----- Titanium Javascript Runtime Error ----- [ERROR] : Message: Uncaught Error: Runtime Error: add: unknown exception {code} {code} var win = Ti.UI.createWindow(); var Canvas = require('Windows.UI.Xaml.Controls.Canvas'); var view = Ti.UI.createView({ backgroundColor: 'white' }); var SolidColorBrush = require('Windows.UI.Xaml.Media.SolidColorBrush'); var Colors = require('Windows.UI.Colors'); var box = new Canvas(); box.Background = new SolidColorBrush(Colors.Red); box.Width = 50; box.Height = 50; win.addEventListener('click', function () { view.add(box); }); win.add(view); win.open(); {code} h5.Steps to reproduce 1. Add the above code to an existing classic project with hyperloop setup 2. Build for any Windows target 3. Click the view when the app launches 4. Click the view again a second time h5.Actual Error shown above is thrown on the second click h5.Expected No error should be thrown
| 8 |
3,172 |
TIMOB-25872
|
02/22/2018 15:49:05
|
iOS: Log-server-port Build Error Masks Real Error
|
*Description* When building an iOS app and there is an issue connecting to the iOS log-server, it always output "Another process is currently bound to port xxxxx" even if there is another server connection issue such as the port not existing. *Workaround* Figure out the real issue by logging the actual error within the sdk itself (at ~/Library/Application Support/Titanium/mobilesdk/osx/7.0.2.GA/iphone/cli/commands/_build.js in the determineLogServerPort function). *Steps to Reproduce* 1. Create a different type of error with the server. For example, my /etc/hosts file did not have an entry for 127.0.0.1 localhost, so the actual node error was 'ENOTFOUND'. 2. Create a new titanium app with `appc ti new`. 3. Build with appc ti build -p ios *Actual Result* Build errors out with following text: {code} [ERROR] Another process is currently bound to port 27973 [ERROR] Set a unique <log-server-port> between 1024 and 65535 in the <ios> section of the tiapp.xml {code} *Expected Result* More detailed error. I.E. Something like: {code}Failed to create/connect to log server port with error "[error given by node net package]".{code} Followed by suggested solution. For example if the node error was EADDRINUSE, then you could still use the existing error message. But if it's another error, log accordingly so the user has the best information for solving the issue.
| 8 |
3,173 |
TIMOB-25801
|
02/22/2018 19:25:15
|
iOS: SDK 7.0.2.GA - VideoPlayer playback issues
|
on iOS titanium SDK 7.0.2.GA once the playback is done the media player fires the complete event (which is correct) and then the stop event (which shouldn't) also the function stop doesn't stop the playback but rather pauses it. and the durationavailable event is fired twice the second time an audio/video is played. {code:javascript} // Some comments here var dataStructure = [{ title : "Play video", action : playVideo }, { title : "Pause video", action : pauseVideo }, { title : "Stop video", action : stopVideo }, { title : "Change video source (local)", action : changeLocalVideoSource }, { title : "Change video source (remote)", action : changeRemoteImageSource }, { title : "Change background color", action : changeBackgroundColor }, { title : "Set volume to 50%", action : decreaseVolume }, { title : "Get playable duration", action : getPlayableDuration }, { title : "Get playback state", action : getPlaybackState }, { title : "Set full width", action : setSizeFullWidth }, { title : "Set width + height to 300 (animated)", action : setSize }, { title : "Is playing?", action : getPlaying }, { title: "Take screenshot at 5s", action: takeScreenshot }, { title: "Take multiple screenshots", action: captureSeriesOfImages }, { title: "Set initial playback time", action: setInitialPlaybackTime }, { title: "Is airPlay allowed?", action: getAllowsAirPlay }, { title: "repeatMode ?", action: getRepeatMode }]; var counter = 0; /* -- UI -- */ var isiOS = (Ti.Platform.osname == "ipad" || Ti.Platform.osname == "iphone"); var win = Titanium.UI.createWindow({ title : 'Video Player Demo', backgroundColor : '#fff', layout : 'vertical' }); var nav = isiOS ? Ti.UI.iOS.createNavigationWindow({ window : win }) : null; var header = Ti.UI.createView({ height : 350, backgroundColor : "#eee" }); var content = Ti.UI.createScrollView({ layout : "horizontal", scrollType : "vertical", contentWidth : Ti.Platform.displayCaps.platformWidth, contentHeight : 1000 }); var videoPlayer = Titanium.Media.createVideoPlayer({ autoplay : true, url : 'http://techslides.com/demos/sample-videos/small.mp4',//'movie.mp4', initialPlaybackTime: 1000, showsControls:true, pictureInPictureEnabled : true, // Only supported on iOS9 & iPad Air or later! scalingMode : Titanium.Media.VIDEO_SCALING_MODE_RESIZE_ASPECT, repeatMode : Titanium.Media.VIDEO_REPEAT_MODE_NONE }); for (var i = 0; i < dataStructure.length; i++) { var btn = Ti.UI.createButton({ top : '3.5%', left : '7%', height : 60, width : '40%', tintColor : '#b50d00', backgroundColor : '#e0e0e0', title : dataStructure[i].title }); btn.addEventListener("click", dataStructure[i].action); content.add(btn); } header.add(videoPlayer); win.add(header); win.add(content); if (nav) { nav.open(); } else { win.open(); } /* -- Events -- */ videoPlayer.addEventListener('complete', function(e) { Ti.API.info('complete ' + JSON.stringify(e)); }); videoPlayer.addEventListener('durationavailable', function(e) { Ti.API.info('durationavailable ' + JSON.stringify(e)); }); videoPlayer.addEventListener('error', function(e) { Ti.API.info('error ' + JSON.stringify(e)); }); videoPlayer.addEventListener('load', function(e) { Ti.API.info('load ' + JSON.stringify(e)); }); videoPlayer.addEventListener('playbackstate', function(e) { Ti.API.info('playbackstate ' + JSON.stringify(e)); }); videoPlayer.addEventListener('playing', function(e) { Ti.API.info('playing ' + JSON.stringify(e)); }); videoPlayer.addEventListener('preload', function(e) { Ti.API.info('preload ' + JSON.stringify(e)); }); {code}
| 8 |
3,174 |
TIMOB-25797
|
02/22/2018 21:47:33
|
Android: Remove unnecessary Google Play Services logs
|
h5.Steps to reproduce: 1. Use the code below in your app.js: {code} var win = Ti.UI.createWindow(); var btn = Ti.UI.createButton({ title: 'Click Me' }); btn.addEventListener('click', function(e) { console.log('Ti.Geolocation.hasLocationPermissions() ' + Ti.Geolocation.hasLocationPermissions()); console.log('Ti.Geolocation.locationServicesEnabled ' + Ti.Geolocation.locationServicesEnabled); alert('locationServicesEnabled = ' + Ti.Geolocation.locationServicesEnabled); if (Ti.Geolocation.hasLocationPermissions()) { getCurrentPosition(); } else { Ti.Geolocation.requestLocationPermissions(null, getCurrentPosition); } }); function getCurrentPosition() { Ti.Geolocation.getCurrentPosition(function(e) { console.log('Ti.Geolocation.getCurrentPosition() ' + JSON.stringify(e)); }); } win.add(btn); win.open(); {code} 2. Make sure you do not have ti.playservices module in your app. 3. Build the app on Android device/emulator. (I saw the logs on Nexus 6P Android 8.0 & Android 4.4.4 emulator). 4. After app launch tap click me button. 5. Allow location permissions. 6. Check the logs. h5.Actual results: 1. These info logs are seen : https://gist.github.com/lokeshchdhry/bc231d92727852c4a74f8f37e3465d53 h5. Expected results: 1. The info logs should not be logged.
| 2 |
3,175 |
TIMOB-25798
|
02/22/2018 21:55:54
|
Android: Unnecessary info logs in console when trying to use geolocation methods with no Ti.playservices
|
h5.Steps to reproduce: 1. Use the code below in your app.js: {code} var win = Ti.UI.createWindow(); var btn = Ti.UI.createButton({ title: 'Click Me' }); btn.addEventListener('click', function(e) { console.log('Ti.Geolocation.hasLocationPermissions() ' + Ti.Geolocation.hasLocationPermissions()); console.log('Ti.Geolocation.locationServicesEnabled ' + Ti.Geolocation.locationServicesEnabled); alert('locationServicesEnabled = ' + Ti.Geolocation.locationServicesEnabled); if (Ti.Geolocation.hasLocationPermissions()) { getCurrentPosition(); } else { Ti.Geolocation.requestLocationPermissions(null, getCurrentPosition); } }); function getCurrentPosition() { Ti.Geolocation.getCurrentPosition(function(e) { console.log('Ti.Geolocation.getCurrentPosition() ' + JSON.stringify(e)); }); } win.add(btn); win.open(); {code} 2. Make sure you do not have ti.playservices module in your app. 3. Build the app on Android device/emulator. (I saw the logs on Nexus 6P Android 8.0 & Android 4.4.4 emulator). 4. After app launch tap click me button. 5. Allow location permissions. 6. Check the logs. h5.Actual results: 1. These info logs are seen : https://gist.github.com/lokeshchdhry/bc231d92727852c4a74f8f37e3465d53 h5. Expected results: 1. The info logs should not be logged.
| 1 |
3,176 |
TIMOB-25799
|
02/23/2018 01:41:34
|
Android: Cannot build titanium project with JDK 1.9
|
When the system has only jdk 9 installed then the titanium project fails to build for android. Steps to Reproduce: 1. Create a default alloy project 2. build the project for android from command line "appc run -p android" Actual Result: The project does not build with following error: {code} [ERROR] Failed to run dexer: [ERROR] [ERROR] Error: Could not create the Java Virtual Machine. [ERROR] Error: A fatal exception has occurred. Program will exit. {code} Running dexer manually shows the error is actually the following, in the dexer args [here|https://github.com/appcelerator/titanium_mobile/blob/d3cadc1bcecec20650fae421355e4edffa4876dd/android/cli/commands/_build.js#L4225] we need to swap {{'-Djava.ext.dirs=' + this.androidInfo.sdk.platformTools.path,}} to {{'-classpath', this.androidInfo.sdk.platformTools.path}}, I don't believe we need to handle this on a per-version basis as Java 1.8 handles the {{-classpath}} arg just fine {code} -Djava.ext.dirs=/Users/eharris/Library/Android/sdk/platform-tools is not supported. Use -classpath instead. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. {code}
| 3 |
3,177 |
TIMOB-25804
|
02/24/2018 09:04:39
|
iOS: Bar Image is not showing properly in iPhone X
|
Issue: For iPhone X, bar image is not showing properly as like iPhone 8 and other. Always crop top portion. Steps To Reproduce: 1. Create a new Alloy App. 2. Use the following test code and image then run it on iOS X and iOS 8 for checking the difference. {code:title=index.xml} <Alloy> <TabGroup id="tabGroup"> <Tab id="tab" title="My Tab" icon="myicon.png"> <Window barImage = "/images/relevent-dark-header.png"> </Window> </Tab> </TabGroup> </Alloy> {code} Thanks!
| 3 |
3,178 |
TIMOB-25805
|
02/24/2018 12:02:27
|
Android: appc info show a leading 0 before NDK Path
|
Current output of {{appc info android}} {noformat} Android NDK 0NDK Path = /home/miga/tools/android-ndk NDK Version = 12.1.2977051 {noformat} with the fix: {noformat} Android NDK NDK Path = /home/miga/tools/android-ndk NDK Version = 12.1.2977051 {noformat}
| 1 |
3,179 |
TIMOB-25807
|
02/24/2018 19:05:01
|
Hyperloop - ES6: Cannot find scoped "this" methods anymore
|
When using ES6 in Hyperloop methods, e.g. {code:js} var ButtonDelegate = Hyperloop.defineClass('ButtonDelegate', 'NSObject'); ButtonDelegate.addMethod({ selector: 'buttonPressed:', instance: true, arguments: ['UIButton'], callback: (sender) => { if (this.buttonPressed) { // ^-- Here is the issue - it cannot find the declared method this.buttonPressed(sender); } } }); var delegate = new ButtonDelegate(); // Not found when being used in "Hyperloop.addMethod" delegate.buttonPressed = function(sender) { alert('Button pressed!'); }; {code} the {{this.buttonPressed}} method cannot be found, although declared. We use this pattern many times, to assign methods to instances afterwards. If there is a better approach, we should replace the usages in the hyperloop-examples sample app. *EDIT*: It only seems to be an issue if the delegate is in the same file as its usage. It works fine for other delegates / sub classes like [here|https://github.com/appcelerator/hyperloop-examples/blob/master/app/lib/ios/subclasses/tableviewdatasourcedelegate.js#L9].
| 1 |
3,180 |
TIMOB-25809
|
02/25/2018 13:50:51
|
ES6: Logs do not work anymore
|
While migrating my [canteen app|https://github.com/hansemannn/studentenfutter-app] to ES6, I noticed that logs (e.g. {{Ti.API.warn}}) do not work anymore. The only logs appearing are: {code} [TRACE] [ioslib] App launched [TRACE] [ioslib] Trying to connect to log server port 28416... [TRACE] [ioslib] Connected to log server port 28416 -- Start simulator log ------------------------------------------------------- [TRACE] updating tiapp metadata with Appcelerator Platform... [TRACE] Uploaded tiapp metadata with Appcelerator Platform! {code} To reproduce: {code:js} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var btn = Ti.UI.createButton({ title: 'Trigger' }); btn.addEventListener('click', function() { Ti.API.error('Hello?') }); win.add(btn); win.open(); {code}
| 0 |
3,181 |
TIMOB-25819
|
02/27/2018 15:32:07
|
Android: ScrollView starts at the wrong location if it contains a ListView
|
When you have a ListView within a ScrollView on Android, sometimes the scroll view starts around the middle of the screen. e.g. {code:xml} <Alloy> <Window class="container"> <ScrollView backgroundColor="blue" width="Ti.UI.FILL" height="Ti.UI.FILL" layout="vertical"> <View backgroundColor="red" width="Ti.UI.FILL" height="471"> <Label top="0">Start of the screen</Label> </View> <ListView backgroundColor="yellow" height="347"/> </ScrollView> </Window> </Alloy> {code} However changing the ListView into a normal view seems to fix the issue. In addition, there are times where the above window opens up fine. But most of the time it opens up incorrectly. Note that this does not happen on iOS. Tested on: - Samsung S6 (real device) and - Nexus 5 emulator (API 19) with SDK: Titanium 7.0.2 GA
| 8 |
3,182 |
TIMOB-25825
|
03/01/2018 11:00:15
|
Android: JNIUtil error message on app launch
|
h5.Description When an app launches I'm seeing the below error logged to the console, it doesn't look to cause any issues to the app but it might give people a scare when upgrading to 7.1.0. From what I can tell it occurs on any app {code} [ERROR] JNIUtil: Couldn't find Java field ID: proxySupport Lorg/appcelerator/kroll/KrollProxySupport; [WARN] W/System.err: java.lang.NoSuchFieldError: no "Lorg/appcelerator/kroll/KrollProxySupport;" field "proxySupport" in class "Lorg/appcelerator/kroll/KrollObject;" or its superclasses [WARN] W/System.err: at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeInit(Native Method) [WARN] W/System.err: at org.appcelerator.kroll.runtime.v8.V8Runtime.initRuntime(V8Runtime.java:95) [WARN] W/System.err: at org.appcelerator.kroll.KrollRuntime.doInit(KrollRuntime.java:207) [WARN] W/System.err: at org.appcelerator.kroll.KrollRuntime.syncInit(KrollRuntime.java:363) [WARN] W/System.err: at org.appcelerator.kroll.KrollRuntime.incrementActivityRefCount(KrollRuntime.java:386) [WARN] W/System.err: at org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:614) [WARN] W/System.err: at org.appcelerator.titanium.TiLaunchActivity.onCreate(TiLaunchActivity.java:175) [WARN] W/System.err: at org.appcelerator.titanium.TiRootActivity.onCreate(TiRootActivity.java:160) [WARN] W/System.err: at android.app.Activity.performCreate(Activity.java:6760) [WARN] W/System.err: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1134) [WARN] W/System.err: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2686) [WARN] W/System.err: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2819) [WARN] W/System.err: at android.app.ActivityThread.-wrap12(ActivityThread.java) [WARN] W/System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1532) [WARN] W/System.err: at android.os.Handler.dispatchMessage(Handler.java:102) [WARN] W/System.err: at android.os.Looper.loop(Looper.java:154) [WARN] W/System.err: at android.app.ActivityThread.main(ActivityThread.java:6321) [WARN] W/System.err: at java.lang.reflect.Method.invoke(Native Method) [WARN] W/System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886) [WARN] W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776) [WARN] TiApplication: (main) [78,78] Registering module with name already in use. {code} h5. Steps to reproduce 1. Create a default app using {{appc new}}/{{ti create}} 2. Build the app for Android h5.Actual On app launch the error/warning log above is shown h5.Expected No error/warning log
| 3 |
3,183 |
TIMOB-25827
|
03/01/2018 16:53:09
|
Windows: Error thrown when building to emulator with forceUnInstall flag for first time
|
h5.Description When building an app for wp-emulator with {{--forceUnInstall}} and the emulator is in a clean state (i.e. no app already installed), then the build will fail because it's trying to uninstall a non-existent app and then doesn't continue on with the install when the uninstall fails {code} [ERROR] A debug application is already installed, please remove existing debug application [ERROR] Error: A debug application is already installed, please remove existing debug application at ChildProcess.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\7.1.0.v20180228160738\node_modules\windowslib\lib\wptool.js:915:15) at emitTwo (events.js:126:13) at ChildProcess.emit (events.js:214:7) at maybeClose (internal/child_process.js:925:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) {code} h5.Steps to reproduce 1. Build an application for wp-emulator with the emulator closed (clean state) h5.Actual Build fails with above h5.Expected Build should not fail
| 5 |
3,184 |
TIMOB-25829
|
03/01/2018 21:56:45
|
Hyperloop: iOS - CocoaPods 1.4.0 breaks metabase generation
|
There are [reports|https://github.com/appcelerator/hyperloop-examples/issues/75] that Hyperloop does not work with CocoaPods 1.4.0. We should investigate it and add support for the new version. [CocoaPods 1.4.0 Change Log|http://blog.cocoapods.org/CocoaPods-1.4.0/]
| 5 |
3,185 |
TIMOB-25831
|
03/02/2018 02:31:59
|
Windows Hyperloop: Style CalendarDatePicker Height not working
|
We are using a Windows.UI.Xaml.Controls.CalendarDatePicker (https://docs.microsoft.com/en-us/uwp/api/Windows.UI.Xaml.Controls.CalendarDatePicker) and we are trying to add some styling. We are able to set the width doing something like this: {code} var CalendarDatePicker = require('Windows.UI.Xaml.Controls.CalendarDatePicker'); var calendarField = new CalendarDatePicker(); calendarField.Width = 272; {code} BUT when we try to set the height like this, it's not working: {code} calendarField.Height = 42; {code} Any idea?
| 3 |
3,186 |
TIMOB-25835
|
03/02/2018 08:18:20
|
Android: Animation with border radius doesn't works properly
|
Affects to 7.0.2, 7.1.RC Animating a view with border radius doesn't works properly. On iOS it works fine. Check attached demo to see code example.
| 8 |
3,187 |
TIMOB-25832
|
03/02/2018 19:45:01
|
Android: Setting Ti.UI.SearchBar "hintText" property after creation causes a crash as of 7.0.0
|
*Summary:* Assigning a string to {{Ti.UI.SearchBar}} property "hintText" after it has been created will cause a crash on Android as of Titanium 7.0.0. *Steps to reproduce:* # Build and run the below code on Android. # Notice the app crashes on startup. {code:javascript} var window = Ti.UI.createWindow(); var searchBar = Ti.UI.createSearchBar({ barColor: "white", top: 0, width: Ti.UI.FILL, height: "50dp", }); window.add(searchBar); window.add(Ti.UI.createLabel({ text: "SearchBar Test" })); window.addEventListener("open", function(e) { searchBar.hintText = "Hint Text"; }); window.open(); {code} *Recommended Fix:* When Titanium's "TiUIText.java" class reads property {{PROPERTY_HINT_TYPE}} via {{TiConvert.toInt()}}, the code needs to set the default value to {{UIModule.HINT_TYPE_STATIC}} in the following places in the code. [TiUIText.java#L350|https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUIText.java#L350] [TiUIText.java#L924|https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUIText.java#L924] *Work-Around 1:* Set the "hintText" property when creating the {{SearchBar}}, but never afterwards. {code:javascript} var searchBar = Ti.UI.createSearchBar({ hintText: "Hint Text", }); {code} *Work-Around 2:* Set {{SearchBar}} property "hintType" to {{Ti.UI.HINT_TYPE_STATIC}}. This is an undocumented feature of {{SearchBar}} but it supports on Android since it internally uses {{Ti.UI.TextField}} within the {{SearchBar}}. {code:javascript} var window = Ti.UI.createWindow(); var searchBar = Ti.UI.createSearchBar({ hintType: Ti.UI.HINT_TYPE_STATIC, // <- This works-around the issue. }); window.add(searchBar); window.addEventListener("open", function() { searchBar.hintText = "Hint Text"; }); window.open(); {code}
| 3 |
3,188 |
TIMOB-25839
|
03/06/2018 03:44:25
|
TiAPI: Touch event coordinate units do not match between platforms
|
*Summary:* The (x,y) units provided by View event's "touchstart", "touchmove", "touchend", and "touchcancel" do not match between Android and iOS. Both platforms ignore the "ti.ui.defaultunit" property setting in "tiapp.xml". On Android, the touch coordinates are always in "px" (ie: pixels). On iOS, the touch coordinates are always in "dip" (aka: "dp"). *Steps to Reproduce:* # Build and run the below code on Android. # Drag your finger in the gray view. # Notice that the blue square does *not* correctly following your finger. # Build and run on iOS. # Drag your finger in the gray view. # Notice that the blue square *correctly* follows your finger. # Change "tiapp.xml" property "ti.ui.defaultunit" to "px". # Build and run on iOS. # Drag your finger in the gray view. # Notice that the blue square does *not* correctly following your finger. # Build and run on Android. # Drag your finger in the gray view. # Notice that the blue square *correctly* follows your finger. {code:javascript} function onTouch(event) { if (event.source == containerView) { touchView.center = { x: event.x, y: event.y }; } } var window = Ti.UI.createWindow( { layout: "vertical", fullscreen: true, theme: "Theme.AppCompat.NoTitleBar", }); window.add(Ti.UI.createLabel( { text: "Touch Drag Test", top: "20dp", })); var containerView = Ti.UI.createView( { touchEnabled: true, backgroundColor: "gray", top: "10dp", bottom: "20dp", width: "90%", }); var touchView = Ti.UI.createView( { touchEnabled: false, backgroundColor: "#008800", width: "100dp", height: "100dp", }); containerView.add(touchView); containerView.addEventListener("touchstart", onTouch); containerView.addEventListener("touchmove", onTouch); containerView.addEventListener("touchend", onTouch); containerView.addEventListener("touchcancel", onTouch); containerView.addEventListener("click", onTouch); containerView.addEventListener("dblclick", onTouch); containerView.addEventListener("doubletap", onTouch); window.add(containerView); window.open(); {code} *Work-Around:* The following will work-around this issue on both Android and iOS... {code:javascript} // Fetch the default unit property set in "tiapp.xml". var defaultUnit = Ti.App.Properties.getString("ti.ui.defaultunit", "dip"); if (defaultUnit === "dp") { defaultUnit = "dip"; } else if (defaultUnit === "system") { defaultUnit = (Ti.Platform.name === "android") ? "px" : "dip"; } // Do the below when a touch event has been received. function onTouch(event) { if (Ti.Platform.name === "android") { event.x = Ti.UI.convertUnits(event.x + "px", defaultUnit); event.y = Ti.UI.convertUnits(event.y + "px", defaultUnit); } else if ((Ti.Platform.name === "iOS") || (Ti.Platform.name === "iPhone OS")) { event.x = Ti.UI.convertUnits(event.x + "dip", defaultUnit); event.y = Ti.UI.convertUnits(event.y + "dip", defaultUnit); } touchView.center = { x: event.x, y: event.y }; } {code} *Ideal Solution:* Convert native touch coordinates to use "ti.ui.defaultunit" on both Android and iOS. This way views can easily be dragged since their "x", "y", and "center" properties already respect the "ti.ui.defaultunit" property. Note that this would be a breaking change.
| 8 |
3,189 |
TIMOB-25843
|
03/06/2018 11:57:19
|
Android: 7.1.0.RC - Setting data in Ti.UI.TableView does not work as before
|
*This is a regression from 7.0.2 to 7.1.0* I have tried 7.1.0.RC It used to work properly in the past ... {code:js} tableData[2] = tableViewSection3; tableView.data = tableData; {code} However, now it only works this: {code:js} tableView.updateSection(2, tableViewSection3); {code} {code:js} function createTableViewRow(e) { var rowView = Titanium.UI.createTableViewRow({ height: 120 }); rowView.add(Titanium.UI.createLabel({ text:'Text', })); return rowView; } var win = Ti.UI.createWindow(); var tableData = []; var tableView = Titanium.UI.createTableView({ separatorStyle:Ti.UI.TABLE_VIEW_SEPARATOR_STYLE_NONE }); var tableViewSection1 = Ti.UI.createTableViewSection(); var tableViewSection2 = Ti.UI.createTableViewSection(); var tableViewSection3 = Ti.UI.createTableViewSection(); tableData.push(tableViewSection1); tableData.push(tableViewSection2); tableData.push(tableViewSection3); tableView.data = tableData; win.add(tableView); var setData = function(e) { tableViewSection3.add(createTableViewRow()); tableViewSection3.add(createTableViewRow()); tableViewSection3.add(createTableViewRow()); //tableView.updateSection(2, tableViewSection3); tableData[2] = tableViewSection3; tableView.data = tableData; }; win.addEventListener('open', function(e) { setData(); }); win.open(); {code}
| 3 |
3,190 |
TIMOB-25842
|
03/06/2018 13:23:30
|
iOS: Cannot remove Ti.App.iOS.handleurl event-listener
|
In my app Titanium.App.iOS.addEventListener("handleurl", iosHandleUrl) can successfully register an event listener for the handle url event. Titanium.App.iOS.addEventListener("handleurl", iosHandleUrl) fails to remove the event listener resulting in the iosHandleUrl function being called multiple times in my app, when redirected back to the app from the browser. To reproduce this I've create a sample project with the following code in index.js {code} function iosHandleUrl(e) { console.log("redirected to app from URL"); } Ti.App.iOS.addEventListener("handleurl",iosHandleUrl); Ti.App.iOS.removeEventListener("handleurl",iosHandleUrl); Ti.App.iOS.addEventListener("handleurl",iosHandleUrl); Ti.App.iOS.removeEventListener("handleurl",iosHandleUrl); Ti.App.iOS.addEventListener("handleurl",iosHandleUrl); Ti.UI.createWindow({ backgroundColor: '#fff' }).open(); {code} And added the following to the plist in tiapp.xml. {code} <key>CFBundleURLTypes</key> <array> <dict> <key>CFBundleURLName</key> <string>com.ideagen.handleurltest</string> <key>CFBundleURLSchemes</key> <array> <string>handleurltest</string> </array> </dict> </array> {code} When I launch the app then open a browser and open handleurltest:// the expected behaviour is that "redirected to app from URL" should be logged once but the actual behaviour is that it's logged three times. The app was built against version 6.3.0.GA of the SDK.
| 5 |
3,191 |
TIMOB-25844
|
03/06/2018 22:21:55
|
Android: Update splash screen and icon
|
- Update Androids splash screen and icon to match the newer assets on iOS
| 5 |
3,192 |
TIMOB-25847
|
03/07/2018 17:28:02
|
iOS: Accessibility support for Dynamic Type
|
h5. Feature Request: Trying to use the accessibility options in iOS: Specifically the option to use larger text (Dynamic Type) but the changes are not applied to the app. Setting the font size to use "sp" as unit identifier for the font size which works on Android but not in iOS. font: { fontSize: '16sp' } In the fontSize documentation it says: "iOS ignores any unit specifier after the size value." when changing font size in accessibility options the alert dialogs have the font size change but nothing else. Can we implement Dynamic Type support so that font size is also changed within the app?
| 5 |
3,193 |
TIMOB-25850
|
03/08/2018 20:48:57
|
iOS: SearchBar doesn't show Bookmark button when set on creation in TableView
|
When showBookmark is set to true on creation of the searchbar and it is in a TableView, the bookmark button does not show. *Steps to reproduce issue* 1. Create a new project with the below code 2. Run the project *Expected Results* The searchbar has the bookmark button shown *Actual Results* The searchbar does not have the bookmark button shown *Notes* The bookmark button can be toggled to show it, but the toggle has to be tapped twice, since it thinks it is being shown. Also, if you just create a searchbar with showBookmark = true, then the button will show. Having the searchbar in the tableview does not show the bookmark button. *Code* Classic: {code:js} var win = Ti.UI.createWindow(); var searchBar = Titanium.UI.createSearchBar({ showBookmark: true }); var table = Ti.UI.createTableView({ data: [{ title: "Toggle Bookmark button" }], search: searchBar }); table.addEventListener('click', function(e){ searchBar.showBookmark = !searchBar.showBookmark; }); win.add(table); win.open(); {code} Alloy: index.xml {code:xml} <Alloy> <Window> <TableView> <SearchBar id="search" showBookmark="true"/> <TableViewRow onClick="toggle" title="Toggle bookmark button"/> </TableView> </Window> </Alloy> {code} index.js: {code:js} function toggle() { $.search.showBookmark = !$.search.showBookmark; } $.index.open(); {code}
| 0 |
3,194 |
TIMOB-25856
|
03/10/2018 16:24:29
|
TiAPI: Explain "run-on-main-thread" usage in tiapp.xml
|
Does somebody explain <property name="run-on-main-thread" type="bool">true</property> real mean ? That defult value is true but if I change value to false my app (especially android) working faster and not freeze. My Project is Alloy Mobile App and shoul I use true? If I use false what problems can arise?
| 2 |
3,195 |
TIMOB-25855
|
03/11/2018 12:45:54
|
Android: Add TextArea lines and maxLines support
|
Add the possibility to set the properties {{lines}} and {{maxLines}} at a TextField. * https://developer.android.com/reference/android/widget/TextView.html#attr_android:lines * https://developer.android.com/reference/android/widget/TextView.html#attr_android:maxLines The TextField will start with the {{lines}} amount of lines and will be extended to {{maxLines}} when pressing the Return key. {code:java} var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var tf = Ti.UI.createTextArea({ lines: 1, maxLines: 5, borderColor: "#000", borderWidth: 1, color: "#000", width: 200, top: 10, }) win.add(tf); var tf2 = Ti.UI.createTextArea({ lines: 2, maxLines: 2, borderColor: "#000", borderWidth: 1, color: "#000", width: 200, bottom: 10 }) win.add(tf); win.add(tf2); win.open(); {code}
| 3 |
3,196 |
TIMOB-25858
|
03/12/2018 18:50:26
|
iOS: Question on how to use "trackSignificantLocationChange" with background location update
|
Hello, On iOS, when using Ti.Geolocation.trackSignificantLocationChange and dealing with background updates with args.launchOptionsLocationKey we are seeing an issue where after a background update has come in while the app was closed and the next launch of the app hangs on the splash screen. The app must be manually closed in order to get farther than the splash screen. *Example Code:* Example app attached. *To reproduce:* 1. Install app on physical device and choose "Always" allow location permission. 2. Force close app with the test switcher 3. Move device until you get a background location update 4. Launch the app and observe the app hang on the launch screen
| 3 |
3,197 |
TIMOB-25859
|
03/12/2018 21:31:53
|
Android: Delay WebView Ti.App.fireEvent() to be fired after page load
|
*Summary:* The JavaScript within a WebView's HTML can call {{Ti.App.fireEvent()}} to communicate with the Titanium JavaScript side. It currently fires events immediately. The problem with this is if the listener immediately calls {{WebView.evalJS()}} to communicate back, it'll always timeout on Android if the web page hasn't finished loading yet and the Titanium runtime runs on the main UI thread (the default). This makes it less convenient to use. *Steps to Reproduce:* # Build and run attached [^WebViewInteropTest.js] on Android. # Observe the Android log. *Result:* An {{Timeout waiting to evaluate JS}} warning message appears in the log. *Expected Result:* The {{evalJS()}} calls should succeed. A countdown message "Reload in: X" should appear in the web page, starting from 5. When it counts down to zero, the page should reload. *Cause:* The {{WebView.evalJS()}} call will not work until the "load" event has been received from the WebView. This is because Titanium injects a "polling" script into the web page in the {{WebViewClient.onPageFinished()}} call... https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/webview/TiWebViewClient.java#L45 This polling script is responsible for fetching/evaluating the script added to the stack by the {{evalJS()}} call... https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/ui/src/java/ti/modules/titanium/ui/widget/webview/TiWebViewBinding.java#L151 Since {{evalJS()}} is getting called before the web page has finished loading, the {{evalJS()}} call will always fail with a timeout warning when the Titanium runtime runs on the main UI thread. *Recommended Solution:* Queue all {{Ti.App.fireEvent()}} calls made within the HTML and do not fire them until the page has finished loading. *Work-Around:* Use the new async version of {{WebView.evalJS()}} that was introduced into 7.5.0. It does not have this issue.
| 3 |
3,198 |
TIMOB-25860
|
03/12/2018 22:37:17
|
Update Android Support libraries to 27.1.1
|
- Update Android Support libraries to version {{27.1.1}} https://developer.android.com/topic/libraries/support-library/revisions.html#27-1-1
| 8 |
3,199 |
TIMOB-25861
|
03/13/2018 10:32:55
|
Liveview: Support transpiling user code
|
h5.Description We added babel transpilation in SDK 7.1.0 (TIMOB-24610), as liveview passes the code to the app we need to introduce a transpilation step there to ensure that the code works as expected. We can pull in node-titanium-sdk to implement this as the information we need to pass down to babel should be available in off the builder property
| 3 |
3,200 |
TIMOB-25864
|
03/13/2018 21:03:36
|
Android: Notifications should use default channel on Android 8 if not assigned
|
*Summary:* If an Android app targets API Level 26 or higher, notifications will fail to be posted to the status bar on Android 8.0 or higher unless they're assigned a notification channel as documented here... https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Android.NotificationChannel We should modify notifications to auto-assign them the default notification channel if a channel was not already assigned by the developer. This way, when we modify Titanium to auto-target API Level 26 in the future (see ticket: [TIMOB-25852]), notifications will still work. Avoids a breaking change. Note that if the app targets API Level 25 or lower, Android 8 will auto-assign the notification the default channel for us. *Test:* # Set up "tiapp.xml" to target API Level 26 as shown below. # Build and run the below code on an Android 8 device. # Tap on the "Send Notification" button. # Verify that the notification was posted to the status bar. {code:xml} <ti:app> <android xmlns:android="http://schemas.android.com/apk/res/android"> <manifest> <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="26"/> </manifest> </android> </ti:app> {code} {code:javascript} var notificationId = 0; var window = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title: "Send Notification" }); button.addEventListener("click", function(e) { var notification = Ti.Android.createNotification( { contentTitle: "Content Title", contentText: "Content Text", contentIntent: Ti.Android.createPendingIntent( { intent: Ti.Android.createIntent({}), }), }); notificationId++; Ti.Android.NotificationManager.notify(notificationId, notification); }); window.add(button); window.open(); {code} *Recommended Solution:* This should be implemented similar to the following "aps_sdk" library's PR here... https://github.com/appcelerator/aps_sdk/pull/307 *Note:* This is not an issue with our "ti.cloudpush" module. It already assigns a default channel to the received push notification.
| 1 |
3,201 |
TIMOB-25865
|
03/14/2018 02:43:13
|
Android: Build warning appears when Android build-tools v27 or higher is installed
|
*Summary:* In the Android SDK, if you install build-tools version 27.0.0 or higher and then do an Android build via Titanium, then the following warning message will be logged... {code} [WARN] : Android Build Tools 27.0.3 are too new and may or may not work with Titanium. [WARN] : If you encounter problems, select a supported version with: [WARN] : appc ti config android.buildTools.selectedVersion ##.##.## [WARN] : where ##.##.## is a version in /Users/user/Library/Android/sdk/build-tools that is 26.x {code} Android build-tools 27.x.x so far appears to work fine with Titanium builds. So, this warning is harmless for now. But in the future, Google could make breaking changes to their build-tools and we need to protect against this to help future proof our build system. *Test:* # Open Google's "Android SDK Manager". # Make sure the newest 26.x.x build-tools version is installed. # Make sure the newest 27.x.x build-tools version is installed. # Do a Titanium Android build. # Observe the log for the above mentioned warning. *Cause:* Titanium currently only supports build-tools version 26.x.x as defined by our "package.json" here... https://github.com/appcelerator/titanium_mobile/blob/master/android/package.json#L25 But the CLI ignores this setting and always uses the newest build-tools version available in the Android SDK instead of using the preferred version defined by our "package.json". This is because the linked code below will return a {{"maybe"}} string instead of {{true}} for a version higher than supported version, but it still evaluates as a positive in the {{if}} condition... https://github.com/appcelerator/node-titanium-sdk/blob/master/lib/android.js#L768 *Recommended Solution:* CLI should be changed to favor the build-tools version defined in the "package.json". A newer version outside of this range should only be selected if no preferred version is installed, in which case, the build-tools warning is desired. We should not make this change until after updating Titanium's "package.json" to support build-tools 27.x.x. This is to avoid a possible breaking change with developers who only have 27.x.x installed. _(Shouldn't cause an issue, but better safe than sorry.)_
| 3 |
3,202 |
TIMOB-25868
|
03/14/2018 23:34:18
|
Windows: Implement WebView.onlink callback
|
h5. description Costumer is attempting to load a pdf for android using intents with webview. in the mobile app they are using webview control for displaying the remote web site by binding a URL. The web pages in the web site contains few pdf links. On click of normal hyperlinks, respective web page is being shown in the web view. Whereas, on tapping a pdf links, a blank window is getting opened in Android devices. In iOS it’s working fine and a PDF is showing. Per Jira WebView cannot disply PDF documents on Android. So they are using intents as a workaround to open the PDF link. The issue is that on click of the pdf link in the web view, they are unable to get the exact PDF url with any of Titanium WebView API methods or events The customer was able to do it natively and open the PDF's with intents. h5. Request The customer wants to know how to get the exact PDF link using the webview API or if there is a workaround they could use. h5. additional information attached are two apps. One is a titanium app and one is an android native application. [titanium app|https://axwaysoftware-my.sharepoint.com/personal/vvazquezmontero_axway_com/_layouts/15/guestaccess.aspx?guestaccesstoken=rsxSxfm51VH5t8MRm7YpDX1bHDfJfDfaycmtpKrlAEE%3d&docid=2_11a957eab95234b6ab84003e12f7b0b41&rev=1]
| 3 |
3,203 |
TIMOB-25871
|
03/15/2018 11:08:16
|
iOS: Add ability to hide back button on NavigationWindow
|
Natively it is possible to hide the backButton programatically using the hidesBackButton attribute. This is discussed in this StackOverflow question: https://stackoverflow.com/questions/614212/how-to-hide-back-button-on-navigation-bar-on-iphone We should consider using this property when the user wants to hide the button.
| 0 |
3,204 |
TIMOB-25874
|
03/15/2018 18:37:12
|
iOS 11.2: Ti.UI.RefreshControl with Ti.UI.Window.largeTitleEnabled hides spinner
|
Hi, I have created a simple navigationWindow in Alloy. The Window has {{largeTitleEnabled: true}}, inside the window I have a simple listView with a refreshControl. When I run a Pull to Refresh the spinner is hidden by large-title.
| 8 |
3,205 |
TIMOB-25873
|
03/16/2018 03:16:50
|
Android: Intent - getData(), getAction() always equal to null
|
*Issue:* When I use the deep link for my project and try to access the Ti.Android.currentActivity.getIntent().getData() it always returns null for Ti SDK 6.2.0 and above but If I downgrade the SDK to 6.1.2 then it works fine. It cannot read data from incoming intents. *Steps to Reproduce* 1. Create a new alloy App and use the following test code 2. Install the app on any android device. 2. Goto the browser and browse to https://uktvplay.uktv.co.uk site. 3. Click on any episodes 4. It will open up the app but getData() is always null but it should return a URL *Test code:* - https://gist.github.com/MotiurRahman/ca8cd6c8b2745c870836602dfb6875fe *Expected Result:* It should return the URL when the App is opened from the deep link. Thanks!
| 2 |
3,206 |
TIMOB-25875
|
03/16/2018 16:29:27
|
Android: Babel rewrites app.js in classic project to generated ES5 code
|
I noticed that Babel rewrites ES6 code in the app.js of classic projects to ES5 code (by using the generated code). It was noticed while moving [ti.mapbox to ES6|https://github.com/hyperloop-modules/ti.mapbox/pull/2].
| 13 |
3,207 |
TIMOB-25876
|
03/16/2018 23:42:02
|
Windows: Support '@' character in node_modules
|
- Including {{@babel}} with Titanium Windows projects will cause compilation errors due to the unsupported {{@}} character
| 3 |
3,208 |
TIMOB-25877
|
03/17/2018 02:48:29
|
Android: "Ti.Platform.ostype" wrongly returns "32bit" on a 64-bit OS
|
*Summary:* The {{Ti.Platform.ostype}} property is currently hardcoded to return "32bit" on Android. [APSAnalyticcsHelper.java#L235|https://github.com/appcelerator/aps_sdk/blob/195633dd10a37d96ecf52be35c0c712dff5ef331/android/analytics/APSAnalytics/src/main/java/com/appcelerator/aps/APSAnalyticsHelper.java#L235] Now that Titanium supports building Android apps for ARM64, it should return "64bit" when running on a 64-bit Android device like how it works for iOS here... [APSUtility.m#L15|https://github.com/appcelerator/aps_sdk/blob/195633dd10a37d96ecf52be35c0c712dff5ef331/ios/support/analytics/APSAnalytics/APSUtility.m#L15] *Steps to Reproduce:* # Build an run the below code on a 64-bit Android device, such as a Pixel XL phone. # Observe the log for an "ostype:" entry. {code:java} Ti.API.info("@@@ ostype: " + Ti.Platform.ostype); {code} *Note:* We had to do something similar for iOS as can be seen here: [TIMOB-18193] *Recommended Solution:* Check if array returned by {{android.os.Build.SUPPORTED_64_BIT_ABIS}} contains at least 1 element. https://developer.android.com/reference/android/os/Build.html#SUPPORTED_64_BIT_ABIS Note that Google added 64-bit support as of Android 5.0 (aka: API Level 21). So, you can't use Google's {{Process.is64Bit()}} method since it is only supported on Android 6.0 and higher. https://developer.android.com/reference/android/os/Process.html#is64Bit()
| 2 |
3,209 |
TIMOB-25878
|
03/17/2018 04:13:24
|
Android: Modify "Ti.Platform.architecture" to provide consistent results like iOS
|
*Summary:* Currently, the {{Ti.Platform.architecture}} property on Android is difficult to use compared to iOS and Windows. It commonly fails to identify the device's architecture by returning "Unknown" or returns a difficult to parse string containing version and revision numbers appended to it. Below is a list of all architecture strings that has been reported to our analytics system: {code} 'Unknown' 'ARMv7 Processor rev 0 (v7l)' 'ARMv7 Processor rev 4 (v7l)' 'AArch64 Processor rev 4 (aarch64)' 'ARMv7 Processor rev 3 (v7l)' 'AArch64 Processor rev 1 (aarch64)' 'ARMv7 Processor rev 5 (v7l)' 'AArch64 Processor rev 2 (aarch64)' 'AArch64 Processor rev 3 (aarch64)' 'AArch64 Processor rev 0 (aarch64)' 'ARMv7 Processor rev 1 (v7l)' 'ARMv7 Processor rev 2 (v7l)' 'ARMv8 Processor rev 2 (v8l)' 'ARMv7 Processor rev 8 (v7l)' 'ARMv7 Processor rev 10 (v7l)' 'ARMv7 Processor rev 9 (v7l)' 'ARMv7 processor rev 4 (v7l)' '64-bit ARMv8 Processor rev 0 (v7l)' 'AArch64 Processor rev 13 (aarch64)' 'ARMv7 processor rev 1 (v7l)' 'sc7731 rev 5 (v7l)' '64-bit ARMv8 Processor rev 1 (v7l)' 'NVIDIA Denver 1.0 rev 0 (aarch64)' 'MT6732 rev 2 (v7l)' 'AArch64 Processor rev 12 (aarch64)' 'ARMv6-compatible processor rev 5 (v6l)' '6591 rev 4 (v7l)processor' 'ARMv7' 'mtk6580L rev 5 (v7l)' 'ARMv8 Processor rev 4 (aarch64)' 'Qualcomm Snapdragon 800' 'UNIVERSAL5410' 'ARMv7 Processor rev 12 (v7l)' 'MT6592 2.0GHZ (Octa-Core) rev 5 (v7l)' 'ARMv7 Processor rev 3 srev 0x23 (v7l)' 'MTK6580 rev 5 (v7l)' 'ARMv7 Processor rev 2 srev 0x23 (v7l)' 'ARMv7 Processor rev 6 (v7l)' 'S805' 'ARMv8 processor rev 1 (aarch64)' 'UNKNOWN rev 0 (UNKNOWN)' 'ARMv7 Processor' 'Quad-Core ARMv7 Processor' 'ARMv8 Processor rev 5 (v7l)' 'S905' 'ARMv7 Processor rev 5 rev 5 (v7l)' 'ARMv7 processor (v7l)' 'Quadcore Cortex-A71.2GHz rev 5 (v7l)' 'arm' 'MT6592 2.0GHZ rev 5 (v7l)' {code} I've tested the following devices and they return the following: ||Device Name||Returned Architecture String|| |Emulator|Unknown| |Pixel XL|Unknown| |Galaxy Tab 3|Unknown| |Galaxy Nexus|ARMv7 Processor rev 10 (v7l)| |Galaxy Note 2|ARMv7 Processor rev 0 (v7l)| |Nexus 4|ARMv7 Processor rev 2 (v7l)| |Nexus 5|ARMv7 Processor rev 0 (v7l)| |Nexus 10|ARMv7 Processor rev 4 (v7l)| |Pixel 2|AArch64 Processor rev 1 (aarch64)| |Amazon Fire HD 8 (7th gen)|AArch64 Processor rev 3 (aarch64)| Note that "Unknown" is the most commonly reported architecture name in our analytics system. Odds are most of these are coming from Google's Android emulator. *Cause:* The {{Ti.Platform.architecture}} property uses our APS library to fetch the architecture name, which attempts to fetch this string from a system file named "cpuinfo". This is an undocumented feature that we should avoid. Especially since it's proven to be unreliable and causes "Unknown" to be returned. [APSAnalyticsHelper.java#L339|https://github.com/appcelerator/aps_sdk/blob/195633dd10a37d96ecf52be35c0c712dff5ef331/android/analytics/APSAnalytics/src/main/java/com/appcelerator/aps/APSAnalyticsHelper.java#L339] *Recommended Solution:* The APS library's {{getArchitecture()}} method should be changed to fetch architecture via Google's {{android.os.Build}} class using its {{Build.SUPPORTED_ABIS}} and {{Build.CPU_ABI}} constants. https://developer.android.com/reference/android/os/Build.html I've tested the above constants on real Android devices and in the emulator. The above always return strings matching the APK's lib folder architecture subfolder names, where the {{*.so}} C/C++ libraries are kept. With the only exception being with the "x86_64" being returned by the emulator. For example: * armeabi-v7a * arm64-v8a * x86 * x86_64 *Ideal Solution:* Android should ideally return the same architecture string types that iOS does. This would make it easier to work with from a portability standpoint. It would also make it easier from an analytics standpoint to identify popular architectures between platforms. iOS fetches CPU architecture from the APS library here... [APSUtility.m#L24|https://github.com/appcelerator/aps_sdk/blob/195633dd10a37d96ecf52be35c0c712dff5ef331/ios/support/analytics/APSAnalytics/APSUtility.m#L24] iOS currently returns the following hardcoded strings: * x86_64 * arm * armv6 * armv7 * armv7s * arm64 * i386 *Work-Around:* You can use hyperloop to fetch the architecture using the above mentioned Java "Build" class constants. {code:javascript} // WARNING: You must add "hyperloop" module to the project for the below to work. var buildClass = require("android.os.Build"); if (Ti.Platform.Android.API_LEVEL >= 21) { Ti.API.info("@@@ Build.SUPPORTED_ABIS[0]: " + buildClass.SUPPORTED_ABIS[0]); } else { Ti.API.info("@@@ Build.CPU_ABI: " + buildClass.CPU_ABI); } {code}
| 2 |
3,210 |
TIMOB-25879
|
03/18/2018 17:48:07
|
iOS: Create modules in "dist" directory (Parity with Android)
|
This is all about parity and developer experience: Currently, iOS modules are created in the module root. Android uses the "dist" directory, which is better for separating it from the actual source code and module configuration.
| 0 |
3,211 |
TIMOB-25880
|
03/18/2018 21:12:28
|
Hyperloop: Logs should show the actual native class, not "HyperloopClass", debug logs should be hidden
|
A few things: - We should use proper class description for native classes. This is mainly for the developer experience, because all classes are logged as "HyperloopClass" right now, instead of printing the actual class behind the wrapper. This PR will replace {{<HyperloopClass: 0x608000072c80>}} with {{<NSMutableArray: 0x608000072c80>}} - Internal logs should be removed from public log level, e.g. {{\[HYPERLOOP\] didStartNewContext <KrollContext: 0x608000074140>}}. They do not have any value for a Titanium developer
| 5 |
3,212 |
TIMOB-25881
|
03/19/2018 07:00:26
|
Windows: Implement WebView.blacklistedURLs
|
{{WebView.blacklistedURLs}} property is missing as well as {{blacklisturl}} event.
| 5 |
3,213 |
TIMOB-25882
|
03/19/2018 16:00:45
|
Android: return event is received twice from Symbol TC55/TC70 scanner
|
Using the scanner of Symbol TC55/TC70 to send return event results in receiving it twice.
| 8 |
3,214 |
TIMOB-25886
|
03/19/2018 22:05:34
|
Android: Improve Ti.App._restart() performance
|
Currently, we use an Intent to re-launch our Titanium application when {{Ti.App._restart()}} is invoked. This isn't the best solution as it results in re-launching the application. Instead, we can terminate all existing acivities and restart the KrollRuntime to reset the Javascript context to a clean state.
| 5 |
3,215 |
TIMOB-25887
|
03/19/2018 22:18:41
|
Android: Ti.Geolocation - Exception when calling Ti.Geolocation.hasLocationPermissions()
|
h5. Issue Customer's app has an android service to get location data in the background. It is encountering an exception when it calls Ti.Geolocation.hasLocationPermissions(): They are receiving the following error: {quote}03-19 08:43:48.855 2764 2764 E TiApplication: (main) [6,1875] No valid root or current activity found for application instance 03-19 08:43:48.855 2764 2764 E KrollProxy: (main) [0,1875] Error creating proxy 03-19 08:43:48.855 2764 2764 E KrollProxy: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.pm.PackageManager android.content.Context.getPackageManager()' on a null object reference 03-19 08:43:48.855 2764 2764 E KrollProxy: at com.google.android.gms.common.zzo.isGooglePlayServicesAvailable(Unknown Source:4) 03-19 08:43:48.855 2764 2764 E KrollProxy: at com.google.android.gms.common.zze.isGooglePlayServicesAvailable(Unknown Source:0) 03-19 08:43:48.855 2764 2764 E KrollProxy: at com.google.android.gms.common.GoogleApiAvailability.isGooglePlayServicesAvailable(Unknown Source:0) 03-19 08:43:48.855 2764 2764 E KrollProxy: at ti.modules.titanium.geolocation.android.FusedLocationProvider$PlayServices.available(FusedLocationProvider.java:184) 03-19 08:43:48.855 2764 2764 E KrollProxy: at ti.modules.titanium.geolocation.android.FusedLocationProvider.hasPlayServices(FusedLocationProvider.java:80) 03-19 08:43:48.855 2764 2764 E KrollProxy: at ti.modules.titanium.geolocation.android.FusedLocationProvider.<init>(FusedLocationProvider.java:61) 03-19 08:43:48.855 2764 2764 E KrollProxy: at ti.modules.titanium.geolocation.GeolocationModule.<init>(GeolocationModule.java:219) 03-19 08:43:48.855 2764 2764 E KrollProxy: at java.lang.Class.newInstance(Native Method) 03-19 08:43:48.855 2764 2764 E KrollProxy: at org.appcelerator.kroll.KrollProxy.createProxy(KrollProxy.java:137) 03-19 08:43:48.855 2764 2764 E KrollProxy: at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(Native Method) 03-19 08:43:48.855 2764 2764 E KrollProxy: at org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModule(V8Runtime.java:187) 03-19 08:43:48.855 2764 2764 E KrollProxy: at org.appcelerator.kroll.KrollRuntime.handleMessage(KrollRuntime.java:325) 03-19 08:43:48.855 2764 2764 E KrollProxy: at android.os.Handler.dispatchMessage(Handler.java:102) 03-19 08:43:48.855 2764 2764 E KrollProxy: at android.os.Looper.loop(Looper.java:164) 03-19 08:43:48.855 2764 2764 E KrollProxy: at android.app.ActivityThread.main(ActivityThread.java:6494) 03-19 08:43:48.855 2764 2764 E KrollProxy: at java.lang.reflect.Method.invoke(Native Method) 03-19 08:43:48.855 2764 2764 E KrollProxy: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438) 03-19 08:43:48.855 2764 2764 E KrollProxy: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807) 03-19 08:43:48.855 2764 2764 E JavaObject: !!! OH NO! We tried to grab a Java Object back out of the reference table, but it must have been GC'd, because it's null! Key: 15 03-19 08:43:48.855 2764 2764 I TiAPI : We do not have location permissions. Exiting. {quote} The exception does not seem to make the service crash, but it doesn't think that it has location permissions (which it definitely does). So they are not getting any location data. h5. Code to create Android service: {code}var location_service_intent = Ti.Android.createServiceIntent( { url: 'LocationService.js' } ); location_service_intent.putExtra('interval', 600000); if (!Ti.Android.isServiceRunning(location_service_intent)) { Ti.Android.startService(location_service_intent); } {code} h5. Service Code: Uses a module to do all the location detection and updating with the back-end service provider. {code}Titanium.API.info("[LocationService] loaded"); var WxAlertSubscriptionUpdater = require ('/util/WxAlertSubscriptionUpdater'); WxAlertSubscriptionUpdater.register(); {code} h5. Additional information - issue not in SDK 7.0.2 - the WxAlertSubscriptionUpdater module is shared by the app and the service; the app doesn't have this problem when it talks to the Geolocation module - They have been unable to replicate this problem with a minimal test app; it's possible that a test app is too small to make garbage collection happen?
| 3 |
3,216 |
TIMOB-25889
|
03/20/2018 16:35:17
|
Android: Emulator builds should not add additional permissions
|
*Summary:* When building with deployment type "development" (ie: for the Android emulator), the Titanium build system adds the following permissions to the "AndroidManifest.xml" file, even if they're not defined in the "tiapp.xml" file. * {{android.permission.ACCESS_COARSE_LOCATION}} * {{android.permission.ACCESS_FINE_LOCATION}} * {{android.permission.ACCESS_MOCK_LOCATION}} The above behavior was intentional and was intended for fast incremental builds with LiveView and the emulator. However, this behavior has been known to cause confusion. *To-Do:* In Titanium 9.0.0, we should remove the above behavior. The build system should produce a consistent "AndroidManifest.xml" for all deployment types (ie: "test", "development", and "production"). *Note:* Titanium should still include its default permissions listed below. * {{android.permission.INTERNET}} * {{android.permission.ACCESS_WIFI_STATE}} * {{android.permission.ACCESS_NETWORK_STATE}} * {{android.permission.WRITE_EXTERNAL_STORAGE}} If you don't want the above default permissions injected, then you can set the following in your "tiapp.xml" file to override this behavior. {code:xml} <ti:app xmlns:ti="http://ti.appcelerator.org"> <override-permissions>true</override-permissions> </ti:app> {code}
| 5 |
3,217 |
TIMOB-25890
|
03/21/2018 02:04:04
|
Windows: Support Hyperloop ES6
|
ES6 {{import}} doesn't work for Hyperloop Windows because Hyperloop scans {{require}} and generates glue code _before transpile ({{import}} to {{require}}) runs_ at compile time. {code:javascript} // ES5-style require call var Int32 = require('System.Int32'); // ES6-style import import Button from 'Windows.UI.Xaml.Controls.Button'; import PropertyValue from 'Windows.Foundation.PropertyValue'; import MessageDialog from 'Windows.UI.Popups.MessageDialog'; import UICommand from 'Windows.UI.Popups.UICommand'; let win = Ti.UI.createWindow({ backgroundColor: 'green' }), button = new Button(); button.Content = "PUSH"; button.addEventListener('Tapped', () => { const dialog = new MessageDialog('My Message'); dialog.Title = 'My Title'; dialog.DefaultCommandIndex = 0; dialog.Commands.Add(new UICommand('OK', null, PropertyValue.CreateInt32(0))); dialog.Commands.Add(new UICommand('Cancel', null, PropertyValue.CreateInt32(1))); dialog.ShowAsync().then(function (command) { const id = Int32.cast(command.Id); alert((id == 0) ? 'Pushed "OK"' : 'Pushed "Cancel"') }); }); win.add(button); win.open(); {code}
| 8 |
3,218 |
TIMOB-25891
|
03/21/2018 05:57:30
|
Windows: Use of deprecated methods in Ti.Media
|
{{Ti.Media}} uses some deprecated methods that causes compile time warning {{C4973}}. {code} Warning C4973 'Windows::Media::Playback::IMediaPlayer::CurrentState::get': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 107 Warning C4973 'Windows::Media::Playback::IMediaPlayer::CurrentStateChanged::add': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 105 Warning C4973 'Windows::Media::Playback::IMediaPlayer::Position::set': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 155 Warning C4973 'Windows::Media::Playback::IMediaPlayer::Position::get': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 159 Warning C4973 'Windows::Media::Playback::IMediaPlayer::SetUriSource': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 181 Warning C4973 'Windows::Media::Playback::IMediaPlayer::Position::set': marked as deprecated TitaniumWindows_Media D:\workspace\titanium_mobile_windows\Source\Media\src\Media\AudioPlayer.cpp 233 {code}
| 13 |
3,219 |
TIMOB-25893
|
03/21/2018 17:47:46
|
Create Github Issue template
|
We decided to reopen the "Issues" tab as part of opening more to the community. While it is still in an experimental phase and we need to see if developer actually use it properly (mainly no SPAM, no duplicates), we also need to add a template like we do for pull requests to force a certain structure. [Here|https://github.com/stevemao/github-issue-templates] are a few cool ones for inspiration
| 5 |
3,220 |
TIMOB-25895
|
03/22/2018 12:30:37
|
Windows: Rename HAL
|
Apparently Microsoft starts rejecting our {{HAL.DLL}} in WACK (Windows Apps Certification Kit) just because Windows system has {{HAL.DLL}} in system library. We need to rename it in order to pass the cert. {code} I had the same issue and i wrote to Microsoft in order to discover what was the real problem and i finally find out: the problem is that the app package includes the HAL.dll library which has unfortunately the name of a Windows system library, so they told me to rename it if it is a different library because the current WACK (Windows Apps Certification Kit) which now is used for the store certification doesn’t accept it. The reason why the local WACK certification doesn’t detect this problem is that the new WACK is not yet available, it will be released with the next Windows update. Conclusion: i think the HAL library needs to be renamed. {code}
| 8 |
3,221 |
TIMOB-25896
|
03/22/2018 21:53:01
|
Android: Add Kotlin language support for modules
|
*Summary:* Titanium currently cannot build modules containing {{*.kt}} kotlin language files. We would like to add support for this language in the future. *Note:* This can easily be implemented once Titanium supports building with gradle. https://developer.android.com/kotlin/add-kotlin
| 5 |
3,222 |
TIMOB-25897
|
03/23/2018 12:41:07
|
iOS: Ti.UI.iOS.Stepper handles "value" boundaries incorrect
|
We handle allowed values for our Stepper UI element with: {code:objc} if (newValue < [[self stepper] maximumValue] && newValue > [[self stepper] minimumValue]) { [[self stepper] setValue:newValue]; } else { NSNumber *currentValue = [NSNumber numberWithDouble:[[self stepper] value]]; [self.proxy replaceValue:currentValue forKey:@"value" notification:NO]; NSLog(@"[WARN] The value passed in must be smaller than the maximum and bigger than the minimum stepper values"); } {code} Which is wrong. It should be newValue <= maximum && newValue >= minimum.
| 2 |
3,223 |
TIMOB-25905
|
03/26/2018 12:26:12
|
Hyperloop: lib file failed to leave a valid exports object
|
With the following files: https://gist.github.com/Topener/3a446122e6807732320aed7268395b43 I get the error {code} [ERROR] : Script Error Couldn't find module: /hyperloop/googlemobileads/gadmobileads for architecture: x86_64 [ERROR] : Script Error Module "titanium-admob/index.js" failed to leave a valid exports object [ERROR] : ErrorController is up. ABORTING showing of modal controller {code} Error doesn't occur when using Hyperloop 3.0.3 with TiSDK 7.2.0
| 0 |
3,224 |
TIMOB-25908
|
03/28/2018 07:21:26
|
Windows: require/import with namespace for Hyperloop
|
{{require(package_name).class_name}} doesn't work for Hyperloop Windows. {code} var Popups = require('Windows.UI.Popups.*'); var MessageDialog = Popups.MessageDialog; var dialog = new MessageDialog(); {code} This doesn't work because Hyperloop Windows {{require}} needs _fully qualified class name or enum_ and require against package name is not implemented.
| 13 |
3,225 |
TIMOB-25910
|
03/28/2018 12:48:07
|
Android: Memory leak when using TextFields in TableView rows
|
h6.Reproduce steps 1. Run the attached simple Alloy app. (Just an Alloy project that opens a modal window which has a TableView with rows containing Textfields. ) 2. Click the "Open Window" 3. Hit the Android "back" button to dismiss the window with the tableview textfield rows 4. Repeat steps 2 & 3 repeatedly until you start seeing messages such as the following: {code} [INFO] : zygote64: Background concurrent copying GC freed 302993(13MB) AllocSpace objects, 31(496KB) LOS objects, 44% free, 30MB/54MB, paused 214us total 258.736ms {code} Attached screenshot for that as well.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.