The devDependency rollup was updated from 1.13.1 to 1.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot :palm_tree:

The devDependency @ngtools/webpack was updated from 6.2.9 to 7.3.8.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Find out more about this release.

Your Greenkeeper bot :palm_tree:

JIRA: https://jira.appcelerator.org/browse/TIMOB-26354

Description: Refactor the implementation of TabGroup - remove deprecated ActioBar tabs UI and replace it with TabLayout. Introduce a new style for using BottomNavigationView. A more detailed description will be available once I am done with everything.

Currently still trying to fix the removal of tabs before opening the TabGroup by simplifying the relation between the tab proxies added and their TiUiAbstractTab counterparts.

Update: How things work after the refactoring:

• all the code related to the deprecated ActionBar Tabs UI has been removed - that way all the problems with themes originating from ActionBar are no longer present. For instance now TabGroup can be used with a Theme.AppCompat.NoTitleBar and children of it without issues;
• handling of the ViewPager that is used to show the Tabs is moved to TiUIAbstractTabGroup;
• TiUIAbstractTabGroup provides an interface for communication with different "controllers";
• this allows us to have the separate styles as different implementations making it easier to support and introduce new styles;
• backwards compatibility with the JS code for the TabGroup implementation before this refactoring. Not defining a style at creation falls back to using the DEFAULT style which is as close as possible the ActionBar UI, but following the Material Design Guidelines ( one difference is the position of the icon relative to the title );
• fixes the behavior of some properties ( tabsBackgroundColor, tabsFocusedBackgroundColor ), adds some new properties ( style, shiftMode ) and brings parity with iOS for other ( titleColor, activeTitleColor );

Note: The constants for style will be used from the same namespace for the TabbedBar component. I will change them in the PR for it once this gets the green light for merging.

Tickets that should be resolved by this refactoring:

• https://jira.appcelerator.org/browse/TIMOB-24961
• https://jira.appcelerator.org/browse/TIMOB-19695
• https://jira.appcelerator.org/browse/TIMOB-15496
• https://jira.appcelerator.org/browse/TIMOB-23271
• https://jira.appcelerator.org/browse/TIMOB-25200
• https://jira.appcelerator.org/browse/TIMOB-17931
• https://jira.appcelerator.org/browse/TIMOB-16900 ( this one was already fixed, listing it here as the same behavior is kept )

Test case: app.js

var mainWindow = Ti.UI.createWindow({
		layout: 'vertical'
	}),
	buttonDefault = Ti.UI.createButton({
		title: 'Default'
	}),
	buttonBottom = Ti.UI.createButton({
		title: 'Bottom'
	}),
	winDefaultA = Ti.UI.createWindow({
		backgroundColor: 'red'
	}),
	winDefaultB = Ti.UI.createWindow({
		backgroundColor: 'green'
	}),
	winDefaultC = Ti.UI.createWindow({
		backgroundColor: 'blue'
	}),
	tabDefaultA = Ti.UI.createTab({
		title: 'Tab A',
		window: winDefaultA
	}),
	tabDefaultB = Ti.UI.createTab({
		title: 'Tab B',
		window: winDefaultB
	}),
	tabDefaultC = Ti.UI.createTab({
		title: 'Tab C',
		window: winDefaultC,
		backgroundColor: 'cyan',
		backgroundFocusedColor: 'magenta',
		titleColor: 'red',
		activeTitleColor: 'blue'
	}),
	tabGroupDefault = Ti.UI.createTabGroup({
		// for backwards compatibility if no style is defined, the component falls back to the default one
		style: Ti.UI.Android.TABS_STYLE_DEFAULT,
		tabs: [tabDefaultA, tabDefaultB, tabDefaultC],
		tabsBackgroundColor: '#88AAAAAA',
		tabsBackgroundSelectedColor: '#AAAAAA'
	}),
	winBottomA = Ti.UI.createWindow({
		backgroundColor: 'red'
	}),
	winBottomB = Ti.UI.createWindow({
		backgroundColor: 'green'
	}),
	winBottomC = Ti.UI.createWindow({
		backgroundColor: 'blue'
	}),
	tabBottomA = Ti.UI.createTab({
		title: 'Tab 1',
		window: winBottomA
	}),
	tabBottomB = Ti.UI.createTab({
		title: 'Tab 2',
		window: winBottomB,
	}),
	tabBottomC = Ti.UI.createTab({
		title: 'Tab 3',
		window: winBottomC,
		backgroundColor: 'cyan',
		backgroundFocusedColor: 'magenta',
		titleColor: 'red',
		activeTitleColor: 'blue'
	})
	tabGroupBottom = Ti.UI.createTabGroup({
		style: Ti.UI.Android.TABS_STYLE_BOTTOM_NAVIGATION,
		tabs: [tabBottomA, tabBottomB, tabBottomC],
		// The following two properties override the colors from TabGroup
		tabsBackgroundColor: '#88994444',
		tabsBackgroundSelectedColor: '#883333',
		// Comment the row below or set it to true to see the difference
		shiftMode: false
	}),
	buttonDisableTabNavigation = Ti.UI.createButton({
		title: 'Disable Tab Navigation'
	}),
	flagTabNavigationDisabled = false,
	buttonSetActiveTab = Ti.UI.createButton({
		title: 'Go to Tab A'
	});

buttonDisableTabNavigation.addEventListener('click', function () {
	flagTabNavigationDisabled = !flagTabNavigationDisabled;
	tabGroupDefault.disableTabNavigation(flagTabNavigationDisabled);
});
winDefaultB.add(buttonDisableTabNavigation);

buttonSetActiveTab.addEventListener('click', function () {
	tabGroupDefault.setActiveTab(tabDefaultA);
});
winDefaultC.add(buttonSetActiveTab);

buttonDefault.addEventListener('click', function () {
	tabGroupDefault.open();
});

buttonBottom.addEventListener('click', function () {
	tabGroupBottom.open();
});

mainWindow.add(buttonDefault);
mainWindow.add(buttonBottom);
mainWindow.open();

tabGroupDefault.addEventListener('open', function () {
	Ti.API.info('Default TabGroup OPEN event fired');
});
tabGroupDefault.addEventListener('close', function () {
	Ti.API.info('Default TabGroup CLOSE event fired');
});
tabGroupDefault.addEventListener('focus', function () {
	Ti.API.info('Default TabGroup FOCUS event fired');
});
tabGroupDefault.addEventListener('blur', function () {
	Ti.API.info('Default TabGroup blur event fired');
});
tabDefaultA.addEventListener('focus', function () {
	Ti.API.info('Default Tab A FOCUS event fired');
});
tabDefaultA.addEventListener('blur', function () {
	Ti.API.info('Default Tab A BLUR event fired');
});
tabDefaultA.addEventListener('selected', function () {
	Ti.API.info('Default Tab A SELECTED event fired');
});
tabDefaultA.addEventListener('UNSELECTED', function () {
	Ti.API.info('Default Tab A UNSELECTED event fired');
});

Note: I haven't added a new example in the docs. I was thinking the test case from here should do, but maybe it is not in the best format to go there (too long?).

JIRA: https://jira.appcelerator.org/browse/TIMOB-23310 https://jira.appcelerator.org/browse/TIMOB-23476

Description:

This is a MAJOR update of the V8 engine we use for Android. Our current engine is 3.9.24.29, which dates back to May/June 2012, so this brings the engine forward a full 4 years!

Note that right now even this version of V8 is behind. Once we get this merged we should regularly update. Right now Android stable version is: 5.1.281.57 - see https://omahaproxy.appspot.com Looks like they "release" pretty much weekly. We should consider having regular updates of V8 ourselves so that next time we don't have a major overhaul of all the native code and can handle API changes as they come.

This is a major breaking change and will mean all compiled/native modules for Android will need to be rebuilt.

This currently builds fine against Android NDK r11c for me, and I was able to run a classic two-tab app without problems.

https://jira.appcelerator.org/browse/TIMOB-28583

E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: ti.map.test, PID: 29094
E AndroidRuntime: java.lang.IllegalArgumentException: No view found for id 0x2 (unknown) for fragment SupportMapFragment{ab59c34} (12aebe3e-06b7-46e3-b9ca-2d53d2ec238d id=0x2)
E AndroidRuntime:        at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:513)
E AndroidRuntime:        at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:282)
E AndroidRuntime:        at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2189)
E AndroidRuntime:        at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2100)
E AndroidRuntime:        at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:2002)
E AndroidRuntime:        at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:524)
E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:873)
E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
E AndroidRuntime:        at android.os.Looper.loop(Looper.java:193)
E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6669)
E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

const mapView = Ti.UI.createView({
  height: 200
});
mapView.add(require('ti.map').createView());

const win = Ti.UI.createWindow({
  title: 'test',
  backgroundColor: 'gray'
});

function addListView() {
  var listView = Ti.UI.createListView({
    footerView: mapView,
    templates: {
      test: {
        childTemplates: [{
          type: 'Ti.UI.View',
          childTemplates: [{
            type: 'Ti.UI.Label',
            bindId: 'label',
            properties: {
              color: 'black',
              bindId: 'label'
            }
          }],
          properties: {
            width: Ti.UI.FILL,
            height: 200,
            cardUseCompatPadding: true,
            backgroundColor: 'white'
          }
        }]
      }
    },
    defaultItemTemplate: 'test'
  });
  var section = Ti.UI.createListSection();
  var items = [];

  for (let i = 0; i < 20; i++) {
    items.push({
      label: {
        text: 'item ' + i
      },
      template: 'test'
    })
  }

  section.setItems(items);
  listView.sections = [section];
  win.add(listView);
}

win.addEventListener('open', function() {
  addListView();
})
win.open();

Original discussion

I think the reason is a race condition between FragmentTransaction and attaching view to a window, i.e. app will crash when the transaction is executed before the view has been attached.

P.S. somehow connecting to the app with debugger make it harder to reproduce the problem.

JIRA:

• https://jira.appcelerator.org/browse/TIMOB-26015
• https://jira.appcelerator.org/browse/TIMOB-26144
• https://jira.appcelerator.org/browse/TIMOB-26128
• https://jira.appcelerator.org/browse/TIMOB-26124
• https://jira.appcelerator.org/browse/TIMOB-25899
• https://jira.appcelerator.org/browse/TIMOB-26217

Summary:

• Added a new "titanium_mobile/common/Resources" JavaScript folder.
  • Provides JS files/extensions intended to be shared by across all platforms.
• Android/iOS now launch using new ti.main.js instead of app.js.
  • Used to load JS extension/bootstrap scripts that are shared on all platforms.
  • Loads app.js once finished loading everything.
• Now logs app version and Titanium version on startup via ti.main.js instead of from native code.
  • New Message: <AppName> <AppVer> (Powered by Titanium <TiVer>.<TiBuildHash>)
• TIMOB-26015 Added bootstrap script support.
  • All files named bootstrap.js or end with name *.bootstrap.js under the "Resources" directory will be automatically required-in before app.js gets loaded. This is a recursive search.
  • This is the CommonJS equivalent of native Android module's onAppCreate() or iOS module's load() method.
  • Bootstrap script can support optional exports.execute(finishedCallback) method intended to display UI to end-user. Will not load app.js until given callback is invoked.
• TIMOB-26124 Fixed bug where Ti.buildHash always returned null on Android as of Titanium 6.0.0.
  • Was a typo in scons-build.js and scons-cleanbuild.js scripts.
  • Fix needed by new Titanium version logging on app startup. (Build hash needed to differentiate between RC and GA versions.)
• TIMOB-26128 Modified Android build system to include asset directory names have a leading underscore '_'.
  • This was an intentional limitation in Google's aapt Android command line tool.
  • Solved by using appt command line argument --ignore-assets and omitting <dir>_* from filter list.
• TIMOB-25899 Modified JS Error object to expose non-enumerable properties via JSON.stringify().
  • Was always returning "{}" on Android since none of the V8 Error object properties are enumerable.
  • Also modified to reveal stack property on iOS. (Not enumerable in JavaScriptCore.)
  • Solved by adding toJSON() method to Error object prototype. (See: ./common/Resources/ti.internal/extensions/Error.js)
  • Implementing this was not needed for this PR, but it's a proof of concept on how JS prototype can be extended on all platforms in Titanium's core JS code.
• TIMOB-26144 Significantly improved Android's performance in accessing files/directories under the "Resources" directory.
  • The File.getDirectoryListing() performance is now about 20x faster. The isDirectory(), isFile(), and existence() calls have been improved too.
  • Now stores a hash table of all file/directory paths under the APK's "assets" folder for quick existence checks. Paths are now obtained by accessing APK as a zip file and fetching its zip entries, which is significantly faster than AssetManager.list() calls.
• TIMOB-26217 iOS: Added missing Ti.Filesystem.File methods isFile() and isDirectory() when referencing an encrypted asset.
  • Was causing JS runtime errors in bootstrap recursive search.
• TIMOB-16678 Modified Android File.read() to not return an empty string when referencing an encrypted asset.
  • Needed to access new bootstrap.json for device/production builds.

Notes:

• I purposely did not document the new *.bootstrap.js handling in our API docs. We should dog-food it first to see how much we like it before setting it in stone. Plus we may want it to use Promises in the future (this feature is missing on iOS 9 at the moment).
• We plan on having our ti.playservices module take advantage of the bootstrapping feature in 7.4.0. It's needed to check/install/update "Google Play Services" before loading the app.js.

Test: Perform the below tests on the following:

• Android device without LiveView (This tests encrypted asset handling.)
• Android emulator (This tests APK's "assets" handling.)
• iOS device
• iOS emulator
• iOS 8 (This tests oldest JavaScript engine version handling.)

Test procedure:

1. Build and run the app with the below app.js and ui.bootstrap.js code. Note that the ui.bootstrap.js needs to be next to the app.js file under the Resources directory.
2. On app startup, verify that an alert is displayed stating that it was launched by a bootstrap.
3. Tap on the "OK" button.
4. Next the app.js will have loaded, displaying a JavaScript Error object in JSON form. (This verifies that our core JS extensions have been loaded.)
5. If running on iOS, verify that the displayed JSON contains a "stack" entry. (This used to be excluded on iOS.)
6. If running on Android, verify that the displayed JSON is not an empty "{}". The JSON should display entries "message" and "stack".
7. If running on Android, press the "Back" button and then restart the app. Verify that the bootstrap alert dialog (mentioned in step 2) is shown again.

app.js

var window = Ti.UI.createWindow({ fullscreen: true });
var scrollView = Ti.UI.createScrollView({
	layout: "vertical",
	showHorizontalScrollIndicator: false,
	shorVerticalScrollIndicator: true,
	width: Ti.UI.FILL,
	height: Ti.UI.FILL,
});
scrollView.add(Ti.UI.createLabel({
	text: "JSON.stringify(new Error('My error message'))",
	width: Ti.UI.FILL,
	top: "10dp",
}));
scrollView.add(Ti.UI.createLabel({
	text: JSON.stringify(new Error('My error message'), null, 4),
	width: "100%",
}));
window.add(scrollView);
window.open();

ui.bootstrap.js

exports.execute = function(finished) {
	var dialog = Ti.UI.createAlertDialog({
		title: 'Alert Dialog',
		message: 'This dialog was launched by a bootstrap script.',
		buttonNames: ['OK'],
		cancel: 0,
	});
	dialog.addEventListener('click', function(e) {
		finished();
	});
	dialog.show();
};

I have searched and made sure there are no existing issues for the issue I am filing

• [X] I have searched the existing issues

Description

The Ti.Airprint module will not work in the XCode simulator on M1 Macs since it was not built for that processor. And since I would also need a module to convert html to a pdf to use ti.airprint in my app, even rebuilding that won't be enough.

And since Google no longer supports Google print, there is no good way to print from an Android app built with Titanium SDK. I am not aware of any modules that address printing on Android.

I would like to see printing for both iOS and Android added to Titanium SDK so no module is needed, or updated modules to handle printing on both platforms that will run in the simulator on an M1 Mac. Printing seems like a core function and should be included in a robust way.

Aside from this suggestion, I have been very much enjoying using VSCode and the Titanium extension on my M1 Mac. Builds go very fast. I really appreciate all the work that went into making the open-source transition work. The new API documentation is very good and very easy to use. Lots of other great documentation as well. Thanks!

Solution

I would like to see printing included in Titanium SDK or new modules for printing for both iOS and Android that will run in the simulator on an M1 Mac as well.

Alternatives

I have tried a few workarounds, include openURL to try to open Safari with an html file to print (this is what I do with my Android app, but this is a clumsy solution, and far from ideal). I also tried doing a webview and then doing evalJS to do window.print() but that didn't work. I'm not sure if that's something that could work with changes to Titanium SDK or if it's a limitation of iOS. But again, that's not an ideal solution.

Platforms

Android & iOS

JIRA: https://jira.appcelerator.org/browse/TIMOB-18082

Description: This calls dexer with the --multi-dex argument, modifies our CLI to copy *.dex (not just classes.dex), and modifies TiApplication to override attachBaseContext to call MultiDex.install (to support loading multiple dex files). We also include the android-support-multidex.jar as a library dependency.

This PR's functionality was confirmed with the module @ashcoding provided.

Add support for Action Bar based Tab Groups. This is a monster refactoring so it is important we do lots of regression hunting.

For regression testing use KitchenSink or any other existing applications which use Tab Groups. To test the new Action Bar modify the android manifest and bump the targetSdkVersion to 14.

• Refactor Android asset encryption to utilize new ti.cloak module

TEST CASE

• Build application with encrypted assets
  • appc run -p android --deploy-type test
• Application should run without any issues

JIRA Ticket

The devDependency webpack was updated from 4.29.6 to 4.30.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot :palm_tree:

Bumps json5 from 1.0.1 to 1.0.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps fast-json-patch from 3.0.0-1 to 3.1.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This crash happens when soft-restarting the app (e.g. with https://github.com/rborn/tiapprestart) after opening an Universal Link / User Activities API. The reason is that we override the internal NSUserActivity to a NSDictionary during initial launch any try to re-access the native value that is already mapped to a dictionary at this point.

The testing setup is a bit complex, but it's basically this:

1. Download the ti.apprestart module: https://github.com/rborn/tiapprestart
2. Setup Universal Links: https://stackoverflow.com/questions/36542001/appcelerator-how-to-add-universal-links-support-in-ios9-app
3. Open a universally-linked URL
4. Return to the app
5. Trigger an app restart

-> App crashes!

I have searched and made sure there are no existing issues for the issue I am filing

• [X] I have searched the existing issues

Description

This is a very weird issue affecting only a few ios users so I really can't give you much details. I only know it is happening at ios devices (with different models or os versions) and it has been happening even when sdks where released by appcelerator team. So this is not a recent change.

Whenever we try to make a rest api call to our server we get a 404 Not found error.

I know you will say this seems a server side issue but the weird thing is that the issue gets resolved if app is deleted and reinstalled!

At some cases users never have the issue again, at others they have to install app every day.

Expected Behavior

Successful rest api calls.

Actual behavior

404 error on rest api calls

Reproducible sample

Random received from very few ios users as feedback

Steps to reproduce

Install app, try to perform a rest api call if this happens you get 404 as response.

Platform

No response

SDK version you are using

11.1.1.GA

Alloy version you are using

No response

I have searched and made sure there are no existing issues for the issue I am filing

• [X] I have searched the existing issues

Description

Currently the SDK still uses the normal ViewPager. Migrating to ViewPager2 would allow to use vertical orientation, RTL support and it's based on RecyclerView tech.

https://developer.android.com/develop/ui/views/animations/vp2-migration

Platforms

Android

This PR adds the option (filterAlwaysInclude) to always show specific rows in your search/filter results, even if they don't match the query

Example:

• run the code
• search for "apple"
• the "apple" row will show up and the "always show..." rows

var win = Ti.UI.createWindow();

var sectionFruit = Ti.UI.createTableViewSection({ headerTitle: 'Fruit' });
sectionFruit.add(Ti.UI.createTableViewRow({ title: 'Apples' }));
sectionFruit.add(Ti.UI.createTableViewRow({ title: 'Bananas' }));
sectionFruit.add(Ti.UI.createTableViewRow({ title: 'Always show (fruits)', filterAlwaysInclude: true}));

var sectionVeg = Ti.UI.createTableViewSection({ headerTitle: 'Vegetables' });
sectionVeg.add(Ti.UI.createTableViewRow({ title: 'Carrots' }));
sectionVeg.add(Ti.UI.createTableViewRow({ title: 'Potatoes' }));
sectionVeg.add(Ti.UI.createTableViewRow({ title: 'Always show (vegetables)', filterAlwaysInclude: true}));

var sectionFish = Ti.UI.createTableViewSection({ headerTitle: 'Fish' });
sectionFish.add(Ti.UI.createTableViewRow({ title: 'Cod' }));
sectionFish.add(Ti.UI.createTableViewRow({ title: 'Haddock' }));
sectionFish.add(Ti.UI.createTableViewRow({ title: 'Always show (fish)' , filterAlwaysInclude: true}));

var table = Ti.UI.createTableView({data: [sectionFruit, sectionVeg, sectionFish], search: Ti.UI.createSearchBar(), height: "45%", top: 0});
win.add(table);

// listview
var listView = Ti.UI.createListView({bottom: 0, height: "45%", searchView: Ti.UI.createSearchBar()});
var sections = [];

var fruitDataSet = [{properties: { title: 'Apple', searchableText:'Apple'}}, {properties: { title: 'Banana', searchableText:'Banana'}}, {properties: { title: 'Always show (fruits)', filterAlwaysInclude:true}}];
var fruitSection = Ti.UI.createListSection({ headerTitle: 'Fruits', items: fruitDataSet});
sections.push(fruitSection);

var vegDataSet = [{properties: { title: 'Carrots', searchableText:'Carrots'}},{properties: { title: 'Potatoes', searchableText:'Potatoes'}}, {properties: { title: 'Always show (vegetables)', filterAlwaysInclude:true}}];
var vegSection = Ti.UI.createListSection({ headerTitle: 'Vegetables', items: vegDataSet});
sections.push(vegSection);

var fishDataSet = [ {properties: { title: 'Cod', searchableText:'Cod'}}, {properties: { title: 'Haddock', searchableText:'Haddock'}}, {properties: { title: 'Always show (fish)', filterAlwaysInclude:true}}];
var fishSection = Ti.UI.createListSection({ headerTitle: 'Fish', items: fishDataSet});
sections.push(fishSection);

listView.sections = sections;
win.add(listView);

win.open();

TODO:

• [x] Android TableView
• [x] Android ListView
• [x] iOS TableView
• [x] iOS ListView