duckduckgo / duckduckgo/Android

[Bug] AMP protection logic breaks websites (same issue seen in browser extension)

Open
#2,969 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs triage
Dominant language
Kotlin
Stars
4.8k
Forks
1.4k
Avg merge
2d 17h
Merged PRs (30d)
170

Description

Describe the bug

I have raised this issue previously on the browser extension repo here (see link for description of problem):

https://github.com/duckduckgo/duckduckgo-privacy-extension/issues/1545

It was resolved by first adding an exemption for our website, and then the feature was removed from the extension altogether. It's become apparent that this is also an issue on the mobile app, although we didn't know about it until now (I'm guessing fewer customers are using the mobile app vs. Firefox + browser extension).

Is it possible to add an exemption for the domain mentioned in that issue? And longer term to consider removing the feature, so it doesn't break other websites?

How to Reproduce

See linked issue for further information

Expected behavior

Expectation is that it works the same way as other browser - instead it does something that results in the user being redirected back to the login page with some cookies missing.

Environment
- DDG App Version: 5
- Device: Unknown (likely several)
- OS: Android 13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked browser-extension issue #1545, then locate the Android app's AMP protection logic and reproduce the login redirect with the reported environment where possible. Done means confirming the behavior and implementing or documenting a scoped resolution for the affected domain or feature, with Android coverage for the regression.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.