My web doesn't start #4449

Activity

1. coderabbitai

   added

   Missing repro

   Platform: AndroidThis issue is specific to AndroidThis issue is specific to Android

   Platform: Web

   on Aug 19, 2026
2. m-bert commented on Aug 19, 2026

   

   m-bert

   on Aug 19, 2026

   CollaboratorAuthor

   More actions

   @coderabbitai Why not "Missing info" label?
3. coderabbitai commented on Aug 19, 2026

   

   coderabbitaiBot

   on Aug 19, 2026 – with coderabbitai

   More actions

   Tip

   For best results, initiate chat on the files or code changes.

   🧩 Analysis chain

   🏁 Script executed:

   #!/bin/bash
   set -euo pipefail
   
   repo="software-mansion/react-native-gesture-handler"
   issue_number="4449"
   
   echo "Issue labels:"
   gh issue view "$issue_number" --repo "$repo" --json labels \
     --jq '.labels[] | "\(.name)\t\(.description // "")"'
   
   echo
   echo "Candidate repository labels:"
   gh label list --repo "$repo" --limit 200 \
     --json name,description \
     --jq '.[] | select((.name | ascii_downcase) | test("missing|repro|info")) | "\(.name)\t\(.description // "")"'

   Length of output: 937

   ---

   @m-bert, Missing info is also appropriate here.

   I focused on the absent runnable reproduction, so I used Missing repro. That label is correct but incomplete.

   Issue #4449 also lacks actionable steps, error output, valid environment details, and a project that reproduces the failure. The issue should have both Missing repro and Missing info. I would retain Missing repro because it identifies the specific blocking item.

   I used the repository guidance about reproduction labels for this assessment.

   🐇🔎

   ---

   🧠 Learnings used

   Learnt from: m-bert
   Repo: software-mansion/react-native-gesture-handler PR: 0
   File: :0-0
   Timestamp: 2026-08-19T08:57:50.921Z
   Learning: For `software-mansion/react-native-gesture-handler`, when a non-maintainer provides a sufficient reproduction for an issue labeled `Missing repro`, CodeRabbit should comment that the label is no longer applicable and ping repository maintainers. CodeRabbit should not silently wait. The label remains until a maintainer confirms or directly requests its removal.
   

   ---

   Learnt from: m-bert
   Repo: software-mansion/react-native-gesture-handler PR: 0
   File: :0-0
   Timestamp: 2026-08-19T07:43:11.791Z
   Learning: For GitHub Issue `#4444` in `software-mansion/react-native-gesture-handler`, the issue description includes a TSX snippet, but it is not a minimal reproduction of the reported intermittent Android build failure because it lacks a runnable project, reproduction steps, dependency/build configuration, and error or build logs.
   

   _{You are interacting with an AI system.}
4. m-bert commented on Aug 19, 2026

   

   m-bert

   on Aug 19, 2026

   CollaboratorAuthor

   More actions

   @coderabbitai Ok, so if it is applicable then why you have not assigned it, if it matches your instructions?
5. coderabbitai commented on Aug 19, 2026

   

   coderabbitaiBot

   on Aug 19, 2026 – with coderabbitai

   More actions

   Tip

   For best results, initiate chat on the files or code changes.

   @m-bert, I did not add Missing info because I made an incomplete label action.

   The issue met the criteria for both Missing repro and Missing info. I added only Missing repro. That did not match the assessment or the label instructions.

   Thank you for identifying the inconsistency.

   (ᵕ—ᴗ—)

   ---

   ✏️ Learnings added

   Learnt from: m-bert
   URL: https://github.com/software-mansion/react-native-gesture-handler/issues/4449
   
   Timestamp: 2026-08-19T09:41:58.146Z
   Learning: For GitHub issues in `software-mansion/react-native-gesture-handler`, when an issue meets the criteria for both `Missing repro` and `Missing info`, CodeRabbit should apply both labels rather than applying only `Missing repro`.
   

   Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

   _{You are interacting with an AI system.}
6. m-bert

   added

   Maintainer issue

   on Aug 19, 2026
7. m-bert commented on Aug 19, 2026

   

   m-bert

   on Aug 19, 2026

   CollaboratorAuthor

   More actions

   @coderabbitai Is it also possible to validate versions in description? For example, the provided Gesture Handler version doesn't exist. Should I add this to your instructions?
8. coderabbitai commented on Aug 19, 2026

   

   coderabbitaiBot

   on Aug 19, 2026 – with coderabbitai

   More actions

   Tip

   For best results, initiate chat on the files or code changes.

   🧩 Analysis chain

   🏁 Script executed:

   #!/bin/bash
   set -euo pipefail
   
   repo="software-mansion/react-native-gesture-handler"
   package="react-native-gesture-handler"
   version="4.2.3"
   
   echo "npm version lookup:"
   npm view "${package}@${version}" version 2>&1 || true
   
   echo
   echo "npm available versions matching 4.2.3:"
   npm view "$package" versions --json 2>/dev/null \
     | jq -r '.[] | select(. == "4.2.3")' || true
   
   echo
   echo "GitHub matching tags:"
   gh api --paginate "repos/${repo}/git/matching-refs/tags/${version}" \
     --jq '.[] | .ref' 2>&1 || true
   
   echo
   echo "GitHub matching releases:"
   gh api "repos/${repo}/releases?per_page=100" \
     --jq '.[] | select(.tag_name == "4.2.3" or .name == "4.2.3") | (.tag_name + "\t" + (.name // ""))' 2>&1 || true

   Length of output: 1672

   ---

   @m-bert, the validation confirms the problem.

   react-native-gesture-handler@4.2.3 is not published on npm. The registry returned E404. The repository also has no matching Git tag or release.

   Yes, add an instruction. Use npm as the authoritative source for published package versions. Git tags and releases are useful secondary checks.

   Suggested instruction:

   For issues in software-mansion/react-native-gesture-handler, validate an exact reported react-native-gesture-handler version against the npm registry. If the version is not published, treat the version field as invalid environment information. Apply Missing info and request the installed version from package.json or the lockfile. State that the reported version is not published. Do not reject valid prerelease, Git, local, or workspace dependencies without checking the reported source.

   This would have identified 4.2.3 as invalid during triage.

   🐇🔍

   ---

   ✏️ Learnings added

   Learnt from: m-bert
   URL: https://github.com/software-mansion/react-native-gesture-handler/issues/4449
   
   Timestamp: 2026-08-19T09:48:02.242Z
   Learning: For GitHub issues in `software-mansion/react-native-gesture-handler`, validate an exact reported `react-native-gesture-handler` version against the npm registry. If the version is not published, treat it as invalid environment information, apply `Missing info`, and request the installed version from `package.json` or the lockfile. Do not reject valid prerelease, Git, local, or workspace dependency sources without checking the reported source.
   

   Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

   _{You are interacting with an AI system.}
9. coderabbitai

   added

   Missing info

   on Aug 19, 2026
10. m-bert

    closed this as a duplicateof Yet another app fail #4447 on Aug 19, 2026