Notice.completion not always called
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When a notice already exists, and a second is presented, it's completion handler isn't called.
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the case described in the issue: present a second notice while one already exists, then observe whether its Notice.completion handler runs. Trace the notice presentation and completion flow in the project to identify the relevant entry point. Done means the completion handler is reliably called for the second notice, with a regression test covering the scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100