[REFACTOR] Deeplink Processing Stabilization.

[doyoonkim3312]

📝 Summary (개요)

• Modify Deeplink Processing logic to stabilize deeplink received via ImplicitIntent/PendingIntent
• Apply missing Manifest Rule to WidgetConfigurationActivity to enhance UX.

🔗 Related Issue (관련 이슈)

• Resolves (if applicable) #
• Jira Ticket: KAN-105

🛠 Type of Change (변경 사항)

• FEAT: New feature (새로운 기능)
• FIX: Bug fix (버그 수정)
• REFACTOR: Code refactoring (no functional change) (코드 리팩토링)
• DESIGN: UI/UX changes (디자인 변경)
• !HOTFIX: Critical fix (치명적인 버그 수정)
• CHORE: Build/Config/CI (빌드/설정/CI)

✨ Key Changes (핵심 변경 사항)

• Resolve identified Deeplink-related edge case. (OS launch Task from History)
• Stabilize current Deeplink processing logic (utilize Channel to ensure correct intent processing while preventing duplicated navigation.
• Modify Manifest Rule for WidgetConfigurationActivity to enhance UX

📸 Screenshots / Video (스크린샷 또는 동영상)

Before (이전)	After (이후)
Screen_recording_20260331_015932.mp4	Screen_recording_20260331_020005.mp4

🧪 Test Plan (테스트 계획)

• Device: Android Emulator (Google Pixel 9 Pro, SDK 36)
• Scenario: (Deeplink Processing Test) Initiate Pending Intent via Push Notification while app is in Foreground/Background -> Requested Deeplink is correctly processed.
• Scenario: (Edge Case Scenario) Launch Application via either Pending Intent or Implicit Intent -> Press back button until app is closed -> Press system Overview button -> Re-enter the app -> Check whether app is correctly navigate user to HomeScreen. (Previous Deeplink is not being processed)

✅ Checklist (체크리스트)

• My code follows the style guidelines of this project (코드 스타일을 준수했습니다).
• I have performed a self-review of my own code (스스로 코드를 검토했습니다).
• I have commented my code, particularly in hard-to-understand areas (이해하기 어려운 부분에 주석을 작성했습니다).

[gemini-code-assist]

Code Review

This pull request updates the application version to 1.7.1 RC2 and refactors deeplink handling in MainActivity to use a Coroutine Channel and Flow instead of mutable state. It also modifies WidgetConfigurationActivity properties in the manifest and adds logic to SplashActivity to prevent re-processing intents when launched from history. Feedback was provided regarding the removal of analytics logging, potential duplicate intent processing during configuration changes, and the effectiveness of the synchronous loading state in the UI.

[doyoonkim3312]

/gemini summary

[gemini-code-assist]

Summary of Changes

This pull request focuses on stabilizing the application's deeplink handling logic to resolve edge cases related to activity lifecycle events and system-level task management. By transitioning to a robust flow-based architecture and implementing smarter intent delegation, the changes ensure that navigation events are processed exactly once, even during configuration changes or when restoring the app from the background.

Highlights

• Deeplink Processing Stabilization: Replaced the mutable state-based intent handling with a Coroutine Channel-based flow to ensure reliable, one-time processing of incoming intents and prevent duplicate navigation during activity recreation.
• History-Aware Intent Delegation: Updated SplashActivity to detect intents launched from history, preventing the re-processing of stale deeplinks when the user returns to the app via the system task manager.
• Widget Configuration UX: Modified the AndroidManifest for WidgetConfigurationActivity to use a dedicated task affinity and singleTask launch mode, improving the user experience when configuring widgets.

Activity

• The pull request was created by doyoonkim3312.
• Gemini Code Assist provided feedback regarding potential analytics regressions, duplicate processing on rotation, and synchronous loading state management.
• The author addressed the feedback by implementing a channel-based flow to handle intent processing and provided explanations for the current state of analytics logging.