Skip to content

Conversation

@shahzaibj
Copy link
Contributor

@shahzaibj shahzaibj commented Oct 8, 2025

Fixes AB#3396027

@shahzaibj shahzaibj self-assigned this Oct 8, 2025
@shahzaibj shahzaibj requested a review from a team as a code owner October 8, 2025 03:01
Copilot AI review requested due to automatic review settings October 8, 2025 03:01
@github-actions
Copy link

github-actions bot commented Oct 8, 2025

❌ Work item link check failed. Description does not contain AB#{ID}.

Click here to Learn more.

@shahzaibj shahzaibj requested a review from a team as a code owner October 8, 2025 03:01
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Removes setting the browser package name on the Custom Tabs intent while preserving it for plain ACTION_VIEW fallback intents.

  • Adds setPackage only when constructing a fresh ACTION_VIEW intent (fallback paths)
  • Removes the unconditional setPackage that previously also affected the CustomTab intent

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@shahzaibj shahzaibj changed the title Don't set browser pkg name in CustomTabIntent [DEV] [Cherry-pick September Hotfix] Don't set browser pkg name in CustomTabIntent Oct 8, 2025
@github-actions github-actions bot changed the title [DEV] [Cherry-pick September Hotfix] Don't set browser pkg name in CustomTabIntent [DEV] [Cherry-pick September Hotfix] Don't set browser pkg name in CustomTabIntent, Fixes AB#3396027 Oct 8, 2025
changelog.txt Outdated
- [MINOR] SDK now handles SMS as strong authentication method #2766
- [MINOR] Added error handling when webcp redirects have browser protocol #2767
- [PATCH] Fix for app link redirect from CCT due to forced browser preference (#2775)
- [PATCH] Don't set browser pkg name in CustomTabIntent (#2780)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if the hotfix resulted in a new common version, so disregard if not relevant, but I would think that maybe this change would be under the hotfix version?

Copy link
Contributor

@mohitc1 mohitc1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@shahzaibj shahzaibj merged commit c85568d into dev Oct 9, 2025
24 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants