@jan-tennert Thank you for your reply. I'll look into the alternative you suggest given that I cannot upgrade. In the meantime, I have a question. The library currently has this: ``` data class CustomTabs(val intentBuilder: CustomTabsIntent.Builder.() -> Unit = {}) : ExternalAuthAction ``` Just as the library user can pass their own `CustomTabsIntent.Builder`, would it help in any way if the user can also pass `intentConfig` to configure the underlying `Intent`, like this? ``` data class CustomTabs( val intentBuilder: CustomTabsIntent.Builder.() -> Unit = {}, val intentConfig: Intent.() -> Unit = {} ) : ExternalAuthAction ``` Then the user can add any `flags`, like this: ``` defaultExternalAuthAction = ExternalAuthAction.CustomTabs( intentBuilder = { setBookmarksButtonEnabled(false) setDownloadButtonEnabled(false) setShareState(CustomTabsIntent.SHARE_STATE_OFF) setShowTitle(true) }, intentConfig = { // FLAG_ACTIVITY_NEW_TASK: Added by the library itself as it is required when the CustomTabsIntent uses the application context // FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS, Intent.FLAG_ACTIVITY_NO_HISTORY: So that the Custom Tab does not appear in the recent apps list addFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS) addFlags(Intent.FLAG_ACTIVITY_NO_HISTORY) } ) ```
@jan-tennert It might not be sensitive in the general sense, but perhaps the SDK user does want to keep it private for whichever reason. Given that things like URLs of external services are usually static and generally do not change after the app starts up, when a `RestException` occurs at run time, I am not sure how useful it is to see the (fixed, static) URL in the stack trace.