As of Titanium 8.0.0, launching/resuming the app using a data intent such as a URL scheme, notification, etc. will cause the app to be opened without any slide-in or fade-in animation. The app will suddenly appear instead.
The app will animate normally when launched from the app list screen (ie: the main launcher intent) or via the startActivityForResult() method.
Titanium's intent and app resume handling was completely rewritten in 8.0.0 (see:
TIMOB-26075) in order to resolve "newintent" issues while an app activity instance already exists in the background. It solved it by quickly destroying the activity instance created by the Android OS, resuming the existing activity, and passing the new intent to it. However, this code change completely disabled the open animation in this case so that new activity instance that is being quickly created/destroy won't ever appear onscreen. This was an issue that can be seen on a , although not all devices showed this behavior such as the Pixel 2.
We need to find a better solution where the new activity that is quickly created/destroyed is never shown, but we can preserve the animation for the resumed activity.
Do the following instead. I don't think there is a good way to know what the default transition animation is per device (ex: slide-up or fade), but a fade effect seems reasonable.