s.build_and_run(False,avd_id) File ""C:\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\1.5.1\android\builder.py"", line 1296, in build_and_run self.copy_project_resources() File ""C:\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\1.5.1\android\builder.py"", line 549, in copy_project_resources shutil.copy(path, dest) File ""C:\Documents and Settings\All Users\Application Data\Titanium\modules\win32\python\1.0.0\lib\shutil.py"", line 85, in copy copyfile(src, dst) File ""C:\Documents and Settings\All Users\Application Data\Titanium\modules\win32\python\1.0.0\lib\shutil.py"", line 52, in copyfile fdst = open(dst, 'wb') IOError: [Errno 13] Permission denied: 'D:\\Test\\TestApp\\build\\android\\bin\\assets\\Resources\\Thumbs.db' {code} Suggest Something ASAP. Regards, Rahul",3
TIMOB-2760,"need to be able to ref adb from either /tools or /platform-tools subdir","{html}as it stands users have to make a symlink in /tools to /platform-tools/adb
Problem
The HTTPClient errors intermittently (around half the time) when making an HTTPS request. The following error message is sent:
Error Domain=ASIHTTPRequestErrorDomain Code=1 ""A connection failure occurred"" UserInfo=0xb236b70 {NSUnderlyingError=0xb234cf0 ""The operation couldn’t be completed. Connection reset by peer"", NSLocalizedDescription=A connection failure occurred}
Tested On
All platforms tested with clean builds from both Titanium Mobile 1.5.1 and 1.6.0 (pulled January 8th, 2011).
BROKEN on iPhone Simulator 4.2
BROKEN on iPod Touch 4.2
WORKS on Android Simulator 2.2
WORKS in browser (hitting the URL)
Sample Code
var win = Titanium.UI.createWindow({ backgroudColor: '#333' }); var statusLabel = Titanium.UI.createTextArea({ top: 10, right: 10, left: 10, bottom: 45 }); win.add(statusLabel); function runRequest() { var xhr = Titanium.Network.createHTTPClient(); xhr.onload = function () { statusLabel.value = this.responseText; //Ti.API.info(this.responseText); }; xhr.onerror = function (e) { statusLabel.value = e.error; Ti.API.error(e.error); }; statusLabel.value = 'Waiting for response...'; xhr.open('GET', 'https://acomsx1.cos.agilent.com/QueryOpenNotificationsCount'); xhr.send(); } var refresh = Ti.UI.createButton({ title: 'Refresh', bottom: 10, left: 10, right: 10, height: 25 }); refresh.addEventListener('click', runRequest); win.add(refresh); win.open(); runRequest();
Associated Helpdesk Ticket
http://developer.appcelerator.com/helpdesk/view/64561
I used Ti.API.log with one argument in an external JS file wrongly. It works on iPhone and a message is printed as info log. But on Android, it fails without error message and scripts after the log line are not executed.
A helpdesk ticket encounter a problem while coming back to the app after it has been in the background (multitasking).
If the app is opened from being close, Ti.App.getArguments().url return nothing, and if it is opened again from backgrounding, it also returns nothing. This is fine, but when the app is launched from Safari (for example: app://), getArguments().url returns ""app://"" (or whatever the name of the app is) as expected. If the app is placed in the background again and reopened normally, the same url appears as if it was opened through safari.
More details and sample app.js in helpdesk ticket 76659.
Steps to Reproduce
1. Launch KitchenSink
2. Run Phone > Geolocation
3. Go back and then go back into geolocation again
Actual Result:
Alert ""error{code
Expected Result:
To return the geolocation values
Note:
Droid 1 happens on first launch
Nexus S, sometimes happen on first launch, sometimes require a second launch
See also bug # 2418
Tested on:
Nexus S 2.3.2 Titanium SDK version: 1.7.0 (Apr 12 2011 15:24 rcc9dd9e1)
Droid 1 2.2.1 Titanium SDK version: 1.7.0 (Apr 12 2011 15:24 rcc9dd9e1)
Counter is: ' + counter + '
'; tab1.open(winwebview,{animated:true}); }); // // create controls tab and root window // var win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff' }); var tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Tab 2', window:win2 }); var label2 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 2', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win2.add(label2); // // add tabs // tabGroup.addTab(tab1); tabGroup.addTab(tab2); // open tab group tabGroup.open(); {code} # Build an run the app in simulator. # Tap on the button ""open webview window"". # The webview shows the line ""Counter is: 1"". # Navigate back to Tab 1 and tap again on the button ""open webview window"". # The webview should show the line ""Counter is: 2"", but the webview shows up empty. With Titaniums SDK 1.8.0.1 and 1.8.1 this works as expected. ",1
TIMOB-7806,"Tooling: Bundle ACS (and potentially MQTT) module binaries with the MobileSDK ","We need to bundle the new ACS module alongside the MobileSDK. Android may also require a second MQTT module that the ACS module will depend on. A brief overview for how this should work: * The ACS (and MQTT) modules will be provided as zip binaries by the Modules team, preferably living under something like support/common * {{site_scons/package.py}} will need to be updated so those zips are extracted and live in the ""modules"" top level directory of the MobileSDK zip. This will ensure that when the MobileSDK zip is extracted, the modules are installed in the system directory as well h3. Testing 1. Download the two ti.* modules attached to this ticket (ignore bogus.zip). 2. Copy these two zips into titanium_mobile/support/module/packaged 3. Run scons to build the SDK. 4. Extract the SDK zip in dist/ and verify the file structure in modules/ matches as described in this ticket (see comments). ",1
TIMOB-7816,"Android: Ignore files that start with ._","On a Mac, some editors will generate a ._ file. When you compile an Android app, the android/compiler.py's make_function_from_file() function will error saying: {code} UnicodeDecodeError: 'utf8' codec can't decode byte 0xb0 in position 37: invalid start byte {code} Just need to ignore ._ files.",3
TIMOB-7833,"Tooling: Add support for a ""common"" CommonJS module installation folder","With our current module system, modules must either be installed into a project or in the system Titanium folder. In both cases, modules are platform-specific compiled binaries (a static lib for iOS, shared lib for Android). It would be nice to allow pure Javascript / CommonJS modules in a common place that could simply be distributed as JS files, for example a {{common}} or {{commonjs}} folder under the system Titanium directory that would be analogous to today's {{iphone}} and {{android}} directories.",1
TIMOB-7862,"iOS: UIPopover background color","Previous to 5.0 there was no way to customize the UIPopover background color. From reading the docs and around the web since 5.0 people have been doing it. References: https://developer.apple.com/library/ios/#documentation/uikit/reference/UIPopoverController_class/Reference/Reference.html#//apple_ref/occ/instp/UIPopoverController/popoverBackgroundViewClass https://developer.apple.com/library/ios/#documentation/uikit/reference/UIPopoverBackgroundView_class/Reference/Reference.html#//apple_ref/occ/cl/UIPopoverBackgroundView http://stackoverflow.com/questions/5974439/customizing-the-uipopovercontroller-view-background-and-border-color http://stackoverflow.com/questions/8490261/change-color-navigation-controller-in-a-popover",1
TIMOB-7865,"Android: XML - On V8, parsing xml multiple times crashes the phone","Details: When running the app.js in SDK build 2.0.0.v20120302093154 for V8, the app will eventually crash and GC will be continuously called. See attachment 2.0_logcat.txt. And when running the app.js in SDK build 1.8.2 for V8, I get a out of memory exception. See attachment 1.8.2_logcat.txt. However, the app.js does not crash when running on Rhino for both builds. Steps to reproduce: 1. Create new project. 2. Replace app.js with attached app.js. 3. Run app. 4. Press 'load' until app crashes. Actual: App crashes. See attachments. Expected: The app should not crash.",1
TIMOB-8486,"iOS: VideoPlayer does not fire touch events since 1.8.1","VideoPlayer is not firing touch events anymore on iOS (other platforms not tested). The next code works with sdk 1.7.5 and 1.8.0.1 on iOS, but is not working with sdk 1.8.1 nor 1.8.2 I tried to capture click, dblclik and touchstart events with same result. Bug has been confirmed by the community at Q&A [http://developer.appcelerator.com/question/132645/bug-videoplayer-does-not-fire-touch-events-sdk-181] {code:title=Test case: App.js|borderStyle=solid} var win = Ti.UI.createWindow(); var videoObject = Titanium.Media.createVideoPlayer({ contentURL:'test.mp4', scalingMode:Titanium.Media.VIDEO_SCALING_MODE_FILL, top:0, left:0, height:'100%', width:'100%', autoplay:true }); videoObject.addEventListener('click', function(){ alert('click!'); }); win.add(videoObject); win.open(); {code}",2
TIMOB-7897,"Android: Memory leak by windows not properly cleaning up after close.","Windows appear to be leaking memory by not properly cleaning up after they have been closed. This only affects ""heavy"" windows that have their own activity. h3. Test Case: Opening a window and adding many child views. Run the application and click the button to open a window. Wait for an alert dialog to popup telling you its okay to back out now. Hit the back button to close out the window. Repeat this process. Expected: Memory usage should peak and remain steady. Actual: Memory usages constantly rises until out of memory crash occurs. {code:javascript} function mainViews() { var newWin = Ti.UI.createWindow({ navBarHidden: true }); Ti.API.info('****** mainViews function has started ******'); var views =[]; var view = null; for (var i=0; i < 500; i++) { view = Ti.UI.createView(); views.push(view); newWin.add(view); } newWin.open(); alert(""You may click back now.""); Ti.API.info('Titanium views created and added to array'); Ti.API.info('****** mainViews function has stopped ******'); } var win = Ti.UI.createWindow({ backgroundColor: ""white"" }); var button = Ti.UI.createButton({ title: ""create 5k views"" }); button.addEventListener(""click"", function(e) { mainViews(); Ti.API.info('Available memory: ' + Ti.Platform.availableMemory); }); win.add(button); win.open(); {code}",1
TIMOB-7948,"Android: Invalid column visibility when querying events in Ti.Android.Calendar","Here is the sample app from our Calendar TDoc that shows the error. The error seems to happen when {{getEventsInYear}} is called {code} var calendars = []; var selectedCalendarName; var selectedCalendarId; var pickerData = []; var win = Ti.UI.createWindow({ backgroundColor: 'white', exitOnClose: true, fullscreen: false, layout: 'vertical', title: 'Calendar Demo' }); var scrollView = Ti.UI.createScrollView({ backgroundColor: '#eee', height: 500, top: 20 }); var label = Ti.UI.createLabel({ backgroundColor: 'white', text: 'Click on the button to display the events for the selected calendar', textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER, top: 20 }); scrollView.add(label); var selectableCalendars = Ti.Android.Calendar.selectableCalendars; for (var i = 0, ilen = selectableCalendars.length; i < ilen; i++) { calendars.push({ name: selectableCalendars[i].name, id: selectableCalendars[i].id }); pickerData.push( Ti.UI.createPickerRow({ title: calendars[i].name }) ); if(i === 0){ selectedCalendarName = selectableCalendars[i].name; selectedCalendarId = selectableCalendars[i].id; } } var selectableCalendars = null; if(!calendars.length){ label.text = 'No calendars available. Select at least one in the native calendar before using this app'; } else { label.text = 'Click button to view calendar events'; var picker = Ti.UI.createPicker({ top:20 }); picker.add(pickerData); win.add(picker); picker.addEventListener('change', function(e){ for (var i = 0, ilen = calendars.length; i < ilen; i++) { if(calendars[i].name === e.row.title){ selectedCalendarName = calendars[i].name; selectedCalendarId = calendars[i].id; } } }); var button = Ti.UI.createButton({ title: 'View events', top: 20 }); win.add(button); button.addEventListener('click', function(e){ label.text = 'Generating...'; var currentYear = new Date().getFullYear(); var consoleString = ''; function print(s) { if (consoleString.length) { consoleString = consoleString + '\n'; } consoleString = consoleString + s; } var calendar = Ti.Android.Calendar.getCalendarById(selectedCalendarId); function printReminder(r) { var typetext = '[method unknown]'; if (r.method == Ti.Android.Calendar.METHOD_EMAIL) { typetext = 'Email'; } else if (r.method == Ti.Android.Calendar.METHOD_SMS) { typetext = 'SMS'; } else if (r.method == Ti.Android.Calendar.METHOD_ALERT) { typetext = 'Alert'; } else if (r.method == Ti.Android.Calendar.METHOD_DEFAULT) { typetext = '[default reminder method]'; } print(typetext + ' reminder to be sent ' + r.minutes + ' minutes before the event'); } function printAlert(a) { print('Alert id ' + a.id + ' begin ' + a.begin + '; end ' + a.end + '; alarmTime ' + a.alarmTime + '; minutes ' + a.minutes); } function printEvent(event) { if (event.allDay) { print('Event: ' + event.title + '; ' + event.begin.toLocaleDateString() + ' (all day)'); } else { print('Event: ' + event.title + '; ' + event.begin.toLocaleDateString() + ' ' + event.begin.toLocaleTimeString()+ '-' + event.end.toLocaleTimeString()); } var reminders = event.reminders; if (reminders && reminders.length) { print('There is/are ' + reminders.length + ' reminder(s)'); for (var i = 0; i < reminders.length; i++) { printReminder(reminders[i]); } } print('hasAlarm? ' + event.hasAlarm); var alerts = event.alerts; if (alerts && alerts.length) { for (var i = 0; i < alerts.length; i++) { printAlert(alerts[i]); } } var status = event.status; if (status == Ti.Android.Calendar.STATUS_TENTATIVE) { print('This event is tentative'); } if (status == Ti.Android.Calendar.STATUS_CONFIRMED) { print('This event is confirmed'); } if (status == Ti.Android.Calendar.STATUS_CANCELED) { print('This event was canceled'); } } var events = calendar.getEventsInYear(currentYear); if (events && events.length) { print(events.length + ' event(s) in ' + currentYear); print(''); for (var i = 0; i < events.length; i++) { printEvent(events[i]); print(''); } } else { print('No events'); } label.text = consoleString; }); } win.add(scrollView); win.open(); {code} Also make sure you add READ_CALENDAR and WRITE_CALENDAR permissions to your tiapp.xml: {code} {code} And finally, here is the trace: {code} /CursorWrapperInner(31255): Cursor finalized without prior close() E/DatabaseUtils(31274): Writing exception to parcel E/DatabaseUtils(31274): java.lang.IllegalArgumentException: Invalid column visibility E/DatabaseUtils(31274): android.database.sqlite.SQLiteQueryBuilder.computeProjection(SQLiteQueryBuilder.java:588) E/DatabaseUtils(31274): android.database.sqlite.SQLiteQueryBuilder.buildQuery(SQLiteQueryBuilder.java:403) E/DatabaseUtils(31274): android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:347) E/DatabaseUtils(31274): android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:291) E/DatabaseUtils(31274): com.android.providers.calendar.CalendarProvider2.handleInstanceQuery(CalendarProvider2.java:1015) E/DatabaseUtils(31274): com.android.providers.calendar.CalendarProvider2.query(CalendarProvider2.java:840) E/DatabaseUtils(31274): android.content.ContentProvider$Transport.query(ContentProvider.java:178) E/DatabaseUtils(31274): android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112) E/DatabaseUtils(31274): android.os.Binder.execTransact(Binder.java:338) E/DatabaseUtils(31274): dalvik.system.NativeStart.run(Native Method) E/TiJSError(31255): (main) [141129,172202] ----- Titanium Javascript Runtime Error ----- E/TiJSError(31255): (main) [0,172202] - In pullRequests/1591.js:135,27 E/TiJSError(31255): (main) [0,172202] - Message: Uncaught Error: Invalid column visibility E/TiJSError(31255): (main) [0,172202] - Source: var events = calendar.getEventsInYear(currentYear); E/V8Exception(31255): Exception occurred at pullRequests/1591.js:135: Uncaught Error: Invalid column visibility {code}",1
TIMOB-7967,"Android: Replace Node.text with Node.textContent","For MobileWeb parity in 2.0, we need to deprecate the current {{Node.text}} property in our XML API, and rename it to {{textContent}}. We won't be fully implementing {{textContent}} from the DOM3 spec as it requires read-write access, and the traversal rules are slightly different than our current implementation. This is mainly for source level equivalence, until we have time to implement it properly.",1
TIMOB-7968,"iOS: Replace Node.text with Node.textContent","For MobileWeb parity in 2.0, we need to deprecate the current {{Node.text}} property in our XML API, and rename it to {{textContent}}. We won't be fully implementing {{textContent}} from the DOM3 spec as it requires read-write access, and the traversal rules are slightly different than our current implementation. This is mainly for source level equivalence, until we have time to implement it properly.",1
TIMOB-8077,"iOS: TableView - setContentInsets not working correctly, values assigned are not always respected","When using many or complex rows in a table view, in connection with a pull to refresh UI, the table does not always stay stuck down (with things like a reloading message showing). To reproduce, do the following: - Run the following code on device (simulator works fine) - Scroll down the table a bit. - scroll back up and try to do a pull to refresh a few times. The result: The table will not always stay ""pulled down"" by 60. sometimes it will, but more often it will be around 5. If however you pull down and hold the table down for about a second before releasing, it seems to work correctly. The code to re-create this issue is in the kitchen sink, I just am having it run with more rows to make the issue more clear... the issue is also clear when using more complex row layouts. {code} var win = Ti.UI.createWindow(); function formatDate() { var date = new Date(); var datestr = date.getMonth()+'/'+date.getDate()+'/'+date.getFullYear(); if (date.getHours()>=12) { datestr+=' '+(date.getHours()==12 ? date.getHours() : date.getHours()-12)+':'+date.getMinutes()+' PM'; } else { datestr+=' '+date.getHours()+':'+date.getMinutes()+' AM'; } return datestr; } var data = []; for(i=0; i<600; i++) { data.push({title:""Row ""+i}); } var lastRow = 4; var tableView = Ti.UI.createTableView({ data: data }); win.add(tableView); var border = Ti.UI.createView({ backgroundColor:""#576c89"", height:2, bottom:0 }); var tableHeader = Ti.UI.createView({ backgroundColor:""#e2e7ed"", width:320, height:60 }); // fake it til ya make it.. create a 2 pixel // bottom border tableHeader.add(border); var arrow = Ti.UI.createView({ backgroundImage:""../images/whiteArrow.png"", width:23, height:60, bottom:10, left:20 }); var statusLabel = Ti.UI.createLabel({ text:""Pull to reload"", left:55, width:200, bottom:30, height:""auto"", color:""#576c89"", textAlign:""center"", font:{fontSize:13,fontWeight:""bold""}, shadowColor:""#999"", shadowOffset:{x:0,y:1} }); var lastUpdatedLabel = Ti.UI.createLabel({ text:""Last Updated: ""+formatDate(), left:55, width:200, bottom:15, height:""auto"", color:""#576c89"", textAlign:""center"", font:{fontSize:12}, shadowColor:""#999"", shadowOffset:{x:0,y:1} }); var actInd = Titanium.UI.createActivityIndicator({ left:20, bottom:13, width:30, height:30 }); tableHeader.add(arrow); tableHeader.add(statusLabel); tableHeader.add(lastUpdatedLabel); tableHeader.add(actInd); tableView.headerPullView = tableHeader; var pulling = false; var reloading = false; function beginReloading() { // just mock out the reload setTimeout(endReloading,2000); } function endReloading() { // simulate loading for (var c=lastRow;c -65.0 && offset < 0) { pulling = false; var t = Ti.UI.create2DMatrix(); arrow.animate({transform:t,duration:180}); statusLabel.text = ""Pull down to refresh...""; } }); tableView.addEventListener('scrollEnd',function(e) { if (pulling && !reloading && e.contentOffset.y <= -65.0) { reloading = true; pulling = false; arrow.hide(); actInd.show(); statusLabel.text = ""Reloading...""; tableView.setContentInsets({top:60},{animated:true}); arrow.transform=Ti.UI.create2DMatrix(); beginReloading(); } }); win.open(); {code}",2
TIMOB-8048,"Android: removeEventListener does not work for the CI Builds","removeEventListener does not work on android, when used to remove and eventlistener on 'focus' event. Run the code below. Do the following: open app alert comes up - clear it click on Win 2's tab click on Win 1's tab Observed behavior: alert comes up again (the event listener wasn't removed during the call to onFocus ()). Expected behavior: the second alert should not come up (the event listener should have been removed during the call to onFocus()) Thinking that maybe it was because I was calling removeEventListener() from within the event listener function, I also added a button that should remove the event listener from the window. It doesn't work either. {code} var tabGroup = Ti.UI.createTabGroup(); var win1 = Ti.UI.createWindow({ backgroundColor: '#fff', title: 'Win 1' }); tabGroup.addTab(Ti.UI.createTab({ window: win1, title: win1.title })); var win2 = Ti.UI.createWindow({ backgroundColor: '#666', title: 'Win 2' }); tabGroup.addTab(Ti.UI.createTab({ window: win2, title: win2.title })); var onFocus = function () { alert('[focus] size: ' + win1.size.width + ', ' + win1.size.height); win1.removeEventListener ('focus', onFocus); } win1.addEventListener('focus', onFocus); var btn1 = Titanium.UI.createButton({ width: 200, height: 50, title: 'Click me', }); btn1.addEventListener('click', function(e) { win1.removeEventListener ('focus', onFocus); }); win1.add(btn1); tabGroup.open(); {code} ",2
TIMOB-8505,"Android: Module build.xml no longer compiles C++ source code in the ""jni"" directory","Marshall's post on using native libraries in an Android module (http://developer.appcelerator.com/blog/2011/01/titanium-and-the-android-ndk.html) states that you need to place C++ source files in the jni directory of the module project and they will be compiled into .so files and included in the module. This is not the case in version 1.8.2 of the SDK -- the build.xml file under TITANIUM_HOME/mobilesdk/osx/1.8.2/modules/android never looks in that directory. To get the described behavior, the following targets can be added to the module's build.xml file: {code:xml} {code} Ideally, these targets would be part of the SDK's build.xml. In the meantime, it would be good to update the blog post to indicate that it is out of date.",1
TIMOB-8066,"Android: xhdpi density folder for extra large screens is not working ","Adding res-notlong-port-xhdpi"" and other related xhdpi folders to android -> images folder does not work as the image is not taken from those folders. As per the Android Developer website, I tried to create a 640 x 960 resolution avd to test this issue for xhdpi. To test: 1. Create an AVD for 640 x 960 resolution for titanium to run on. (This link explains the resolution needed for different densities: http://developer.android.com/guide/practices/screens_support.html) *You might have to edit the already created AVD to appropriate resolution since Titanium creates a new AVD by itself (unless there is another way)* 2. Create any default app with res-long-port-xhdpi, res-long-land-xhdpi, res-notlong-port-xhdpi, res-notlong-land-xhdpi folders under android and add differen images to these folder to differentiate easily. (See Screenshot for the folder structure) 3. Run the app with the desired AVD. The starting screen image that appears is not of xhdpi but of mdpi folder. Please clarify about this issue. *Note: You would also need to set the tool-api-level and some other properties as below since the xhdpi has been added to android after api level 8.* {noformat} 8 {noformat} ",2
TIMOB-8076,"Android: V8: GC lag can cause crash on older devices","On older devices like Droid 2, GC lag cause result in a crash when: 1) alot of object are created resulting in high memory allocation on the java side 2) said objects are available for cleanup (no reference maintained in JS) 3) GC has not scanned yet due to the memory overhead on the V8 side not causing enough pressure on the GC We need a way to notify V8 that we are running low on memory so that a GC occurs sooner than V8 would normally do on it's own. A ticket has been linked that provides a fail case for this issue (original test case in ticket - not the one attached in the comments)",5
TIMOB-8094,"Android: App crashes on the device while uploading images, Memory issues","The app uses camera to click pictures, and upload to their server. Before uploading they perform image compression and resizing. Ti.imagefactory module is used for these purposes. The pictures are high resolution images, taken by a 8MP camera on the Motorola Droid X. The issue arises, when he uploads more than 1 image or multiple similar images or displaying the image in imageview. He gets ""Unable to load bitmap.Not enough memory.bitmap size exceeds VM budget."" error on the device. You can see the crash log here {code}03-19 10:32:54.837: E/dalvikvm-heap(3474): 5752604-byte external allocation too large for this process. 03-19 10:32:54.916: E/GraphicsJNI(3474): VM won't let us allocate 5752604 bytes 03-19 10:32:54.916: D/dalvikvm(3474): GC_FOR_MALLOC freed 0K, 47% free 9431K/17479K, external 11586K/13634K, paused 73ms 03-19 10:32:54.923: E/TiDrawableReference(3474): (main) [1277,430400] Unable to load bitmap. Not enough memory: bitmap size exceeds VM budget 03-19 10:32:54.923: E/TiDrawableReference(3474): java.lang.OutOfMemoryError: bitmap size exceeds VM budget 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.graphics.Bitmap.nativeCreate(Native Method) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.graphics.Bitmap.createBitmap(Bitmap.java:507) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.graphics.Bitmap.createBitmap(Bitmap.java:474) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.graphics.Bitmap.createScaledBitmap(Bitmap.java:379) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.view.TiDrawableReference.getBitmap(TiDrawableReference.java:558) 03-19 10:32:54.923: E/TiDrawableReference(3474): at ti.modules.titanium.ui.widget.TiUIImageView.setImage(TiUIImageView.java:736) 03-19 10:32:54.923: E/TiDrawableReference(3474): at ti.modules.titanium.ui.widget.TiUIImageView.processProperties(TiUIImageView.java:849) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.KrollProxy.setModelListener(KrollProxy.java:641) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.proxy.TiViewProxy.realizeViews(TiViewProxy.java:464) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.proxy.TiViewProxy.handleGetView(TiViewProxy.java:456) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.proxy.TiViewProxy.getOrCreateView(TiViewProxy.java:434) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.proxy.TiViewProxy.handleToImage(TiViewProxy.java:716) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:303) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.os.Handler.dispatchMessage(Handler.java:95) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.common.TiMessenger.dispatchMessage(TiMessenger.java:318) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.common.TiMessenger.dispatchPendingMessages(TiMessenger.java:303) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.common.TiMessenger$2.getResult(TiMessenger.java:188) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.common.TiMessenger.sendBlockingMessage(TiMessenger.java:215) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.common.TiMessenger.sendBlockingRuntimeMessage(TiMessenger.java:143) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.kroll.KrollProxy.fireSyncEvent(KrollProxy.java:417) 03-19 10:32:54.923: E/TiDrawableReference(3474): at org.appcelerator.titanium.TiBaseActivity.onRestart(TiBaseActivity.java:830) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.Instrumentation.callActivityOnRestart(Instrumentation.java:1139) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.Activity.performRestart(Activity.java:3865) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.Activity.performResume(Activity.java:3876) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2191) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2228) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:994) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.os.Handler.dispatchMessage(Handler.java:99) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.os.Looper.loop(Looper.java:123) 03-19 10:32:54.923: E/TiDrawableReference(3474): at android.app.ActivityThread.main(ActivityThread.java:3806) 03-19 10:32:54.923: E/TiDrawableReference(3474): at java.lang.reflect.Method.invokeNative(Native Method) 03-19 10:32:54.923: E/TiDrawableReference(3474): at java.lang.reflect.Method.invoke(Method.java:507) 03-19 10:32:54.923: E/TiDrawableReference(3474): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839) 03-19 10:32:54.923: E/TiDrawableReference(3474): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597) 03-19 10:32:54.923: E/TiDrawableReference(3474): at dalvik.system.NativeStart.main(Native Method) 03-19 10:32:54.923: I/TiUIHelper(3474): (main) [8,430408] view does not have parent, calling layout {code} Created sample apps, using the ti.imagefactory module, but could not reproduce this issue. Also tested the code on Motorola Droid3, LG OptimusV but still could not reproduce the issue. ",3
TIMOB-8113,"Android: Ti.UI.WebView doesn't seem to load pages that try to open a new window","*Code* * app.js {code} var win = Ti.UI.createWindow(); var webview = Titanium.UI.createWebView({ url: 'index.html' }); win.add(webview); win.open(); {code} * index.html {code} Click to load Google in a new window.
Click to load Google in the same window. {code} *Expected behavior* When you click on either of the two links, it should load up Google. *Actual behavior* What actually happens, is that the first link doesn't seem to do anything, only the second one seems to work. *Notes* -Only tested on a HTC Sensation and Samsung Galaxy S2, both giving me the same result. -Same result, whether I use the Rhino or V8 engine. -When testing the same code on the iOS simulator, both links seem to work fine. -The issue is 'target=""_blank""' without this, it seems to work fine. -HD ticket: http://support-admin.appcelerator.com/display/APP-257637",3
TIMOB-8127,"iOS: You can't call the Facebook Authorization from a Dialog (not even with app events)","h4. Problem Description Customer adds a Facebook.authorize(); from an app, without any results. h4. Actual Results The function never goes and logs into facebook. h4. Expected results The app should be able to login into fb h4. Test Case 1. Create a new mobile project 2. Add the code in the example to a button 3. Run it {code} wishToShareViaFacebook.addEventListener('click', function(e){ if (e.index == 0) { if (Titanium.Facebook.loggedIn) { var data = { link: ""www.jokwear.com"", name: ""Great Apparel, Great Message"", message: ""Check out JokWear!"", caption: ""Follow your favourite athletes, support other athletes"", picture: ""http://jokwear.com/images/joklogo.gif"", description: ""JokWear is a clothing brand that not only touts excellent fabric but also a social movement that you can achieve anything you set your mind to."", test: [ {foo:'Encoding test', bar:'Durp durp'}, 'test' ] }; Titanium.Facebook.requestWithGraphPath('me/feed', data, 'POST', showRequestResult); } else { Titanium.Facebook.authorize(); } } }); {code} h4. Extra info There is a bug where platform didn't want to launch the FB authorize from a dialog, since it's bad practice to get a dialog from a dialog. So, we recommended the customer to add an app event catching this, closing the dialog and then adding the other dialog. It's not runnning. The customer creates a small function doing a setTimeout, and that way, the function it's called properly within the if. ",1
TIMOB-8136,"iOS: Coverflow - @2x images don't have a very clear retina display","h6.Issue Images in the carrousel don't have a very clear retina display. It does show the @2x image but there's not much difference in the quality of the image. h6.Tested on iPhone 4 iOS simulator retina h6.Current behavior Same image is shown both in the coverflow and in an imageview, the rendered final image shows differently. h6.Steps to reproduce Import Resources.zip into a Studio project. Attached ZIP. ",2
TIMOB-8172,"Android: memory leaks opening/closing tabGroups","h2. Problem Memory leaks when opening and closing a window including a tabGroup h2. Code and steps to reproduce {code:lang=javascript|title=app.js} var mainwin = Ti.UI.createWindow({ title:'TEST WINDOW', backgroundColor:'#fff', fullscreen:true, statusBarHidden: true, navBarHidden:true, exitOnClose:true }); var button = Ti.UI.createButton({ title: ""create tabGroup"" }); var MY_TABGROUP = null; Titanium.App.addEventListener('tabGroupclosed', function(e) { Ti.API.debug('MY_TABGROUP close...'); MY_TABGROUP = null; }); button.addEventListener('click', function(e) { MY_TABGROUP = require('/myNewTabGroup').innerTabGroup(); MY_TABGROUP.open({ animated: true }); }); var button2 = Ti.UI.createButton({ bottom: 200, title:'show MY_TABGROUP' }); button2.addEventListener('click', function(){ alert(MY_TABGROUP) }); mainwin.add(button2); var button3 = Ti.UI.createButton({ bottom:5, title:'GC' }); button3.addEventListener('click', function(){ views1 = []; views2 = []; MY_TABGROUP=null; }); mainwin.add(button3); mainwin.add(button); mainwin.open(); {code} {code:lang=javascript|title=myNewTabGroup.js} exports.innerTabGroup = function() { var tabGroup = null; var win1 = null; var tab1 = null; var win2 = null; var tab2 = null; var views1 =[]; var view1 = null; var views2 =[]; var view2 = null; tabGroup = Titanium.UI.createTabGroup(); win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff' }); for (var i=0; i < 600; i++) { view1 = Ti.UI.createView(); views1.push(view1); win1.add(view1); } tab1 = Titanium.UI.createTab({ icon:'KS_nav_views.png', title:'Tab 1', window:win1 }); win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff' }); for (var i=0; i < 600; i++) { view2 = Ti.UI.createView(); views2.push(view2); win2.add(view2); } tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Tab 2', window:win2 }); tabGroup.addTab(tab1); tabGroup.addTab(tab2); return tabGroup; }; {code} Steps followed with allocated memory and # of objects: 1. Run the app (memory 3144MB - #Objects 60,139) and click on 'create tabGroup' button (mem 8053 - Obj 148,156) 2. Hit back button (mem 4457 - 91,059). Reference to MY_TABGROUP is still present and is still not GC 3. Click the GC button to set MY_TABGROUP to null (mem 4234 - Obj 86,654) 4. Click on create tabGroup button (mem 9007 - 172,396) 5. Hit back button (5408 - 115,292) Memory increase in size subsequently repeating the steps. Attaching also the log file. h2. Additional info Customer ticket: http://support-admin.appcelerator.com/display/APP-355811",4
TIMOB-8173,"iOS: Rejection for use of deprecated UDID property","We have had reports of two Apple rejections today for Titanium apps submitted for clients using an older 2.0 CI build and 1.8.2. The rejection is based on the use of deprecated UDID property. Was confirmed by a Titanium developer with at least one other native dev who got rejected: https://twitter.com/#!/steipete/status/182640647113687040 This seems to be a very recent occurrence, so little data is available at this time. This will require investigation and validation, along with a measured approach at dealing with moving totally over to the new UDID generation mechanism.",2
TIMOB-8185,"iOS: TextField loses focus if resized","h2. Problem TextField in a TableViewRow loses focus if it has been resized after being focused h2. Code and steps to reproduce {code:lang=javascript|title=app.js} var win = Ti.UI.createWindow({ title:'pippo', backgroundColor:'white' }); function addRow(addTextArea) { var row = Ti.UI.createTableViewRow({height:200}); var $tTF = Ti.UI.createTextField({ height: 30, top : 30, width: 100, borderStyle:Titanium.UI.INPUT_BORDERSTYLE_ROUNDED }); $tTF.addEventListener('focus',function(_e){ Ti.API.error(""focus ""+_e.source.height); Ti.API.error(_e); _e.source.animate({height: _e.source.height*2}); }); row.add($tTF); row.selectionStyle = Ti.UI.iPhone.TableViewCellSelectionStyle.NONE; row.className = 'control'; return row; } // create table view data object var data = []; for (var x=0;x<1;x++) { if (x==1){ data[x] = addRow(true); } else { data[x] = addRow(); } } var tableView = Ti.UI.createTableView({ data:data, style: Titanium.UI.iPhone.TableViewStyle.GROUPED }); win.addEventListener('focus', function() { Ti.API.info('window focus fired'); }); win.add(tableView); win.open(); {code} To reproduce: - Run the app and click the textField: textField is animated increasing in height. Result: focus on textField is lost. h2. Additional notes Ticket associated: http://support-admin.appcelerator.com/display/APP-995689/conversation/read_all",5
TIMOB-8186,"iOS: Feature request to add X.509 certificate authentication over SSL in HTTPClient connection","It has been requested to add the functionality to send x.509 certificate through SSL to the server while establishing HTTPClient connection. So basically, during authentication process, client would be able to send a (.cer) file through HTTPS. Essentially, something like this: 1) Package .p12 files/ .cer files as part of Resources, and 2) Extract data from these files (an API from TiHTTPClient) and send it over to server.",3
TIMOB-8200,"Android: webViews has a white background when turning on hardware acceleration ","h6.Issue When using android:hardwareAccelerated=""true"" (most likely in android manifest), the transparency of the WebView is lost and replaced by plain white background. Not all devices seem affected by this issue. h6.Non affected devices Droid Razr 2.3.5 Samsung Galaxy Tab p1000, Froyo(2.2) h6.Affected device Asus Transformer TF101, Honeycomb(ver3.1) h6.Repro sequence {code:title=app.js} var win = Ti.UI.createWindow({ backgroundImage : 'KS_nav_ui.png', //'/images/guide_fond_notice.png', navBarHidden : true, exitOnClose : true, top : '0dp', left : '0dp', right : '0dp', bottom : '0dp' }); var webView = Ti.UI.createWebView({ backgroundColor : 'transparent', html : 'This WebView\'s Background Must Be transparent', top : '50dp', left : '470dp', right : '0dp', bottom : '50dp' }); win.add(webView); win.open(); {code} h6.Setting HW accelerated via Tiapp.xml {code:title=Tiapp.xml} v8 true true true true false 1.8.2 com.appcelerator.com AcScreenConfs 1.0 egomez http:// not specified 2012 by egomez appicon.png false false default false false false true 95f32b4c-0c20-4f0e-86d5-3bc8ece20641 Ti.UI.PORTRAIT Ti.UI.PORTRAIT Ti.UI.UPSIDE_PORTRAIT Ti.UI.LANDSCAPE_LEFT Ti.UI.LANDSCAPE_RIGHT 11 {code} h6.Or via Manifest {code:title=platform/android/AndroidManifest.xml} 11 {code}",4
TIMOB-8241,"Core: Define Java coding standards","Define a document that outlines all Java coding standards any Java written for Appcelerator (internal or community contributions) should adhere to. This should represent more than syntax, but general design approaches and process flow. This document will be focused on language only. Platform Specific information will be contained inside another document.",5
TIMOB-8243,"Android: ScrollView - If a view is added to a scrollview, the view will not fill the screen","Steps to reproduce: 1. Run the following code on Android: {code} //Create a Ti.UI.View with scroll view and do not put any content var win = Ti.UI.createWindow(); win.backgroundColor = 'white'; var label = Ti.UI.createLabel({ text: 'View Size is: ', top: 20, left: 10, height: Ti.UI.SIZE, width: Ti.UI.SIZE, color: 'black' }); var scrollView = Titanium.UI.createScrollView({ contentHeight:'auto', contentWidth:'auto', showVerticalScrollIndicator:true, showHorizontalScrollIndicator:true }); var view = Ti.UI.createView(); var view2 = Ti.UI.createView({ backgroundColor:'red' }) scrollView.add(view2); win.addEventListener('postlayout', function layoutHandler(e) { win.removeEventListener('postlayout', layoutHandler); label.text = 'ScrollView\'s height and width: ' + scrollView.size.height + 'x' + scrollView.size.width + '\n' + 'Screen\'s height and width: ' + win.size.height + 'x' + win.size.width; win.addEventListener('postlayout', layoutHandler); }); win.add(scrollView); win.add(view); view.add(label); win.open(); {code} Actual: A white view appears. Expected: A red view should fill the screen similarly to iOS. See attachments",2
TIMOB-8301,"Android: Unable to create mapview","The user is having a tabbedview application. And he is trying to access mapview, by calling the Ti.map.createview. I dont have the complete code sample, but the mapview snippet, and the crash log. Here is the code {code} to setup tabs: app.tabs.stores = Ti.UI.createTab({ title:'Stores', icon:'/images/nav_icons/stores.png', tabIndex:nextTabIndex++ }); app.tabs.stores.window = gs.presenter.createStoreLocator(app.tabs.stores,{hideTabs:false}).window; tabGroup.addTab(app.tabs.stores); later, in the presenter: MapView = Ti.Map.createView({ regionFit:true, userLocation:false, visible:false }); mapView = MapView; mapView.left = 321; mapView.top = 45; // 44 (search) mapView.height = viewHeight; mapView.width = gs.ui.screenWidth; mapView.addEventListener('regionChanged', regionChanged); mapView.addEventListener('click', annotationClick); window.add(mapView); {code} i have attached the crash log.",2
TIMOB-8303,"iOS: Text Field/Area needs hasText method","h2. Problem TextField and TextArea hasText() method not functioning. h2. Test Case {code:lang=javascript|title=app.js} var win = Ti.UI.createWindow({ backgroundColor : 'white', exitOnClose : true, fullscreen : false, layout : 'vertical', title : 'hasText Demo' }); var textField = Ti.UI.createTextField({ color: '#336699', backgroundColor:'#eee', top: 10, left: 10, width: 250, height: 60, borderStyle: Ti.UI.INPUT_BORDERSTYLE_ROUNDED }); win.add(textField); var textArea = Ti.UI.createTextArea({ borderStyle: Ti.UI.INPUT_BORDERSTYLE_ROUNDED, backgroundColor:'#eee', color: '#336699', top: 10, left: 10, width: 250, height: 200 }); win.add(textArea); win.open(); textField.addEventListener('change', function(e){ Ti.API.info('hasText? ' + e.source.hasText()); }); textArea.addEventListener('change', function(e){ Ti.API.info('hasText? ' + e.source.hasText()); }); {code}",1
TIMOB-8306,"Android: Upgrade V8 to 3.9.24","We should upgrade to a newer version of V8. One of the main new features that has been implemented is incremental GC. This also exposes some additional API that can help us better tune the GC. Targeting V8 version 3.9.24 (3.9 stable branch).",3
TIMOB-8308,"Android: Javascript array [] seems to have some inconsistence behavior compared to iOS","*Code* Attached with this ticket. *Expected behavior* When you tap on the button, DDMS should show the following in the output: {code} [INFO] print_object > [object Object] [INFO] object data: [object Object] [INFO] object data.screen_name: bhushan,bhaskar,deore [INFO] object data.screen_name[0]: bhushan {code} *Actual behavior* What it actually prints out is the following: {code} INFO/TiAPI(4756): print_object > {screen_name=[Ljava.lang.Object;@40576ad0, idea_title=[Ljava.lang.Object;@40576b18} INFO/TiAPI(4756): object data: [object Object] INFO/TiAPI(4756): object data.screen_name: undefined {code} *Notes* -As you can see, it doesn't even print out 'object data.screen_name[0]', since the array itself seems to be 'undefined'. -The expected behavior is what I get from the iOS simulator's output. -Only tested on the iOS simulator and HTC Sensation 4G running 2.3.x. -Marked as a parity issue, not sure if this is correct, please edit the ticket as appropriate. -HD ticket: http://support-admin.appcelerator.com/display/APP-927227",1
TIMOB-8314,"iOS: Close event is not firing when closing a window","h4. Problem description I have a NavigationGroup, and two windows. Intermittently, when the second window is closed, the first window goes comatose (won't respond to any clicks). h4. Actual results the window is not throwing the close event when closing. h4. Expected results the window should throw the close event when closing h4. Test case 1. Create a mobile project 2. Add this three files {code:title=app.js|borderStyle=solid} var FirstWindow=Ti.UI.createWindow({ url:'MOMain.js', layout:'vertical', navBarHidden:false }); Ti.App.NavGroup=Ti.UI.iPhone.createNavigationGroup({window:FirstWindow}); var NavBase=Ti.UI.createWindow(); NavBase.add(Ti.App.NavGroup); NavBase.open(); // this opens the ""root"" window, which is FirstWindow, automatically {code} {code:title=MOMain.js|borderStyle=solid} var MainWin=Ti.UI.currentWindow; function OnFocus(evt) { if (evt.source == MainWin) { Ti.App.CurrentWindow=MainWin; } } MainWin.title='Here is something'; Ti.App.CurrentWindow=MainWin; MainWin.addEventListener('focus',OnFocus); function SetupButtonClick() { var SecondWin=Ti.UI.createWindow({ url:'MOSetup.js', layout:'vertical', navBarHidden:false }); Ti.App.NavGroup.open(SecondWin,{animated:true}); } var SetupButton=Ti.UI.createButton({width:200, height:100, title:'Hit Me'}); SetupButton.addEventListener('click',SetupButtonClick); MainWin.add(SetupButton); {code} {code:title=MOMain.js|borderStyle=solid} var Win2=Ti.UI.currentWindow; function HandleiPhoneCloseEvent() { if (Ti.App.DevelopmentMode) Ti.API.info('# Window HandleiPhoneCloseEvent fired'); Win2.removeEventListener('close',HandleiPhoneCloseEvent); Win2=null; // attempt to release the window's memory } Win2.title='Window 2'; Ti.App.CurrentWindow=Win2; Win2.addEventListener('close',HandleiPhoneCloseEvent); // catches the iPhone NavGroup back button close {code} 3. Run the app 4. Click on the ""Hit Me"" button 5. Click the navgroup's back button 6. Try to click on the ""Hit Me"" button again h4. Extra info This seems to be timing dependent, so you may have to repeat the 2 clicks several times. I can make it happen in under 30 seconds...usually within 5 seconds. My best reproduction comes by waiting 2.5 seconds before clicking the back button. If you have trouble reproducing this, vary the time between seeing the second window and clicking the back button (faster and then slower). After some investigation, I can see that the 'close' event of the second window never fires when the problem occurs (neither does the focus event of the first window). This seems to point to a serious flaw. In a larger app, the failure occurs 80% of the time. Our app is totally dead in the water because of this, and we need to release it soon. Can you please take a look into this? Please note that I've reduced this down about as far as possible, while still demonstrating the error. Removing any of the references to Ti.App or removing any of the event listeners hides the problem, but all of my apps are dependent on these.",3
TIMOB-8362,"Android: Ti.UI.createScrollView sizing incorrectly in a vertical layout","h2.Problem Setting Ti.UI.createScrollView.height to Ti.UI.SIZE causes the scrollView to take up the entire screen. If navBarHidden:true is set in app.js, a scrollView whose contents are minor will now scroll. This did not occur in Android 2.2. h2.Steps to Reproduce # Make a project with the below app.js. # Run in Android 4.0 emulator You will see that most of the screen (excluding the custom navbar) is red. If you click and drag, you will see it scroll even though the components are very minor. One other point of interest, I added a label at the bottom of the window, but it is not visible since the scrollview wants to take up the entire parent. {code:title=Bar.java|borderStyle=solid} var win = Ti.UI.createWindow({ backgroundColor: '#7B6700', exitOnClose:true, layout:'vertical', navBarHidden:true }); var NavBarView = Ti.UI.createView({height: '25dp', top:0, backgroundColor: 'green', width:'100%'}); var View1 = Ti.UI.createScrollView({left:'3dp', right:'3dp', height: Ti.UI.SIZE, showVerticalScrollIndicator:true, scrollType:'vertical', layout:'vertical', backgroundColor: 'red', showHorizontalScrollIndicator:false, touchEnabled: true }); var button = Ti.UI.createButton({title: 'Click', width: '100dp', height: '50dp' }); button.addEventListener('click', ButtonClick); function ButtonClick(e) { Ti.API.info('View1 height: ' + View1.size.height); } Label1 = Ti.UI.createLabel({text:'Label 1'}); View1.add(button); win.add(NavBarView); win.add(View1); win.add(Label1); win.open(); {code}",3
TIMOB-8332,"Android: tableView textField focus is lost while typing","h2. Problem description TableView textField loses focus when typing in. h2. Steps to reproduce Create a tableView and a tableViewRow with a textField. Click on the textField and start typing some text Result: after the first character, focus on the textField is lost. {code:lang=javascript|name=app.js} var win = Ti.UI.createWindow({ backgroundColor:'black' }); var data = []; var tableview; var row = Ti.UI.createTableViewRow({ clickName: 'row' }); var textfield = Titanium.UI.createTextField({ width: '80%', height: 80, color: '#000', returnKeyType: Titanium.UI.RETURNKEY_DONE, enableReturnKey: true, keyboardType: Titanium.UI.KEYBOARD_ASCII, autocorrect: false, hintText: 'Enter text Field', textAlign: 'left', clearOnEdit: false, borderStyle: Titanium.UI.INPUT_BORDERSTYLE_ROUNDED, clearButtonMode: Titanium.UI.INPUT_BUTTONMODE_ONFOCUS, leftButtonMode: Titanium.UI.INPUT_BUTTONMODE_ALWAYS }); textfield.font = { fontSize: '15sp', fontFamily: 'Arial' }; textfield.autocorrect = true; textfield.borderStyle = Titanium.UI.INPUT_BORDERSTYLE_NONE; row.add(textfield); data = [row]; tableview = Titanium.UI.createTableView({ data: data, rowBackgroundColor: 'white', }); win.add(tableview); win.open(); {code} h2. Additional notes Ticket associated: http://support-admin.appcelerator.com/display/APP-682796",3
TIMOB-8342,"Android: keyDispatchingTimedOut when trying to resume an app from background to foreground","*Code* I personally would say majority of Titanium Android apps, but for this ticket, please try it with the KitchenSink app. *Expected behavior* When you put an app into the background, and bring it back into the foreground, it should work perfectly fine. *Actual behavior* The app seems to show a black background for 1-2 seconds and then restarts. *Steps to reproduce* I can reproduce this issue 3 out of 5 times, by doing the following: *1.* If you have the KitchenSink app open in memory from before, kill it. We want to make sure we start from a clean slate. *2.* Make sure you have your USB cable connected to your laptop and phone. *3.* Run the KitchenSink app, wait for it to load and press the home button (don't press the back button, but instead the home button!) *4.* Run a few other apps in the background, I ran 'Gmail', 'Contacts', 'Internet', 'Peep', 'Places', 'Stocks' and 'Market'. It's important that you press the home button and NOT the back button! (NOTE if it doesn't work for you the first time, try opening more or even less apps, it might make a difference, depending on the device's specs). *5.* Once you have some apps running in the background, make sure you are back on the main home screen. *6.* Press the power button (lock your screen, turn the screen off, but don't power the device off!) *7.* Unplug the USB cable. *8.* Unlock your phone. *9.* Press on the KitchenSink app icon. *10.* Expect to see a black background for a second or two and then it will restart the app. *11.* If you don't, repeat from step 1. *Notes* -Different apps behave differently. The KitchenSink app, for example, seems to show a black background for 1-2 seconds and then restart the whole app. Other apps, such as Mister (from Google Play), actually shows a black screen and never continues to do anything else. The Jiffy Lube app, restarts and has the loading screen image visible as the background border. -KitchenSink was packaged with a 2.0 CI build. -Mister on Google Play is packaged with a 1.9.0.v20120209110134 build. -Jiffy Lube on Google Play is packaged with the 1.8.2 build. -If it doesn't work the first time, please keep trying for a while. Sometimes it takes a few tries, before you can reproduce this issue. Also try to restart your device, so all other apps are unloaded from memory. Try to open a few more apps, or maybe even less apps, it should eventually be reproducible. -Only tested on a HTC Sensation 4G, running Android 2.3.x.",1
TIMOB-8368,"iOS: soft keyboard behavior during orientation change is now different across handheld devices","Description: While writing bug TIMOB-8363 we checked the behavior of this iOS feature on a variety of devices and found new behavior but unique in all of them. For the 4.0.2 device, the keyboard is not rendered correctly during rotation (see TIMOB 8363) On 4.3.5 when starting with the soft keyboard on screen, on orientation change, the keyboard animates off-screen then is redrawn after the UI has handled the orientation change. This occurred on both portrait to landscape and landscape to portrait orientation changes. On iPod 5.1 the same behavior like on iPod 4.3.5, but this occurs only when making a portrait to landscape orientation change. For landscape to portrait orientation changes, the soft keyboard does not leave the screen during the orientation change, it simply rotates with the other UI elements. Steps to reproduce: 1) Using SDK 2.0.0.v20120328000206 build and install KS 2) Bring up the soft KB 3) Rotate the device Result: All devices show unique behavior, but in general there is a KB redraw. The older behavior was that the KB stayed on screen and rotated with the UI. Expected: The KB stays on screen and rotates with the UI. Notes: Does not occur with 1.8.2",1
TIMOB-8383,"iOS: Feature to add a property to detect if keyboard is being displayed or not","It has been requested to add a new feature to check if soft keyboard on the device is displayed or not. ",1
TIMOB-8414,"Android: Debugger - On V8, JNIUtil error messages appear when debugging with breakpoints","Steps to reproduce: 1. Unzip and import attachment 2. From https://wiki.appcelerator.org/display/tp/Debugger+Test+Plan, execute test case 1013 Actual: After step 9, the following error messages appear: {code} E/JNIUtil ( 398): !!! Unable to convert unknown Java object class 'org.appcelerator.kroll.KrollRuntime$1' to Js value !!! E/JNIUtil ( 398): !!! Unable to convert unknown Java object class 'org.appcelerator.kroll.KrollRuntime$1' to Js value !!! E/JNIUtil ( 398): !!! Unable to convert unknown Java object class 'org.appcelerator.kroll.KrollRuntime$1' to Js value !!! {code} Even though these error messages appear, it does not seem to affect the debugger i.e. the debugger does not terminate and I am still getting expected results from the debugger test plan. Expected: Error messages should not appear. Note: * The error messages do not appear in 1.8.2 * Only tested in v8. Did not test in rhino. * The error messages appear only when using breakpoints.",1
TIMOB-8417,"iOS: Textfield in a scrollview scrolls if bluetooth keyboard is connected to iPad","h3. Code h1. Please test on the iPad device {noformat} var win = Ti.UI.createWindow({ backgroundColor:'white' }); var field = Ti.UI.createTextField({ hintText: 'password', color:'#666', width:'94%', left: '3%', top: 140, width: '50%', height: 45, borderRadius:0, borderStyle:Titanium.UI.INPUT_BORDERSTYLE_BEZEL, passwordMask: true }); var scroll = Ti.UI.createScrollView({ left: 11, top: 12, width: 433, height: 390, contentHeight:'auto', contentWidth: 'auto', }); scroll.add(field); win.add(scroll); win.open(); {noformat} h3. Expected Behavior Clicking on the textField should not scroll it up when a bluetooth keyboard is connected to the iPad. h3. Actual Behavior On connecting the keyboard and clicking on the textfield, the textfield scrolls up as if the soft keyboard is present.",1
TIMOB-8418,"iOS: AudioPlayer is failing for some mp3, even if are in a supported format/encoding.","h4. Problem Description This doesn't seem to work for me, the mp3 plays fine via a web browser though. The code is correct so internally it doesn't like the file format. Is there a reason for this or something I can do (including encoding the audio differently) so that it's compatible. 90% of the audio files I encode all work, it's only a small number that don't and they are encoded the same way always. Replacing the audio file with something else works fine. This is the last stumbling block to release my app. h4. Actual Results One file it's working, one it's not. EVen if they are encoded in the same way. h4. Expected results Similar encoded mp3 files should play just fine h4. Test Case 1. Create a new mobile Project 2. Add this code {code} var win = Ti.UI.createWindow(); var vurl = ""http://www.voxsci.com/turtle2.mp3""; Ti.API.info(vurl); var streamer = Titanium.Media.createAudioPlayer({ allowBackground: true, url:vurl, preload:true }); streamer.start(); Ti.API.info(""Audio started""); win.open(); {code} 3. If you change the vurl to ""http://www.voxsci.com/turtle1.mp3"", it will work just fine. h4. Extra info I checked the files, they are similar: Mono, 44100hz, 32 bits float and they work in browser and audacity. ",2
TIMOB-9153,"Android: Deployment: Android Emulator intermittently fails to launch app after timed out","Emulator launches and fails to load app with timed out log: [INFO] logfile = /Users/dhyde/Documents/Titanium Studio 2.0.0 Workspace/NewProject/build.log [INFO] Building NewProject for Android ... one moment [INFO] Titanium SDK version: 2.0.0 (03/28/12 18:32 7c5487f) [ERROR] Timed out waiting for emulator to be ready, you may need to close the emulator and try again Steps to Reproduce: 1. Create project, launch on emulator. Expected Result: App should launch. Actual Result: Intermittently app does not install. Timed out error.",2
TIMOB-8425,"iOS: Textfield in scrollview does not slide back to original position on blur","h3. Code Test this code in landscape orientation {noformat} var win = Ti.UI.createWindow({ backgroundColor:'white' }); var formboxLeft = Ti.UI.createView({ backgroundImage:'bg-white-box--with-shadow.png', left: 20, top: 265, width: 460, height: 420, }); var field = Ti.UI.createTextField({ hintText: 'password', color:'#666', width:'94%', left: '3%', top: 140, width: '50%', height: 45, borderRadius:0, borderStyle:Titanium.UI.INPUT_BORDERSTYLE_BEZEL, passwordMask: true }); var scroll = Ti.UI.createScrollView({ left: 11, top: 12, width: 433, height: 390, contentHeight:'auto', contentWidth: 'auto', }); scroll.add(field); formboxLeft.add(scroll); win.add(formboxLeft); win.open(); {noformat} h3. Expected Behavior Clicking on the textfield should bring up the keyboard and on textfield blur (keyboard down), the textfield should scroll back to original position h3. Actual Behavior Textfield does not scroll back to original position and there is a gap that can be seen between the textfield and the border of the scrollview.",1
TIMOB-8431,"iOS: 4.3: KitchenSink: Base UI > Views > Map View: mapview annotation view does not appear","When KitchenSink > UI > Views > Map View is run, the annotation view (white box with title and subtitle) is not displayed on mapview load. However, clicking the annotation pin will correctly display the annotation view. Otherwise, the annotation view correctly displays on mapview load on the iPad3 5.1 and iPad/iPhone Simulator 5.0. This is a regression, as it works on iPad/iPhone Simulator 4.3 using SDK 1.8.2. This is not directly related to https://jira.appcelerator.org/browse/TIMOB-5305, as the bug is fixed on the iPad 4.3 device and simulator. Steps to Reproduce: 1. Run KitchenSink > UI > Views > Map View on iOS. Expected Result: Annotation view should be visible. Actual Result: Annotation view not visible.",1
TIMOB-8437,"Android: TextField layout bug on tablet","h6.Issue When using the texfield on android tablet in the following way, the background of the textfield and its cursor becomes invisible. Modal property true should cause the issue. h6.Tested on Droid Razr 2.3.5 > non affected Asus Transformer Tf101 with honeycomb(3.1) > affected h6.Repro sequence {code} /** * @author Carlo Blanco Benitez */ var win = Ti.UI.createWindow({ backgroundImage:'guide_fond_notice.png',//backgroundImage attached navBarHidden:true, exitOnClose:true, //modal:true,//having modal enabled backgroundColor:'black', top:'0dp', left:'0dp', right:'0dp', bottom:'0dp' }); var wrapper = Ti.UI.createView({ top:'0dp', left:'0dp', right:'0dp', bottom:'0dp' }); win.add(wrapper); var textField = Ti.UI.createTextField({ color:'black', width:'100dp', height:'50dp', returnKeyType: Titanium.UI.RETURNKEY_SEARCH, autocorrect:false }); wrapper.add(textField); win.open(); {code} ",3
TIMOB-8439,"Android: Unable to get any results when pulling events by date range","h6.Issue Exception is thrown as Android is unable to get any results when pulling events by date range h6.Tested on sdk-version: 2.1.0.v20120329000337 h6.Runtime engines Same thing happens with V8 and Rhino. h6.Device Galaxy Tab 7 Plus model GT-P6210 Android version 3.2 Kernel 2.6.36-P6210UEKJC-CL567728 se.infra@SEI-20 #3 h6.Repro sequence {code} // this sets the background color of the master UIView (when there are no windows/tab groups on it) Titanium.UI.setBackgroundColor('#000'); var win = Titanium.UI.createWindow({ title:'Calendar', backgroundColor:'#fff' }); win.open(); var startDate = new Date(); startDate.setFullYear(startDate.getFullYear()-1,0,1); Ti.API.info('startDate: '+startDate); var endDate = new Date(); endDate.setFullYear(endDate.getFullYear()+1,0,1); Ti.API.info('endDate: '+endDate); function showCalendars(calendars) { for (var i = 0; i < calendars.length; i++) { Ti.API.info(calendars[i].name); Ti.API.info(JSON.stringify(calendars[i])); } } Ti.API.info('ALL CALENDARS:'); showCalendars(Ti.Android.Calendar.allCalendars); Ti.API.info('SELECTABLE CALENDARS:'); showCalendars(Ti.Android.Calendar.selectableCalendars); var out = []; Ti.API.info('TRY TO GET EVENTS IN ALL CALENDARS:'); var calendars = Ti.Android.Calendar.allCalendars Ti.API.info(JSON.stringify(calendars)); for (var i=0; i < calendars.length; i++) { Ti.API.info(JSON.stringify(calendars[i])); try { var cal_events = calendars[i].getEventsBetweenDates(startDate,endDate); for (var j=0; j < cal_events.length; j++) { out.push(cal_events[j]); }; } catch(err) { Ti.API.error(""ERROR ""+err); } }; Ti.API.info('TRY TO GET EVENTS IN SELECTABLE CALENDARS:'); var calendars = Ti.Android.Calendar.selectableCalendars Ti.API.info(JSON.stringify(calendars)); for (var i=0; i < calendars.length; i++) { Ti.API.info(JSON.stringify(calendars[i])); try { var cal_events = calendars[i].getEventsBetweenDates(startDate,endDate); for (var j=0; j < cal_events.length; j++) { out.push(cal_events[j]); }; } catch(err) { Ti.API.error(""ERROR ""+err); } }; Ti.API.info('ALL THE EVENTS:'); Ti.API.info(JSON.stringify(out)); {code} h6.Console output {code} 03-30 10:49:38.935: I/TiApplication(23751): (main) [98,98] Titanium 2.1.0 (2012/03/29 00:04 ac3852d) 03-30 10:49:38.945: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:38.955: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:38.960: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:38.975: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:38.995: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.010: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.025: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.035: D/dalvikvm(23751): GC_CONCURRENT freed 281K, 6% free 6505K/6919K, paused 1ms+1ms 03-30 10:49:39.040: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.055: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.075: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.080: D/dalvikvm(23751): Trying to load lib /data/data/info.rborn.calendar/lib/libstlport_shared.so 0x4079b9e0 03-30 10:49:39.080: I/TiApplication(23751): (main) [146,244] Titanium Javascript runtime: v8 03-30 10:49:39.080: D/dalvikvm(23751): Added shared lib /data/data/info.rborn.calendar/lib/libstlport_shared.so 0x4079b9e0 03-30 10:49:39.080: D/dalvikvm(23751): No JNI_OnLoad found in /data/data/info.rborn.calendar/lib/libstlport_shared.so 0x4079b9e0, skipping init 03-30 10:49:39.080: D/dalvikvm(23751): Trying to load lib /data/data/info.rborn.calendar/lib/libkroll-v8.so 0x4079b9e0 03-30 10:49:39.090: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.090: I/TiRootActivity(23751): (main) [0,0] checkpoint, on root activity create, savedInstanceState: null 03-30 10:49:39.095: D/dalvikvm(23751): Added shared lib /data/data/info.rborn.calendar/lib/libkroll-v8.so 0x4079b9e0 03-30 10:49:39.105: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.120: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.140: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.140: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.140: I/LiveWallpaper(2895): Engine.onVisibilityChanged() - false 03-30 10:49:39.140: I/SurfaceFlinger(2698): id=1870 Removed com.android.launcher/com.android.launcher2.Launcher idx=2 Map Size=3 03-30 10:49:39.150: I/SurfaceFlinger(2698): id=1870 Removed com.android.launcher/com.android.launcher2.Launcher idx=-2 Map Size=3 03-30 10:49:39.390: E/TiApplication(23751): (KrollRuntimeThread) [298,298] APP PROXY: ti.modules.titanium.app.AppModule@407b5cd0 03-30 10:49:39.485: I/TiAPI(23751): startDate: Sat Jan 01 2011 10:49:39 GMT+0100 (CET) 03-30 10:49:39.485: I/TiAPI(23751): endDate: Tue Jan 01 2013 10:49:39 GMT+0100 (CET) 03-30 10:49:39.485: I/TiAPI(23751): ALL CALENDARS: 03-30 10:49:39.495: I/TiAPI(23751): My calendar 03-30 10:49:39.495: I/TiAPI(23751): {""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""} 03-30 10:49:39.495: I/TiAPI(23751): dan.tamas.tst@gmail.com 03-30 10:49:39.495: I/TiAPI(23751): {""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""} 03-30 10:49:39.495: I/TiAPI(23751): dan tamas 03-30 10:49:39.500: I/TiAPI(23751): {""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""} 03-30 10:49:39.500: I/TiAPI(23751): test 1 03-30 10:49:39.500: I/TiAPI(23751): {""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.500: I/TiAPI(23751): test 1 03-30 10:49:39.500: I/TiAPI(23751): {""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.500: I/TiAPI(23751): test 2 03-30 10:49:39.500: I/TiAPI(23751): {""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""} 03-30 10:49:39.500: I/TiAPI(23751): SELECTABLE CALENDARS: 03-30 10:49:39.505: I/TiAPI(23751): My calendar 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""} 03-30 10:49:39.505: I/TiAPI(23751): dan.tamas.tst@gmail.com 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""} 03-30 10:49:39.505: I/TiAPI(23751): dan tamas 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""} 03-30 10:49:39.505: I/TiAPI(23751): test 1 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.505: I/TiAPI(23751): test 1 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.505: I/TiAPI(23751): test 2 03-30 10:49:39.505: I/TiAPI(23751): {""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""} 03-30 10:49:39.505: I/TiAPI(23751): TRY TO GET EVENTS IN ALL CALENDARS: 03-30 10:49:39.515: I/TiAPI(23751): [{""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""},{""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""},{""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""},{""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""},{""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""},{""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""}] 03-30 10:49:39.515: I/TiAPI(23751): {""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""} 03-30 10:49:39.520: W/TiEvent(23751): (KrollRuntimeThread) [132,430] unable to get any results when pulling events by date range 03-30 10:49:39.520: I/TiAPI(23751): {""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""} 03-30 10:49:39.525: W/TiEvent(23751): (KrollRuntimeThread) [4,434] unable to get any results when pulling events by date range 03-30 10:49:39.525: I/TiAPI(23751): {""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""} 03-30 10:49:39.525: W/TiEvent(23751): (KrollRuntimeThread) [2,436] unable to get any results when pulling events by date range 03-30 10:49:39.525: I/TiAPI(23751): {""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.530: W/TiEvent(23751): (KrollRuntimeThread) [3,439] unable to get any results when pulling events by date range 03-30 10:49:39.530: I/TiAPI(23751): {""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.530: W/TiEvent(23751): (KrollRuntimeThread) [3,442] unable to get any results when pulling events by date range 03-30 10:49:39.535: I/TiAPI(23751): {""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""} 03-30 10:49:39.535: W/TiEvent(23751): (KrollRuntimeThread) [3,445] unable to get any results when pulling events by date range 03-30 10:49:39.535: I/TiAPI(23751): TRY TO GET EVENTS IN SELECTABLE CALENDARS: 03-30 10:49:39.540: I/TiAPI(23751): [{""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""},{""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""},{""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""},{""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""},{""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""},{""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""}] 03-30 10:49:39.540: I/TiAPI(23751): {""hidden"":false,""id"":""1"",""selected"":true,""name"":""My calendar""} 03-30 10:49:39.545: W/TiEvent(23751): (KrollRuntimeThread) [8,453] unable to get any results when pulling events by date range 03-30 10:49:39.545: I/TiAPI(23751): {""hidden"":false,""id"":""2"",""selected"":true,""name"":""dan.tamas.tst@gmail.com""} 03-30 10:49:39.545: W/TiEvent(23751): (KrollRuntimeThread) [3,456] unable to get any results when pulling events by date range 03-30 10:49:39.545: I/TiAPI(23751): {""hidden"":false,""id"":""3"",""selected"":true,""name"":""dan tamas""} 03-30 10:49:39.550: W/TiEvent(23751): (KrollRuntimeThread) [3,459] unable to get any results when pulling events by date range 03-30 10:49:39.550: I/TiAPI(23751): {""hidden"":false,""id"":""4"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.550: W/TiEvent(23751): (KrollRuntimeThread) [3,462] unable to get any results when pulling events by date range 03-30 10:49:39.550: I/TiAPI(23751): {""hidden"":false,""id"":""5"",""selected"":true,""name"":""test 1""} 03-30 10:49:39.555: W/TiEvent(23751): (KrollRuntimeThread) [3,465] unable to get any results when pulling events by date range 03-30 10:49:39.555: I/TiAPI(23751): {""hidden"":false,""id"":""6"",""selected"":true,""name"":""test 2""} 03-30 10:49:39.560: W/TiEvent(23751): (KrollRuntimeThread) [2,467] unable to get any results when pulling events by date range 03-30 10:49:39.560: I/TiAPI(23751): ALL THE EVENTS: 03-30 10:49:39.560: I/TiAPI(23751): [] 03-30 10:49:39.590: D/dalvikvm(23751): GC_FOR_ALLOC freed 246K, 6% free 6610K/6983K, paused 13ms 03-30 10:49:39.590: I/dalvikvm-heap(23751): Grow heap (frag case) to 7.996MB for 1536016-byte allocation 03-30 10:49:39.620: D/dalvikvm(23751): GC_FOR_ALLOC freed <1K, 5% free 8109K/8519K, paused 12ms 03-30 10:49:39.620: W/CursorWrapperInner(23751): Cursor finalized without prior close() 03-30 10:49:39.645: W/CursorWrapperInner(23751): Cursor finalized without prior close() 03-30 10:49:39.645: D/dalvikvm(23751): GC_CONCURRENT freed 1K, 5% free 8108K/8519K, paused 1ms+1ms 03-30 10:49:39.645: W/CursorWrapperInner(23751): Cursor finalized without prior close() 03-30 10:49:39.645: W/CursorWrapperInner(23751): Cursor finalized without prior close() 03-30 10:49:39.670: D/dalvikvm(23751): GC_FOR_ALLOC freed 14K, 5% free 8094K/8519K, paused 12ms 03-30 10:49:39.670: I/dalvikvm-heap(23751): Grow heap (frag case) to 8.630MB for 682256-byte allocation 03-30 10:49:39.690: D/dalvikvm(23751): GC_FOR_ALLOC freed 0K, 6% free 8760K/9223K, paused 12ms 03-30 10:49:39.725: D/dalvikvm(23751): GC_CONCURRENT freed 0K, 6% free 8760K/9223K, paused 1ms+1ms 03-30 10:49:39.730: I/TiRootActivity(23751): (main) [0,0] checkpoint, on root activity resume. activity = info.rborn.calendar.CalendartestActivity@407f22c8 03-30 10:49:39.735: D/WindowManager(2827): addWindowToListInOrder() : current mSkipWidgetFocus='true' 03-30 10:49:39.740: I/SurfaceFlinger(2698): id=1872(1) createSurface 0x40514 for pid 23751 (1x1),2 flag=0, info.rborn.calendar/info.rborn.calendar.CalendartestActivity 03-30 10:49:39.745: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.750: I/WindowManager(2827): Putting input method here! 03-30 10:49:39.750: D/WindowManager(2827): w.mAttrs.token=ActivityRecord{40decca0 info.rborn.calendar/.CalendartestActivity} 03-30 10:49:39.750: D/WindowManager(2827): w.mToken=AppWindowToken{41ae2ef8 token=ActivityRecord{40decca0 info.rborn.calendar/.CalendartestActivity}} 03-30 10:49:39.750: D/WindowManager(2827): Desired input method target: Window{40ba9a60 info.rborn.calendar/info.rborn.calendar.CalendartestActivity paused=false} 03-30 10:49:39.750: D/WindowManager(2827): Current focus: Window{40ba9a60 info.rborn.calendar/info.rborn.calendar.CalendartestActivity paused=false} 03-30 10:49:39.750: D/WindowManager(2827): Last focus: Window{40ba9a60 info.rborn.calendar/info.rborn.calendar.CalendartestActivity paused=false} 03-30 10:49:39.750: D/WindowManager(2827): IM target client: com.android.internal.view.IInputMethodClient$Stub$Proxy@41040b20 03-30 10:49:39.750: D/WindowManager(2827): IM target client binder: android.os.BinderProxy@41066c90 03-30 10:49:39.750: D/WindowManager(2827): Requesting client binder: android.os.BinderProxy@41066c90 03-30 10:49:39.750: D/CLIPBOARD(4466): Hide Clipboard dialog at Starting input: finished by someone else... ! 03-30 10:49:39.750: W/CPUclock(2827): mDVFSUpperLock.release() 03-30 10:49:39.750: D/CLIPBOARD(2827): Hide Clipboard dialog inside hideSoftInput() ! 03-30 10:49:39.750: D/CLIPBOARD(2827): Hide Clipboard dialog inside windowGainedFocus() ! 03-30 10:49:39.750: D/WindowManager(2827): token=AppWindowToken{41ae2ef8 token=ActivityRecord{40decca0 info.rborn.calendar/.CalendartestActivity}} 03-30 10:49:39.750: I/WindowManager(2827): Placing input method @10 03-30 10:49:39.765: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.765: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.765: I/ActivityManager(2827): Displayed info.rborn.calendar/.CalendartestActivity: +1s156ms 03-30 10:49:39.765: D/CLIPBOARD(23751): Hide Clipboard dialog at Starting input: finished by someone else... ! 03-30 10:49:39.770: D/KeyguardViewMediator(2827): setHidden false 03-30 10:49:39.770: D/TabletStatusBar(2886): lights on {code}",2
TIMOB-8455,"Android: Email Dialog - Email View does not appear on Kindle Fire","Description: While testing Email Dialog, I noticed that after picking an image email view does not appear. Does not occur on 1.8.2. Spets: 1. Run KitchenSink 2. Go to Base UI-Views-Email Dialog 3. Pick an image Expected result: Email view should appear Actual result: Email view is not shown",1
TIMOB-8459,"Android: KitchenSinkNook - Photo Gallery - After selecting an image from the photo gallery, it is not displayed","Steps to reproduce: 1. Launch KS Nook on the Kindle Fire 2. Navigate to Miscellaneous > Photo Gallery 3. Choose a photo Actual result: A gray image view is displayed Expected result: The image is displayed in the image view *Note* works in 1.8.2 Log is attached",1
TIMOB-8465,"Android: Activities don't get correctly handled if first opening a Window and then a TabGroup ","h2. Problem description The app opens a window for login - then opens a tabGroup. Android activities are no longer handled correctly. h2. Steps to reproduce See location for the project in the comments. Attaching logs relative to successful and failing case. Successful scenario: The first window is not included in a tab group. Click on on ""connect with facebook"" - then click the 'buy' button and click the ""facebook friends"" button (window i snow included in a tabGroup). Facebook friends are displayed. Failure scenario: Click on login with buddy beers and use the credentials: - test case added below h2. Additional notes login window when you start the app is 'ui/login/start.js' ; tabgroup is in 'ui/common.js' ; facebook api are invoked in 'ui/send/person_via_faceboook.js' and in 'lib/webservice.js' ",1
TIMOB-8470,"Android: Picker in scrollView not working","h6.Issue Picker in scrollView not working. h6.Tested on Android Emulator 2.2 Droid Razr 2.3.5 h6.Runtime Engines Rhino / V8 h6.Steps to reproduce 1. Run code below 2. Click the picker h6.Expected behavior See fully operational Pickers whose options render on screen h6.Repro sequence {code} Titanium.UI.setBackgroundColor('#000'); var win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff' }); var win5 = Titanium.UI.createScrollView({ contentHeight:'auto', left:15, right:5 ,layout:'vertical' }); var names = ['Joanie', 'Mickey', 'Jean-Pierre', 'Gustav', 'Raul', 'Mimi', 'Emily', 'Sandra', 'Carrie', 'Chachi']; var verbs = ['loves', 'likes', 'visits', 'loathes', 'waves to', 'babysits', 'accompanies', 'teaches', 'announces', 'supports', 'knows', 'high-fives']; var rows1 = []; for (var i = 0; i < names.length; i++) { rows1.push(Ti.UI.createPickerRow({title: names[i]})); } var rows2 = []; for (i = 0; i < verbs.length; i++) { rows2.push(Ti.UI.createPickerRow({title: verbs[i]})); } var rows3 = []; for (i = (names.length -1); i >=0; i--) { rows3.push(Ti.UI.createPickerRow({title: names[i]})); } var column1 = Ti.UI.createPickerColumn( { rows: rows1, font: {fontSize: ""12""} }); var column2 = Ti.UI.createPickerColumn( { rows: rows2, font: {fontSize: ""12""} }); var column3 = Ti.UI.createPickerColumn( { rows: rows3, font: {fontSize: ""12""} }); var picker = Ti.UI.createPicker({ useSpinner: true, visibleItems: 7, type : Ti.UI.PICKER_TYPE_PLAIN, top: 20, height: '200', columns: [ column1, column2, column3 ] }); picker.addEventListener('change', function(e) { Ti.API.info(e.selectedValue[0] + "" "" + e.selectedValue[1] + "" "" + e.selectedValue[2]); }); win5.add(picker); win1.add(win5); win1.open(); {code} ",1
TIMOB-8484,"iOS: Ti.UI.Window not restoring correctly after a youtube-in-app view exits","*Code* http://pastebin.com/NXYbpfRH *Expected behavior* When you run the app, watch the YouTube video, it should return without messing up any UI. *Actual behavior* Once the video has finished, it actually shows the status bar overlapping the window. *Steps to reproduce* 1) Click ""Watch YouTube Video"" 2) Click on webview to play Youtube video while holding device in PORTRAIT orientation 3) While video is loading, turn device to LANDSCAPE. You will notice that status bar moves to the PORTRAIT orientation. 4) While video is playing in LANDSCAPE, return device to PORTRAIT orientation (you will notice that statusbar is in proper position). 5) Return device to LANDSCAPE orientation, and end video by clicking ""Done"". 6) The Youtube player will close and the window will reopen with window's navbar underneath the status bar. *Notes* -Only happens on a device, I tried with an iPhone 3GS running 5.0.1. -HD ticket: http://support-admin.appcelerator.com/display/APP-333237",3
TIMOB-8492,"Android: Impossible to lock the app in Landscape mode","h4. Problem Description Have been trying to setup a tab app to be locked in landscape mode via tiapp.xml (modifying the android manifest): {code} {code} h4. Actual Results The tabbed app doesn't show in landscape h4. Expected results The tabbed app showing in landscape mode. h4. Test Case. 1. Create a new mobile Project 2. Replace the default android manifest section in the tiapp.xml with this: {code} {code} 4. Run h4. HD Discussion http://support-admin.appcelerator.com/display/APP-654753",2
TIMOB-8513,"iOS: Tableview shifting after 1.8.2 update","h4. Problem Description I have a tableview in a window. If I open that window using tab1.open(theWindow), the tableview appears as it should. BUT if I close that window using tab1.close(theWindow) and open it again later using the same tab1.open(theWindow), the tableview quickly shifts up to it's position. It is almost like it is animating 20px when the window is opened. I am NOT using any animations. Sample code below h4. Actual Results After the first time, the tableview appears animated. h4. Expected results Tableview without animation h4. Test Case 1. Create new mobile project. 2. Paste this code {code} //create main window var window1 = Titanium.UI.createWindow({ navBarHidden:true,tabBarHidden:true }); //create and add button to open window 2 var btn = Ti.UI.createButton({height:100,width:100}); window1.add(btn); //create window 2 for tableview var window2 = Titanium.UI.createWindow({ navBarHidden:true,tabBarHidden:true }); //create back button to go back to main menu var backBtn = Titanium.UI.createButton({height:30,width:50,top:10,left:10}); //create search bar var search = Titanium.UI.createSearchBar({ showCancel:false }); //create data for tableview var theData = [ { title:""One"", hasChild:true }, { title:""Two"", hasChild:true }, { title:""Three"", hasChild:true }, { title:""Four"", hasChild:true }, { title:""Five"", hasChild:true } ]; //create tableview var menu = Ti.UI.createTableView({ height:405, top:55, data:theData, search:search }); //add menu and back button to window 2 window2.add(menu); window2.add(backBtn); //Set up the Tab Group var tabGroup = Titanium.UI.createTabGroup(); var tab1 = Titanium.UI.createTab({ title:'window1', window: window1 }); //Add and open tabgroup tabGroup.addTab(tab1); tabGroup.open(); //button click events btn.addEventListener('click',function(){tab1.open(window2);}) backBtn.addEventListener('click',function(){tab1.close(window2);}) {code}",2
TIMOB-8621,"Android: Error creating Module projects with new installation of SDK r18 and Google APIs r8","When creating an Android module project, the process ends in error: {code} [ERROR] Couldn't find the Google APIs r8 add-on directory {code} 1. Create a new module project using titanium, for example: {code} dhydeMBPSnowLeopard:~ dhyde$ ""/usr/bin/python"" ""/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120407201726/titanium.py"" ""create"" ""--type=module"" ""--id=com.appcelerator.mymodule"" ""--name=MyModule"" ""--dir=/var/folders/Jt/Jte2czQvFoaxMh25z-WDKE+++TM/-Tmp-/module_temp8018343781039291630.tmp"" ""--platform=android"" ""--sdk=/Users/dhyde/Documents/android/android-sdk-macosx"" {code} Expected Result: Module project should be created.",1
TIMOB-8515,"Android: runtime error in ti/window.js","A client has encounter a problem in the window.js file in the SDK. I have not been able to reproduce it. There is a ""delete account"" button than when pressed, it will fire a global app event. Ti.App.fireEvent(); This event will close all the open windows, except the ""BaseWindow"" (heavyweight window in declared in app.js), including the one where the button is. The button is in a lightweight window that sits on top of the BaseWindow. After the windows are closed, a lightweight window (login window) opens on top of the BaseWidow (in place of the previously closed one). And this is where they're seeing this runtime error. ",3
TIMOB-8549,"Android: Memory Managment Issue","*Code* http://pastie.org/3732988 *Steps to reproduce* Run the app inside the emulator/device, load up ddms, watch the heap size increase. *Expected behavior* The code is creating and releasing Ti objects, so it should allocate and deallocate memory over time. *Actual behavior* It actually keeps building up and gradually increases the heap size, it doesn't seem to go down a lot, it mainly increases. *Notes* -You might have to run this for a few minutes, in order to replicate this behavior. -The app is opening a new window, and releases it. So you will see the window going back and forth, which is the expected behavior. It will automatically open/close the window over time. You should only have to observe the 'heap size' and 'allocated' in ddms. -Only tested on the emulator. -HD ticket: http://support-admin.appcelerator.com/display/APP-341636",5
TIMOB-8558,"iOS: Transport.py is not working in CI ","h4. Problem Description I've been running into issues with the 2.X CI builds and transport.py. Due to how we handle builds, I need to use transport.py for all submissions and ad hoc builds. Any of the 2.X or Master builds have this build issue. h4. Actual Results The build via transport.py is failing. h4. Expected Results The build via transport.py working just fine h4. Test Case 1. Create a new Titanium project targeting a 2.X CI build 2. Run the transport.py process as usual 3. Open in xcode and try to run in the simulator h4. Extra info When xcode tries to compile you will get the below error [TRACE] app property, ti.ui.defaultunit : system [INFO] wrote Resources/stylesheet.plist Traceback (most recent call last): File ""titanium/iphone/compiler.py"", line 7, in import os, sys, re, shutil, time, run, sgmllib, codecs, tempfile File ""/Users/benjamin/Dev/Projects/Ti/myTravel/test/build/iphone/titanium/iphone/run.py"", line 2, in from tools import ensure_dev_path ImportError: No module named tools Command /bin/sh failed with exit code 1 I tried this again today using the below build version. h4. HD Discussion http://support-admin.appcelerator.com/display/APP-522817 ",2
TIMOB-8562,"BlackBerry: Adapt scons script (SConstruct) [build script for mobile_sdk] to build for blackberry",NULL,3
TIMOB-8563,"BlackBerry: Support ability to create new blackberry project in Titanium Studio","Work with the studio team to integrate project creation ",2
TIMOB-8564,"BlackBerry: Run and debug on device/simulator from Titanium Studio","- Some testing/investigation required to figure out how this can be accomplished, can likely use help from RIM technical contact to mimic what's available in the QNX IDE - minimum: trap console logging",7
TIMOB-8565,"BlackBerry: Extend the ndk classes to create the shell application"," Extend the ndk classes to create our shell application that will contain the app.js and the kroll and v8 runtimes (equiv. android/titanium/.project) - learn what is needed to create the blackberry shell app to contain the app.js as resource - Create actual classes extending the classes in the ndk, they will form the titanium library - Do the minimum to get the app up and loading the js file, leave the rest stubbed out with TODOs - create file templates for the shell app - link with libV8 and Kroll",2
TIMOB-8566,"BlackBerry: Build v8 on the QNX ndk as static lib","Possibly create wrappers for the v8",3
TIMOB-8567,"BlackBerry: Build blackberry native app","Build blackberry native app from shell application, v8 and Kroll from titanium (tie in with builder)",10
TIMOB-8568,"BlackBerry: Integrate with the cascades framework",NULL,3
TIMOB-8569,"BlackBerry: Integrate unit tests","need more info from Vishal, drillbit vs module tests?",20
TIMOB-8570,"BlackBerry: Run on simulator and device","minimum BB10 for demo",5
TIMOB-8572,"BlackBerry: Implement Analytics module",NULL,20
TIMOB-8573,"BlackBerry: Implement BlackBerry specific components",NULL,3
TIMOB-8574,"BlackBerry: Implement important Ti.API functionality","This may be completed. It only looks like the following are required: * Titanium.API.debug * Titanium.API.error * Titanium.API.info * Titanium.API.log * Titanium.API.timestamp * Titanium.API.trace * Titanium.API.warn",19
TIMOB-8576,"BlackBerry: Implement important Titanium.Codec functionality",NULL,2
TIMOB-8577,"BlackBerry: Implement Contacts module",NULL,20
TIMOB-8579,"BlackBerry: Implement Facebook module",NULL,8
TIMOB-8580,"BlackBerry: Implement important Titanium.Filesystem functionality","* Titanium.Filesystem * Titanium.Filesystem.applicationDataDirectory * Titanium.Filesystem.File * Titanium.Filesystem.File.append * Titanium.Filesystem.File.createDirectory * Titanium.Filesystem.File.deleteFile * Titanium.Filesystem.File.exists * Titanium.Filesystem.File.getNativePath * Titanium.Filesystem.File.nativePath * Titanium.Filesystem.File.read * Titanium.Filesystem.File.writable * Titanium.Filesystem.File.write * Titanium.Filesystem.getFile * Titanium.Filesystem.resourcesDirectory * Titanium.Filesystem.tempDirectory h3. Test code: Reading a file from the Resources dir {code} Ti.API.info('------------------------'); Ti.API.info('Testing resources directory reading app.js'); var app_js = Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory, 'app.js'); var blob = app_js.read(); Ti.API.info('---------'); Ti.API.info(blob.text); {code} Creating, writing, and reading a file from the data dir {code} Ti.API.info('------------------------'); Ti.API.info('Testing data directory reading writing and reading'); var file = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory, 'hello_world.txt'); if(!file.exists()) { Ti.API.info('file does not exist'); file.write('this is a test'); Ti.API.info('file exists? ' + file.exists()); } Ti.API.info('---------'); var blob = file.read(); Ti.API.info(blob.text); {code} Getting the directory listing from the data dir {code} Ti.API.info('------------------------'); Ti.API.info('Testing data directory get listing'); var directory = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory); var files = directory.getDirectoryListing(); for(var i = 0; i < files.length; i++) { Ti.API.info('====================='); var file = files[i]; Ti.API.info('filename: ' + file); var _file = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory, file); Ti.API.info('isDirectory: ' + _file.isDirectory()); Ti.API.info('isFile: ' + _file.isFile()); } {code}",17
TIMOB-8582,"BlackBerry: Implement important Gesture functionality","Implement the Gesture module. h3. Acceptance Test {code} function orientationToString(orientation) { switch (orientation) { case Ti.UI.PORTRAIT: return 'portrait'; case Ti.UI.UPSIDE_PORTRAIT: return 'upside portrait'; case Ti.UI.LANDSCAPE_LEFT: return 'landscape left'; case Ti.UI.LANDSCAPE_RIGHT: return 'landscape right'; case Ti.UI.FACE_UP: return 'face up'; case Ti.UI.FACE_DOWN: return 'face down'; default: return 'unknown'; } } var win = Ti.UI.createWindow({ backgroundColor: 'red', layout: 'vertical' }); var labelA = Ti.UI.createLabel({ width: Ti.UI.FILL, text: 'e.orientation = N/A' }); win.add(labelA); var labelB = Ti.UI.createLabel({ width: Ti.UI.FILL, text: 'Gesture.orientation = N/A' }); win.add(labelB); var labelC = Ti.UI.createLabel({ width: Ti.UI.FILL, wrap: true, text: 'No shake yet.' }); win.add(labelC); function onShake(e) { Ti.API.info('Shake: {' + e.x + ', ' + e.y + ', ' + e.z + '}'); labelC.text = 'Shake!'; win.backgroundColor = 'yellow'; setTimeout(function() { labelC.text = 'No shake yet.'; win.backgroundColor = 'red'; }, 500); } var toggleShake = Ti.UI.createButton({ title: 'Toggle Shake' }); var shakeEnabled = false; toggleShake.addEventListener('click', function() { shakeEnabled ? Ti.Gesture.removeEventListener('shake', onShake) : Ti.Gesture.addEventListener('shake', onShake); shakeEnabled = !shakeEnabled; }); win.add(toggleShake); Ti.Gesture.addEventListener('orientationchange', function(e) { labelA.text = 'e.orientation = ' + orientationToString(e.orientation); labelB.text = 'Gesture.orientation = ' + orientationToString(Ti.Gesture.orientation); }); win.open(); {code} # Rotate the device and flip it around. The first two labels should be equal and display the current orientation. # Try shaking the device, nothing should happen. # Click the ""Toggle Shake"" button and shake again. The background should flash yellow. # Try clicking the ""Toggle Shake"" button and shake again. Nothing should happen.",17
TIMOB-8583,"BlackBerry: Implement important Titanium.Locale functionality",NULL,19
TIMOB-8585,"BlackBerry: Implement Media module",NULL,20
TIMOB-8587,"BlackBerry: Implement Network module for Anvil",NULL,8
TIMOB-8589,"BlackBerry: Implement important Titanium.Stream functionality",NULL,8
TIMOB-8591,"BlackBerry: Implement important Titanium.Utils functionality",NULL,17
TIMOB-8592,"BlackBerry: Implement important Titanium.XML functionality",NULL,17
TIMOB-8593,"BlackBerry: Implement important Titanium.Yahoo functionality",NULL,15
TIMOB-8594,"BlackBerry: Full support for builder script","Implement all targets",20
TIMOB-8597,"BlackBerry: Get KitchenSink to work",NULL,30
TIMOB-8598,"BlackBerry: Setup and test guide","Guide for QE/developers to setup and test the Blackberry port of Titanium SDK using KitchenSink Should be placed on a separate page in this space: https://wiki.appcelerator.org/display/PEBKBRY/Home",2
TIMOB-8602,"BlackBerry: Integrate the final deliverable into the current build, testing and development infrastructure",NULL,20
TIMOB-8610,"Android: Tab.open(windowName) doesn't open a new window inside the Tab container","In android tab.open(windowName) doesn't open a new window inside the tab container. It works fine in iOS. h4. tab.open(windowName) works in iOS and h4. tab.add(windowName); h4. windowName.open(); h4. works fine in android I have commented it in the app.js file as well. Please find it attached. h4. Repo Steps 1. Run the attached app.js file. 2. Click the window 1 and you can see the new window is opening outside the tab container.",2
TIMOB-8653,"Tooling: Separate SDK from the Platform","This task comprises a few high level tasks: * The SDK should live as it's own standalone component, with it's own git repository * The SDK and Platform should be able to have their own release cycles, and the SDK should be able to work with multiple versions of the Platform",5
TIMOB-8658,"Android: Switch search order of folders/environment variables in androidsdk.py","I accidentally updated my ANDROID_SDK environment variable to a bad value, and suddenly Studio was unable to find my Android platforms, even though I had a correct SDK specified in preferences. Digging into the code, I see that we pass a specific directory to search to avd.py, by androidsdk.py/find_sdk() defers to ANDROID_SDK before utilizing ""supplied"". It seems we should respect the passed-in directory first before defaulting to backup options like environment variables.",2
TIMOB-8662,"Tooling: Write a CLI specification","Write a CLI specification that covers: * CLI workflow * Argument naming and value standards * Initial set of CLI commands * Initial set of CLI arguments * External CLI APIs (for CLI modules) The target list of commands should contain: * Validation of project (module+app) creation arguments per platform * Project creation - modules + apps * Project migration between Titanium SDK versions * Per-platform setup * Environment / project validation * Build project (APK, IPA, deployable web app in MobileWeb) * Publish (may be type of build) * Obfuscation/minification * Optional Lint * Emulator/Simulator launch * Deploy project (to a device, to an emulator) * Debugger / REPL Other requirements that were gathered: * Studio needs standardized logging and errpr message parsing * Standard interfaces to basic commands across platforms * Have a list of command capabilities / implementations per platform ",5
TIMOB-8665,"Android: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES when installing different app with same app id","When an android app is installed, and that app is already installed using a different deploy type (i.e., production vs. testing), or a different app is installed with the same app id, there is an error INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES logged to the console. I would expect the script to fail with a meaningful error message (and Titanium Studio to have an error prompt if necessary) indicating an app with the same app id and a different certificate is already installed on device, remove this app to continue installation. Steps to Reproduce (Scenario 1): 1. Create a new Android project. 2. Distribute for production and install to device. 3. Deploy again to device from studio. Steps to Reproduce (Scenario 2): 1. Create a new Android project. 2. Install to device in development mode. 3. Create another Android project with the same app id. 4. Deploy second app to device. Expected Result: Script fails with meaningful error message, studio prompts error if necessary. Actual Result: Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] logs to console, difficult to know exactly what the problem is.",3
TIMOB-8680,"Core: Define Javascript coding standards","Define a document that outlines all Javascript coding standards any javascript written for Appcelerator (internal or community contributions) should adhere to. This should represent more than syntax, but general design approaches and process flow. This document will be focused on language only. Platform Specific information will be contained inside another document. This is a collaboration ticket.",5
TIMOB-8681,"Core: Define C/C++ coding standards","Define a document that outlines all C/C++ coding standards any C/C++ written for Appcelerator (internal or community contributions) should adhere to. This should represent more than syntax, but general design approaches and process flow. This document will be focused on language only. Platform Specific information will be contained inside another document.",5
TIMOB-8710,"Core: Research source code validation tool","Investigate the use of a validation tool for source code against our defined language standards. Do we need one per language? Can we use a single tool with plugins perhaps?",1
TIMOB-8714,"Android: 'focus' events are not correctly handled for windows in a tabGroup","h2. Problem description 'Focus' events might not correctly handled when associated to a window set in tabGroup and with the url property h2. Steps to reproduce h3. Steps - Create a tabGroup with 2 windows. - Set the url property for each window and define 'focus' event listener in the two 'win1.js' and 'win2.js' files. - Don't set event listeners in the app.js Result: 'focus' event listeners ae not triggered on Android (on iOS works fine). h3. Code {code:lang=javascript} // app.js var tabGroup = Titanium.UI.createTabGroup(); var win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff', url:'win1.js' }); var tab1 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Win 1', window:win1 }); var win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff', url:'win2.js' }); var tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Win 2', window:win2 }); tabGroup.addTab(tab1); tabGroup.addTab(tab2); tabGroup.open(); {code} {code:lang=javascript} // win1.js var win1 = Ti.UI.currentWindow; win1.addEventListener('focus',function(e){ alert('test win1'); }); {code} {code:lang=javascript} // win2.js var win2 = Ti.UI.currentWindow; win2.addEventListener('focus',function(e){ alert('test win2'); }); {code} h2. Additional notes: Customer ticket : http://support-admin.appcelerator.com/display/APP-221687/conversation/read_all",1
TIMOB-8718,"Core: Compare possible CLI technologies","In order to select the appropriate tool for the new CLI, we need to perform a side-by-side evaluation for the following proposed technologies: * node.js (TIMOB-8640) * Python 2.7.x (TIMOB-8715) * Python 3.2.x (TIMOB-8715) * Ruby (no ticket, proposed) * Java + RHINO (no ticket, hat tip to cbarber for the suggestion) Advantages, disadvantages, etc. of each of these technologies is documented in their specific tickets and via meeting notes being compiled by Marshall. Note that one of the suggestions proposed in the node.js meeting was to create a pluggable {{git}}-like infrastructure, so that the command {{titanium xxx}} would call out to a {{titanium-xxx}} script, which could be in any scripting language (or a compiled tool). This evaluation may recommend this approach if we believe multiple technologies are appropriate for different tasks. These are the high level tests we should use in judging any solution: * Subprocess / Child process APIs ([ipc side-by-side comparison|https://gist.github.com/2583397]) ** A test that executes a short-lived process and collects it's results ** A test that executes a long-lived process and collects it's stdout / stderr output and reprints that output in real time * Logging APIs ([log side-by-side comparison|https://gist.github.com/2581199]) ** A test that creates a simple unified logger with a base string format and configures certain log levels as visible ** A test that associates multiple loggers with various system components * Compression (zip) APIs ([zip side-by-side comparison|https://gist.github.com/2572795]) ** A test that opens a ZIP file, scans the contents, and extracts one of the files for processing ** A test that creates a new ZIP file using a mix of normal files, deep paths, and symlinks * Javascript AST parsing / manipulation: *NOTE:* This is now part of a separate technology evaluation. See TIMOB-8947 for discussion relating to AST. We have been delivered the requirement for a single AST for the product, and it is assumed that CLI tooling will call out to this rather than have an AST. ** A test that parses a simple Javascript file, and reports back an AST ** A test that does minor manipulation of the AST, and transforms back to JS Each test should include performance metrics over many runs, and information about external module(s) used along with versions.",3
TIMOB-8721,"BlackBerry: Implement module API","This is the api that will be available for 3rd party module extensions. This api also needs to be well documented. ""The ""Extending Titanium"" set of guides might be a good starting point: http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Extending_Titanium_Mobile There will need to be a C/C++ API for module developers. You can look at the API documentation for Android and iOS to get an idea of what sort of native API we expose for extensions. Module developers should be able to create their own proxy and views. Need to also figure out how these external modules get compiled into the application. I am guess module developers will provide some sort of static/dynamic library that gets included into the application. For application developers they use the require() function to load these external modules. So you will need to add support into your require implementation to search for these external modules if it can't find any files in the applications resources folder. For external modules we use the module's ID string for the require lookup. Ex: require('com.my.module') We also support external CommonJS modules. The Titanium Cloud module is an example of this type of module. This document provides some details: https://wiki.appcelerator.org/display/guides/CommonJS+Modules+in+Titanium Basically this allows module developers to distribute JS only modules. This works by extending the require() search path to include these modules when the application developers adds them to their tiapp.xml section. So I hope that gives you a good starting line. Feel free to ask for detailed questions on each of these requirements. We should also loop in the module team and work closely with them on any requirements they require for creating modules for BB. -- Joshua Roesslein Platform Engineer Appcelerator, Inc. jroesslein@appcelerator.com""",15
TIMOB-8730,"Android: When invoking other intent from the app, the pause event is not being triggered ","h4. Problem Description If we call another app or activity in the android app, the pause event is not being fired. h4. Actual Results Event is not fired h4. Expected Results The event pause should be fired. h4. Test case 1. Create mobile project. 2. Paste this into the app.js {code} if(Ti.Platform.osname == 'iphone') { // WORKING FOR iPHONE // do nothing } else { // event listeners for android // NOT WORKING Ti.Android.currentActivity.addEventListener('create',function(){Ti.API.info('Create call')}); Ti.Android.currentActivity.addEventListener('destroy',function(){Ti.API.info('Destroy call')}); Ti.Android.currentActivity.addEventListener('pause',function(){Ti.API.info('Pause call')}); Ti.Android.currentActivity.addEventListener('resume',function(){Ti.API.info('Resume call')}); Ti.Android.currentActivity.addEventListener('start',function(){Ti.API.info('Start call')}); Ti.Android.currentActivity.addEventListener('stop',function(){Ti.API.info('Stop call')}); } Ti.Platform.openURL('tel://911'); {code}",1
TIMOB-8743,"Android: Intermittent 'force close' issue","*Issue* -The app randomly 'force quits' when launched, I personally don't seem to be able to reproduce this (yet). -What one of the users reported back: ""I launch and it's basically frozen...the small black ""app name"" bar appears at the top but nothing happens...now finally after minutes (3-5) got the error message ""sorry! Activity APPNAME (in application APPNAME is not responding...force close...wait...report"" -Attached are the log files. App source code can also be attached, if required. *Notes* -Name of the actual app has been removed and replaced with 'APPNAME'.",2
TIMOB-8745,"Android: Intermittent app 'freeze' issue","*Issue* -The app randomly freezes when it's on the loading screen. -Comments: ""User reported a hanging login (loading bar went to full green, but then nothing happened) directly after a force-close and relaunch. Log attached."" -Attached is the log file. App source code can also be attached, if required. *Notes* -Name of the actual app has been removed and replaced.",3
TIMOB-8772,"Android: Alignment Issues on Android, layout appears broken","8 Buttons are added to the window, and have a background image. When they are aligned together in a line, it appears broken. It looks continuous on iOS. I have attached images to explain this. Also have included the code sample. {code} var win = Titanium.UI.createWindow({ backgroundColor:'white', title:'window', barColor:'#ff7b01', top:0 }); var arr = ['5d', '1m', '3m', '6m', 'YTD', '1yr', '2yr', '4yr']; for(var i=0;i. A TabGroup tab instance. Each tab includes a button and one or more windows, which holds the ""contents"" of the tab. Users can select a tab by clicking on the tab button. In iOS, this actually is more of a combination of UITabBarItem and UINavigationController meant to go into a tab group. Android does not have a navigationController concept, so it depends on what Blackberry provides. https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UITabBarItem_Class/Reference/Reference.html#//apple_ref/doc/c_ref/UITabBarItem https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UINavigationController_Class/Reference/Reference.html#//apple_ref/doc/c_ref/UINavigationController ",5
TIMOB-8837,"BlackBerry: Implement UI.TabGroup elements needed for KitchenSink",NULL,12
TIMOB-8838,"BlackBerry: Implement UI.TableView - Part 1",NULL,10
TIMOB-8839,"BlackBerry: Implement Simple TableViewRows","h3. Feature Implement TableViewRow proxies which support the simple row style. For simple rows (title, leftImage, etc) can probably use the Cascades StandardListItem. This is already implemented for using plain objects for the data array. Developers should also be able to listen for click and swipe events on rows. h3. Acceptance Test 1. Download the test case (tableview-test.zip) which includes the resources. 2. Create a project with the resources and run the app. 3. A list of items should appear with title text and a left image. 4. After a few seconds the last item should change to a pear. 5. Try clicking various rows. The text should change to ""Click!"" for a few seconds. The text should revert back to its original value. ",19
TIMOB-8840,"BlackBerry: Implement important Titanium.UI.TableViewSection functionality","A TableView section object. Usually contains TableViewRows In iOS, this is an abstract non-iOS class used to group rows into sections. There is no native analog.",17
TIMOB-8841,"BlackBerry: Implement important Titanium.UI.TextArea functionality",NULL,17
TIMOB-8842,"BlackBerry: Implement UI.TextField - Part 1",NULL,8
TIMOB-8843,"BlackBerry: Implement UI.View based on R4","Every UI control in Titanium extends the View and as such inherit methods from it. This implementation is missing from the current framework. It needs to be implemented asap so as to minimize the rework to be done in existing controls at the time this is implemented. To facilitate this change, we will likely include a container for all controls that we have, so the View methods to act upon.",30
TIMOB-8844,"BlackBerry: Implement UI.WebView",NULL,5
TIMOB-8851,"Core: Write a specification for the new Unit Test Harness","We need to write a specification for these components of our new Unit Test Harness: * CLI interface * Unit test APIs that cover basic assertions, and UI testing * Test Results output (JSON) for collection by CI This task is evolving with data found from prototyping and integration.",5
TIMOB-8852,"Core: Integrate Drillbit into the CI Loop",NULL,5
TIMOB-8870,"BlackBerry: Integrate Cascades R4","Condition: Cascades R4 needs to be available - tentative date April 30th 1) resolve conflicts, pay special attention to things that have already been implemented in Titanium.API 2) investigate if there is anything new added to controls that we already implemented 3) if any, implement new additions to controls that we already implemented",10
TIMOB-8897,"BlackBerry: Implement important Titanium.Blob functionality","* Titanium.Blob * Titanium.Blob.text * Titanium.Blob.toString Implement basic Blob functionality: accessing data, getting size, appending, convert to string. Blobs are primarily used to wrap native data structures or sources (ex: file descriptor, image, buffers). The goal of this ticket is just implement the proxy front facing APIs. Internally it should be architected to support wrapping various data sources. For the initial implementation support ""buffer"" based blobs would be a good first step. Blobs are not creatable, but returns by various API methods in Titanium. For testing this ticket implement the Buffer.toBlob() method. This should return a Blob which should allocate a buffer and copy the data over. Blob streams and to image conversions will not be implemented at this time. Separate tickets for those will be created. h3. Acceptance Test Look into using the test in Anvil for Blobs. The test is currently very small, so try to improve it. Anvil may not run right now on BlackBerry, but we can just copy the test into an application for now.",17
TIMOB-8925,"Blackberry: Add support for debugging titanium apps in studio",NULL,8
TIMOB-8926,"Blackberry: Implement proper packaging of blackberry mobile sdk","Add building of libtibb.ca in the scons script and package it properly in the resulting zip file, also remove any unnecessary files from the zip",5
TIMOB-8983,"Blackberry: Add formatting check in git pre-commit hook",NULL,3
TIMOB-8996,"BlackBerry: Complete remaining issues from code review","See pull request: #18 1. void TiUIBase::setTiMappingProperties(const TI_PROPERTY* prop, int propertyCount) prop should be props since it's a pointer to an array of prop objects -- 2. TiUIBase::setParametersFromObject(Local obj) Local propValue; + Handle propString; + TiObject* foundProp; 3 last lines, It's cleaner to declare variables inside the smallest scope they are to be used in and also helps prevent referencing them outside of their scope. In this case the declarations should be inside the for -- 3. int NativeContainerObject::initialize() add protection agains multiple invocations -- 4. if((args.Length()!=2)||(!args[0]->IsString())||(!args[1]->IsFunction())) This line is definitely worth a comment. How come args[0] needs to be a string and args[1] needs to be a function? reminds me of perl :S -- 5. blackberry/tibb/TiUIObject.cpp • createXXXX_ methods out of 14 lines of code in the functions, only 1 really differs. It'd be nice to have a way of abstrating that to remove code duplication which would be a maintenance nightmare as i also forsee many many such functions being created for all the UI controls we need to implement Similarly the associtated classes look very bare and very much alike, is there actual value in having all these look alike classes? Maybe the actual question is can we avoid them? -- 6. VALUE_MODIFY TiPropertyMapObject::onValueChange(Handle oldValue, Handle newValue) the 3 lines inside the the ifs are the same in all cases, they should be rolled into a helper function. -- 7. we should review the logical separation of classes with regards to cascades awareness, separation into folders -- 8. review error handling strategy - run it by appcelerator -- 9. class TiEventContainer please add spaces around the = sign for consistency with the rest of the code.
The formatter doesn't enforce it here. There is at least another instance of that in TiEvent.h -- 10. blackberry/tibb/TiUIBase.h description comment references TiCascadesApp when it should be TiUIBase -- 11. embed class TiInternalEventListener inside TiV8EventContainer? To reenforce it's internalness",5
TIMOB-9102,"iOS: getVisible() / getEnabled() functions could return null value","h2. Problem description Boolean functions like getVisible() or getEnabled() can return null value h2. Code sample {code} var win = Ti.UI.createWindow({ exitOnClose:true }); var view = Ti.UI.createView({ top:0, left:0, width: 10, height:10 }); var button = Ti.UI.createButton({ title:'Click Me!' }); button.addEventListener('click', function(e) { alert(view.getVisible()); view.setVisible(!view.getVisible()); }); win.add(button); win.add(view); win.open(); {code} Result: After running the sample code, click on the button to execute view.getVisible(), which return value 'null'. Expected result: If the property was never defined by the user, then the default value should be returned. ",5
TIMOB-9028,"CLI: ""build"" command for Android apps","Port the Python-based Android builder.py to Node.js. Portions of this has already been completed. h3. Build Process * Validate command line arguments and tiapp.xml settings (TIMOB-14973) * fire ""build.pre.construct"" event * create Builder object * fire ""build.pre.compile"" event * Detect if need to force rebuild (TIMOB-14974) * Init the build/android directory and files (TIMOB-14976) * if not --build-only ** make sure adb server is running (adb lib does this for us) ** wait for the emulator/device to boot ** detect if app is already installed (adb lib does this for us) * Compile resources (TIMOB-14977) * determine Google APIs are required (true unless not build only and building for emulator running non-Google API AVD) * if building for emulator and using Ti.Map.MapView, make sure the emulator is running Google APIs (TIMOB-5438 Compiler Warning When Using Maps with Non-Google APIs SDK) (TIMOB-6860 Tooling: Android build process requires ""Google APIs"" even if ""Ti.Map.createView"" only occurs in comments) * generate build/android/bin/assets/index.json with contents of build/android/bin/assets * generate jss stylesheet => build/android/gen//ApplicationStylesheet.java * generate aidl * process build/android/res/*.xml for all i18n strings ** support app.xml to localize app name (TIMOB-2824 Android: App name localization) * handle splash screen * generate build/android/res/values/theme.xml * Create android.manifest (TIMOB-14978) * remove duplicate res in xml files??? * Build Java files and run dexer (TIMOB-14979) * if not --build-only and not package build, push deploy.json to emulator/device ** wait for sdcard *** gracefully handle timeouts (TIMOB-11827 Android: Installing an app to Android with 4.2 version takes long time) * Package and sign app (TIMOB-14980) * fire ""build.post.compile"" event * fire ""build.finalize"" event ---- h3. Hooks * Package Hook (TIMOB-14981) * Run Hook (TIMOB-14982) ---- h3. Misc * logcat * wait for emulator * delete unused support/android/templates/AppUserData.java * when subprocessing Java-based tools (android, etc), override ""_JAVA_OPTIONS"" environment variable (TIMOB-14322 CLI: Setting _JAVA_OPTIONS global variable breaks building of project) * convert default ""dark"" splash screen to a red-based one (TIMOB-4517 Android: default.png file is a gray image, should be the red default image) * TIMOB-11120 Android: Expose a way for users to exclude js files from being encrypted * TIMOB-339 Android: Missing Icons * TIMOB-13311 Android: CLI: possibility to build apk for beta release (like ios adhoc) (should be resolved with build profiles) * remove dependency on old Android SDKs (TIMOB-13983 Android: Titanium should use the latest stable Android SDK and NDK and not depend on 2.2 API 8)",8
TIMOB-9037,"CLI: Implement ""export"" command","Exports a project to a standalone project without any dependencies on Titanium. The arguments will be similar to the build command.",34
TIMOB-9092,"BlackBerry: Implement UI.ActivityIndicator - Part2","Implement the rest based on TIMOB-8810 To be implemented: Properties color : String font : Font message : String messageid : String style : Number Methods getColor( ) getFont( ) getMessage( ) getMessageid( ) getStyle( ) setColor( String color ) setFont( Font font ) setMessage( String message ) setMessageid( String messageid ) setStyle( Number style ) ",12
TIMOB-9111,"iOS: Ti.Utils.base64encode result is different between iOS and Android","h3. Problem The result of Ti.Utils.base64encode is different between iOS and Android. On iOS there are newline characters included when the string is long enough, on Android the newline characters are stripped out (which is the correct way to do base64 UTF8 encoding). Please see the attached screenshot explaining the issue. h3. Sample Code {noformat} (function() { var win = Ti.UI.createWindow({backgroundColor:'white'}); win.open(); var shortString = 'ABCDEFGHIJ1234567890ABCDEFGHIJ12|psndemo2|abcd:1'; var longString = 'ABCDEFGHIJ1234567890ABCDEFGHIJ12|psndemo2|abcd:12345678901234567890'; var tiBase64ShortResult = Ti.Utils.base64encode(shortString); var tiBase64LongResult = Ti.Utils.base64encode(longString); tiBase64ShortResult = String(tiBase64ShortResult); tiBase64LongResult = String(tiBase64LongResult); // BUG #2: Run this code in iOS and Android and compare the results // On iOS we get newline characters. On Android the newline characters are stripped out. // The correct behavior for UTF8 base64 encoding is to strip out the newline characters. // Android's implementation is correct. tiBase64ShortResult = tiBase64ShortResult.replace(/\r\n/g,""***NEWLINE***""); tiBase64LongResult = tiBase64LongResult.replace(/\r\n/g,""***NEWLINE***""); var alertDialog = Titanium.UI.createAlertDialog( { title: 'Result', message: 'short: ' + tiBase64ShortResult + '\nlong: ' + tiBase64LongResult, buttonNames: ['OK','Cancel'] }); alertDialog.show(); })(); {noformat}",5
TIMOB-9139,"Android: Tooling: How to set the deploytype ","h4. Problem Description When you do a deployment for distribution, you will think that the deploytype in analytics will switch to production. But it's not happening with some projects. A customer is not getting analytics from his app, and he reported it, the people in the Cloud replied that he didn't set the app to be in prod: The second issue, for the other app GUID 473b9203-836a-4d48-ac13-2993873efa2c, the problem is that the user is using deploytype:test, and analytics only shows up for deploytype:production. When I asked the client to do for production (i.e., deploy it to the Market), he already did that, as the attached image shows. h4. Actual Results App is not set for production in the deploytype. h4. Expected results If you build an app for distribution in the market, the deploytype should be production. h4. Extra info See attached image. ",3
TIMOB-9142,"BlackBerry: Implement BB animations","In matching what's currently available on other platform, look for 2Dmetric, 3Dmetric and other references to animation",17
TIMOB-9143,"BlackBerry: Implement BB Application Menu (Crosscut Menu)","On BB10 devices swiping from the top of the screen will display a menu bar of action items it is used to control not often use actions that apply (crosscut) across the entire app. See https://developer.blackberry.com/cascades/reference/bb__Application.html#function-swipedown https://developer.blackberry.com/cascades/documentation/ui/navigation/menus.html Look at NativeWindowObject.cpp to see how to do ActionItems",2
TIMOB-9144,"BlackBerry: Implement BB push","registerForPushNotifications() for starting point BB push should be available after R6 release early in July. To see an overview of the BB10 push system see http://developer.blackberry.com/cascades/documentation/device_comm/push/index.html Java Based Server Side SDK http://developer.blackberry.com/devzone/develop/platform_services/push_overview.html To enable ASC some server side work is require. Make sure to give the ASC/360 teams early heads before working on this task. ",8
TIMOB-9158,"Blackberry: Update the tibbapp project to work with the R4 release of Cascades","- remove extra libs from common.mk - adjust paths to R4 ndk for default detection in blackberryndk.py - And other things that might not work",3
TIMOB-9164,"Blackberry: [Studio integration] regenerate the bar-descriptor file at packaging time","the bar-descriptor file needs to be updated everytime we package to pick up potential changes to the tiapp.xml file",8
TIMOB-9202,"BlackBerry: Implement important Titanium.UI.OptionDialog functionality","For now used native DropDown component for OptionDialog. In future when modal dialog will be supported by cascades, we need to switch to something more similar thing for OptionDialog, as already in Android and iPhone.",15
TIMOB-9203,"BlackBerry: Handle JavaScript exceptions in runtime","Currently the Titanium runtime haults JS execution prints information to the stdout during an exception and then the Cascades message loop is entered. This should be changed to shutdown the app and return an error code. Pull request: https://github.com/Macadamian/titanium_mobile/pull/66 ",3
TIMOB-9204,"BlackBerry: Bring API doc up to date","Updating API doc is now part of the patch cycle. However, some components added in the past have not been reflected in API doc: - ImageView - TextField - ActivityIndicator (maybe, check it out) This task is to add past work to the API doc.",2
TIMOB-9219,"BlackBerry: Refactoring event handler implementation","Add event handler embedded class for each native controllers, which will be responsible for handling QT cascade events.",5
TIMOB-9286,"Android: Animation code review","The current state of Android animation APIs and its limitations/bugs needs a review to address various animation issues.",5
TIMOB-9291,"BlackBerry: Generate moc files during the build",NULL,5
TIMOB-9293,"BlackBerry: Create string table for Titanium error messages","Error messages during runtime are, in most cases, not returning a readable message. A centralized string table should be created with properly formatted messages to help users with debugging.",10
TIMOB-9306,"Blackberry: add a universal logging mechanism for tibb","Need to add a universal logger to the framework. May use exceptions and stop the app in debug mode and only log in release mode. Also go over all existing qDebug and printf to update them to use the new logger. The logger will also need to do some locking to ensure that logging from concurrent threads doesn't result in logs cut and merged in the middle.",5
TIMOB-9309,"BlackBerry: Convert argparse to optparse","The argparse module was introduced in python 2.7 but we need to support 2.6 so we need to use optparse instead. It's fairly similar except it doesn't support sub-parsers.",7
TIMOB-9369,"BlackBerry: bring in the latest Appcelerator code into BB branch",NULL,3
TIMOB-9378,"BlackBerry: Add script to create and install debug token","[Tatyana] A note to myself: this task is a necessary step to be able to deploy an app to a device. This could be added to the devicemanagement.py script. {noformat} blackberry/devicemanagement.py createDebugToken --store-pass --csj-pin --csj-file (--device-pin | --device-pin-list ) --debug-token-bar-file --device --device-password password for keystore and device PIN associated with CSJ file input CSJ file for registration device PIN in hex without the '0x' (e.g. 50F2D211) file containing a list of device PINs debug token file hostname or the IP address of the target device or simulator {noformat} This is an example of what the script should do: {noformat} blackberry-debugtokenrequest -register -storepass 123456 -csjpin 729759 client-RDK-584232624.csj client-PBDT-584232624.csj blackberry-debugtokenrequest -storepass 123456 -devicepin 29AFDEBD dt.bar blackberry-deploy -installDebugToken dt.bar 169.254.0.1 -password 1234 {noformat}",2
TIMOB-9398,"Blackberry: Get standard JS keywords to work in V8","things like the following don't currently work in V8: var v = new String('bla bla'); // v is undefined after executing that line var i = parseInt('5'); // TypeError: parseInt not a member of #error These are just 2 examples, many more likely have the same behavior. ",5
TIMOB-9403,"Android: Map - Add centerOffset property to Ti.Map.Annotation","This is the parity ticket for Android to see if such functionality can be ported over. ------ Add centerOffset property to a custom annotation to be able to set a x & y offset to the image of the annotation. Right now the center of the annotation is the center of the image size. This makes that some images appear not to be in their proper place at certain zoom levels. Reference to official documentation: http://developer.apple.com/library/ios/#documentation/MapKit/Reference/MKAnnotationView_Class/Reference/Reference.html#//apple_ref/doc/uid/TP40008207 I have already coded the feature and I open this ticket in order to get the pull request accepted.",2
TIMOB-9454,"BlackBerry: Complete Layout Handling of UI View","Part of this task need to clean left and top properties from inherited classes that don't need to override the default implementation. One such occurence is in NativeListViewObject",5
TIMOB-9481,"iOS: cancelLocalNotification on iOS is broken","In 'bg.js' of kitchensink, notifications cannot be cancelled using 'id' passed as userinfo dictionary to the notification. {panel:title=bg.js} {code} var notification = Ti.App.iOS.scheduleLocalNotification({ alertBody:""Kitchen Sink was put in background"", alertAction:""Re-Launch!"", userInfo:{id:""1""}, sound:""pop.caf"", date:new Date(new Date().getTime() + 3000) // 3 seconds after backgrounding }); // we cancel our notification if we don't want it to continue // notification.cancel(); //this works!!!! Ti.App.iOS.cancelLocalNotification(""1"");// this does not work. {code} This is fixed by Pedro and the fix is available here. https://gist.github.com/48a765c50f64aa7c47ed",3
TIMOB-9539,"BlackBerry: Implement include()","Needed for unit tests and Kitchen Sink",19
TIMOB-9542,"BlackBerry: Implement important Titanium.Buffer functionality",NULL,15
TIMOB-9543,"BlackBerry: Implement Ti.BufferStream",NULL,3
TIMOB-9552,"Android: Emulator: Not recognized by adb, unable to install to Emulator.","When Android emulator deployed, adb fails to recognize the emulator. This is intermittent issue, it effect all emulator versions. This is not an regression it occurred in 2.0.2 Step to reproduce: 1) Create default project. 2) Right Click, Select ""Run As"", Select ""Run Configurations..."" 3) Select ""Titanium Android Emulator"" 4) Select platform Android API: ""Google API Android 4.0.3"" 5) Apply and Run. Expected Result: adb should recognized the emulator or if this occur then studio should be provide error correction to handle the error properly. Actual Result: adb doesn't recognize the emulator. Studio fails to notified to developer of the failure and App never installed. ",13
TIMOB-9604,"BlackBerry: Implement important Titanium.UI.TabGroup functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE Add at least: * Titanium.UI.TabGroup.enabled * Titanium.UI.TabGroup.touchEnabled",21
TIMOB-9605,"BlackBerry: Implement important Titanium.UI.Window functionality","Use the implementation matrix to see what's remaining: https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE Implement at least: * Titanium.UI.Window.modal (sheets/dialogs in Cascades?) * Titanium.UI.Window.setKeepScreenOn",21
TIMOB-9658,"BlackBerry: Add JavaScript bootstrapping to framework","Some of the Titanium implementation can be done using JavaScript so we need to provide a way to run our own bootstrapping .js files before we load app.js. There is possibly a lot of JavaScript code we can reuse from the android directory. The method I suggest is to package the .js files into the .bar file. The files should be put into a new folder called ""framework"" that is next to, not inside, the ""assets"" folder. The ""assets"" and ""framework"" folders should be separate so we don't have conflicts. The only complication would be that the require() and include() functions might need a flag to know whether the app has been bootstrapped or not (ie read from ""framework"" if bootstrapping and ""assets"" if not). A flag may not be sufficient if things are done asynchronously so the other solution would be to check if the file calling the require/include is in ""framework"" or ""assets"" and make sure to load the file from the same directory. There should be one file called boostrap.js that will include/require the other files, as needed.",5
TIMOB-9665,"Blackberry: fix property enumeration on JS object created by the framework","calling toString() on an object created by the Ti framework fails. We think that the property enumeration doesn't enumerate the inherited properties. ",1
TIMOB-9682,"Android: Packaging:No warning displayed for default system value of 'ti.ui.defaultunit'.","It is not a regression.It exists as far as 1.8.2 While packaging the app,when the value of ti.ui.defaultunit is 'abc' - Expected - Display warning during packaging, use default system value Actual - No warnings are displayed while packaging. Logs generated while packaging are attached with the bug.",3
TIMOB-9685,"Blackberry: Resolve and clean TODOs and FIXMEs in the code",NULL,8
TIMOB-9788,"BlackBerry: Implement important Titanium.UI.Picker functionality","Need to implement plain picker using BB drop down control. Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",17
TIMOB-9830,"BlackBerry: Support UI Controller property which value is another controller",NULL,5
TIMOB-9840,"BlackBerry: Integrate Anvil unit test framework and get tests to run","- Implement platform specific file in anvil/driver/platforms (closest match likely to be android.js) - minor updates to anvil/driver/driver.js to add BB as a known platform - select a socket port for BB in anvil/driver/config.js created from a copy of exampleConfig.js - Identify necessary Ti API calls needed for the harness app and implement them - Figure out the communication between driver and harness",7
TIMOB-9859,"Android: increase AVD storage size to reduce [FAILED_INSUFFICIENT_STORAGE] errors","h2. Expected results: I should be able to build and install more than a few Ti apps to an Android emulator. h2. Actual results: Due to defaults defined in builder.py, I can fit only a couple of Ti apps before the emulator runs out of storage space. This results in a [FAILED_INSUFFICIENT_STORAGE] error. I can delete other apps to free space. However, if I need to work on multiple apps, I end up having to delete/install frequently. h2. Fix In builder.py (in my version, line 491) increase the partition size value. Current value is 128 (MB). I suggest at least 1024. ",1
TIMOB-9897,"Blackberry: address comments from Martin's review",NULL,3
TIMOB-9916,"BlackBerry: Upgrade Cascades to R6",NULL,3
TIMOB-9930,"Android: Packaging: With a non-existing module added to the project in the tiapp.xml,app packages without error and gets installed on device","This is not a regression. IT exists as far as 1.8.2. Adding a module to the project in the tiapp.xml which does not exist such as not.there should prevent the app from getting packaged but it is not. App gets successfully packaged and gets installed on android device.It runs on emulator also without error/warnings. If I try to install it directly on simulaor or iOS/android device, it gives appropriate error for module not found like: For iOS simulator and device error is: [ERROR] Could not find the following required iOS modules: [ERROR] id: not.there version: 1.0 For android device, error is: [ERROR] Failed installing com.appcelerator.timob9090: pkg: /data/local/tmp/app.apk Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] Steps to reproduce 1. Create a new app in TiStudio 2. Add a module to the project in the tiapp.xml which does not exist such as not.there 3. Package the app/run on android emulator Actual result: The app gets packaged/runs on emulator without error. Expected result: The app should fail packaging with appropriate error result like [ERROR] Could not find the following required iOS modules: [ERROR] id: not.there version: 1.0 And give error for emulator also like(as we get in case of device) [ERROR] Failed installing com.appcelerator.timob9090: pkg: /data/local/tmp/app.apk Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES]",3
TIMOB-9933,"BlackBerry: make sure that TiObjects get to the destruction state",NULL,2
TIMOB-9950,"BlackBerry: Fix/implement relative include/require","Currently, include()'s method of doing relative files only works if all done in successive order. It does not work for windows with a url (not implemented) or if include is used in a function of a file in a subdir. Also, require() does not have any method right now. My proposal is to store the filepath in each TiObject so it can be retrieved later when needed. Also, we need to make sure that require() properly handles a ""native Titanium module"" by its ID (eg com.example.module).",2
TIMOB-9953,"BlackBerry: Fix logging/exception tags and exception output","Currently, when we throw an exception while a file is being loaded by include or require, both files are shown in the message (eg ""file1.js line 2: file2.js line 5: Missing argument""). We need to make changes so the following is true: # the exception has the [ERROR] tag # only the filename containing the actual error is shown ** might need to get rid of some TryCatch's ** might need to use Message::GetScriptResourceName # the filename shows the full path (minus the .../assets/) # an exception thrown from an event handler shows the filename and crashes the app (eg calling Ti.API.debug() with no params in a button handler) Also need to clean/split up TiRootObject::executeScript and implement Ti.API.log in .js.",2
TIMOB-9971,"BlackBerry: Complete 'remove' method in UI View","Implement 'remove' method for removing child controls from a container.",3
TIMOB-9972,"BlackBerry: Implement UI.Tab.open and .setWindow, needed for KitchenSink","To get this to work in KS, we need TIMOB-9879 and whatever else to fix the click event for TableView, but the Tab.open and setWindow can still be implemented separately. Take a look at android/modules/ui/src/js/tab.js for .open(), but currently we can't use the bootstrapping to extend the API because we create different objects instead of using the prototype.",7
TIMOB-10025,"BlackBerry: Sync with Appcelerator branch",NULL,3
TIMOB-10059,"BlackBerry: Revisit UI.AlertDialog implementation based on R6","Depends on Cascades R6 An alert dialog is a modal view that includes an optional title, a message and buttons, positioned in the middle of the display. In iOS: https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIAlertView_Class/UIAlertView/UIAlertView.html",2
TIMOB-10224,"Blackberry: Implement startLayout, finishLayout, updateLayout methods",NULL,3
TIMOB-10233,"BlackBerry: Sync with Appcelerator branch (Sprint 11)",NULL,2
TIMOB-10257,"BlackBerry: Implement Titanium.IOStream","IOStream is the interface that all stream types implement. Methods: 5 Sub Classes: 4",3
TIMOB-10264,"Blackberry: adjust UI controls based on R8","This umbrella task is to address functional delta in controls that were previously implemented using R4 release of Cascades. It could either mean implementing new functionality now available in R6, or redoing something that no longer works or was implemented as a workaround. Refer to the implementation matrix to see what elements need to be implemented",2
TIMOB-10266,"BlackBerry: Complete Ti.UI.View methods / properties / events","Complete UI View methods / properties / events NOT required by Kitchen Sink Add at least: * Titanium.UI.View.animate * Titanium.UI.View.append * Titanium.UI.View.backgroundGradient * Titanium.UI.View.borderColor * Titanium.UI.View.borderRadius * Titanium.UI.View.borderWidth * Titanium.UI.View.control * Titanium.UI.View.currentIndex * Titanium.UI.View.currentY * Titanium.UI.View.fireEvent * Titanium.UI.View.id * Titanium.UI.View.layout * Titanium.UI.View.on * Titanium.UI.View.refreshRssTable * Titanium.UI.View.reset * Titanium.UI.View.scrollView * Titanium.UI.View.showArticle * Titanium.UI.View.shuffle * Titanium.UI.View.state * Titanium.UI.View.titleId * Titanium.UI.View.toggle * Titanium.UI.View.toImage * Titanium.UI.View.touchEnabled * Titanium.UI.View.updateHandheldNav * Titanium.UI.View.updateSubNav * Titanium.UI.View.videoId ",21
TIMOB-10269,"BlackBerry: Implement Ti.UI.View setLayout / getLayout",NULL,4
TIMOB-10270,"BlackBerry: Implement getWidth, getHeight in R6 UI View",NULL,2
TIMOB-10271,"BlackBerry: Implement getZIndex on R6 UI View",NULL,2
TIMOB-10272,"BlackBerry: Finish size and position methods / properties on R6 UI View","Implement: getHeight getWidth getBottom setBottom getRight setRight getSize setSize",3
TIMOB-10275,"BlackBerry: Implement important Titanium.Network functionality","Implement at least: * Titanium.Network.httpURLFormatter * Titanium.Network.networkType * Titanium.Network.online * Titanium.Network.registerForPushNotifications",21
TIMOB-10299,"Blackberry: Update API doc to state what is NOT implemented","This activity should be done at the ""feature complete"" stage of the project",3
TIMOB-10305,"Blackberry: Support overriding the default UI unit via tiapp.xml","On Android and iOS, the default unit can be overriden on a per-application level by setting the ti.ui.defaultunit property in tiapp.xml. For example, to use DIPs as the default on all platforms, set defaultunit to dip: dip The value for ti.ui.defaultunit can be any of the unit specifiers defined above, or system to specify that the platform's default unit should be used.",5
TIMOB-10307,"BlackBerry: Add support of javascript implementation of parts of the Ti API","Unmbrella task to link to all the bug and issue of the current framework that prevent easy extension of the api using js. Will also need to be figured out: inheritance between native objects and js objects",8
TIMOB-10345,"Blackberry: Implement applyProperties({}) method on Ti.UI objects to take a list of json properties as is done at create time.",NULL,8
TIMOB-10371,"Blackberry: Imageview parity for scaling behavior","As part of TIMOB-3749 scaling behavior of imageViews was changed. If either width or height of image view are set to follow SIZE behavior('auto',Ti.UI.SIZE,undefined) then the image is scaled with aspect ratio intact. Otherwise the image is scaled ignoring aspect ratio. Test code below {code} var win = Ti.UI.createWindow({ backgroundColor:'#fff', layout:'vertical' }); var image = Ti.UI.createImageView({ image: ""http://www.catravelservices.com/management/hotels/pictures/Mawamba_lodge_nature.jpg"", backgroundColor : ""red"" }); var label = Ti.UI.createLabel({ text:'Results Here' }) var updateLabel = function(){ var size = image.size; label.text = 'ImageView size is '+size.width+'x'+size.height; } var controlsContainer = Ti.UI.createView({ height:Ti.UI.SIZE }) var widthControls = Ti.UI.createView({ width:'50%', layout:'vertical', left:0, height:Ti.UI.SIZE }) var heightControls = Ti.UI.createView({ width:'50%', layout:'vertical', right:0, height:Ti.UI.SIZE }) controlsContainer.add(widthControls); controlsContainer.add(heightControls); var b1 = Ti.UI.createButton({title:'WIDTH=SIZE'}) var b2 = Ti.UI.createButton({title:'WIDTH=165'}) var b3 = Ti.UI.createButton({title:'WIDTH=250'}) var b4 = Ti.UI.createButton({title:'HEIGHT=SIZE'}) var b5 = Ti.UI.createButton({title:'HEIGHT=50'}) var b6 = Ti.UI.createButton({title:'HEIGHT=165'}) b1.addEventListener('click',function(e){ image.width=Ti.UI.SIZE; setTimeout(updateLabel,500); }) b2.addEventListener('click',function(e){ image.width=165; setTimeout(updateLabel,500); }) b3.addEventListener('click',function(e){ image.width=250; setTimeout(updateLabel,500); }) b4.addEventListener('click',function(e){ image.height=Ti.UI.SIZE; setTimeout(updateLabel,500); }) b5.addEventListener('click',function(e){ image.height=50; setTimeout(updateLabel,500); }) b6.addEventListener('click',function(e){ image.height=165; setTimeout(updateLabel,500); }) win.add(image); widthControls.add(b1); widthControls.add(b2); widthControls.add(b3); heightControls.add(b4); heightControls.add(b5); heightControls.add(b6); win.add(controlsContainer); win.add(label) win.open(); {code}",8
TIMOB-10442,"BlackBerry: Anvil: Make list of anvil tests that can be run for BlackBerry",NULL,1
TIMOB-10534,"Tooling: Android emulator silently fails","When I try to run the android emulator I see the following in the Debug output: {noformat} [DEBUG] C:\SDK\tools\emulator.exe -avd titanium_6_WVGA854 -port 5560 -sdcard ""C:\Users\qatester\.titanium\titanium_6_WVGA854.sdcard"" -logcat *:d,*,TiAPI:V -no-boot-anim -partition-size 128 armeabi-v7a [DEBUG] signal caught: 3 [DEBUG] calling emulator kill on 3872 {noformat} A bit of poking around finds that the emulator does not launch when the armeabi-v7a argument is attached. {noformat} Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\qatester>C:\SDK\tools\emulator.exe -avd titanium_6_WVGA854 -port 5560 - sdcard ""C:\Users\qatester\.titanium\titanium_6_WVGA854.sdcard"" -logcat *:d,*,TiA PI:V -no-boot-anim -partition-size 128 armeabi-v7a C:\Users\qatester>invalid command-line parameter: armeabi-v7a. Hint: use '@foo' to launch a virtual device named 'foo'. please use -help for more information {noformat} I think this has something to do with the x86 emulators I had tested against, but can not figure out how to undo that change. Steps to reproduce: 1. Create an Android project. 2. Run the project in the emulator. Expected results: The app should run in the emulator or should throw a relevant error. Actual results: The debug shows the above message before flipping the view to waiting for the emulator to be ready which finally times out.",8
TIMOB-10468,"Blackberry: Merge Appcelerator's KS branch with our branch",NULL,2
TIMOB-10713,"BlackBerry: Anvil: Add ability to run on device",NULL,2
TIMOB-10717,"Blackberry: Implement Titanium.UI.TextField value property","Create TextField. Try to set Value or get value during some action (for example button click event). for getValue() - undefined is returned. for setValue() - doesn't set the textfield value. ",1
TIMOB-10748,"Blackberry: AlertDialog inherits from View rather than Proxy","AlertDialog inherits from the wrong parent. To change this, the properties of UI.AlertDialog need to be moved to TIProxy otherwise the properties don't work on AlertDialog and this is why it is currently this way. This will be the case for all UI objects that should extend Proxy directly instead of View.",19
TIMOB-10763,"CLI: Android: ""run"" hook for Android apps",NULL,3
TIMOB-10778,"BlackBerry: Sync with Appcelerator branch (Sprint 13)",NULL,2
TIMOB-10800,"iOS: TableView scrolls back to focused text field on scroll end","*Code* http://pastie.org/4674079 *Expected Behaviour* The user should be able to scroll through the table without being taken back to focused textField. The textField should stay focused. *Actual Behaviour* TableView of textFields scrolls back to focussed text field on scroll end. *Notes* - Tested on iOS 5.1 - To Replicate the issue, click on textField in row 6 then once the textfield gains focus scroll down the table, as soon the scrolling ends it will take you back to row 6.",13
TIMOB-10814,"Blackberry: Fix Anvil issue caused by sync",NULL,2
TIMOB-10820,"Blackberry: Upgrade to R8",NULL,8
TIMOB-11373,"Android Device Debugging: console window fails to display console output after port forward","Titanium Studio Console output fail to display output results. Steps to Reproduce: 1. Create default project, add sample code: {code} Ti.API.info('INFO LOGGED'); {code} 2. Run 'debug' on Android Device. Port forward message should appear on console. 3. Launch app from device. Actual Result: Titanium Studio console log fail to display the console output Expected Result: Titanium Studio console log display the console output as DDMS or Catlog. ",13
TIMOB-10849,"Blackberry: Implement important Ti.UI.Label functionality","Implement at least: * Titanium.UI.Label.opacity * Titanium.UI.Label.touchEnabled * Titanium.UI.Label.url",21
TIMOB-10869,"Blackberry: Implement important Titanium.UI methods","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",2
TIMOB-10870,"BlackBerry: Implement important Titanium.UI.ActivityIndicator functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE Add at least: * Titanium.UI.ActivityIndicator.style (does not appear to be applicable in Cascades)",21
TIMOB-10872,"BlackBerry: Implement important Titanium.UI.TextField functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE Implement at least: * Titanium.UI.TextField.blur * Titanium.UI.TextField.focus * Titanium.UI.TextField.keyboardType",21
TIMOB-10873,"BlackBerry: Implement important Titanium.UI.ImageView functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",19
TIMOB-10875,"Blackberry: Implement important Titanium.UI.ProgressBar functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",15
TIMOB-10876,"Blackberry: Implement important Titanium.UI.Slider functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",15
TIMOB-10877,"Blackberry: Implement important Titanium.UI.Switch functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE",15
TIMOB-10878,"Blackberry: Implement important UI.TableView functionality","Use the implementation matrix to see what's remaining (these are things that are not implemented but supported in Cascades): https://docs.google.com/a/macadamian.com/spreadsheet/ccc?key=0Ajs-e76-B0yIdG1oLVVleVVxaGRYd3lWWXd0czhqUFE Implement at least: * Titanium.UI.TableView.addEventListener * Titanium.UI.TableView.appendRow * Titanium.UI.TableView.setData",21
TIMOB-10919,"Windows: Implement UI.PickerRow ""title"" and ""setTitle""",NULL,3
TIMOB-11093,"iOS: Update jscore to 538.11.1 version","Ticket for tracking the update of JSCore to the version shipping with a later version of iOS. Document is here: https://wiki.appcelerator.org/display/pe/iOS+-+Updating+JSCore. We can pick a version based on a tag from https://trac.webkit.org/browser/tags?order=name. Some versions we have been able to ascertain, but it is unclear why we wouldn't just pick the latest stable version. iOS 8.X: https://trac.webkit.org/browser/tags/Safari-600.1.4 iOS 8.1.0: AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B411 Safari/600.1.4 iOS 8.0.2: AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12A405 Safari/600.1.4 iOS 8.0.0: AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12A365 Safari/600.1.4 iOS: 7.1: https://trac.webkit.org/browser/tags/Safari-537.51.2 7.1: AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D167 Safari/9537.53 iOS 6.1.3: http://www.opensource.apple.com/release/ios-613/ ",34
TIMOB-11172,"iOS: Debugger: breakpoint at unassigned variable declaration skipped","Breakpoints at unassigned variable declarations are skipped. For example: {code} var deadVar1; // breakpoint Ti.API.info('Global Variables Defined!'); (function(){ var deadVar2; // breakpoint Ti.API.info('Anonymous Function Called!'); })(); alert('App Exited!'); {code} Running this code in debug mode will skip all breakpoints. This does not occur in Android, this is a parity issue. Steps to Reproduce: 1. Run code in debug (manually insert breakpoints as per code comments): {code} var deadVar1; // breakpoint Ti.API.info('Global Variables Defined!'); (function(){ var deadVar2; // breakpoint Ti.API.info('Anonymous Function Called!'); })(); alert('App Exited!'); {code} Actual Result: App exits without hitting any breakpoints. Expected Result: The first breakpoint should be hit and pressing 'Resume' should hit the next breakpoint. Here is the expected console log for the sample code: {code} [INFO] Global Variables Defined! [INFO] Anonymous Function Called! {code}",1
TIMOB-11188,"iOS: Debugger: breakpoints ignored if app is only primitive assignment statements","Breakpoints ignored if the app is only comprised of primitive assignment statements. This is not a regression. This does not occur on Android. This is a parity issue. This is basic functionality. Steps to Reproduce: 1. Run code in debug (manually insert breakpoints as per code comments): {code} var a = 1; // breakpoint var b = 2; // breakpoint var c = 3; // breakpoint var d = 4; // breakpoint var e = 5; // breakpoint var f = 6; // breakpoint {code} Actual Result: All breakpoints ignored. Expected Result: All breakpoints should be hit (as 'Resume' is pressed).",1
TIMOB-11628,"Correct spacing and grammar in Android NDK console warning.","When packaging an Android module and you forget to make a link to the NDK, it provides a warning, but the warning is missing a space and a period. ""Check your modules' build properties)You may need to install""",3
TIMOB-14008,"Android: layout vertical and zIndex problem","*Expected result* The red view should be located on the black view. *Actual result* The black view is missing. *Note* Works on iOS (both the red view and black view show), but not Android. *Test case* {code:javascript}var win = Ti.UI.createWindow({ backgroundColor : '#fff', navBarHidden : true, exitOnClose : true }); var view = Ti.UI.createView({ layout : 'vertical' }); view.add(Ti.UI.createView({ width : 200, height : 50, backgroundColor : 'red', zIndex : 1 })); view.add(Ti.UI.createView({ height : 50, backgroundColor : 'black', top : -15 })); win.add(view) win.open(); {code}",8
TIMOB-11603,"Android: invalid android path in bash profile results in project creation error, improve error message","Failed to build a project for Android in Titanium Studio due to incorrect path to android SDK in a bash profile. *It happens only in 3.0.0.version of Studio.* It creates projects in Studio 2.1.2 Test steps: 1.Go to Titanium Studio > Preferences > Titanium 2. Browse and set Android SDK Home 3. Browse and set Android NDK Home Note the difference with a bash profile. export ANDROID_SDK=/myname/Documents/android-sdk-macosx export ANDROID_NDK=/myname/Documents/android-ndk-r8 4. Create a project for Android. Actual result: Fail to create a project. Failed to locate android-8 and android 2.2 Expected result: A project should be created successfully. ",3
TIMOB-11637,"Ti.Network.HTTPClient needs to be implemented",NULL,21
TIMOB-11769,"CLI: colors, lines, and messages ill-formatted with CLI enabled","Console: colors, lines, and messages ill-formatted with CLI enabled (see screenshots). Steps to Reproduce: 1. Run code: {code} /* console */ if(Ti.Platform.osname != 'android') // TIMOB-11294 - Android: console: log functions fail in commonjs require { console.log('console LOG'); console.log(['console LOG', 'ARG1', 'ARG2']); console.debug('console DEBUG'); console.debug(['console DEBUG', 'ARG1', 'ARG2']); console.info('console INFO'); console.info(['console INFO', 'ARG1', 'ARG2']); console.warn('console WARN'); console.warn(['console WARN', 'ARG1', 'ARG2']); console.error('console ERROR'); console.error(['console ERROR', 'ARG1', 'ARG2']); } else { Ti.API.info('TIMOB-11294 - Android: console: log functions fail in commonjs require'); } /* Ti.API */ Ti.API.trace('Ti.API TRACE'); Ti.API.trace(['Ti.API TRACE', 'ARG1', 'ARG2']); Ti.API.debug('Ti.API DEBUG'); Ti.API.debug(['Ti.API DEBUG', 'ARG1', 'ARG2']); Ti.API.info('Ti.API INFO'); Ti.API.info(['Ti.API INFO', 'ARG1', 'ARG2']); Ti.API.warn('Ti.API WARN'); Ti.API.warn(['Ti.API WARN', 'ARG1', 'ARG2']); Ti.API.error('Ti.API ERROR'); Ti.API.error(['Ti.API ERROR', 'ARG1', 'ARG2']); /* Ti.API.log */ Ti.API.log('TRACE', 'Ti.API.log TRACE'); Ti.API.log('TRACE', ['Ti.API.log TRACE', 'ARG1', 'ARG2']); Ti.API.log('DEBUG', 'Ti.API.log DEBUG'); Ti.API.log('DEBUG', ['Ti.API.log DEBUG', 'ARG1', 'ARG2']); Ti.API.log('INFO', 'Ti.API.log INFO'); Ti.API.log('INFO', ['Ti.API.log INFO', 'ARG1', 'ARG2']); Ti.API.log('WARN', 'Ti.API.log WARN'); Ti.API.log('WARN', ['Ti.API.log WARN', 'ARG1', 'ARG2']); Ti.API.log('ERROR', 'Ti.API.log ERROR'); Ti.API.log('ERROR', ['Ti.API.log ERROR', 'ARG1', 'ARG2']); Ti.API.log('LOG', 'Ti.API.log LOG'); Ti.API.log('LOG', ['Ti.API.log LOG', 'ARG1', 'ARG2']); /* Ti.iOS.API */ if(Ti.Platform.osname == 'iphone' || Ti.Platform.osname == 'ipad') { Ti.API.timestamp('Ti.API TIMESTAMP'); Ti.API.timestamp(['Ti.API TIMESTAMP', 'ARG1', 'ARG2']); } {code} Actual Result: colors, line formatting misaligned, and some messages do not display at all. Expected Result: colors, lines, and messages should appear and be properly formatted",8
TIMOB-11686,"BlackBerry: Invocations","As a BlackBerry developer, I want the ability to integrate with other applications on the platform in order to provide better multitasking for the user.",3
TIMOB-11700,"Android: Make generated projects importable into Eclipse","When we build an android projects using our build scripts, it would be nice if we could directly import that project into eclipse and run it from there to debug. We will need to create things like .project to make this an eclipse project.",3
TIMOB-12646,"iOS: TableViewRow selection causes child view's backgroundColor to disappear","Platform: iOS Device: iOS Simulator 6.0 & iPod Touch (4th gen, software version 6.0.1) Repro: 1. Create a TableView 2. Create a TableViewRow 3. Create a View with a backgroundColor 4. Add the view to the row 5. Add the row to the table 6. Tap and hold on the row Result: The row's selectedBackgroundColor becomes visible and the view's backgroundColor becomes transparent Expected: The row's selectedBackgroundColor becomes visible and the view's backgroundColor remains visible Additional Notes: 1. If the view inside of the row has children, they are still displayed. Only the view's backgroundColor is affected. 2. Setting the row's selectionStyle to NONE prevents the backgroundColor of the view from disappearing.",8
TIMOB-11867,"CLI: Alloy: Mobile Packaging Failed","Steps To Reproduce: 1. Create Alloy project 2. Package to Mobile Web Project Actual: Failed to package appears Expected: Mobile Package must occur without error",8
TIMOB-11932,"BlackBerry: Implement important Titanium.Media functionality",NULL,17
TIMOB-11943,"Android: blur event not called when keyboard is hidden","h1. Problem description When a TextArea is focused, and the user clicks the back button to hide the soft keyboard, the blur event is not fired. It is not also possible to use the 'android:back' event, as it is not fired when hiding the keyboard. h1. Steps to reproduce - Use the following code to test the bug. - Click on the black window to open a second one with a TextArea - Click on it to show the keyboard - Hit the back button: the 'blur' and 'android:back' events are not fired when keyboard is being hidden {code} // Create a window var root = Ti.UI.createWindow({ backgroundColor : 'black', modal: true }); root.addEventListener('click', function() { var win = Ti.UI.createWindow({ backgroundColor : 'white', modal: true }); var toolbar = Titanium.UI.createTextArea({ height: 37, width: 200, font: {fontSize:16,fontFamily:'ARIAL', fontWeight:'solid'}, color: '#000', borderWidth: 1, borderColor: '#828281', borderRadius: 12, suppressReturn: false, scrollable: false }); toolbar.addEventListener('blur', function() { alert('blurrrred'); }); win.addEventListener('android:back', function() { alert('baaaack'); }); win.add(toolbar); win.open(); }) root.open(); {code}",5
TIMOB-12246,"Android: Auto correct set to false on TextField with KEYBOARD_DECIMAL_PAD doesn't allow decimal point","h2.Problem When the keyboardType propery of a TextField is set to Ti.UI.KEYBOARD_DECIMAL_PAD and autocorrect is set to false, the decimal point is not allowed to be entered into the textfield. This leaves no way to enter dollar amounts without using the default keyboard, which allows any character, and is therefore not appropriate. h2.Expected Behavior autocorrect should not be interfering with numbers in the text field. h2.Actual Behavior When auto correct is set to false The ""numbers and punctuation"" keyboard appears, but clicking on the decimal point has no effect. h2.Testcase {panel:title=app.js} {code} var win = Ti.UI.createWindow({ backgroundColor : 'white' }); var textField = Ti.UI.createTextField({ borderStyle : Ti.UI.INPUT_BORDERSTYLE_ROUNDED, color : '#336699', keyboardType : Ti.UI.KEYBOARD_DECIMAL_PAD, returnKeyType : Ti.UI.RETURNKEY_DEFAULT, autocorrect : false, textAlign : 'right', width : '50%' }); win.add(textField); win.open(); {code} {panel}",3
TIMOB-13401,"iOS 6: insertRowBefore uses animation with animated set to false and animationStyle set to none","*Description* insertRowBefore uses a fade animation although animated is set to false and animationStyle is set to NONE (see code sample) *Expected result* row is simply inserted without an animation *current result* row is inserted with fade animation *additional notes* might also apply to insertRowAfter and appendRow and deleteRow (not tested) *sample* {code} /* * Single Window Application Template: * A basic starting point for your application. Mostly a blank canvas. * * In app.js, we generally take care of a few things: * - Bootstrap the application with any data we need * - Check for dependencies like device type, platform version or network connection * - Require and open our top-level UI component * */ //bootstrap and check dependencies if (Ti.version < 1.8) { alert('Sorry - this application template requires Titanium Mobile SDK 1.8 or later'); } // This is a single context application with mutliple windows in a stack (function() { //determine platform and form factor and render approproate components var win = Ti.UI.createWindow({ width : Ti.UI.FILL, height : Ti.UI.FILL, }); var tv = Ti.UI.createTableView({ width : Ti.UI.FILL, height : Ti.UI.FILL, }); var rows = []; for (var i = 0; i < 50; i++) { rows.push(Ti.UI.createTableViewRow({ title : 'Row ' + i })); } var row = Ti.UI.createTableViewRow({ title : 'Insert Row Before 0' }); row.addEventListener('click', function() { tv.insertRowBefore(0, { title : 'Row inserted before 0' }); }); rows.push(row); var row = Ti.UI.createTableViewRow({ title : 'Insert Row Before 1' }); row.addEventListener('click', function() { tv.insertRowBefore(1, { title : 'Row inserted before 1 w/o anim' }, { animationStyle : Ti.UI.iPhone.RowAnimationStyle.NONE }); }); rows.push(row); var row = Ti.UI.createTableViewRow({ title : 'Insert Row Before this' }); row.addEventListener('click', function(e) { tv.insertRowBefore(e.index, { title : 'Row inserted before 0' }); }); rows.push(row); var row = Ti.UI.createTableViewRow({ title : 'Insert Row Before this' }); row.addEventListener('click', function(e) { tv.insertRowBefore(e.index, { title : 'Row inserted before w/o anim' }, { animationStyle : Ti.UI.iPhone.RowAnimationStyle.NONE, animated : false, }); }); rows.push(row); tv.data = rows; win.add(tv); win.open(); })(); {code}",5
TIMOB-12034,"CLI: Building for android with '-b' -build only flag starts the daemon & waits for the device after building the app","Steps to reproduce: 1.Launch CLI by typing 'titanium' in the terminal. 2.Run 'ti build -p android -b -d --log-level trace -s 3.0.0.v20121211130203'. Actual results: 1.The app builds but it starts the deamon & waits for the device. Expected results: 1.The app should build but the deamon should not start & not wait for the android device as we have specified the '-b' i.e build only flag. Trace output: {code} LChoudharyMBP:~ lokeshchoudhary$ ti build -p android -b true -d /Users/lokeshchoudhary/Desktop/test/test --log-level trace -s 3.0.0.v20121211130203 Titanium Command-Line Interface, CLI version 3.0.21, Titanium SDK version 3.0.0.v20121211130203 Copyright (c) 2012, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ Android SDK path: /Users/lokeshchoudhary/Desktop/android-sdk-macosx [DEBUG] No project level plugins to load [DEBUG] Loaded plugin hooks: [DEBUG] /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121211130203/cli/hooks/plugins.js [DEBUG] /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121211130203/android/cli/hooks/install.js [DEBUG] /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121211130203/android/cli/hooks/run.js [INFO] logfile = /Users/lokeshchoudhary/Desktop/test/test/build.log [DEBUG] /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/builder.py build test /Users/lokeshchoudhary/Desktop/android-sdk-macosx /Users/lokeshchoudhary/Desktop/test/test com.app.test [INFO] Titanium SDK version: 3.0.0 (12/07/12 12:02 fc56f4c) [DEBUG] com.app.test installed? False [DEBUG] Detecting modules in /Users/lokeshchoudhary/Desktop/test/test/modules [DEBUG] Detecting modules in /Users/lokeshchoudhary/Library/Application Support/Titanium/modules [DEBUG] Detected module for android: ti.cloudpush 2.0.7 @ /Users/lokeshchoudhary/Library/Application Support/Titanium/modules/android/ti.cloudpush/2.0.7 [DEBUG] Detected module for android: ti.brightcove 2.0.1 @ /Users/lokeshchoudhary/Library/Application Support/Titanium/modules/android/ti.brightcove/2.0.1 [DEBUG] Detected module for commonjs: ti.cloud 2.3.0 @ /Users/lokeshchoudhary/Library/Application Support/Titanium/modules/commonjs/ti.cloud/2.3.0 [DEBUG] Detected module for iphone: com.soasta.touchtest 1.0 @ /Users/lokeshchoudhary/Library/Application Support/Titanium/modules/iphone/com.soasta.touchtest/1.0 [INFO] Copying CommonJS modules... [INFO] Copying project resources.. [INFO] Tiapp.xml unchanged, skipping class generation [DEBUG] detected module analytics, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-analytics.jar [DEBUG] detected module android, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-android.jar [DEBUG] adding required library: jaxen-1.1.1.jar [DEBUG] adding required library: ti-commons-codec-1.3.jar [DEBUG] adding required library: kroll-common.jar [DEBUG] adding required library: titanium.jar [DEBUG] detected module app, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-app.jar [DEBUG] detected module ui, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar [DEBUG] adding required library: android-support-v4.jar [DEBUG] detected module filesystem, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-filesystem.jar [DEBUG] detected module media, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-media.jar [DEBUG] detected module locale, path = /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-locale.jar [INFO] Compiling Javascript Resources ... [DEBUG] Processing Android resource drawables [DEBUG] found drawable-long-land-hdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-long-land-hdpi/default.png [DEBUG] found drawable-long-land-ldpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-long-land-ldpi/default.png [DEBUG] found drawable-long-port-hdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-long-port-hdpi/default.png [DEBUG] found drawable-long-port-ldpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-long-port-ldpi/default.png [DEBUG] found drawable-notlong-land-hdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-land-hdpi/default.png [DEBUG] found drawable-notlong-land-ldpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-land-ldpi/default.png [DEBUG] found drawable-notlong-land-mdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-land-mdpi/default.png [DEBUG] found drawable-notlong-port-hdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-port-hdpi/default.png [DEBUG] found drawable-notlong-port-ldpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-port-ldpi/default.png [DEBUG] found drawable-notlong-port-mdpi splash screen at /Users/lokeshchoudhary/Desktop/test/test/Resources/android/images/res-notlong-port-mdpi/default.png [DEBUG] /Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools/aapt package -f -M AndroidManifest.xml -A /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/assets -S res -I /Users/lokeshchoudhary/Desktop/android-sdk-macosx/platforms/android-8/android.jar -I ""/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar"" -F /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app.ap_ [DEBUG] creating unsigned apk: /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app-unsigned.apk [DEBUG] from resource zip => assets/Resources/KS_nav_ui.png [DEBUG] from resource zip => assets/Resources/KS_nav_views.png [DEBUG] from resource zip => assets/Resources/app.js [DEBUG] from resource zip => assets/Resources/appicon.png [DEBUG] from resource zip => assets/Resources/default.png [DEBUG] from resource zip => assets/app.json [DEBUG] from resource zip => assets/index.json [DEBUG] from resource zip => assets/tiapp.xml [DEBUG] from resource zip => res/drawable/appicon.png [DEBUG] from resource zip => res/drawable/background.png [DEBUG] from resource zip => res/layout/titanium_tabgroup.xml [DEBUG] from resource zip => AndroidManifest.xml [DEBUG] from resource zip => resources.arsc [DEBUG] from resource zip => res/drawable-long-land-hdpi/background.png [DEBUG] from resource zip => res/drawable-long-land-ldpi/background.png [DEBUG] from resource zip => res/drawable-long-port-hdpi/background.png [DEBUG] from resource zip => res/drawable-long-port-ldpi/background.png [DEBUG] from resource zip => res/drawable-notlong-land-hdpi/background.png [DEBUG] from resource zip => res/drawable-notlong-land-ldpi/background.png [DEBUG] from resource zip => res/drawable-notlong-land-mdpi/background.png [DEBUG] from resource zip => res/drawable-notlong-port-hdpi/background.png [DEBUG] from resource zip => res/drawable-notlong-port-ldpi/background.png [DEBUG] from resource zip => res/drawable-notlong-port-mdpi/background.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar => ti/modules/titanium/ui/widget/webview/binding.js [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar => ti/modules/titanium/ui/widget/webview/binding.min.js [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar => ti/modules/titanium/ui/widget/webview/json2.js [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar => ti/modules/titanium/ui/widget/webview/polling.js [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/modules/titanium-ui.jar => ti/modules/titanium/ui/widget/webview/polling.min.js [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/build.properties [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/background.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_check_buttonless_on.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_check_buttonless_on_18.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_check_buttonless_on_48.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_check_buttonless_on_64.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_more.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_more_18.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_more_48.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_more_64.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_picker_normal.9.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_picker_pressed.9.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/btn_picker_selected.9.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/default_icon.png [DEBUG] from JAR /Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/titanium.jar => org/appcelerator/titanium/res/drawable/photoDefault.png [DEBUG] installing native SDK libs [DEBUG] keytool -v -list -keystore ""/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/dev_keystore"" -storepass ******* -alias tidev [DEBUG] jarsigner -sigalg MD5withRSA -digestalg SHA1 -storepass ******* -keystore ""/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121207120202/android/dev_keystore"" -signedjar /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app.apk /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app-unsigned.apk tidev [DEBUG] /Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools/zipalign -v 4 /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app.apk /Users/lokeshchoudhary/Desktop/test/test/build/android/bin/app.apkz [INFO] Project built successfully in 7s 903ms * daemon not running. starting it now on port 5037 * * daemon started successfully * - waiting for device - {code}",3
TIMOB-13392,"Android: Implement Scrollable Tabs","As seen in the [documentation|http://developer.android.com/design/patterns/actionbar.html] [(another place)|http://developer.android.com/design/building-blocks/tabs.html], there's a new subtype of tab bar in the Android, called Scrollable Tabs.",13
TIMOB-12848,"Android: Using the camera on certain devices causes the app to crash","Call Ti.Media.showCamera and the camera opens up fine, takes the picture fine, then click ok, and the app crashes before reaching the success function. The picture does manage to get saved into the photo gallery. Sample code. Paste this into a new Android application. {code} var win = Titanium.UI.createWindow(); var imageView = Ti.UI.createImageView({height: Ti.UI.FILL, width: Ti.UI.Fill}); win.add(imageView); Titanium.Media.showCamera({ success:function(event) { Ti.API.info('#### Camera Success'); var cropRect = event.cropRect; var image = event.media; Ti.API.info(image.length); var filename = Titanium.Filesystem.tempDirectory + ""/""+ 'camera_photo' + new Date().getTime() + "".png""; Ti.API.info(filename); var f = Titanium.Filesystem.getFile(filename); Ti.API.info(f.nativePath); if (f.exists()) { Ti.API.info('The file exist , trying to delete it before using it :' + f.deleteFile()); f = Titanium.Filesystem.getFile(filename); } f.write(image); alert('Camera Success! The file size is '+f.size+' bytes.\n Now trying to assign it to an image on the screen (this may fail for hi res images)') imageView.image = f.nativePath; }, cancel:function() { Ti.API.info('#### Camera Cancel'); }, error:function(error) { // create alert Ti.API.info('#### Camera Error'); var a = Titanium.UI.createAlertDialog({title:'Camera'}); // set message if (error.code == Titanium.Media.NO_CAMERA) { a.setMessage('Device does not have video recording capabilities'); } else { a.setMessage('Unexpected error: ' + error.code); } // show alert a.show(); }, allowEditing:true }); win.open(); {code}",13
TIMOB-12116,"BlackBerry: Implement Titanium.Database","Need to implement at least: * Titanium.Database * Titanium.Database.DB ** Titanium.Database.DB.close ** Titanium.Database.DB.execute ** Titanium.Database.DB.lastInsertRowId ** Titanium.Database.DB.remove * Titanium.Database.install * Titanium.Database.open * Titanium.Database.ResultSet ** Titanium.Database.ResultSet.close ** Titanium.Database.ResultSet.fieldByName ** Titanium.Database.ResultSet.getRowCount ** Titanium.Database.ResultSet.isValidRow ** Titanium.Database.ResultSet.next",21
TIMOB-13398,"iOS: support ellipsize property of Ti.UI.Label (parity)","Android and mobileweb support the ellipsize property of Ti.UI.Label. Please add support for this property under iOS as well.",5
TIMOB-12169,"CLI: Project compilation - no build.log is being created","Building a mobile project to iOS device or simulator wont create build.log if CLI is enabled. Occurs in 3.0.0 and 3.1.0 Test steps: 1. Create a project in Titanium Studio 2. Run it as iOS simulator or build it to device 3. Check project's build folder for build.log Actual result: No build.log Expected result: build.log should be created in both scenarios (success or failure) ",13
TIMOB-12457,"iOS: Ti.Locale.currentLocale and currentCountry issues","h6.Ti.Locale issue Ti.Locale is NOT working as expected after reading the doc. h6.Expected currentLocale and getCurrentLocale() to work like language i.e. http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.Locale-method-getCurrentLocale h6.Repro sequence {code} Ti.API.error(""locale: "" + Ti.Locale.currentLocale); Ti.API.error(""country: "" + Ti.Locale.currentCountry); Ti.API.error(""language: "" + Ti.Locale.currentLanguage); Ti.API.error(""locale: "" + Ti.Locale.getCurrentLocale()); Ti.API.error(""country: "" + Ti.Locale.getCurrentCountry()); Ti.API.error(""language: "" + Ti.Locale.getCurrentLanguage()); {code} h6.returns {code} [ERROR] locale: undefined [ERROR] country: undefined [ERROR] language: fr [ERROR] locale: fr-BE [ERROR] country: BE [ERROR] language: fr {code} h6.yet another console output {code} [ERROR] : locale: undefined [ERROR] : country: undefined [ERROR] : language: en [ERROR] : locale: en-US [ERROR] : country: US [ERROR] : language: en {code} I am not competent enough in objective-C and mobile SDK knowledge but the implementation of locale module here looks fishy to me (I would expect implementations for currentLocale and currentCountry). I tested w/ SDKs 1.8.2, 2.1.2.GA and 3.0.0.GA on Mac OSX for iOS.",2
TIMOB-12223,"BlackBerry: Implement Titanium.UI.WebView","Add at least: * Titanium.UI.WebView.addEventListener * Titanium.UI.WebView.evalJS * Titanium.UI.WebView.html * Titanium.UI.WebView.onCreateWindow * Titanium.UI.WebView.remove * Titanium.UI.WebView.url",21
TIMOB-12225,"BlackBerry: Implement important Titanium.Facebook functionality",NULL,17
TIMOB-12226,"BlackBerry: Implement important Titanium.Media.AudioPlayer functionality",NULL,15
TIMOB-12227,"BlackBerry: Implement important Titanium.Media.Item functionality",NULL,15
TIMOB-12228,"BlackBerry: Implement important Titanium.Media.MusicPlayer functionality",NULL,15
TIMOB-12230,"BlackBerry: Implement important Titanium.Media.VideoPlayer functionality",NULL,15
TIMOB-12233,"BlackBerry: Implement important Titanium.Accelerometer functionality","h3. Acceptance Test {code} var win = Ti.UI.createWindow({ layout: 'vertical' }); var enableAccelerometer = Ti.UI.createButton({ title: 'Toggle Accelerometer' }); win.add(enableAccelerometer); var labels = ['x', 'y', 'z'].map(function(coord) { var label = Ti.UI.createLabel({text: coord + ': N/A'}); win.add(label); return label; }); function onUpdate(e) { labels[0].text = e.x; labels[1].text = e.y; labels[2].text = e.z; } var accelerometerEnabled = false; enableAccelerometer.addEventListener('click', function() { accelerometerEnabled ? Ti.Accelerometer.removeEventListener('update', onUpdate) : Ti.Accelerometer.addEventListener('update', onUpdate); accelerometerEnabled = !accelerometerEnabled; }); win.open(); {code} # Try moving the device around. No updates should be displayed. # Click ""Toggle Accelerometer"". Move device and you should now see updates (x, y, z values). # Click the toggle button again and the updates should stop. Repeat and verify. ",15
TIMOB-12235,"BlackBerry: Implement important Titanium.Contacts functionality",NULL,15
TIMOB-12236,"BlackBerry: Implement important Titanium.Analytics functionality",NULL,15
TIMOB-12237,"BlackBerry: Implement important Titanium.Map functionality","Need to implement at least: * Titanium.Map.createAnnotation * Titanium.Map.createView * Titanium.Map.STANDARD_TYPE",21
TIMOB-12238,"BlackBerry: Implement important Titanium.Map.Annotation functionality","Need to implement at least: * Titanium.Map.ANNOTATION_GREEN * Titanium.Map.ANNOTATION_PURPLE * Titanium.Map.ANNOTATION_RED",21
TIMOB-12239,"BlackBerry: Implement important Titanium.Map.View functionality","Need to implement at least: * Titanium.Map.View.add * Titanium.Map.View.addAnnotation * Titanium.Map.View.addEventListener * Titanium.Map.View.removeAnnotation * Titanium.Map.View.setLocation",21
TIMOB-12280,"Log messages lost when logging commands are placed in a loop","While testing TISTUD-3120 I ran into the issue where log output in a for loop did not appear (see screenshot). I can only reproduce this issue in 3.0.2 not 3.1.0 or 3.0.1 using the attached app.js file in a standard titanium project. This is a regression. Steps to reproduce: 1. Open the Titanium project. 2. Run in Simulator. Expected results: All console output should be shown filtered based on settings. Actual results: Console output missing lines from the looped log calls.",8
TIMOB-12372,"Android: Layout resources in res/layout/filename.xml no longer work","h4. Description Android layout resources no longer work as they did in 2.1.4GA. h4. Code to reproduce To customize the tab group in Android so that it is hidden, we used to be able to add a file in /platform/android/res/layout/titanium_tabgroup.xml. Code inside titanium_tabgroup.xml: {code} {code} app.js {code} // create base UI tab and root window // var win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff' }); var tab1 = Titanium.UI.createTab({ icon:'KS_nav_views.png', title:'Tab 1', window:win1 }); var label1 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 1', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win1.add(label1); // // create controls tab and root window // var win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff' }); var tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Tab 2', window:win2 }); var label2 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 2', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win2.add(label2); // // add tabs // tabGroup.addTab(tab1); tabGroup.addTab(tab2); // open tab group tabGroup.open(); {code} This no longer works in 3.0GA.",3
TIMOB-12409,"BlackBerry: Implement important Titanium.Platform functionality","Implement at least: * Titanium.Platform.createUUID * Titanium.Platform.openURL",21
TIMOB-12410,"BlackBerry: Implement important Titanium.App functionality","Implement at least: * Titanium.App.deployType * Titanium.App.getArguments * Titanium.App.guid * Titanium.App.id",21
TIMOB-12411,"Android: Ti.Android.getCurrentActivity() fails with an exception","h1. Problem description Calling Ti.Android.getCurrentActivity() always fails with an exception in the logs. {code} E/TiJSError( 1288): (main) [2,1195] - Message: Uncaught TypeError: Object # has no method 'getCurrentActivity' {code} h1. Steps to reproduce Use this simple app to test: {code} Titanium.UI.setBackgroundColor('#000'); var win1 = Titanium.UI.createWindow({ backgroundColor:'#fff', fullscreen: true }); win1.open(); Titanium.API.info(""Activity: "" + Titanium.Android.getCurrentActivity()); {code} Changing from getCurrentActivity() to currentActivity (direct access to the property) works fine.",3
TIMOB-12516,"BlackBerry: Implement important Titanium.UI.Toolbar functionality",NULL,15
TIMOB-12600,"CLI: building for Android device while the emulator is open generates a wrong Error Message","h6. Problem Building for Android device from CLI, while the Android emulator open, generates an Error Message at the end. However the app is actually correctly installed. h6. Steps to reproduce 1. Be sure to have the Android Emulator open 2. Attach a device and build a project for the device from CLI: $ ti build -p android -T device Result: application is correctly installed on the device, however from console there is an Error message in the end. {code} [INFO] Application installed. Launch from drawer on Home Screen [INFO] Launching appliation on device. error: more than one device and emulator [ERROR] Project failed to build after 13s 197ms {code} (also note the typo: ""appliation"" in the [INFO] line)",2
TIMOB-12604,"Android: Closing the emulator, 'Emulator has exited' log in not printed on console.","Android: Closing the emulator, 'Emulator has exited' log in not printed on console. Its not a regression. Steps to reproduce: 1. Run a application in android emulator. 2. Close the emulator. Actual: no new log occur on console. Expected: 'Emulator has exited' should occur on console. ",2
TIMOB-12661,"CLI: Support adb's -s option for pointing a build to a specific emulator or device","It would be extremely helpful, and give the CLI more power with Android, if developers were able to specify specifically which device or emulator for which they would like to build. Right now the build process allows us to specify and avd id which would let you pick an emulator, but even that is not ideal as you don't really have a way of knowing an emulator's id from the *android list avd* as it isn't listed. Ideally, I should be able to call *adb devices*, see my listing of emulators and devices, than be able to pass that serial number to the *titanium build* command as an option, directing the build process to that specific emulator or device. The build process _tries_ to be intelligent about this, but more often than not I get errors like: * It fails if there is a connected device AND an emulator open * Even with an emulator already it open, it often attempts to load an entirely different one * Tries to use emulators not compatible with the app (like a non-Google API emulator with an app that uses maps) Allowing a command like the following would make it really easy for developers to have multiple open emulators and connected devices and still get expected behavior: {code} titanium build -p android -s EMULATOR_OR_DEVICE_SERIAL {code} Obviously I leave the choice of the option flag to the implementor. ""-s"" would correspond to the adb command, but this is already in use for *titanium build* for specifying the target Titanium SDK. ",3
TIMOB-12764,"Windows: Android SDKs not recognized without moving them","This is a regression. Works correctly in TISTUD 2.1.2. Windows: Android SDKs not recognized in Preferences. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium. 3. Clear Android SDK Path and Apply. 4. Browse to Android SDK to select path. Actual Result: Android SDKs not recognized. Expected Result: Android SDKs recognized.",8
TIMOB-12765,"Backport: Windows: Android SDKs not recognized without moving them","This is a regression. Works correctly in TISTUD 2.1.2. Windows: Android SDKs not recognized in Preferences. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium. 3. Clear Android SDK Path and Apply. 4. Browse to Android SDK to select path. Actual Result: Android SDKs not recognized. Expected Result: Android SDKs recognized.",8
TIMOB-12960,"TiAPI: Cannot add a whitespace at the end of string in i18n strings.xml","Use the following xml in the i18n en strings.xml file: {code} There should be space of that thing. {code} And use the following in app js: {code} var win = Ti.UI.createWindow({ layout: ""vertical"" }); // build a string from the strings file that has built-in space. var s = L(""share"") + ""!on each side!"" + L(""share2""); alert(s); {code} The result is different in 3.0 vs 2.1.3. In 3.0, it seems all whitespaces from strings from the language file are trimmed. The same behavior is seen in Android also. ",1
TIMOB-13190,"BlackBerry: support project creation with multiple deployment targets","Description: 1.Create a default app with templates in the studio & select other deploy targets along with blackberry 2.Now open the resources folder of the created app in studio Actual Result: 1.The 'blackberry' folder does not get created in the resources folder as 'android','iphone','mobileweb' 2.due to this running the app gives errors: {code} [INFO] Running retCode = builder.run(ipAddress, devicePassword, debugToken, storePass, outputDir) File ""/Users/lokeshchoudhary/Desktop/bb-mobilesdk-osx/mobilesdk/osx/3.1.0.v20130204182020/blackberry/builder.py"", line 78, in run resources = os.listdir(self.blackberryResources) OSError: [Errno 2] No such file or directory: '/Users/lokeshchoudhary/Desktop/Titanium BB Workspace/default_123/Resources/blackberry'[INFO] Running retCode = builder.run(ipAddress, devicePassword, debugToken, storePass, outputDir) File ""/Users/lokeshchoudhary/Desktop/bb-mobilesdk-osx/mobilesdk/osx/3.1.0.v20130204182020/blackberry/builder.py"", line 78, in run resources = os.listdir(self.blackberryResources) OSError: [Errno 2] No such file or directory: '/Users/lokeshchoudhary/Desktop/Titanium BB Workspace/default_123/Resources/blackberry' {code} NOTE : If we create a default app with only blackberry as target then the 'blackberry' folder is getting created Expected Result: 1.The 'blackberry' folder gets created along with other targets ",5
TIMOB-13254,"Windows: Implement Ti.UI.WebView","Implement TI.UI.WebView functionality. This may require some other functionality to be implemented first.",21
TIMOB-13364,"Android: TextArea maxLength not working in Android","According to the docs, TextArea supports maxLength property from SDK 3.0. However, maxLength does not work in Android. In TiUIText.java, the code that reads the maxLength is: if (d.containsKey(TiC.PROPERTY_MAX_LENGTH) && field) { maxLength = TiConvert.toInt(d, TiC.PROPERTY_MAX_LENGTH); } TextArea has ""field"" boolean set to false, so maxLength is always ignored. Steps to reproduce. Create simple App.js: {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var textArea = Ti.UI.createTextArea({ borderWidth: 2, borderColor: '#bbb', borderRadius: 5, color: '#888', textAlign: 'left', maxLength: 10, top: 60, width: 300, height : 150 }); win.add(textArea); win.open(); {code} Launch app and start writing in the text area. You can enter more than 10 chars, despite maxLength is set to 10. Tested with SDK 3.0.0.GA in Android 2.3.3 and Android 4.1",3
TIMOB-13520,"Android Emulator: improve error message from missing ia32-libs dependency on linux","The first android emulator run experience of a linux user on a clean system is: {code} Titanium Command-Line Interface, CLI version 3.1.0-cr, Titanium SDK version 3.0.2.GA Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ [INFO] logfile = /home/linux/Desktop/Titanium_Studio/Titanium_Studio_RC/Work_Space/MyProject/build.log [ERROR] : Project failed to build after 275ms [INFO] Building MyProject for Android ... one moment [INFO] Titanium SDK version: 3.0.2 (02/15/13 19:02 5a77fe7) [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File ""/home/linux/.titanium/mobilesdk/linux/3.0.2.GA/android/builder.py"", line 2392, in [ERROR] builder.build_and_run(False, avd_id, debugger_host=debugger_host) [ERROR] File ""/home/linux/.titanium/mobilesdk/linux/3.0.2.GA/android/builder.py"", line 1984, in build_and_run [ERROR] self.wait_for_device('e') [ERROR] File ""/home/linux/.titanium/mobilesdk/linux/3.0.2.GA/android/builder.py"", line 450, in wait_for_device [ERROR] devices = self.sdk.list_devices() [ERROR] File ""/home/linux/.titanium/mobilesdk/linux/3.0.2.GA/android/androidsdk.py"", line 264, in list_devices [ERROR] (out, err) = subprocess.Popen([adb, 'devices'], stdout=subprocess.PIPE, stderr=subprocess.PIPE).communicate() [ERROR] File ""/usr/lib/python2.7/subprocess.py"", line 679, in __init__ [ERROR] errread, errwrite) [ERROR] File ""/usr/lib/python2.7/subprocess.py"", line 1249, in _execute_child [ERROR] raise child_exception [ERROR] OSError: [Errno 2] No such file or directory [ERROR] : Project failed to build after 584ms {code} It seems a bit cryptic. Please improve error message if possible.",8
TIMOB-13545,"Android: ImageView: Remote image with ""@"" character doesn't display","*Problem description* If you set an image with a ""@"" in the path, the image won't be loaded. This is because getCleanUri thinking it's a domain address. Therefore the test on the hash will return false. So the image is downloaded but not drawn. *Repro notes* Paste the @2x URL in the browser to verify the URL is valid. Uncomment cd-mini-graphic image to verify it working for standard images. Only the URL with @2x doesn't work. Works on iOS, not on Android. *Test case* {code} var win = Ti.UI.createWindow({ backgroundColor : 'white' }); var image = Ti.UI.createImageView({ bottom : 0, width : 200, height : 200, backgroundColor : 'red', image : 'http://dl.dropboxusercontent.com/u/255893/appcelerator@2x.png' //image : 'http://www.appcelerator.com.s3.amazonaws.com/web/home/platform/cd-mini-graphic.png' }); win.add(image); win.open(); {code}",5
TIMOB-13582,"CLI: Launching emulator without specifying skin will use HVGA and will fail if chosen AVD does not support HVGA","If you pass in an AVD ID without Skin, HVGA is used as default and passed with the emulator command. If the AVD you chose does not support HVGA, the launch will fail with: {code} [ERROR]Emulator process exited with code 1 {code} The behavior I was expecting was for the default skin listed with the AVD would be used. You can see the set default in the output of ""android list"". Steps to reproduce: 1) Run command ""android list"" in the terminal to see available AVDs 2) Make a note of an AVD ID that does not support HVGA Skin 3) Create a new project 4) Run command ti build -p android -I Result: HVGA Skin is chosen as Default, and will fail if AVD ID does not support that skin. Expected: AVD launches with AVD default skin if no skin passed in.",5
TIMOB-14762,"CLI: Toast says android build succeeded when build failed","If a build fails, TiStudio still says it succeeded, console says (correctly) build failed. See screenshot. The problem is if the build callback receives an error, it says there was an error, but doesn't exit with a non-zero exit code.",5
TIMOB-13656,"CLI needs to support the ability to specify different login endpoints","Different environments will have different login endpints: test, dev, pre-prod, enterprise, vpc. To accommodate these different environments, the cli will have to make the login endpoint configurable - currently it is hard-coded to api.appcelerator.net. This can be configured via the config file or via a parameter This is preventing Studio from working properly against the enterprise cluster, ie unable to login means users can't create projects. As a work-around, users would have to have the same username/password on all api.appcelerator.net type servers",8
TIMOB-13862,"CLI: tiapp.xml sdk-version not honored if selected sdk has same base digits","If the tiapp.xml is set to 3.1.1.v20130514180723, but the CLI is set to 3.1.1.v20130513120107, since both start with 3.1.1, the CLI thinks they are the same version which is wrong.",3
TIMOB-13890,"iOS: Accessibility: Accessibility does not work on Slider Control","iOS: Accessibility: Accessibility does not work on Slider Control This is not a regression. Issue also exist on SDK 3.1.0. Steps: 1) Run Acceptance Access_1109 on Accessibility module. 2) Touch the second slider (with LVH defined in sequence) Actual Result: Device just reads ""50.0"". Expected Result: Device should read aloud LVH(This is slider2 label , This is slider2 value , This is slider2 hint) followed by 'seek control'value(android) and value adjustable {code} var win = Ti.UI.createWindow({ title : 'Welcome', backgroundColor: ""#fff""}); var slider1 = Titanium.UI.createSlider({ top: 50, min: 0, max: 100, width: '100%', value: 50 }); var label1 = Ti.UI.createLabel({ text: slider1.value, width: '100%', height: 'auto', top: 30, left: 0, textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER }); slider1.addEventListener('change', function(e) { label1.text = String.format(""%3.1f"", e.value); }); var slider2 = Titanium.UI.createSlider({ top: 150, min: 0, max: 100, width: '100%', value: 50, accessibilityLabel: ""This is slider2 label"", accessibilityValue: 'This is slider2 value', accessibilityHint: ""This is slider2 hint"" }); var label2 = Ti.UI.createLabel({ text: slider2.value, width: '100%', height: 'auto', top: 130, left: 0, textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER }); slider2.addEventListener('change', function(e) { label2.text = String.format(""%3.1f"", e.value); }); var slider3 = Titanium.UI.createSlider({ bottom: 130, min: 0, max: 100, width: '100%', value: 50, accessibilityHint: ""This is slider3 hint "", accessibilityLabel: ""This is slider3 label"", accessibilityValue: 'This is slider3 value', }); var label3 = Ti.UI.createLabel({ text: slider3.value, width: '100%', height: 'auto', bottom: 150, left: 0, textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER }); slider3.addEventListener('change', function(e) { label3.text = String.format(""%3.1f"", e.value); }); var slider4 = Titanium.UI.createSlider({ bottom: 30, min: 0, max: 100, width: '100%', value: 50, accessibilityLabel: ""This is slider4 label"", accessibilityValue: 'This is slider4 value', accessibilityHint: ""This is slider4 hint"", accessibilityHidden: true }); var label4 = Ti.UI.createLabel({ text: slider4.value, width: '100%', height: 'auto', bottom: 50, left: 0, textAlign: Ti.UI.TEXT_ALIGNMENT_CENTER }); slider4.addEventListener('change', function(e) { label4.text = String.format(""%3.1f"", e.value); }); win.add(slider1); win.add(slider2); win.add(slider3); win.add(slider4); win.add(label1); win.add(label2); win.add(label3); win.add(label4); win.open(); {code}",3
TIMOB-13892,"iOS: Accessibility - Label.accessibilityLabel does not work properly inside a ScrollView properly","Label.accessibilityLabel does not work properly inside a ScrollView properly i.e. the device's VoiceOver will not read the label. This is not a regression. Issue also exist on SDK 3.1.0 *Steps:* 1. Create a Titanium app with the following app.js code: {code} var _window = Ti.UI.createWindow({ backgroundColor: 'white' }); var scroll1 = Ti.UI.createScrollView({ backgroundColor : 'red', accessibilityLabel : 'This is ScrollView1', accessibilityValue : 'Value1', accessibilityHint : 'hint 1', height : 200, top : 0 }); var label1 = Ti.UI.createLabel({ text : 'Label Text', accessibilityLabel : 'Label on first Scrollview' }); scroll1.add(label1); _window.add(scroll1); _window.open(); {code} 2. Install app to device. Make sure VoiceOver is on: Settings > General > Accessibility > VoiceOver > On 3. Double-press on app to launch app 4. Double-press on the label *Actual:* ""Label on first Scrollview"" is not read out. *Expected:* ""Label on first Scrollview"" should be read out. ",8
TIMOB-13914,"Android: 'longpress' event is not working in ListView","'longpress' event is not working in listView. Here is the test case: {code} var win = Ti.UI.createWindow({backgroundColor: 'white'}); var plainTemplate = { childTemplates: [ { type: 'Ti.UI.Label', // Use a label bindId: 'rowtitle', // Bind ID for this label properties: { // Sets the Label.left property left: '10dp' } }, { type: 'Ti.UI.ImageView', // Use an image view bindId: 'pic', // Bind ID for this image view properties: { // Sets the ImageView.image property image: 'KS_nav_ui.png' } }, { type: 'Ti.UI.Button', // Use a button bindId: 'button', // Bind ID for this button properties: { // Sets several button properties width: '80dp', height: '30dp', right: '10dp', title: 'press me' } } ] }; function report(e) { Ti.API.info(e.type); } var listView = Ti.UI.createListView({ // Maps the plainTemplate object to the 'plain' style name templates: { 'plain': plainTemplate }, // Use the plain template, that is, the plainTemplate object defined earlier // for all data list items in this list view defaultItemTemplate: 'plain' }); var data = []; for (var i = 0; i < 3; i++) { data.push({ // Maps to the rowtitle component in the template // Sets the text property of the Label component rowtitle : { text: 'Row ' + (i + 1) }, // Sets the regular list data properties properties : { itemId: 'row' + (i + 1), accessoryType: Ti.UI.LIST_ACCESSORY_TYPE_NONE } }); } listView.addEventListener('longpress', function(e){ alert(""longpress fired!!!""); }); win.add(listView); win.open(); {code}",5
TIMOB-13922,"Android: KitchenSink: text does not size to fit in buttons","Please see screenshots for references. Test steps: 1. Install and run KS>Base UI>Window Layout or 2. KS> Base UI> Window(Standalone) and press any of the buttons Actual result: Text of the button is being cut off. Expected: Text should fit inside the button",3
TIMOB-13974,"Android: KS takes a long time to package - I've seen nine minutes, others report longer in some cases","h5. Description: While verifying some JIRA tickets I was packaging KS (from 3.1.X branch). Hieu reported having this take a long time, so I monitored the process. The console ticked slowly away, and it took 9 minutes and 30 seconds to finish the task. This was from clean. h5. Steps to reproduce: 1) Pull KS from 3_1_X branch 2) Import into Studio 3) Package for distribution 4) Monitor the duration of the task h5. Result: It took 9:30 in my first test and others have reported longer. h5. Expected Result: Much quicker packaging process. h5. Notes: I'll be checking to see if this is a regression and will add it here.",3
TIMOB-13986,"iOS: backgroundImage of view from remote URL not loading","*Problem* The backgroundImage of the view from a remote URL is not loading on iOS. It works fine on Android. *Test case* {code:javascript} var win = Ti.UI.createWindow({ backgroundColor : ""#FFF"" }); var view = Ti.UI.createView({ backgroundImage : 'http://dl.dropboxusercontent.com/u/72783403/AtoZ/1.png' }); win.add(view); win.open(); {code}",3
TIMOB-14003,"Android: showDatePickerDialog and showTimePickerDialog can't be cancelled","The callback of showDatePickerDialog and showTimePickerDialog always return with the cancel property set to false. It doesn't matter if you press the back button or press outside the modal dialog, cancel gets never true. Furthermore, if you click on the Set/Ok/Done/Ready button, the callback is called twice. Note that in the picker dialog, we have only a single button ""Set"", so no Cancel button. This is fine as you should be able to cancel dialog with the back button. Clicking the back button fires wrongly a success (cancel=false) event. {code:title=Example code|borderStyle=solid} var picker = Ti.UI.createPicker( { type : Ti.UI.PICKER_TYPE_TIME }); picker.showDatePickerDialog({ callback: function(e) { if (e.cancel) { Ti.API.info('user canceled dialog'); } else { Ti.API.info('user selected date: ' + e.value); } } }); {code} Problem does not occur on older Android devices, like Android 2.3. See https://github.com/markruys/titanium-test-picker for a working project to reproduce.",5
TIMOB-13999,"LiveView: App not updating upon editing localization files","Steps to reproduce: # Create a new SingleWindow application from a template # Start the project under LiveView (in this case, iOS simulator) # Edit the files in i18n. Note that saving those files doesn't restart the app. Expected behavior Editing a *.xml file in the i18n folder would refresh the application.",13
TIMOB-14123,"Android: Add support for creating video thumbnails","h2. Problem Unable to create a thumbnail of a video on Android using Titanium SDK 3.1.0.GA. Titanium.Media.VideoPlayer.thumbnailImageAtTime(Number time, Number option) and Titanium.Media.VideoPlayer.requestThumbnailImagesAtTimes(Number[] times, Number option, Callback callback) appear to be the only methods available to achieve this, but they are not supported for Android, only on iOS. Would like to see similar functionality to get a thumbnail from a video. It appears to be supported by the Android APIs per http://developer.android.com/reference/android/provider/MediaStore.Video.Thumbnails.html h2. Test case N/A - not currently supported h2. Logs N/A - not currently supported h2. Discussions Q/A: http://developer.appcelerator.com/question/152946/video-thumbnails-on-android ",8
TIMOB-14194,"TiAPI: Problem with floating point numbers in Titanium","*Problem* The output of floating point values in Titanium differ from browser JavaScript parsers such as [jsbin.com|http://www.jsbin.com/]. For example, Ti.API.info(94.1) displays 94.0999999 On jsbin.com the output of alert(94.1) is 94.1 *Note* Since I have to input floating number for some modules, I must use floating number solution. I can't use a string method. I have also tried parseFloat(x.toFixed(1)), Math.round(x*10)/10 etc. The output was the same. *Test case* {code:javascript} var win = Ti.UI.createWindow({ backgroundColor : ""#FFF"" }); for (var i = 0; i < 50; i++) Ti.API.info(94.1); win.open(); {code} *Extended test case* {code:javascript} var win = Ti.UI.createWindow({ backgroundColor : ""#FFF"" }); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.1); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.2); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.3); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.4); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.5); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.6); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.7); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.8); for (var i = 0; i < 1000; i++) Ti.API.info(i + 0.9); win.open(); {code} *Log - Unusual Titanium values* {code} [INFO] : 64.09999999999999 [INFO] : 65.09999999999999 [INFO] : 66.09999999999999 [INFO] : 67.09999999999999 [INFO] : 68.09999999999999 [INFO] : 69.09999999999999 ... [INFO] : 70.09999999999999 [INFO] : 71.09999999999999 [INFO] : 72.09999999999999 [INFO] : 73.09999999999999 [INFO] : 74.09999999999999 [INFO] : 75.09999999999999 [INFO] : 76.09999999999999 [INFO] : 77.09999999999999 [INFO] : 78.09999999999999 [INFO] : 79.09999999999999 [INFO] : 80.09999999999999 [INFO] : 81.09999999999999 [INFO] : 82.09999999999999 [INFO] : 83.09999999999999 [INFO] : 84.09999999999999 [INFO] : 85.09999999999999 [INFO] : 86.09999999999999 [INFO] : 87.09999999999999 [INFO] : 88.09999999999999 [INFO] : 89.09999999999999 [INFO] : 90.09999999999999 [INFO] : 91.09999999999999 [INFO] : 92.09999999999999 [INFO] : 93.09999999999999 [INFO] : 94.09999999999999 [INFO] : 95.09999999999999 [INFO] : 96.09999999999999 [INFO] : 97.09999999999999 [INFO] : 98.09999999999999 [INFO] : 99.09999999999999 ... [INFO] : 8.199999999999999 [INFO] : 9.199999999999999 ... [INFO] : 8.300000000000001 [INFO] : 9.300000000000001 ... [INFO] : 64.40000000000001 [INFO] : 65.40000000000001 [INFO] : 66.40000000000001 [INFO] : 67.40000000000001 [INFO] : 68.40000000000001 [INFO] : 69.40000000000001 [INFO] : 70.40000000000001 [INFO] : 71.40000000000001 [INFO] : 72.40000000000001 [INFO] : 73.40000000000001 [INFO] : 74.40000000000001 [INFO] : 75.40000000000001 [INFO] : 76.40000000000001 [INFO] : 77.40000000000001 [INFO] : 78.40000000000001 [INFO] : 79.40000000000001 [INFO] : 80.40000000000001 [INFO] : 81.40000000000001 [INFO] : 82.40000000000001 [INFO] : 83.40000000000001 [INFO] : 84.40000000000001 [INFO] : 85.40000000000001 [INFO] : 86.40000000000001 [INFO] : 87.40000000000001 [INFO] : 88.40000000000001 [INFO] : 89.40000000000001 [INFO] : 90.40000000000001 [INFO] : 91.40000000000001 [INFO] : 92.40000000000001 [INFO] : 93.40000000000001 [INFO] : 94.40000000000001 [INFO] : 95.40000000000001 [INFO] : 96.40000000000001 [INFO] : 97.40000000000001 [INFO] : 98.40000000000001 [INFO] : 99.40000000000001 ... [INFO] : 64.59999999999999 [INFO] : 65.59999999999999 [INFO] : 66.59999999999999 [INFO] : 67.59999999999999 [INFO] : 68.59999999999999 [INFO] : 69.59999999999999 [INFO] : 70.59999999999999 [INFO] : 71.59999999999999 [INFO] : 72.59999999999999 [INFO] : 73.59999999999999 [INFO] : 74.59999999999999 [INFO] : 75.59999999999999 [INFO] : 76.59999999999999 [INFO] : 77.59999999999999 [INFO] : 78.59999999999999 [INFO] : 79.59999999999999 [INFO] : 80.59999999999999 [INFO] : 81.59999999999999 [INFO] : 82.59999999999999 [INFO] : 83.59999999999999 [INFO] : 84.59999999999999 [INFO] : 85.59999999999999 [INFO] : 86.59999999999999 [INFO] : 87.59999999999999 [INFO] : 88.59999999999999 [INFO] : 89.59999999999999 [INFO] : 90.59999999999999 [INFO] : 91.59999999999999 [INFO] : 92.59999999999999 [INFO] : 93.59999999999999 [INFO] : 94.59999999999999 [INFO] : 95.59999999999999 [INFO] : 96.59999999999999 [INFO] : 97.59999999999999 [INFO] : 98.59999999999999 [INFO] : 99.59999999999999 ... [INFO] : 8.800000000000001 [INFO] : 9.800000000000001 ... [INFO] : 64.90000000000001 [INFO] : 65.90000000000001 [INFO] : 66.90000000000001 [INFO] : 67.90000000000001 [INFO] : 68.90000000000001 [INFO] : 69.90000000000001 [INFO] : 70.90000000000001 [INFO] : 71.90000000000001 [INFO] : 72.90000000000001 [INFO] : 73.90000000000001 [INFO] : 74.90000000000001 [INFO] : 75.90000000000001 [INFO] : 76.90000000000001 [INFO] : 77.90000000000001 [INFO] : 78.90000000000001 [INFO] : 79.90000000000001 [INFO] : 80.90000000000001 [INFO] : 81.90000000000001 [INFO] : 82.90000000000001 [INFO] : 83.90000000000001 [INFO] : 84.90000000000001 [INFO] : 85.90000000000001 [INFO] : 86.90000000000001 [INFO] : 87.90000000000001 [INFO] : 88.90000000000001 [INFO] : 89.90000000000001 [INFO] : 90.90000000000001 [INFO] : 91.90000000000001 [INFO] : 92.90000000000001 [INFO] : 93.90000000000001 [INFO] : 94.90000000000001 [INFO] : 95.90000000000001 [INFO] : 96.90000000000001 [INFO] : 97.90000000000001 [INFO] : 98.90000000000001 [INFO] : 99.90000000000001 {code}",5
TIMOB-14178,"Android: Real Switch on Android","It would be nice to have a Real Android Switch when developing for Android 14 and above. The one supplied with Titanium now is not very nice.",5
TIMOB-14242,"Android: x86 libs not included in production APK","I was going to upload my app to the Google play store when I saw that x86 native SDK libraries were not included in the APK (libkroll-v8.so, libtiverify.so, libtiprofiler.so, libstlport_shared.so). I noticed these lines in builder.py (lines from 1696): {quote} if abi == 'x86' and ((not os.path.exists(lib_source_dir)) or self.deploy_type == 'production'): # x86 only in non-production builds for now. continue {quote} and removing them did the trick. It is normal behaviour not to including that libraries in production releases or it is a mistake? And if it is normal what is the reason? Way to reproduce: - Use the feature ""Distribute - Android App Store"" - Open the created APK with some zip reader - Navigate in lib/x86 - No native libraries included",3
TIMOB-14241,"Android: TextArea.maxLength doesn't work","*Problem* TextArea.maxLength not working in android, works perfectly fine on iOS *Steps to Reproduce* 1. run code provided on iOS (notice the maxLength is working, limits characters to 20) 2. run code provided on android (unlimited characters can be entered) {code} var win = Ti.UI.createWindow({ title : ""Test"", backgroundColor : 'gray' }); var view = Ti.UI.createView({ height : 200, top : 5, left : 5, right : 5, layout : 'vertical' }); var textFieldTwitter = Ti.UI.createTextArea({ left : 0, right : 0, height : 200, value : ""Testing1"", maxLength : 20 }); var tweetMax = 140; var viewTexteRestant = Ti.UI.createLabel({ text : 'Caractères restants : ' + (tweetMax - textFieldTwitter.value.length), height : Ti.UI.SIZE, width : Ti.UI.SIZE, top : 20, backgroundColor : ""red"" }); textFieldTwitter.addEventListener('change', function(e) { Ti.API.info(tweetMax - textFieldTwitter.value.length); viewTexteRestant.text = 'Caractères restants : ' + (tweetMax - textFieldTwitter.value.length); }); view.add(textFieldTwitter); view.add(viewTexteRestant); win.open(); win.add(view); {code} see : http://developer.appcelerator.com/question/153431/maxlength-in-textarea-doesnt-work",3
TIMOB-14262,"LiveView: Does not trigger code errors","*Steps to reproduce* 1. Create a default application 2. Enable LiveView in Run Configurations 3. Run on iOS simulator 4. Replace ""win1.add(label1);"" into ""win1.add(mylabel);"" 5. Save app.js *Actual Result* LiveView error is not triggered *Expected Result* LiveView error is triggered ",13
TIMOB-14267,"LiveView - Running multiple instances of the application on iOS and Android, iOS instances lose connection to LiveView Server","When trying to run multiple instances of the application with Liveview enabled across multiple devices/platform notice that Android will continue to update, however iOS instances lose the connection and do not continue to update. (have validated this against iOS on Device and iOS on Simulator). See attached video for further clarification. steps to reproduce: 1) enable an existing application (simple screen) for LiveView 2) run android and iOS builds (emulator/simulator) 3) make a change to the code Expected Behavior: Both instances of the application should update continuously Actual Behavior: Android will continue to update, however iOS will stop updating after it updates once. Simulator or Device will need to restart to show updates. ",8
TIMOB-14285,"Android: applyProperties() does not apply custom properties to proxy","h2. problem When using {{applyProperties()}} to add a number of properties to a Titanium proxy object, custom properties are not added on Android. On iOS and Mobileweb all properties, including custom ones, are added with the {{applyProperties()}} call. Android leaves the custom properties as {{undefined}}. h2. expected Android should behave like other supported platforms and attach custom properties to the Titanium proxy object when they are added via {{applyProperties()}}. h2. test case {code:javascript} var win = Ti.UI.createWindow({ backgroundColor: '#fff', fullscreen: false, exitOnClose: true }); win.open(); win.applyProperties({ customString: 'Ti.UI.Window', customArray: ['class1','class2','class3'], customObject: { x: 1, y: 2, z: 3 }, navBarHidden: true, backgroundGradient: { type: 'linear', startPoint: { x: '0%', y: '50%' }, endPoint: { x: '100%', y: '50%' }, colors: [ { color: 'red', offset: 0.0}, { color: 'blue', offset: 0.25 }, { color: 'red', offset: 1.0 } ], } }); Ti.API.info('customString: ' + JSON.stringify(win.customString)); Ti.API.info('customArray: ' + JSON.stringify(win.customArray)); Ti.API.info('customObject: ' + JSON.stringify(win.customObject)); Ti.API.info('navBarHidden: ' + JSON.stringify(win.navBarHidden)); Ti.API.info('backgroundGradient: ' + JSON.stringify(win.backgroundGradient)); {code} h2. output iOS does not show the {{backgroundGradient}} after the {{applyProperties()}} call, but this is a peripheral issue not associated with this ticket. h4. iOS 6.1 iPhone sim {code} [INFO] customString: ""Ti.UI.Window"" [INFO] customArray: [""class1"",""class2"",""class3""] [INFO] customObject: {""x"":1,""y"":2,""z"":3} [INFO] navBarHidden: true [INFO] backgroundGradient: {} {code} h4. Android 2.3.3 HVGA emulator {code} I/TiAPI ( 517): customString: undefined I/TiAPI ( 517): customArray: undefined I/TiAPI ( 517): customObject: undefined I/TiAPI ( 517): navBarHidden: true I/TiAPI ( 517): backgroundGradient: {""endPoint"":{""y"":""50%"",""x"":""100%""},""type"":""linear"",""colors"":[{""offset"":0,""color"":""red""},{""offset"":0.25,""color"":""blue""},{""offset"":1,""color"":""red""}],""startPoint"":{""y"":""50%"",""x"":""0%""}} {code} h4. mobileweb + chrome {code} [INFO] customString: ""Ti.UI.Window"" [INFO] customArray: [""class1"",""class2"",""class3""] [INFO] customObject: {""x"":1,""y"":2,""z"":3} [INFO] navBarHidden: true [INFO] backgroundGradient: {""type"":""linear"",""startPoint"":{""x"":""0%"",""y"":""50%""},""endPoint"":{""x"":""100%"",""y"":""50%""},""colors"":[{""color"":""red"",""offset"":0},{""color"":""blue"",""offset"":0.25},{""color"":""red"",""offset"":1}]} {code}",8
TIMOB-14382,"Enable Media.openPhotoGallery to select multiple media items instead of 1 at a time.","In relation to this Q&A thread: http://developer.appcelerator.com/question/153838/select-multiple-images-using-photo-gallery-picker-android-and-ios Would it be possible to add a property/the functionality to Media.openPhotoGallery() to enable the selection of multiple media items? Maybe something like: itemLimit, which defaults to 1, but by setting to a greater value enables multiple selection functionality?",3
TIMOB-14393,"Android: JS proxies are prematurely cleaned up when dalvik gc is triggered ","Originally from https://jira.appcelerator.org/browse/TIMOB-13664: The problem is about Javascript scope for Titanium objects. In the logs, the problem was clearly after a garbage collect, so, first of all, we created a small module called ""androidgc"" which simply launch Android garbage collector (not the V8 GC). You can find this module here : https://github.com/ChrOnOs83/TiModuleAndroidGC Then, we decided to use your files and made it as simple as possible. We finally got a unique app.js file with this content : {code} function createView(){ var view = Ti.UI.createView({backgroundColor: 'white'}); var gc = Ti.UI.createButton({top: '10dp',title: ""First, click here many time quickly (cause GC)""}); var btn = Ti.UI.createButton({title: ""Next, click here""}); var label = Ti.UI.createLabel({text: 'Hello World', bottom: '10dp'}); view.add(btn); view.add(gc); btn.addEventListener('click', function(){ view.add(label); }); var androidgc = require('ti.nartex.androidgc'); gc.addEventListener('click', function(){ androidgc.gc(); }); return view; } var win = Ti.UI.createWindow({}); win.open(); var view = createView(); win.add(view); {code} When you run this code on your Android Device, you should press many times on the ""GC"" button, because garbage collector may not clean your ressources each time... If GC has be done correctly, the second button press will fail, because the label is not here anymore. If you add the label to the view, and then change its title, no problem If you create the label in the event listener, no problem *If you makes a reference to a global variable (without the _var_ keyword for example), it works* If you put the function in a CommonJS module, the same rules apply. So... Titanium objects created in a function (all the Ti.something) may be killed by garbage collector at any time if they are not attached to a view/window, or declared as global var. It breaks the Javascript scope pattern... ",34
TIMOB-14425,"LiveView: iOS simulator is no longer updated once Android emulator is terminated when both are run with LiveView","1. Create a mobile project (e.g. the default two-tab classic project); 2. Run iPhone simulator with LiveView; 3. Run Android emulator with LiveView; 4. Updating app.js and confirm LiveView is working for both; 5. Exit Android emulator; 6. Updating app.js. Expected result: iPhone simulator will continue to update the app. Actual result: iPhone simulator no longer updates. Here is the end of the log: {code} [LiveView] Client disconnected [LiveView] Client connected [LiveView] Client disconnected [LiveView] Reload Triggered -REASON: File Changed -FILE: /Users/mxia/Documents/Appcelerator_Studio_Workspace/testLiveView/Resources/app.js [LiveView] Reload Triggered -REASON: File Changed -FILE: /Users/mxia/Documents/Appcelerator_Studio_Workspace/testLiveView/Resources/app.js [LiveView] Reload Triggered -REASON: File Changed -FILE: /Users/mxia/Documents/Appcelerator_Studio_Workspace/testLiveView/Resources/app.js {code} It appears the LiveView server got disconnected when Android emulator exited, but it didn't try to re-launch the server, and future reload events, although fired, could not update the app. ",8
TIMOB-15247,"iOS: Ti.Blob.imageAsResized always returns a png image","This is the same issue as [TIMODOPEN-228|https://jira.appcelerator.org/browse/TIMODOPEN-228] but for Ti.Blob (core). On iOS, all images created by Ti.Blob.imageAsResized are of type png (mime-type ""image/png"") instead of jpeg. As a result resized images are much bigger (in terms of bytes) than what they're supposed to be had they been jpegs. This seems to be related to the handling of alpha channel, according to [TIMODOPEN-228|https://jira.appcelerator.org/browse/TIMODOPEN-228] It works fine on android (Ti.Blob.imageAsResized returns jpegs).",1
TIMOB-14494,"iOS: Ti.Map should handle touch events on the view not just annotations","Touch events are currently only fired on Map Annotations and not else where on the map view. Implement touch events on the Map View.",8
TIMOB-14496,"Android: setHeaderView for Titanium.UI.TableViewSection","Currently, it is only possible to set the *headerView* of a TableViewSection at creation-time in Android. It would be great to use the *setHeaderView* method for Android too. In the Docs there is no note that this method is not available in Android: [http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.UI.TableViewSection-method-setHeaderView]. There is only a hint at the *headerView* property description (_""On Android, must be set at creation.""_): [http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.UI.TableViewSection-property-headerView] Q&A: [http://developer.appcelerator.com/question/154498/alloy-how-to-set-controller-as-headerview-to-tableviewsection-in-android] ",3
TIMOB-14544,"iOS: keyboardFrameChanged before keyboard is shown","keyboardFrameChanged event doesn't do much good as it is fired after the keyboard has already been displayed. to create responsive layouts with different keyboard sizes we need to know keyboard size BEFORE the keyboard is displayed. iphone/Classes/AppModule.m line 386-407 could be changed to something like this {code:objc} -(void)startup { WARN_IF_BACKGROUND_THREAD_OBJ; //NSNotificationCenter is not threadsafe! NSNotificationCenter * nc = [NSNotificationCenter defaultCenter]; [nc addObserver:self selector:@selector(willShutdown:) name:kTiWillShutdownNotification object:nil]; [nc addObserver:self selector:@selector(willShutdownContext:) name:kTiContextShutdownNotification object:nil]; #if __IPHONE_OS_VERSION_MIN_ALLOWED >= __IPHONE_5_0 if ([TiUtils isIOS5OrGreater]) { [nc addObserver:self selector:@selector(keyboardFrameChanged:) name:UIKeyboardWillChangeFrameNotification object:nil]; } #else [nc addObserver:self selector:@selector(keyboardFrameChanged:) name:UIKeyboardWillShowNotification object:nil]; [nc addObserver:self selector:@selector(keyboardFrameChanged:) name:UIKeyboardWillHideNotification object:nil]; [nc addObserver:self selector:@selector(timeChanged:) name:UIApplicationSignificantTimeChangeNotification object:nil]; #endif [super startup]; } {code} Either that or provide access to both Will and Did. e.x. {code:javascript} Ti.App.addEventListener('keyboardFrameChanged', function(e){ var val = Ti.Platform.displayCaps.platformHeight - e.keyboardFrame.y; $.container.animate({bottom:val, duration:300}, function() { Ti.API.log(""handleAnimateEnd""); }); }); {code}",8
TIMOB-14582,"LiveView: Create Error/Warning Screen","create window to display liveview errors/warnings. examples: error connecting to server, parse error, etc..",8
TIMOB-14637,"Android: Fix Titanium Build Script in order to support Genymotion Android Emulator","Genymotion is an enhanced android emulator that leverages x86 emulation with builtin HAXM-like optimizations and Google APIs. In order to have an simulator with a performance like the iOS Simulator we need to setup a x86 android emulation with Intel HAXM support. The problem is that by using the native AVD on Android SDK you can do this setup BUT without the Google APIs, namely the GMaps API, which makes testing apps depending on those APIs, impossible on this high performance simulation. Although it is possible to add Google APIs to a standard x86 AVD, the process is very complex and involves copying the libraries from other non-x86 AVDs and rebuilding a system image which takes a lot of time and effort for each simulator setup you want to have. So Genymotion does it all under the hood and allows us to select between several android models and even simulate external sensors and GPS location, much like the Apple Simulator does. The standard Titanium build script has some problems that causes the Simulator session not to be recognized as a valid deployment target (using titanium build -p android -T device), even though adb successfully recognizes the simulation under adb devices. In order to fix this I have found some hints on a russian weblog and changed it a bit for working on my Mac. I have successfully run my Titanium app on Genymotion using Titanium CLI by doing the following: http://reinraus.ru/wordpress/nastraivaem-titanium-studio-dlya-zapuska-prilozhenij-v-android-x86/ It is written in Russian, so please use the Google Translate tool, he has made 3 changes on the build script. The tutorial is for windows, so if you're running Titanium on a Mac or Windows, just change the first patch from: {code} dev_id, dev_type=output.split(""\r\n"")[1].split(""\t"") {code} to: {code} dev_id, dev_type=output.split(""\n"")[1].split(""\t"") {code} It seems there is still a tiny problem with Logcat on the end, but the app successfully run on Genymotion after this patch.",3
TIMOB-14652,"CLI: When selected SDK is not 3.0.0 or 3.0.2 and building for 3.0.0 and 3.0.2, verify Node.js version is 0.8.x","If the CLI's selected Ti SDK is 3.1.0.GA and the tiapp.xml is set to 3.0.0.GA or 3.0.2.GA, then those SDKs require Node.js 0.8.x. Today we allow those builds to fail. The build should be smarter to detect those SDKs and if Node.js is not 0.8 and fail gracefully.",2
TIMOB-14743,"BlackBerry: 'java' processes belonging to 'Appcelerator Studio' might kill the CPU","h5. Problem description After installing the BlackBerry tools and using Appcelerator Studio for building BlackBerry apps, I've experienced intermittent issues, leading to a sluggish and clumsy experience and eventually to completely freezing the system (forcing a hard restart). From the Activity Monitor, a number of java processes were occupying most of the machine CPU. All those processes were belonging to Appcelerator Studio Process Group. It seems those processes are related to BlackBerry development and have been experienced so far only when building projects on BlackBerry. Attached screenshots of my Activity Monitor and detail of a single process. h5. Notes Another similar issue occurred in the past: https://jira.appcelerator.org/browse/TISTUD-3514",8
TIMOB-14699,"LiveView: Create Unit Test Suite",NULL,20
TIMOB-14701,"CLI: Android: For emulator builds, check that emulator has sufficient space","See if there's a way to check how much space is free in an AVD before install the app. We probably will need to build the app first to get the APK file size.",2
TIMOB-14740,"Android: Automatically generate ProGuard configuration file","Hi, Create a sample Android module and build it. Then follow this step by step. 1. Extract the contents of the zip file inside the dist folder. 2. Extract the JAR file obtained from the zip file. 3. Use JAD (Decompile tool) to decompile the any *.class file. You will observe that the entire source code is displayed. There is no obfuscation. I think Appcelerator must provide an obfuscation procedure during the build process. If any such process is present (using ProGuard for example), then can you please let us know. If no such process exists then it will be a great idea to add this feature. This will increase the security and also reduce the module size.",21
TIMOB-14735,"iOS: Accessibility: ButtonBar: Accessibility does not work on Button Bar ","iOS: Accessibility: ButtonBar: Accessibility does not work on Button Bar. The Label, Value or Hint are not voiced over. This is not a regression. It occurs since sdk 3.0.0.GA. Steps to reproduce: 1. Run the app as Accessibility Acceptance Access_1102 iOS Only under Accessibility module. 2. Touch the first Buttonbar (with LVH defined in sequence) Actual: if 'red' is touched then 'red button 2 of 3"" is spoken. The Label, Value or Hint are not voiced over. Expected: 2. The device reads aloud: buttontext, tab, (button number) of (total number of buttonson buttonbar) [eg. 2 of 3] followed by """"Buttonbar1"""", """"Value1"""", """"Hint1"""" ",3
TIMOB-14780,"iOS: Ti.UI.orientationModeFilter to app-wide block orientations","Note: While this spec is for iOS only, consideration in the design should include Android. On iOS, not all view controllers are under Titanium control (e.g., Mail composer, Activities). Because of issues (especially in 5.x and before), we did not control their orientation. But with iOS 6, native applications can control them. We should provide a means similar. Ti.UI.orientationModeFilter is an array of orientations allowed with the following pseudocode: On startup, the info.plist is checked. If no such orientation limits are mentioned, the default for the device (all but upside down for iPod/iPhone, all orientations for iPad) is used. This property can be changed. Whenever the OS requests the window's orientation, Titanium reports to the OS the orientationModes as such: # The orientation flags are set to all orientations. # If the Ti.UI.orientationModeFilter is valid, change the orientations to that. # If the window's orientationModes are set, bitwise AND it with the orientation flags. # if the result is 0, replace the orientation flags with the windows orientationModes, and warn about the edge case. # Return orientation flags. The behavior of the Ti.UI.orientationModeFilter changed at any time after startup is undefined. There is no guarantee that changes made to it will propagate to existing windows.",8
TIMOB-14784,"CLI: Create ADB Library","We need an ADB library that provides the following functions: * devices * start-server * kill-server * install ** allow installation to a specific device/emulator (TIMOB-12600 CLI: building for Android device while the emulator open generates a wrong Error Message) ** gracefully handle FAILED_INSUFFICIENT_STORAGE errors (TIMOB-14701 CLI: Android: For emulator builds, check that emulator has sufficient space) *** if insufficient storage space, display instructions on how to resolve (TIMOB-9859 Android: increase AVD storage size to reduce \[FAILED_INSUFFICIENT_STORAGE\] errors) * shell * push * forward * start app (TIMOB-13105 CLI: Add build support for building android apps on emulator without starting the app) * kill running app",20
TIMOB-14785,"CLI: Create Android Emulator Library","We need an Android emulator library that provides the following functions: * create AVD ** improve emulator naming convention (TIMOB-1872 Android: Fix AVD naming scheme) * launch emulator ** make sure adb server is running ** if the emulator we want is already running, return ** if avd does not exist, create it ** if skin is not specified, select a valid skin for the AVD's Android SDK (TIMOB-13582 CLI: Launching emulator without specifying skin will use HVGA and will fail if chosen AVD does not support HVGA) ** custom launch params (TIMOB-2646 Android: Feature Request: Customized launch params) ** gracefully handle when emulator doesn't start in timely manner (TIMOB-9153 Android: Deployment: Android Emulator intermittently fails to launch app after timed out) ** NOTE: do not launch a useless emulator, especially on Windows (TIMOB-4730 Android 3.2 Simulator behavior on windows is very poor (not launched at all or useless emulator launched)) ** pipe emulator output to logger (TIMOB-13381 Android Emulator: process launches in new terminal on Windows) ** fire callback when emulator has booted ** fire callback when sdcard is ready ** fire callback when emulator is quit (TIMOB-12604 Android: Closing the emulator, 'Emulator has exited' log in not printed on console) ** NOTE: be careful when running multiple x86 instances as to avoid ""Starting emulator for AVD 'titanium_10_800x1280_armeabi-v7a' \ emulator: The memory needed by this VM exceeds the driver limit. \ HAX is not working and emulator runs in emulation mode"" errors * kill emulator ** NOTE: make sure emulator is properly killed on Windows (TIMOB-7468 Android: tooling - Rhino/V8 - On windows systems during emulator build, console reports error attempting to kill emulator process) * NOTE: make sure to support directories with &, especially on Windows (TIMOB-2527 Android: App launch/build problem if ampersand in home folder name)",20
TIMOB-14786,"CLI: Create Genymotion Library","We need an Genymotion library that provides the following functions: * detect Genymotion (TIMOB-14637 Android: Fix Titanium Build Script in order to support Genymotion Android Emulator) * launch emulator",20
TIMOB-14787,"CLI: Improve detection of Android SDK and SDK Home locations","The Android environment detection library needs a few additional features for the build command to properly validate the development environment. * detect Android SDK ** detect abd location (TIMOB-2760 need to be able to ref adb from either /tools or /platform-tools subdir) ** detect proguard availability (TIMOB-2782 Android: Generate / Run a Proguard configuration based on API usage) ** search configured Android SDK path first, then try ANDROID_SDK environment variable (TIMOB-8658 Android: Switch search order of folders/environment variables in androidsdk.py) ** if 64-bit Linux *** check if ia32-libs package is installed (dpkg-query -l ia32-libs) (TIMOB-13520 Android Emulator: improve error message from missing ia32-libs dependency on linux) *** check if /usr/lib/libGL.so exists *** check if i386 architecture set in dpkg * detect Android SDK Home (ANDROID_SDK_HOME) ",13
TIMOB-14799,"iOS: Prevent clearing TextField after password field had focus","*Problem* On iOS textfields are cleared by default after some password field had the focus. Is this something that could be prevented. I looked at the docs for textfields, but either I cannot find it or it just isn't there. *Example code to reproduce* {code:javascript} var win = Ti.UI.createWindow({ backgroundColor : 'white' }); var tf1 = Ti.UI.createTextField({ value : ""textfield1"", passwordMask : true, top : 10, width : 200 }); win.add(tf1); var tf2 = Ti.UI.createTextField({ value : ""textfield2"", top : 80, width: 200 }); win.add(tf2); win.open(); {code} *Steps to reproduce* 1. click in the password field 2. click in the ""normal"" textfield 3. press backspace *Expected result* The last character of the textfield is deleted *Actual result* The entire contents of the textfield is now cleared instead of only the last character.",3
TIMOB-14806,"ProjectTemplate: values used as comparison to determine device form factor are wrong","h5. Problem description In Appcelerator Studio template samples for classic projects, the values used as comparison to determine if the device is a tablet or a handheld are outdated and could lead to a wrong detection. h5. Steps to reproduce Create a new Single Window Project and open app.js. Check line: {code} var isTablet = osname === 'ipad' || (osname === 'android' && (width > 899 || height > 899)); {code} A Google Galaxy Nexus device (for example) has those values: {code} height: 1184 width: 720 {code} As a result, it is being detected as a 'tablet' while is a 'handheld' device.",5
TIMOB-14836,"LiveView: when device and machine are not on the same network, no graceful error message is displayed","h5. Problem description In order to work, LiveView development machine and device must be on the same network. When this is not happening, there is no graceful error message to inform the user. On Android a Runtime error is displayed and on iOS the app is stuck at the splashscreen.",5
TIMOB-15732,"CLI: Changelog (release notes) shows 3.1.1 as latest entry for the 3.1.2 release","h5. Description: When studio prompts users to install CLI 3.1.2, the changelog is displayed. Currently the changelog is only listing 3.1.1 as the latest entry. This might cause confusion. h5. Steps to reproduce: 1) Remove CLI with ""sudo npm -g remove titanium"" OR if you have a version earlier than 3.1.2, skip this step. 2) Launch studio and ""check for appcelerator updates"" 3) Examine the ""release notes"" (changelog) displayed h5. Result: The latest entry is 3.1.1 h5. Expected Result: The latest entry is 3.1.2 and describes the fixes made.",1
TIMOB-14899,"Tooling: Include Google Maps V2 metadata into timodule.xml so can be added to the manifest with the correct app id.","h6.Feature Request To add ability to have the application name automatically updated in the timodule.xml file when building an application. h6.Rationale Forgive me if I'm missing something obvious. The problem is that if they use the included module they have to assume it will be upgraded and replaced when a new Titanium SDK is released. Since the module will be replaced they cannot use the timodule.xml file to add the app id to the required permissions for the maps module. We have to add the permissions below to the tiapp.xml file. {code} {code} When we add them like that to the tiapp.xml file we get errors like: {code} [TRACE] Writing out AndroidManifest.xml [DEBUG] /Users/egomez/android-sdks/build-tools/17.0.0/aapt package -m -J ""/Users/egomez/Documents/Titanium Studio Workspace/TravisTestApp/build/android/gen"" -M ""/Users/egomez/Documents/Titanium Studio Workspace/TravisTestApp/build/android/AndroidManifest.xml"" -S ""/Users/egomez/Documents/Titanium Studio Workspace/TravisTestApp/build/android/res"" -I /Users/egomez/android-sdks/platforms/android-10/android.jar [ERROR] /Users/egomez/Documents/Titanium Studio Workspace/TravisTestApp/build/android/AndroidManifest.xml:4: Tag attribute name has invalid character '$'. [ERROR] /Users/egomez/Documents/Titanium Studio Workspace/TravisTestApp/build/android/AndroidManifest.xml:39: Tag attribute name has invalid character '$'. [ERROR] Error generating R.java from manifest {code} h6.Steps to reproduce Do a project clean, and build the android app and the map did not load. We then checked the generated AndroidManifest.xml file and looked for the required permissions that are outlined in the index.html file of the maps module. In the AndroidManifest file I found that the following permissions were present: {code} {code} The other 4 were not present in the manifest file and they need to be included for the Maps Module to work. Client would like to propose that the following be included in the timodule.xml that is included with the maps module that way they are automatically added to the manifest with the correct app id. The 4 which should be added to timodule.xml are: {code} {code} h6.Additional info Client also tested this by modifying the timodule.xml file for the module in the following directory: - ""/Library/Application Support/Titanium/Modules/android/ti.map/2.1.1/"" When they just added those 4 lines the maps module started working properly. Also can be confirmed that the 4 missing permissions/features are now present in the AndroidManifest.xml file.",3
TIMOB-14963,"Android: Ti.Map and Ti.Cloudpush return ""already added: Lcom/google/android/gms/games/achievement/Achievement""","I'm trying to add Push to my app (iOS/Android) but I'm getting the following error message when I compile the android version: {code} [ERROR] UNEXPECTED TOP-LEVEL EXCEPTION: [ERROR] java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/games/achievement/Achievement; [ERROR] at com.android.dx.dex.file.ClassDefsSection.add(ClassDefsSection.java:123) [ERROR] at com.android.dx.dex.file.DexFile.add(DexFile.java:163) [ERROR] at com.android.dx.command.dexer.Main.processClass(Main.java:490) [ERROR] at com.android.dx.command.dexer.Main.processFileBytes(Main.java:459) [ERROR] at com.android.dx.command.dexer.Main.access$400(Main.java:67) [ERROR] at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:398) [ERROR] at com.android.dx.cf.direct.ClassPathOpener.processArchive(ClassPathOpener.java:245) [ERROR] System Error while compiling Android classes.dex [ERROR] at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:131) [ERROR] at com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:109) [ERROR] at com.android.dx.command.dexer.Main.processOne(Main.java:422) [ERROR] at com.android.dx.command.dexer.Main.processAllFiles(Main.java:333) [ERROR] at com.android.dx.command.dexer.Main.run(Main.java:209) [ERROR] at com.android.dx.command.dexer.Main.main(Main.java:174) [ERROR] at com.android.dx.command.Main.main(Main.java:91) [ERROR] 1 error; aborting {code} Modules added: {code} ti.cloudpush com.acktie.mobile.android.qr ti.cloud com.acktie.mobile.ios.qr facebook ti.map facebook {code} other users confirm that ti.cloudpush and ti.map inside the same project will cause this error for them too. Thread: http://developer.appcelerator.com/question/155815/already-added-lcomgoogleandroidgmsgamesachievementachievement",3
TIMOB-14931,"MobileWeb: option not properly toggling touch events for Ti.UI and ScrollableView","The flag needs to override the touch detection, but we forgot to add this to titanium/Ti/UI/ScrollableView.js and titanium/Ti/UI.js. We simply need to change both instances of {code} useTouch = 'ontouchstart' in global, {code} to {code} useTouch = has('touch'), {code}",2
TIMOB-14933,"CLI: Builds where tiapp.xml sdk-version differs from selected SDK fail to properly fork in Windows","The CLI tries to strip the first argument if it's the actual ""node"" executable before parsing the args. The problem is on Windows the node executable can sometimes contain the .exe and the following line of code fails: {code} // cli.js (line 218) args[0].slice(-4) === 'node' && args.shift(); {code} This line needs to look like this: {code} args[0].replace(/\\/g, '/').split('/').pop() == process.execPath.replace(/\\/g, '/').split('/').pop().replace(/\.exe$/, '') && args.shift(); {code}",1
TIMOB-15253,"Android: singleTask launchMode with HeavyWeight window hangs after 1st launch","When launching your app with it's main activity set to {{android:launchMode=""singleTask""}} and it's main window a HeavyWeight one, it will hang on the second and every following launch. This bug blocks me from allowing users to open my app by using an URL scheme on a webpage or in a email message, send to them when they lost their password, received an invite to play a game etc. h1. Why use launchMode? By default, when launching your app via another app, e.g. using an URL scheme in the browser, your apps main activity will be stacked onto the current app's task. If your app was already running in the background, you will have 2 instances of the app running. Android has a [launchMode|http://developer.android.com/guide/topics/manifest/activity-element.html#lmode] attribute that allows you to instruct the OS to always open the activity as the root of a new task, using {{singleTask}} as value. This works fine, but not when the app's main window is HeavyWeight, for example a {{Ti.UI.TabGroup}} or a {{Ti.UI.Window}} with {{modal:false}}. h1. To reproduce # Create a new project: {{titanium create -p android -n test}} # Build (only) to generate manifest: {{titanium build -b -p android}} # Open the generated {{build/android/AndroidManifest.xml}} and copy the first {{}} tree to the {{tiapp.xml}} under {{ti:app/android/manifest/application}}. You will need to create the empty {{}} and {{}} elements yourself. # Add {{android:launchMode=""singleTask""}} to the {{}} element and save {{tiapp.xml}}. # Build the app to the device: {{titanium build -p android -T device}} # Open the updated {{AndroidManifest.xml}} to confirm the only effective change is the newly added attribute. # Seeing the app properly launched on the device, move it to the background by clicking the device's home button. # Lookup the app on the device and launch it again. You'll see a black screen with a titlebar ({{test}}) only. # Now replace the app's {{app.js}} with a lightweight window instead of the default heavyweight tabgroup: {code} Ti.UI.createWindow({backgroundColor:'white'}).open(); {code} # Repeat steps 5-8 and this time, the app will properly launch.",8
TIMOB-14973,"Android Build: Validate command line arguments and tiapp.xml settings","* validate command line options ** --alias ** --android-sdk ** --avd-abi ** --avd-id ** --avd-name NEW! ** --avd-skin ** --device NEW! (TIMOB-12661 CLI: Support adb's -s option for pointing a build to a specific emulator or device) ** --debug-host ** --deploy-type NEW! (TIMOB-9139 Android: Tooling: How to set the deploytype) ** --key-password NEW! (TIMOB-6423 builder.py should accept an alias password) ** --keystore ** --output-dir ** --store-password (formerly --password) ** --target (emulator, device, dist-playstore) * if 64-bit Linux ** make sure i386 architecture has been added (not sure how to check, but to add run ""dpkg --add-architecture i386"") ** make sure ia32-libs package is installed (TIMOB-13520 Android Emulator: improve error message from missing ia32-libs dependency on linux) ** make sure /usr/lib/libGL.so exists * enforce sdk dependencies ** check java version is <=1.6 (TIMOB-5010 Latest version of Java unusable for building Android projects) * check that build directory is writeable * read tiapp.xml ** read proguard flag (TIMOB-2782 Android: Generate / Run a Proguard configuration based on API usage) ** determine tool api level *** ensure correct version fallback (TIMOB-11603 Android: invalid android path in bash profile results in project creation error, improve error message) ** packageid must contain at least one period (prepend ""com."" if no periods present) ** appversion should be the tiapp.xml and is injected into the AndroidManifest.xml (TIMOB-559 Android: Appversion never taken from tiapp.xml) ** default minimum Android SDK is 2.3.3 (10) ** default target Android SDK is latest or 2.3.3 (10) ** classname is the app name, capitalized, only alpha-numeric and _, prepend _ if starts with a number ** make sure deploy type is correct ** validate ""ti.ui.defaultunit"" property (must be 'system', 'px', 'dp', 'dip', 'mm', 'cm', or 'in') (TIMOB-9682 Android: Packaging:No warning displayed for default system value of 'ti.ui.defaultunit') ** get ""ti.android.loadfromsdcard"" property ** get ""ti.android.compilejs"" property ** get ""ti.android.include_all_modules"" property??? * scrub debugger/profiler args * find the android sdk home * validate icon from tiapp.xml * detect modules from tiapp.xml ** if required module is not found, fail (TIMOB-9930 Android: Packaging: With a non-existing module added to the project in the tiapp.xml,app packages without error and gets installed on device) (TIMOB-14064 Android build select wrong module jars for dex build) ** load module hooks *** allow module hooks to modify classpath (TIMOB-14170 Android: Provide mechanism for partners to specify the classpath for builds)",13
TIMOB-14974,"Android Build: Detect if need to force rebuild","* detect if need to force rebuild (TIMOB-4510 Force full re-build discrepancy between Android and iOS - Android requires modified tiapp.xml) ** yes if --force flag is set ** yes if build/android does not exist ** yes if build/android/AndroidManifest.xml does not exist ** yes if app id changes ** yes if app name changes ** yes if app version changes ** yes if publisher changes ** yes if url changes ** yes if copyright changes ** yes if description changes ** yes if icon changes ** yes if analytics changes ** yes if guid changes ** yes if fullscreen changes ** yes if navbar-hidden changes ** yes if classname changes ** yes if deploy type changes ** yes if compile js changes ** yes if list of modules change ** yes if any of the module's manifest or api name changes ** yes if any module's binary is changed (TIMOB-5837 Tooling: Adding a module requires a clean build) ** yes if new properties are added to tiapp.xml ** yes if Android target SDK version changes ** yes if any changes to activities in the Android in the tiapp.xml ** yes if any changes to activities in the Android in the tiapp.xml ** yes if any jss files change",5
TIMOB-14976,"Android Build: Init the build/android directory and files","* init the build/android directory and files ** if force rebuild, remove build/android if exists ** create build/android if does not exist ** remove directories, if exists *** build/android/src *** build/android/res ** create directories, if does not exist *** build/android/assets *** build/android/gen *** build/android/gen/ *** build/android/lib *** build/android/res *** build/android/res/drawable *** build/android/res/values *** build/android/src (IS THIS EVEN USED??? if not, we don't need the aidl file) ** copy over files *** AppInfo.java => build/android/gen//AppInfo.java *** AndroidManifest.xml => build/android/AndroidManifest.xml *** App.java => build/android/gen//Application.java *** Activity.java => build/android/gen//Activity.java *** classpath => build/android/.classpath *** project => build/android/.project **** make sure the .project file is a valid Eclipse project (TIMOB-11700 Make generated android projects importable into eclipse) *** default.properties => build/android/default.properties *** gitignore => build/android/.gitignore *** NOTE: each of the files must be converted from mako templates to handlebars templates ** merge custom classpath with build/android/.classpath ** generate activities from tiapp.xml ** generate services from tiapp.xml ** write app_modules to build/android/bin/assets/app.json??? * create directories, if does not exist ** build/android/bin ** build/android/bin/assets ** build/android/bin/assets/Resources ** build/android/bin/classes",5
TIMOB-14977,"Android Build: Compile resources","* compile resources ** copy Resources directory (exclude all platform directories) *** load dependency.json *** load modules.json *** handle tiapp.xml ""ti.android.include_all_modules"" property *** walk specified directory **** ignore globally ignored files and directories (TIMOB-2733 Android: Getting Error at Rebuilding after changing tiapp.xml) (TIMOB-7816 Android: Ignore files that start with ._) **** if file is a html file, scan for all A basic bar chart