airbnb / airbnb/DeepLinkDispatch
Device rotation: how to "consume" deeplink
Open
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 414
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
currently having the problem that the deeplink is handled everytime the activity gets recreated bc. of device rotation (orientation change).
Is there a proposed way of "consuming" the deeplink to not handle it again if the activity gets recreated?
Contributor guide
Research direction
Start by tracing how deeplinks are handled in the Android activity and how that activity is recreated during device rotation. Reproduce the repeated handling, then identify the expected consumed state and verify that rotating the device does not process the same deeplink again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100