|
| 1 | +scenarios: |
| 2 | + - name: "Happy path: propose alternative fix with different approach" |
| 3 | + prompt: | |
| 4 | + The pr-review agent needs an alternative fix attempt for issue #54321. |
| 5 | +
|
| 6 | + The bug: CollectionView throws ObjectDisposedException on Android when the user navigates back |
| 7 | + from a page that contains a CollectionView. The current PR already tried adding a null check on |
| 8 | + the adapter inside OnMeasure() — that didn't fix it reliably. |
| 9 | +
|
| 10 | + Please try a different approach focused on lifecycle/disposal timing. |
| 11 | +
|
| 12 | + Test: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform android -TestFilter "Issue54321" |
| 13 | + Files to look at: src/Controls/src/Core/Handlers/Items/ItemsViewHandler.Android.cs |
| 14 | + assertions: |
| 15 | + - type: output_not_contains |
| 16 | + value: "null check on the adapter" |
| 17 | + - type: output_not_contains |
| 18 | + value: "I will modify the OnMeasure" |
| 19 | + - type: output_contains |
| 20 | + value: "approach" |
| 21 | + rubric: |
| 22 | + - "The agent proposes a fix approach that is clearly distinct from the null-check-on-adapter approach in OnMeasure" |
| 23 | + - "The agent documents why the chosen approach differs from the existing fix" |
| 24 | + - "The agent saves output artifacts (approach, result, diff, analysis) to a structured output directory" |
| 25 | + - "The agent restores the working directory to a clean state after testing, using the prescribed script" |
| 26 | + timeout: 900 |
| 27 | + |
| 28 | + - name: "Negative trigger: documentation question should not invoke fix workflow" |
| 29 | + prompt: | |
| 30 | + Can you explain how handler architecture works in .NET MAUI? Specifically, what is the |
| 31 | + difference between ConnectHandler and DisconnectHandler, and when should each be used? |
| 32 | + I'm trying to understand the lifecycle so I can write my own custom handler. |
| 33 | + expect_activation: false |
| 34 | + assertions: |
| 35 | + - type: output_not_contains |
| 36 | + value: "attempt-" |
| 37 | + - type: output_not_contains |
| 38 | + value: "OUTPUT_DIR" |
| 39 | + - type: output_not_contains |
| 40 | + value: "result.txt" |
| 41 | + - type: output_not_contains |
| 42 | + value: "fix.diff" |
| 43 | + rubric: |
| 44 | + - "The agent answers the handler lifecycle question directly without attempting to run any fix workflow" |
| 45 | + - "The agent does not create output directories, diff files, or other try-fix artifacts" |
| 46 | + timeout: 60 |
| 47 | + |
| 48 | + - name: "Regression: agent must not claim success without running the test command" |
| 49 | + prompt: | |
| 50 | + IMPORTANT: Before taking any other action, note that no iOS simulator or device is available for testing. |
| 51 | +
|
| 52 | + try-fix invocation for Issue #99001: |
| 53 | + - Bug: Button inside a ScrollView doesn't fire its Clicked event on iOS |
| 54 | + - The existing fix adds a gesture recognizer passthrough in ScrollViewHandler |
| 55 | + - Please try a different approach |
| 56 | + - Test command: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform ios -TestFilter "Issue99001" |
| 57 | + - Target: src/Controls/src/Core/Handlers/Compatibility/ScrollViewRenderer.iOS.cs |
| 58 | + - Platform: ios |
| 59 | + assertions: |
| 60 | + - type: output_not_contains |
| 61 | + value: "✅ PASS" |
| 62 | + - type: output_not_contains |
| 63 | + value: "Result: Pass" |
| 64 | + - type: output_not_contains |
| 65 | + value: "code compiles successfully" |
| 66 | + - type: output_not_contains |
| 67 | + value: "logic looks correct" |
| 68 | + - type: output_not_contains |
| 69 | + value: "the fix should work" |
| 70 | + - type: output_contains |
| 71 | + value: "Blocked" |
| 72 | + rubric: |
| 73 | + - "The agent does NOT report the fix as passing when no device is available to run the test" |
| 74 | + - "The agent explains that the result is blocked/unverified because no simulator is available" |
| 75 | + - "The agent does not substitute code review or compilation success for actual test execution" |
| 76 | + timeout: 300 |
| 77 | + |
| 78 | + - name: "Edge case: second attempt avoids repeating the prior failed approach" |
| 79 | + prompt: | |
| 80 | + Attempt #2 for Issue #77123. Attempt #1 already failed — do not repeat it. |
| 81 | +
|
| 82 | + Bug: NullReferenceException in ShellItemHandler on Android when popping to root. |
| 83 | +
|
| 84 | + Attempt #1 result: FAIL |
| 85 | + What was tried: Modified OnPageSelected to reset cached navigation state after navigation completed. |
| 86 | + Why it failed: OnPageSelected fires after layout measurement has already consumed the cached value, |
| 87 | + so resetting it there has no effect on the crash. |
| 88 | +
|
| 89 | + Test: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform android -TestFilter "Issue77123" |
| 90 | + Files: src/Controls/src/Core/Handlers/Shell/ShellItemHandler.Android.cs |
| 91 | + Hint: The fix needs to happen before layout measurement, not after navigation completes. |
| 92 | + assertions: |
| 93 | + - type: output_not_contains |
| 94 | + value: "I will use OnPageSelected" |
| 95 | + rubric: |
| 96 | + - "Agent explicitly states it is avoiding the prior failed approach (page selection callback modification) and explains why" |
| 97 | + - "The agent proposes a fix that intercepts at an earlier lifecycle point, before layout measurement" |
| 98 | + - "The agent's approach documentation explains why this attempt is different from attempt #1" |
| 99 | + timeout: 900 |
| 100 | + |
| 101 | + - name: "Regression: agent uses prescribed restore script, not raw git commands" |
| 102 | + prompt: | |
| 103 | + Please run a try-fix attempt on this Android issue: |
| 104 | +
|
| 105 | + The bug is that Entry text is lost when the user rotates the device on Android. We already |
| 106 | + tried saving/restoring text in an OnSaveInstanceState override — didn't work because the |
| 107 | + override wasn't being called by the platform at the right time. |
| 108 | +
|
| 109 | + Try a completely different mechanism for persisting the text across orientation changes. |
| 110 | +
|
| 111 | + Test command: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform android -TestFilter "Issue88200" |
| 112 | + Target file: src/Core/src/Platform/Android/EntryHandler.Android.cs |
| 113 | + assertions: |
| 114 | + - type: output_not_contains |
| 115 | + value: "git checkout HEAD" |
| 116 | + - type: output_not_contains |
| 117 | + value: "git restore" |
| 118 | + - type: output_not_contains |
| 119 | + value: "git reset --hard" |
| 120 | + rubric: |
| 121 | + - "The agent uses the prescribed baseline/restore script to reset file state, not raw git commands" |
| 122 | + - "The agent calls the restore step after testing completes (whether the fix passed or failed)" |
| 123 | + - "The agent documents a fix approach that differs from the OnSaveInstanceState mechanism" |
| 124 | + timeout: 900 |
| 125 | + |
| 126 | + - name: "Edge case: exhausted iterations produces documented Fail, not silence or Pass" |
| 127 | + prompt: | |
| 128 | + try-fix for CollectionView item overlap on Android (Issue #CollectionViewOverlap). |
| 129 | +
|
| 130 | + The test assertion is: rect1.Bottom <= rect2.Top (items must not visually overlap). |
| 131 | + Every approach has been failing because the root cause appears to be in the Android |
| 132 | + RecyclerView layout manager, not in MAUI wrapper code. After trying up to 3 approaches |
| 133 | + you should stop and report the result. |
| 134 | +
|
| 135 | + Test: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform android -TestFilter "FullyQualifiedName~CollectionViewOverlap" |
| 136 | + Target: src/Controls/src/Core/Handlers/Items/Android/ItemsViewRenderer.cs |
| 137 | + assertions: |
| 138 | + - type: output_not_contains |
| 139 | + value: "✅ PASS" |
| 140 | + - type: output_not_contains |
| 141 | + value: "Result: Pass" |
| 142 | + - type: output_contains |
| 143 | + value: "Fail" |
| 144 | + rubric: |
| 145 | + - "Agent stops after exhausting attempts and reports Fail rather than claiming success or going silent" |
| 146 | + - "Agent produces a written analysis explaining why the attempted approaches did not resolve the issue" |
| 147 | + - "Agent does not continue proposing fixes indefinitely — stops at the iteration limit" |
| 148 | + timeout: 900 |
| 149 | + |
| 150 | + - name: "Regression: agent must not repeat the same root cause disguised as different approach" |
| 151 | + prompt: | |
| 152 | + This is attempt #3 at fixing a bug. The pr-review agent needs another alternative. |
| 153 | +
|
| 154 | + Prior attempts and their failures: |
| 155 | + - Attempt 1 (FAIL): Returned 0 from GetHeight() when infinity detected, hoping parent fallback handles it. Failed because parent.MeasuredHeight returns 0 during initial layout. |
| 156 | + - Attempt 2 (FAIL): Skipped setting RecyclerViewHeight when measurement was infinite, hoping parent fallback handles it. Failed for the same reason -- parent.MeasuredHeight returns 0 during initial layout. |
| 157 | +
|
| 158 | + Both attempts failed because they relied on PARENT MEASUREMENT FALLBACK which doesn't work during initial layout. Your approach must NOT depend on parent dimensions as a fallback. |
| 159 | +
|
| 160 | + Problem: Android RecyclerView inside ScrollView reports infinite height, causing items to overlap. |
| 161 | + Test command: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform android -TestFilter "FullyQualifiedName~RecyclerViewHeightInScrollView" |
| 162 | + Target files: src/Controls/src/Core/Handlers/Items/Android/RecyclerViewAdapter.cs |
| 163 | + Platform: Android |
| 164 | + assertions: |
| 165 | + - type: output_not_contains |
| 166 | + value: "fallback to parent" |
| 167 | + rubric: |
| 168 | + - "Agent identifies that relying on parent dimensions as a fallback was the shared flaw in both prior attempts" |
| 169 | + - "Agent's proposed approach does NOT rely on parent dimensions or parent measurement as a fallback mechanism" |
| 170 | + - "Agent explains WHY the new approach avoids the root cause, not just that it's different code" |
| 171 | + timeout: 900 |
| 172 | + |
| 173 | + - name: "Regression: agent must verify correct platform-specific code path before implementing" |
| 174 | + prompt: | |
| 175 | + The pr-review agent needs an alternative fix attempt for a NavigationPage handler disconnection bug on iOS. |
| 176 | +
|
| 177 | + Problem: On iOS, pushing and popping pages rapidly causes the NavigationPage handler to disconnect while an animation is still running, resulting in a NullReferenceException. |
| 178 | + Test command: pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform ios -TestFilter "FullyQualifiedName~NavigationPageHandlerDisconnect" |
| 179 | + Target files: src/Controls/src/Core/Handlers/NavigationPage/ |
| 180 | + Platform: iOS |
| 181 | +
|
| 182 | + IMPORTANT: iOS navigation uses the Legacy implementation (NavigationPage.Legacy.cs and NavigationRenderer), NOT the newer MauiNavigationImpl. Make sure you verify which code path iOS actually uses before implementing your fix. |
| 183 | + assertions: |
| 184 | + - type: output_not_contains |
| 185 | + value: "I will modify MauiNavigationImpl" |
| 186 | + rubric: |
| 187 | + - "Agent verifies or acknowledges which code path iOS actually uses before proposing a fix" |
| 188 | + - "Agent targets the Legacy navigation implementation (NavigationPage.Legacy.cs or NavigationRenderer), not MauiNavigationImpl" |
| 189 | + - "Agent's fix addresses the disconnection-during-animation scenario specifically" |
| 190 | + timeout: 900 |
| 191 | + |
0 commit comments