Migration Guide Custom URL Scheme #440
Conversation
….xml to clear internally set intent filters.
| @@ -250,3 +250,30 @@ Kotlin: | |||
|
|
|||
| DropIn handles browser switching internally. Specifying an `<intent-filter />` in `AndroidManifest.xml` is no longer required. Any payment method that requires a browser switch will work automatically. | |||
|
|
|||
| On the other hand, there are some scenarios that will require you to set a custom URL scheme for browser switch deep linking. For example, if your `applicationId` contains uppercase letters, you will need to override the default deep link configuration set by the DropIn library. | |||
|
|
|||
| Internally we use a manifest placeholder to support deep linking into `DropInActivity`. You can override the deep link intent filter for `DropInActivity` by placing the following xml snippet in your app's `AndroidManifest.xml`: | |||
There was a problem hiding this comment.
Should we also add a line like: If you are not setting a custom URL scheme for deep linking, you do not need to add an intent filter to support Drop-in?
In case merchants see this an think they always need to add this to their manifest.
There was a problem hiding this comment.
Yeah I thought about adding another section for this to make it clear. Technically we say "no additional configuration required" in the first paragraph of this section, but it may not be prominent enough.
There was a problem hiding this comment.
Oh true ok that's probably enough
There was a problem hiding this comment.
Do we have a ticket for adding this to the public dev docs?
There was a problem hiding this comment.
Ended up creating DTBTSDK-3020 for this.
Summary of changes
DropInRequestChecklist
- [ ] Added a changelog entryAuthors