fix(android): prevent showing base activity

[m1ga]

fixes #13791

var win1 = Ti.UI.createWindow({
	backgroundColor: "green"
})
win1.addEventListener("click", function() {
	var win2 = Ti.UI.createWindow({
		backgroundColor: "red"
	})
	win2.open();
})
win1.open();

Steps to reproduce

• open the app (green window)
• click to open the second window (red)
• close the red window and close the green window right away
• you will see the root activity

more infos in the ticket

Update

I've changed the PR a bit. Instead of checking the stuff when closing the window I'll do it when adding a new activity. If we have more then one and the first one is still TiRootActivity (the launch screen) then it will be removed. This also helps you add <application android:enableOnBackInvokedCallback="true"/> in your tiapp.xml to enable Androids new predictive back feature. This way it will show the dashboard instead of the icon!

NOTE:

It will only run in a production build. It looks like LiveView needs it so it can restart the app without loading the whole app again.

If you test it make sure to build a dist-playstore app!

[hansemannn]

@m1ga We are currently testing this, but needed some other adjustments done by @prashantsaini1 to support Gradle 8 properly.

[hansemannn]

I feel like this hack might be a symthome of not using the best possible solution. According to both Apple and Google, apps should have the same core-functionality between dev and prod

[m1ga]

I only need it for Liveview as that needs the first activity not to be closed to restart the app. But we don't have a way to check for Liveview, that's why I've used dev/prod to do the check

[hansemannn]

Alright, then @prashantsaini1 will know what to do. It's still odd to have this check, but looking at Liveview it may make sense.

[m1ga]

it works without it but Liveview will look a bit different as you'll see the home screen and then it will launch again. I don't like the dev/prod difference either 😄 Let's see what Prashant will find 👍