The Chrome custom tab launched by ConnectLoginButton always launches in a new Android Task.
This means that our login UI will from the user's point of view seem be a separate "app" in the app switcher, which can be confusing.
We will also have to set the launchMode="singleTask" of the Activity that launches the Custom tab in order to prevent the callback to start another instance of that Activity in the same task as the Custom tab.
It would be nice if ConnectLoginButton had a way to chose between new task and same task. This could for example be done with a constructor, or a setter, or in some other way (builder pattern etc).
The Chrome custom tab launched by ConnectLoginButton always launches in a new Android Task.
This means that our login UI will from the user's point of view seem be a separate "app" in the app switcher, which can be confusing.
We will also have to set the launchMode="singleTask" of the Activity that launches the Custom tab in order to prevent the callback to start another instance of that Activity in the same task as the Custom tab.
It would be nice if ConnectLoginButton had a way to chose between new task and same task. This could for example be done with a constructor, or a setter, or in some other way (builder pattern etc).