wordpress-mobile / wordpress-mobile/WordPress-Android
Blaze Search Campaigns - Invoke DSP user create flow
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
When a new user first attempts to access the Blaze campaigns list, the initial call encounters a 400 error accompanied by the following error message: {"errorMessage":"No local user for WPCOM user {id}","errorCode":"no_local_user","cookies":[],"exists":0}.
This occurs because the DSP server requires synchronization of the WPCOM user and its insertion into the database.
To resolve this issue, is to invoke the DSP endpoint /sites/%s/wordads/dsp/api/v1/user/check to initiate the user creation process. Subsequently, retry the operation for the Blaze campaign search endpoint.
See conversation: p1697620395920789-slack-C04LJFS1G5P
iOS https://github.com/wordpress-mobile/WordPress-iOS/issues/21817
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Android Blaze campaigns list and campaign search flow, then inspect how the DSP request is made. Start with the /sites/%s/wordads/dsp/api/v1/user/check endpoint and verify that it runs before retrying the Blaze campaign search. Done means a first-time WPCOM user no longer receives no_local_user or the initial 400 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100