pichillilorenzo/flutter_inappwebview

Executive summary

pichillilorenzo/flutter_inappwebview scores 41 out of 100 and is rated Weak, while four of its six lenses score higher still: Architecture at 93, rated Adequate, Security and Compliance at 71 and Performance at 70, both rated Strong, and Code Health at 43, rated Weak.

The score is lower than those four because the weakest lens counts most, and here that is Production Readiness, which scores 32 and is rated Weak. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in Secret Scanning and to resolve the 403 Orphaned file finding(s) in Knowledge Freshness, and if Production Readiness rose to 70, the score would rise from 41 to about 49.

Six findings are critical: three in Static Analysis (SAST), two in Secret Scanning and one in Secrets (history).

Watchdog couldn't measure 12 dimensions in this code, among them Code Coverage, Test Reliability and Navigability, so they are left out of the score. The product code is 181,185 lines, which would take an estimated 1.1 person-years, around €160,000, to rebuild.

Code Health 43 Weak, capped by Cognitive Complexity, Type Safety and Large Files Architecture 93 Adequate, capped by Project Cohesion Maturity 39 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 32 Weak, capped by Secret Scanning, Tooling, CI/CD gates and Security & performance tooling Security and Compliance 71 Strong Performance 70 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 32 · counts for 46%Maturity 39 · counts for 25%Code Health 43 · counts for 14%Performance 70 · counts for 8%Security and Compliance 71 · counts for 4%Architecture 93 · counts for 2%

If Production Readiness rose from 32 to 70, the lowest score rated Strong, the score would rise from 41 to about 49.

Code composition: what the lines of code are

Product code 97%Tests 3%

New since the last survey: 34 findings

These 34 critical or serious findings weren't in the previous survey, on 9 October 2026.

Code Duplication · Edited copy of a member (135 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift
Code Duplication · Edited copy of a member (15 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift
Code Duplication · Edited copy of a member (7 corresponding lines) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java
Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java
Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 39 findings

These 39 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.

Code Duplication · Edited copy of a member (135 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift
Code Duplication · Edited copy of a member (15 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift
Code Duplication · Edited copy of a member (7 corresponding lines) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java
Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java
Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_distinguished_names.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_web/lib/src/web_storage/web_storage.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart
Exception handling · Swallowed exception (empty catch) flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart

Rebuild cost: about €160,000 · Estimate

Cost to rebuild	€53,000 to €270,000, for 883 to 2,802 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Large: 181,185 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).

Raises the score by about 9 points · Low effort · Secret Scanning

Resolve the 403 Orphaned file finding(s) in Knowledge Freshness — start with in_app_webview_controller.dart (8), headless_in_app_webview.dart (7), in_app_webview.dart (7).

Raises the score by about 6 points · High effort · Knowledge Freshness

Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.

Raises the score by about 5 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 32 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

What hard-to-read code costs each year · Cost

Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.9 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 5% to 12% on every change. The history of the code shows how much it changes: about 213,088 lines over the last 90 days, which is about 864,190 lines a year. At that pace, the extra work comes to an estimated 114.5 to 687 engineer-days a year, and it grows as more code changes.

How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.

Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history

What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

37 modules, with 77 dependencies between them. 2 loops run through 19 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	2 android.print	6 flutter_inappwebview_ios~ios~flutter_inappwebview_ios~flutter_inappwebview_ios	9 repository.src	11 web_support.src.types	12 com.pichillilorenzo.flutter_inappwebview_android.content_blocker	13 com.pichillilorenzo.flutter_inappwebview_android.find_interaction	14 com.pichillilorenzo.flutter_inappwebview_android.print_job	15 com.pichillilorenzo.flutter_inappwebview_android.pull_to_refresh	17 repository.utils	19 com.pichillilorenzo.flutter_inappwebview_android.webview.in_app_webview	20 repository.models	21 com.pichillilorenzo.flutter_inappwebview_android.in_app_browser	22 repository.providers	23 com.pichillilorenzo.flutter_inappwebview_android.webview	27 com.pichillilorenzo.flutter_inappwebview_android.webview.web_message	28 com.pichillilorenzo.flutter_inappwebview_android.types	29 com.pichillilorenzo.flutter_inappwebview_android.chrome_custom_tabs	30 com.pichillilorenzo.flutter_inappwebview_android.credential_database	31 com.pichillilorenzo.flutter_inappwebview_android.headless_in_app_webview	33 com.pichillilorenzo.flutter_inappwebview_android.process_global_config	34 com.pichillilorenzo.flutter_inappwebview_android.proxy	35 com.pichillilorenzo.flutter_inappwebview_android.service_worker	36 com.pichillilorenzo.flutter_inappwebview_android.tracing	37 com.pichillilorenzo.flutter_inappwebview_android
1 (global)
2 android.print
3 flutter_inappwebview.example.assets.js
4 flutter_inappwebview.example.test_assets
5 flutter_inappwebview.example.web
6 flutter_inappwebview_ios~ios~flutter_inappwebview_ios~flutter_inappwebview_ios
7 flutter_inappwebview_linux.example.assets
8 flutter_inappwebview_web.example.web
9 repository.src
10 test_node_server
11 web_support.src.types
12 com.pichillilorenzo.flutter_inappwebview_android.content_blocker										1						1
13 com.pichillilorenzo.flutter_inappwebview_android.find_interaction														1		3								2
14 com.pichillilorenzo.flutter_inappwebview_android.print_job																6								3
15 com.pichillilorenzo.flutter_inappwebview_android.pull_to_refresh																2								2
16 flutter_inappwebview_macos~macos~flutter_inappwebview_macos~flutter_inappwebview_macos		354
17 repository.utils											1
18 web_support.src				1
19 com.pichillilorenzo.flutter_inappwebview_android.webview.in_app_webview	1				1	1	1	1				5		5	2	13								4
20 repository.models									8
21 com.pichillilorenzo.flutter_inappwebview_android.in_app_browser								1		1						5								2
22 repository.providers									1		8
23 com.pichillilorenzo.flutter_inappwebview_android.webview							1			4		1			2	58								4
24 repository		1	1								1		1
25 repository.screens			5						6		16		5
26 repository.widgets									4		11		1
27 com.pichillilorenzo.flutter_inappwebview_android.webview.web_message														2		9
28 com.pichillilorenzo.flutter_inappwebview_android.types															1									2
29 com.pichillilorenzo.flutter_inappwebview_android.chrome_custom_tabs																8								3
30 com.pichillilorenzo.flutter_inappwebview_android.credential_database																4								1
31 com.pichillilorenzo.flutter_inappwebview_android.headless_in_app_webview										1						4								2
32 com.pichillilorenzo.flutter_inappwebview_android.plugin_scripts_js																9
33 com.pichillilorenzo.flutter_inappwebview_android.process_global_config																1								3
34 com.pichillilorenzo.flutter_inappwebview_android.proxy																2								2
35 com.pichillilorenzo.flutter_inappwebview_android.service_worker																8								1
36 com.pichillilorenzo.flutter_inappwebview_android.tracing																2								2
37 com.pichillilorenzo.flutter_inappwebview_android							1					1		2		6	2	1	1	1	1	1	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 43% · Weak · gated by D2, R1, R3 ·

The Good

D3 · Dart God Classes 8.2 D4 · Dart Code Duplication 7.6 D17 · Dart Explicit Debt 10.0 R10 · React / TS Code Duplication 9.3 R2 · React / TS Cyclomatic Complexity 7.6 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

X5 · Repo Nullable reference types 6.5

The Ugly

D1 · Dart Cyclomatic Complexity 4.3 D2 · Dart Cognitive Complexity 3.7 R1 · React / TS Type Safety 3.3 R3 · React / TS Large Files 0.0 X18 · Repo Disposal-pattern correctness 4.9 X3 · Repo Exception handling 4.9

At a glance — Architecture · 93% · Adequate · gated by D26 ·

The Good

D5 · Dart Coupling 10.0 D6 · Dart Cohesion (LCOM4) 7.9 D35 · Dart Change Coupling 9.9 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.4 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0 R9 · React / TS Circular Imports 10.0

The Ugly

D22 · Dart Internal API Consistency 3.0 D26 · Dart Project Cohesion 3.8

At a glance — Maturity · 39% · Weak · gated by D34, M2 ·

The Good

D15 · Dart Churn × Complexity Hotspots 9.2 D19 · Dart Documentation Quality 8.0 D21 · Dart Naming Consistency 10.0 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0

The Bad

M1 · Repo Documentation (README) 6.7

The Ugly

D34 · Dart Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 32% · Weak · gated by D13, R6, P1, P3 ·

The Good

D9 · Dart Test Distribution 10.0 D12 · Dart Dependency Hygiene 9.9 D14 · Dart License Compliance 10.0 P6 · Repo Release Hygiene 10.0 R5 · React / TS Dependency Freshness 10.0 R8 · React / TS Dependency Hygiene 9.5

The Bad

P10 · Repo Library API & versioning 6.0

The Ugly

D13 · Dart Secret Scanning 0.0 P1 · Repo CI/CD gates 1.5 P3 · Repo Security & performance tooling 0.0 R6 · React / TS Tooling 0.0

At a glance — Security · 71% · Strong ·

The Good

D28 · Dart Secrets (history) 9.0 D30 · Dart Dependency Vulnerabilities 9.8 D43 · Dart Malicious Dependencies 10.0 D44 · Dart Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Bad

S1 · Repo Web-Security Posture 6.0

The Ugly

D29 · Dart Static Analysis (SAST) 4.5 X24 · Repo Document value interpolated into markup unescaped 2.7

At a glance — Performance · 70% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 7.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A05:2025 — Injection	15	High / Critical
A07:2025 — Authentication Failures	4	High / Critical
A03:2025 — Software Supply Chain Failures	1	Medium

Roadmap

Immediately resolve the two leaked secrets in REDACTED and address the forty-three orphaned files in the webview controllers to restore code hygiene. Strengthen the CI pipeline by integrating SAST tools like the Dart analyzer and semgrep to block security regressions, while adding standard test, lint, and type-checking scripts to ensure consistent quality. Finally, document significant design decisions in a dedicated ADR folder to preserve architectural context for the team.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).	+8.7 pts	Low	Secret Scanning
Resolve the 403 Orphaned file finding(s) in Knowledge Freshness — start with in_app_webview_controller.dart (8), headless_in_app_webview.dart (7), in_app_webview.dart (7).	+5.7 pts	High	Knowledge Freshness
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.	+4.6 pts	Medium	Security & performance tooling
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.	+4.6 pts	Medium	Tooling
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+4.5 pts	Medium	Architecture documentation
Add a CI workflow that triggers on push and pull_request, checks the code out, and runs the build and the test suite — so a change cannot merge without having been compiled and exercised.	+3.9 pts	Medium	CI/CD gates
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.	+2.3 pts	Medium	Large Files
Improve Documentation Quality — currently 8.0/10.	+1.9 pts	Medium	Documentation Quality

File quality

Per-file score 0–10 — a quality signature. Of 287 files carrying findings, judged against the Production bar: 0% slop · 60% mixed · 40% near-clean.

File	Score	Band	Worst signal
REDACTED	4.6	Mixed	Secret Scanning: Leaked secret: REDACTED
flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart	5.5	Mixed	Cyclomatic Complexity: WindowsInAppWebViewController._handleMethod (cyclomatic 514)
flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart	5.5	Mixed	Cyclomatic Complexity: AndroidInAppWebViewController._handleMethod (cyclomatic 437)
flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart	5.5	Mixed	Cyclomatic Complexity: IOSInAppWebViewController._handleMethod (cyclomatic 431)
flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart	5.5	Mixed	Cyclomatic Complexity: AndroidChromeSafariBrowser._handleMethod (cyclomatic 30)
flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart	5.5	Mixed	God Classes: TooManyMethods: InAppBrowser
flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart	5.5	Mixed	God Classes: FileTooLong: web_storage/platform_web_storage.dart
flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart	5.5	Mixed	Cyclomatic Complexity: LinuxInAppWebViewController._handleMethod (cyclomatic 303)
flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart	5.5	Mixed	Cyclomatic Complexity: AndroidInAppWebViewWidget._inferInitialSettings (cyclomatic 26)
flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart	5.5	Mixed	Cyclomatic Complexity: IOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24)
flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart	5.5	Mixed	Cyclomatic Complexity: WebPlatformInAppWebViewController._handleMethod (cyclomatic 64)
flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart	5.5	Mixed	Code Duplication: Duplicated block (18 lines × 2)
flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart	5.7	Mixed	Cyclomatic Complexity: LinuxInAppWebViewWidget._inferInitialSettings (cyclomatic 24)
flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart	5.7	Mixed	God Classes: TooManyMethods: PlatformInAppBrowserEvents
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): Medium: REDACTED
flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart	5.9	Mixed	Cyclomatic Complexity: MacOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24)
flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart	5.9	Mixed	Cyclomatic Complexity: WindowsInAppWebViewWidget._inferInitialSettings (cyclomatic 24)
flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview.dart	5.9	Mixed	Cyclomatic Complexity: WebPlatformInAppWebViewWidget._inferInitialSettings (cyclomatic 18)
flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_certificate.dart	5.9	Mixed	Cognitive Complexity: X509Certificate.decodeToDER (cognitive 16)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 6

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 1521

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 452

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 14

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 71 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 71 dimensions across the health lenses

D1D2D3D4D5D6D9D12D13D14D15D17D19D21D22D26D28D29D30D34D35D43D44AX1AX10AX3AX4AX6AX8AX9M1M2M3M4P1P10P3P6PF3R1R10R2R3R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1958 of 1979 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1690b-85f0-790a-ad00-62cb44754cdb.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 879 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cc (31,841 lines, 14% of production source), .cpp (10,968 lines, 5% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.dart) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.dart) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Dart pubspec.yaml, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Dart dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (108 contributor(s) across 1806 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 107 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D26 Project Cohesion — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Project size and spread are measured over build units whose source a code model reads. This repository's .cc, .cpp source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift`, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/SafariViewController/ChromeSafariBrowserManager.swift` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity4.3 / 10Weak✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.3 / 10 · rule-coverage 100% · ceiling Prevented

97 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WindowsInAppWebViewController._handleMethod at 514. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being InAppWebViewSettings.parse at 106 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_identifier.dart (ASN1IdentifierTagNumber.toString at 30). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

CredentialDatabase.handle (cyclomatic 47) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22

WebMessageListener.isOriginAllowed (cyclomatic 37) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139

WebMessageListener.assertOriginRulesValid (cyclomatic 26) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32

InAppWebView.webView (cyclomatic 22) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952

WebMessageChannelChannelDelegate.handle (cyclomatic 19) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19

+ 86 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 5 bodies over 240 down to 240 or less in Cyclomatic Complexity — start with WindowsInAppWebViewController._handleMethod (cyclomatic 514), AndroidInAppWebViewController._handleMethod (cyclomatic 437), MacOSInAppWebViewController._handleMethod (cyclomatic 432). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 4.3 to about 5.1/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity3.7 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 3.7 / 10 · rule-coverage 100% · ceiling Prevented

157 method(s) exceeded the cognitive complexity threshold of 15; the worst was WindowsInAppWebViewController._handleMethod at 875.

InAppWebView.injectJavascriptFileFromUrl (cognitive 22) · ×3flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1264

InAppWebView.injectCSSFileFromUrl (cognitive 19) · ×3flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1326

InAppWebView.userContentController (cognitive 149) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947

CredentialDatabase.handle (cognitive 86) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22

WebMessageListener.isOriginAllowed (cognitive 60) · ×2flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139

+ 132 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 8 bodies over 240 down to 240 or less in Cognitive Complexity — start with WindowsInAppWebViewController._handleMethod (cognitive 875), AndroidInAppWebViewController._handleMethod (cognitive 747), MacOSInAppWebViewController._handleMethod (cognitive 739). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 3.7 to about 5.1/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes8.2 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Prevented

135 god class(es) detected.

MethodTooLong: WindowsInAppWebViewController._handleMethod · ×52flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207

TooManyMethods: PlatformInAppWebViewController · ×29flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:68

ClassTooLong: WindowsInAppWebViewController · ×27flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:47

FileTooLong: in_app_webview/in_app_webview_controller.dart · ×27flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart

What to do

Resolve the 52 MethodTooLong finding(s) in God Classes — start with in_app_webview_controller.dart (11), InAppWebView.swift (8), headless_in_app_webview.dart (6). — One of this dimension's main actionable groups (52 warning-level).
Resolve the 29 TooManyMethods finding(s) in God Classes — start with in_app_webview_controller.dart (7), inappwebview_platform.dart (7), InAppWebView.swift (2). — One of this dimension's main actionable groups (29 warning-level).
Resolve the 27 ClassTooLong finding(s) in God Classes — start with in_app_webview_controller.dart (6), InAppWebView.swift (2), WebViewChannelDelegate.swift (2). — One of this dimension's main actionable groups (27 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication7.6 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Verified

879 duplicated block group(s) detected. A further 113 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 145 of the 992 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .cc, .cpp (19% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (7 lines × 2) · ×46flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:133

Duplicated block (10 lines × 2) · ×41dev_packages/generators/lib/src/exchangeable_enum_generator.dart:69

Duplicated block (6 lines × 2) · ×40dev_packages/generators/lib/src/exchangeable_enum_generator.dart:391

Duplicated block (5 lines × 2) · ×36flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:85

Members sharing a duplicated core (5 members, 50+ identical tokens) · ×34flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:64

+ 258 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 46 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with WebViewChannelDelegate.swift (9), InAppWebView.swift (6), WebMessagePort.swift (3). — One of this dimension's main actionable groups (46 warning-level).
Resolve the 41 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with InAppWebView.swift (5), InAppWebViewClient.java (3), Util.swift (3). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 40 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with WebViewChannelDelegate.swift (11), pull_to_refresh_controller.dart (3), in_app_webview_controller.dart (2). — One of this dimension's main actionable groups (40 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

14 production modules (Gradle+npm+SwiftPM+pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)7.9 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 100% · ceiling Verified

42 of 240 classes have LCOM4 above 3.

Low cohesion: PlatformInAppWebViewController (LCOM4 158) · ×42flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:68

What to do

Resolve the 42 Low cohesion finding(s) in Cohesion (LCOM4) — start with in_app_webview_controller.dart (6), in_app_webview.dart (6), chrome_safari_browser.dart (2). — One of this dimension's main actionable groups (42 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

3 test methods: 3 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

2 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.

Outdated: swift-collections

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

2 secret(s) detected.

REDACTED

What to do

Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 5 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 6 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json and a Dart pubspec.yaml, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.2 / 10Stronggated by 12 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart (9×514=4626); flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart (15×303=4545); flutter_inappwebview/example/lib/providers/test_runner.dart (12×43=516)

Hotspot: flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart · ×12flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207

What to do

Resolve the 12 Hotspot finding(s) in Churn × Complexity Hotspots — start with in_app_webview_controller.dart (2), test_runner.dart, method_tester_widget.dart. — One of this dimension's main actionable groups (12 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

5 deducted task-comment markers across 181185 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×5flutter_inappwebview/example/integration_test/chrome_safari_browser/sf_safari_view_controller.dart:26

What to do

Resolve the 5 TodoComment finding(s) in Explicit Debt — start with sf_safari_view_controller.dart, category_screen.dart, InputAwareWebView.java. — One of this dimension's main actionable groups (5 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

The repository is well documented: a single root README (1741 words) gives an overview of the Flutter InAppWebView plugin with links to Twitter/Facebook share badges, supported platforms, articles/resources, and a showcase; it also states requirements, installation, usage, platform setup, support, and contributors. The individual subdirectory READMEs (e.g., flutter_inappwebview_android/README.md) each document their own directories (Android/iOS/Linux/macOS/Web/Windows examples/platform interface/internal annotations), with the root README covering the project as a whole.

What to do

Improve Documentation Quality — currently 8.0/10. — The repository is well documented: a single root README (1741 words) gives an overview of the Flutter InAppWebView plugin with links to Twitter/Facebook share badges, supported platforms, articles/resources, and a showcase; it also states requirements, installation, usage, platform setup, support, and contributors. The individual subdirectory READMEs (e.g., flutter_inappwebview_android/README.md) each document their own directories (Android/iOS/Linux/macOS/Web/Windows examples/platform interface/internal annotations), with the root README covering the project as a whole.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyWeak◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Verified

4 API inconsistencies across a 400-member sample of 252 exposed types.

Duplicate operation with inconsistent naming and signature. 'evaluateJavaScript' and 'evaluateJavascript' differ only by case (camelCase vs PascalCase for the method name), which is a common source of confusion in Swift/ObjC interop. Furthermore, the 'evaluateJavascript' variant drops the Error parameter from the completion handler, implying different error handling semantics or a legacy wrapper, creating ambiguity for the caller.

Duplicate operation with inconsistent signatures. Two methods named 'close' exist: one with an optional completion handler and one without. This forces the caller to guess which overload is appropriate or handle the lack of callback in the no-arg version, violating the principle of least surprise.

Conflicting lifecycle management. 'disposeAndGetFlutterWebView' implies a transition of ownership/state, while 'dispose' has an overloaded version with a boolean flag and a no-arg version. The intent of 'disposeWebView: Bool' is unclear compared to the explicit 'disposeAndGet...' method. It is unclear if 'dispose()' is a no-op or performs a default action.

Inconsistent navigation API surface. 'InAppWebView' uses a single 'goBackOrForward(steps: Int)' method, while 'InAppBrowserWebViewController' provides separate 'goBack()' and 'goForward()' methods. This forces developers to remember different APIs for similar concepts depending on the specific controller type.

What to do

Resolve the 1 Duplicate operation with inconsistent naming and signature.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate operation with inconsistent signatures. Two methods named… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Conflicting lifecycle management. 'disposeAndGetFlutterWebView' implies… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D26 · Project Cohesion3.8 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 3.8 / 10 · rule-coverage 100% · ceiling Documented

5 of 15 build units (Gradle, SwiftPM, npm, pub) flagged as possibly oversized/incoherent. This repository's .cc, .cpp source was read by no build unit, so this covers part of the tree, not all of it.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)4.5 / 10Weak✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 4.5 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 3 high, 12 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.

REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

406 of 406 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart. Counted over 406 of the 971 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×403flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1

Most significant orphaned file · ×3flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:1

Dormant codebase

What to do

Resolve the 403 Orphaned file finding(s) in Knowledge Freshness — start with in_app_webview_controller.dart (8), headless_in_app_webview.dart (7), in_app_webview.dart (7). — One of this dimension's main actionable groups (403 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with platform_inappwebview_controller.dart, InAppWebView.swift, in_app_webview_settings.dart. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: web_support.js↔in_app_web_view_web_element.dart 80%; in_app_browser.dart↔headless_in_app_webview.dart 63%; in_app_browser.dart↔in_app_webview.dart 57%

Change coupling: web_support.js ↔ in_app_web_view_web_element.dart · ×3flutter_inappwebview_web/lib/assets/web/web_support.js:1

Change-coupling hub: in_app_browser.dart → chrome_safari_browser.dart, headless_in_app_webview.dart, in_app_webview.dartflutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart

What to do

Resolve the 3 Change coupling finding(s) in Change Coupling — start with web_support.js, chrome_safari_browser.dart, in_app_webview_controller.dart. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with in_app_browser.dart. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 10 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

Do you agree with this assessment?

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

Do you agree with this assessment?

AX6 · Interface segregation9.4 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

`InAppWebView` declares 26 required operations: `disableContextMenuHandler`, `prepare`, `setSettings`, `reload`, `goBack`, `goForward`, `goBackOrForward`, `evaluateJavascript`, `stopLoading`, `getUrl`, `getTitle`, `injectJavascriptFileFromUrl`, `injectCSSCode`, `injectCSSFileFromUrl`, `scrollTo`, `scrollBy`, `printCurrentPage`, `getContentHeight`, `getContentWidth`, `getSelectedText`, `getScrollX`, `getScrollY`, `isSecureContext`, `canScrollVertically`, `canScrollHorizontally`, `getSize`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — web_support/src/types.ts:12
`InAppWebViewInterface` declares 90 abstract methods: `addWebMessageListener`, `callAsyncJavaScript`, `canGoBack`, `canGoBackOrForward`, `canGoForward`, `canScrollHorizontally`, `canScrollVertically`, `clearAllCache`, `clearFocus`, `clearHistory`, `clearMatches`, `clearSslPreferences`, `createCompatWebMessageChannel`, `createWebMessageChannel`, `disposeWebMessageChannels`, `disposeWebMessageListeners`, `evaluateJavascript`, `findAllAsync`, `findNext`, `getCertificate`, `getChannelDelegate`, `getContentHeight`, `getContentHeight`, `getContentWidth`, `getContext`, `getContextMenu`, `getCopyBackForwardList`, `getCustomSettings`, `getCustomSettingsMap`, `getHitTestResult`, `getHitTestResult`, `getInAppBrowserDelegate`, `getOriginalUrl`, `getPlugin`, `getProgress`, `getScrollX`, `getScrollY`, `getSelectedText`, `getTitle`, `getUrl`, and 50 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 90 declarations carry 86 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 86 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/InAppWebViewInterface.java:30

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 9 of 9 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

Do you agree with this assessment?

M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates1.5 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

A workflow is configured, but none of the repository's 3 workflows (`REDACTED`, `no-response.yaml`, `REDACTED`) runs on a code change (no `push` or `pull_request` trigger) or checks the code out — so nothing here builds or tests a change before it merges. This is automation for the repository's ISSUES AND HOUSEKEEPING, not a gate on its code: a pull request can land without anything having compiled or run it. The rows about missing build and test steps are deliberately not reported beside this one, because there is no pipeline for them to be missing from — adding the gate is one action, not three.

What to do

Add a CI workflow that triggers on push and pull_request, checks the code out, and runs the build and the test suite — so a change cannot merge without having been compiled and exercised.

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

1158/1277 types (91%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

What to do

Keep implementation types off the public surface (Dart: a `_` name, or keep it under `lib/src/` unexported; Java: package-private (no modifier), or leave its package out of `module-info` exports; Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 2956 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

PF3 · Async & latency hygiene7.0 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

`fs.statSync` in `app.get("/test-download-file")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:216
`fs.readFileSync` in `app.get("/test-download-file")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:217

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

R1 · Type Safety3.3 / 10Weak✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

2 typed · 4 plain JS — the untyped files are flutter_inappwebview_web/lib/assets/web/web_support.js, test_node_server/client.js, REDACTED, test_node_server/public/js/main.js. 0 production file(s) opt out entirely with @ts-nocheck · 7 @ts-ignore suppression(s).

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication9.3 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

flutter_inappwebview_web/lib/assets/web/web_support.js:24 · web_support/src/index.ts:43 — the two spans are one implementation copied and then locally edited — 4013 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — flutter_inappwebview_web/lib/assets/web/web_support.js:24
web_support/src/index.ts:186 · web_support/src/index.ts:198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — web_support/src/index.ts:186

What to do

Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.

Do you agree with this assessment?

R2 · Cyclomatic Complexity7.6 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

(anonymous) has cyclomatic complexity 29 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — flutter_inappwebview_web/lib/assets/web/web_support.js:47, web_support/src/index.ts:73
setSettings has cyclomatic complexity 21 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — flutter_inappwebview_web/lib/assets/web/web_support.js:296, web_support/src/index.ts:352
getSize has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — flutter_inappwebview_web/lib/assets/web/web_support.js:638, web_support/src/index.ts:704

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

web_support/src/index.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web_support/src/index.ts:1
flutter_inappwebview_web/lib/assets/web/web_support.js has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — flutter_inappwebview_web/lib/assets/web/web_support.js:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R5 · Dependency Freshness10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

Do you agree with this assessment?

R6 · Tooling0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.

Do you agree with this assessment?

R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

Do you agree with this assessment?

R8 · Dependency Hygiene9.5 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

Declared in test_node_server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

Do you agree with this assessment?

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves HTTP itself (flutter_inappwebview_platform_interface/lib/src/in_app_localhost_server.dart:96 — `HttpServer.bind(`), so its Dart source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Dart spelling appears in production source, not proven on every route. Every server it binds listens on the loopback interface only, so its traffic never leaves the device and HTTPS enforcement is N/A, as it is for a native app's loopback redirect listener (RFC 8252 §7.3).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: flutter_inappwebview_platform_interface/lib/src/in_app_localhost_server.dart:96 — `HttpServer.bind(`.
No handler of this repository's Dart server answers 400, 413 or 422 (`Response.badRequest`, `HttpStatus.badRequest`, `statusCode = 400`) and no validation package (luthor, acanthis, ez_validator, json_schema, …) is imported — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: flutter_inappwebview_platform_interface/lib/src/in_app_localhost_server.dart:96 — `HttpServer.bind(`.

What to do

Set security response headers on what the server sends — `response.headers.set('X-Content-Type-Options', 'nosniff')` in a `dart:io` handler, or a shelf middleware that adds `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy to every `Response`.
Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it, so a client and a proxy can tell a refusal from a success.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness4.9 / 10Weak✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

`CustomPlatformViewController` carries a disposal duty — it declares its own release — and it creates `_cursorStreamController` itself (line 139, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_cursorStreamController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_cursorStreamController.close();` in `dispose()` before `super.dispose()`. — flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:139
`CustomPlatformViewController` carries a disposal duty — it declares its own release — and it creates `_cursorStreamController` itself (line 114, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_cursorStreamController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_cursorStreamController.close();` in `dispose()` before `super.dispose()`. — flutter_inappwebview_windows/lib/src/in_app_webview/custom_platform_view.dart:114

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped2.7 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

`source` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — flutter_inappwebview_web/lib/assets/web/web_support.js:487, web_support/src/index.ts:550

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling4.9 / 10Weak✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×33) — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:716, flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:690, flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1630, …
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — flutter_inappwebview_platform_interface/lib/src/types/sandbox.dart:22, flutter_inappwebview_platform_interface/lib/src/types/sandbox.dart:36, flutter_inappwebview_platform_interface/lib/src/x509_certificate/oid.dart:114, …

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X5 · Nullable reference types6.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

~26.6 `!` null assertions per 1k Dart product lines — 2671 across the 100392 line(s) of the 550 Dart file(s) read (generated, test and example code not counted; a file opted out with a `// @dart=` comment below 2.12 counts once). Densest: flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart (516), flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart (463), flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart (457). Each one tells the analyzer to trust the author about null and becomes a `Null check operator used on a null value` the first time the author is wrong.

What to do

Raise every package's `environment: sdk:` lower bound to 2.12 or above (`^3.0.0` today) and migrate with `dart migrate` on an SDK that still has it, so `String` and `String?` mean different things. Then replace assertions rather than adding to them: each `!` is a run-time null check the analyzer could not prove — promote the value with a null check or an early return, use `?.` / `??` where absence is legitimate, make the field non-nullable and `late final` only where initialisation is truly guaranteed, or change the API so the null cannot arrive.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	43%	Weak — gated by D2, R1, R3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	93%	Adequate — gated by D26	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	39%	Weak — gated by D34, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	32%	Weak — gated by D13, R6, P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	71%	Strong	Strongest area.
Performance	70%	Strong	Solid.

Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 55 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~6217 lines of test source are present (.dart) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .dart test runner
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JavaScript/TypeScript, Dart, JVM, Swift source (15 module(s), 970 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Dart, Java and Swift code has 151,519 production line(s), 7 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 3 test file(s) reach none of 3 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 6 finding(s)

D13 · Secret Scanning · Leaked secret · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D28 · Secrets (history) · High secret · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

Serious — 1521 finding(s)

D3 · God Classes · MethodTooLong · ×52

MethodTooLong: WindowsInAppWebViewController._handleMethod flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207 — MethodTooLong — _handleMethod runs 1506 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1406 over it, 15.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AndroidInAppWebViewController._handleMethod flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206 — MethodTooLong — _handleMethod runs 1289 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1189 over it, 12.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MacOSInAppWebViewController._handleMethod flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:207 — MethodTooLong — _handleMethod runs 1273 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1173 over it, 12.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IOSInAppWebViewController._handleMethod flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:207 — MethodTooLong — _handleMethod runs 1270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1170 over it, 12.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LinuxInAppWebViewController._handleMethod flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198 — MethodTooLong — _handleMethod runs 826 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 726 over it, 8.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebViewChannelDelegate.handle flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20 — MethodTooLong — handle runs 576 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 476 over it, 5.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebViewChannelDelegate.onMethodCall flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:81 — MethodTooLong — onMethodCall runs 559 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 459 over it, 5.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebViewChannelDelegate.handle flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:20 — MethodTooLong — handle runs 552 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 452 over it, 5.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExchangeableObjectGenerator.generateForAnnotatedElement dev_packages/generators/lib/src/exchangeable_object_generator.dart:45 — MethodTooLong — generateForAnnotatedElement runs 529 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 429 over it, 5.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExchangeableEnumGenerator.generateForAnnotatedElement dev_packages/generators/lib/src/exchangeable_enum_generator.dart:47 — MethodTooLong — generateForAnnotatedElement runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebViewSettings.parse flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java:168 — MethodTooLong — parse runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.setSettings flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:830 — MethodTooLong — setSettings runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.setSettings flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1031 — MethodTooLong — setSettings runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.prepare flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:258 — MethodTooLong — prepare runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebViewSettings_.InAppWebViewSettings_ flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:3279 — MethodTooLong — InAppWebViewSettings_ runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InterceptAjaxRequestJS.INTERCEPT_AJAX_REQUEST_JS_SOURCE flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:60 — MethodTooLong — INTERCEPT_AJAX_REQUEST_JS_SOURCE runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.userContentController flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947 — MethodTooLong — userContentController runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.userContentController flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2158 — MethodTooLong — userContentController runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.webView flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092 — MethodTooLong — webView runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.webView flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1372 — MethodTooLong — webView runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebPlatformInAppWebViewController._handleMethod flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:112 — MethodTooLong — _handleMethod runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ContentBlockerHandler.checkUrl flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerHandler.java:53 — MethodTooLong — checkUrl runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.prepare flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:377 — MethodTooLong — prepare runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppWebView.setSettings flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:559 — MethodTooLong — setSettings runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InterceptFetchRequestJS.INTERCEPT_FETCH_REQUEST_JS_SOURCE flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:31 — MethodTooLong — INTERCEPT_FETCH_REQUEST_JS_SOURCE runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
+ 27 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×46

Duplicated block (7 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:133 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:133-139 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:109-115 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2611 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2611-2617 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2583-2589 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3404 — flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3404-3410 | flutter_inappwebview_windows/lib/src/webview_environment/webview_environment.dart:96-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:73 — flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:73-79 | flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart:73-79 — before extracting anything, compare `flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/HttpAuthResponse.java:26 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/HttpAuthResponse.java:26-32 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsAlertResponse.java:23-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:25 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:25-31 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java:25-31 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/MediaSizeExt.java:44 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/MediaSizeExt.java:44-50 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/ResolutionExt.java:44-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1067 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1067-1073 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1076-1082 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:15 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:15-21 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java:15-21 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerActionType.java:18 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerActionType.java:18-24 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerTriggerResourceType.java:24-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:16 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:16-22 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/CustomSchemeHandler.swift:16-22 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/CustomSchemeHandler.swift` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1091 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1091-1097 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:573-579 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1091` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1708 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1708-1714 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1042-1048 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1708` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1721 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1721-1727 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1055-1061 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1721` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:21 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:21-27 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:21-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:53 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:53-59 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift:52-58 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/InAppBrowserMenuItem.swift:32 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/InAppBrowserMenuItem.swift:32-38 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/InAppBrowserMenuItem.swift:31-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/InAppBrowserMenuItem.swift:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:46 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:46-52 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift:46-52 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:50 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:50-56 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:50-56 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167-173 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:96-102 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1727 — flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1727-1733 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1788-1794 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3207 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3207-3213 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2417-2423 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3321 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3321-3327 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2615-2621 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:93 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:93-99 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift:93-99 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:87 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:87-93 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:87-93 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 21 more in this group — see findings.md.

D6 · Cohesion (LCOM4) · Low cohesion · ×42

Low cohesion: PlatformInAppWebViewController (LCOM4 158) flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:68 — PlatformInAppWebViewController's methods fall into 158 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 158 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LinuxInAppWebViewController (LCOM4 73) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:43 — LinuxInAppWebViewController's methods fall into 73 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 73 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WindowsInAppWebViewController (LCOM4 73) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:47 — WindowsInAppWebViewController's methods fall into 73 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 73 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: IOSInAppWebViewController (LCOM4 71) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:47 — IOSInAppWebViewController's methods fall into 71 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 71 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InAppBrowser (LCOM4 70) flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart:16 — InAppBrowser's methods fall into 70 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 70 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AndroidInAppWebViewController (LCOM4 68) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:45 — AndroidInAppWebViewController's methods fall into 68 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 68 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MacOSInAppWebViewController (LCOM4 64) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:46 — MacOSInAppWebViewController's methods fall into 64 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 64 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WebPlatformInAppWebViewController (LCOM4 33) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:41 — WebPlatformInAppWebViewController's methods fall into 33 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 33 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformInAppBrowser (LCOM4 26) flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart:78 — PlatformInAppBrowser's methods fall into 26 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 26 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformChromeSafariBrowser (LCOM4 25) flutter_inappwebview_platform_interface/lib/src/chrome_safari_browser/platform_chrome_safari_browser.dart:20 — PlatformChromeSafariBrowser's methods fall into 25 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 25 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformPullToRefreshController (LCOM4 17) flutter_inappwebview_platform_interface/lib/src/pull_to_refresh/platform_pull_to_refresh_controller.dart:82 — PlatformPullToRefreshController's methods fall into 17 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 17 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformWebViewEnvironment (LCOM4 15) flutter_inappwebview_platform_interface/lib/src/webview_environment/platform_webview_environment.dart:57 — PlatformWebViewEnvironment's methods fall into 15 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 15 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ChromeSafariBrowser (LCOM4 14) flutter_inappwebview/lib/src/chrome_safari_browser/chrome_safari_browser.dart:8 — ChromeSafariBrowser's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformFindInteractionController (LCOM4 14) flutter_inappwebview_platform_interface/lib/src/find_interaction/platform_find_interaction_controller.dart:101 — PlatformFindInteractionController's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformWebAuthenticationSession (LCOM4 13) flutter_inappwebview_platform_interface/lib/src/web_authentication_session/platform_web_authenticate_session.dart:47 — PlatformWebAuthenticationSession's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AndroidServiceWorkerController (LCOM4 11) flutter_inappwebview_android/lib/src/service_worker_controller.dart:29 — AndroidServiceWorkerController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformCookieManager (LCOM4 10) flutter_inappwebview_platform_interface/lib/src/platform_cookie_manager.dart:68 — PlatformCookieManager's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformServiceWorkerController (LCOM4 10) flutter_inappwebview_platform_interface/lib/src/platform_service_worker_controller.dart:36 — PlatformServiceWorkerController's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformLocalStorage (LCOM4 10) flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:577 — PlatformLocalStorage's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformSessionStorage (LCOM4 10) flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:812 — PlatformSessionStorage's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformWebStorageManager (LCOM4 10) flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage_manager.dart:42 — PlatformWebStorageManager's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AndroidChromeSafariBrowser (LCOM4 8) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:30 — AndroidChromeSafariBrowser's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformHeadlessInAppWebView (LCOM4 8) flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_headless_in_app_webview.dart:227 — PlatformHeadlessInAppWebView's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformHttpAuthCredentialDatabase (LCOM4 7) flutter_inappwebview_platform_interface/lib/src/platform_http_auth_credentials_database.dart:41 — PlatformHttpAuthCredentialDatabase's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlatformPrintJobController (LCOM4 7) flutter_inappwebview_platform_interface/lib/src/print_job/platform_print_job_controller.dart:74 — PlatformPrintJobController's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
+ 17 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×41

Duplicated block (10 lines × 2) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:69 — dev_packages/generators/lib/src/exchangeable_enum_generator.dart:69-78 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:73-82 — before extracting anything, compare `dev_packages/generators/lib/src/exchangeable_enum_generator.dart` and `dev_packages/generators/lib/src/exchangeable_object_generator.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:75 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:75-84 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:77-86 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:47 — flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:47-56 | flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart:47-56 — before extracting anything, compare `flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_platform_interface/lib/src/in_app_webview/apple/in_app_webview_options.dart:231 — flutter_inappwebview_platform_interface/lib/src/in_app_webview/apple/in_app_webview_options.dart:231-240 | flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:3375-3384 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) flutter_inappwebview_windows/lib/src/cookie_manager.dart:141 — flutter_inappwebview_windows/lib/src/cookie_manager.dart:141-150 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:183-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/lib/src/cookie_manager.dart:452 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:452-461 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:452-461 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:112 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:112-121 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:114-123 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:188 — flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:188-197 | flutter_inappwebview_windows/lib/src/in_app_webview/custom_platform_view.dart:163-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1296 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1296-1305 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1344-1353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:127 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:127-136 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:126-135 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:140 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:140-149 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:139-148 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:140` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:348 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:348-357 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:359-368 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:359` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:61 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:61-70 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:41-50 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:411 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:411-420 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:95-104 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:411` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:675 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:675-684 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:278-287 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771-780 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:324-333 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2641 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2641-2651 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1853-1862 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2641` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3560 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3560-3569 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2829-2838 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3560` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:459 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:459-468 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:433-442 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:459` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift:30 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift:30-39 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptAjaxRequestJS.swift:30-39 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptAjaxRequestJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift:41 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift:41-50 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptAjaxRequestJS.swift:41-50 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptAjaxRequestJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptAjaxRequestJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertResponse.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertResponse.swift:23-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ClientCertResponse.swift:23-32 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ClientCertResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:23-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift:23-32 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift:23-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsAlertResponse.swift:23-32 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsAlertResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:30 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:30-39 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:31-40 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 16 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×40

Duplicated block (6 lines × 2) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:391 — dev_packages/generators/lib/src/exchangeable_enum_generator.dart:391-396 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:692-697 — before extracting anything, compare `dev_packages/generators/lib/src/exchangeable_enum_generator.dart` and `dev_packages/generators/lib/src/exchangeable_object_generator.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:334 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:334-339 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:181-186 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2790 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2790-2795 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1002-1007 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 58 separate duplicated blocks between them, totalling at least 765 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3054 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3054-3059 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3082-3087 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:81 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:81-86 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:79-84 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:116 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:116-121 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:114-119 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:123 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:123-128 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:121-126 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:343 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:343-348 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:434-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:343` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:433` calls `putInt` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:342` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:123 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:123-128 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:132-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:621 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:621-626 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageChannel.java:97-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:621` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeSafariBrowserManager.java:36 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeSafariBrowserManager.java:36-41 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java:64-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerChannelDelegate.java:135 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerChannelDelegate.java:135-140 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1273-1278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:807 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:807-812 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:833-838 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLCredentialDao.java:99 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLCredentialDao.java:99-104 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLProtectionSpaceDao.java:94-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:52 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:52-57 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionController.swift:22-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionController.swift` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146-151 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:144-149 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:285 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:285-290 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:275-280 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebView.swift:61 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebView.swift:61-66 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebView.swift:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:872 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:872-877 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:405-410 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1424 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1424-1429 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:793-798 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:780 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:780-785 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:745-750 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:788` calls `defaultBehaviour` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:751` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:806 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:806-811 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:767-772 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:814` calls `defaultBehaviour` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:773` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:832 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:832-837 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:789-794 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:840` calls `defaultBehaviour` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:795` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:888 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:888-893 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:841-846 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:895 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:895-900 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:848-853 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 15 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×36

Duplicated block (5 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:85 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:85-89 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:87-91 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:288 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:288-292 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:170-174 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2605 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2605-2609 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2563-2567 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2986 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2986-2990 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3386-3390 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 119 separate duplicated blocks between them, totalling at least 2751 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2992 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2992-2996 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3392-3396 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 119 separate duplicated blocks between them, totalling at least 2751 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2998 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2998-3002 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3398-3402 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 119 separate duplicated blocks between them, totalling at least 2751 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:88 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:88-92 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:86-90 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:94 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:94-98 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:92-96 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:110 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:110-114 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:108-112 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/lib/src/cookie_manager.dart:463 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:463-467 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:463-467 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:142 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:142-146 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:144-148 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:148 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:148-152 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:150-154 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_platform_interface/lib/src/types/trusted_web_activity_default_display_mode.dart:15 — flutter_inappwebview_platform_interface/lib/src/types/trusted_web_activity_default_display_mode.dart:15-19 | flutter_inappwebview_platform_interface/lib/src/types/trusted_web_activity_immersive_display_mode.dart:39-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:65 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:65-69 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:142-146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:37 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:37-41 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/tracing/TracingControllerManager.java:24-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLProtectionSpaceDao.java:41 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLProtectionSpaceDao.java:41-45 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/URLProtectionSpaceDao.java:72-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:78 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:78-82 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:92-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java:179 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java:179-183 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/FlutterWebView.java:50-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:78 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:78-82 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:61-65 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:26 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:26-30 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift:26-30 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:28 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:28-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift:27-31 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:22 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:22-26 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/NSColor.swift:22-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:45 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:45-49 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift:45-49 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2054 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2054-2058 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1334-1338 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:43 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:43-47 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:43-47 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 11 more in this group — see findings.md.

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×34

Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:64 — flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_ios/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_linux/lib/src/find_interaction/find_interaction_controller.dart:62-83 | flutter_inappwebview_macos/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_windows/lib/src/find_interaction/find_interaction_controller.dart:64-85 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:124 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:124-149 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:123-148 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:125-154 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:118-147 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:125-154 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:151 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:151-186 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:150-185 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:156-195 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:149-184 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:156-195 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:188 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:188-203 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:187-202 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:197-212 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:186-201 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:197-212 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:205 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:205-220 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:204-219 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:214-229 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:203-218 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:214-229 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:249 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:249-256 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:248-255 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:258-265 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:247-254 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:258-265 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:324 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:324-332 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:323-331 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:333-341 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:322-330 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:333-341 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:352 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:352-361 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:351-360 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:361-370 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:350-359 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:361-370 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:433 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:433-445 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:427-439 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:420-432 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:411-423 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:454-466 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:403 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:403-430 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:342-369 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:268-302 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:337-363 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:351-377 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:481 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:481-496 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:416-431 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:349-363 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:410-424 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:424-438 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:151 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:151-191 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:152-192 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:149-183 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:152-192 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:155-192 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:193 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:193-204 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:185-196 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1825 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1825-1862 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1805-1842 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1812-1849 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:324-351 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2114-2151 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2151 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2151-2157 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2131-2137 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2138-2144 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:571-577 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2471-2477 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2196 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2196-2202 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2176-2182 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1927-1933 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2183-2189 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2516-2522 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2224 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2224-2241 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2204-2214 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2211-2221 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:616-633 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2544-2561 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2340 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2340-2352 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2313-2325 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2320-2332 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:698-710 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2661-2673 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2719 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2719-2755 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2691-2727 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2619-2655 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:899-935 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2946-2982 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2779 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2779-2788 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2751-2762 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2679-2690 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:991-1000 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3012-3023 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2797 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2797-2811 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2773-2789 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2701-2717 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1009-1023 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3034-3050 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2813 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2813-2836 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2791-2816 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2719-2744 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1025-1048 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3052-3077 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2862 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2862-2881 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2846-2864 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1343-1380 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2774-2792 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3165-3184 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2883 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2883-2899 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2866-2884 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1877-1893 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2794-2812 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3186-3204 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2921 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2921-2933 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2906-2918 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1761-1773 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2834-2846 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3151-3163 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
+ 9 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×34

Duplicated block (9 lines × 2) flutter_inappwebview_windows/lib/src/cookie_manager.dart:229 — flutter_inappwebview_windows/lib/src/cookie_manager.dart:229-237 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:252-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:70 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:70-78 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:68-76 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:58 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:58-66 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:56-64 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:596 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:596-604 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:610-618 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:596` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:104 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:104-112 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java:104-112 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ISettings.swift:20 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ISettings.swift:20-28 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ISettings.swift:20-28 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ISettings.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ISettings.swift` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ISettings.swift:20` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:622 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:622-630 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:300-308 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:609 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:609-617 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:215-223 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:609` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:881 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:881-889 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:414-422 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:881` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3351 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3351-3359 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3365-3373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3351` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:578 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:578-586 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:566-574 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:578` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:639 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:639-647 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:625-633 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:639` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:656 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:656-664 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:642-650 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:656` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:714 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:714-722 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:687-695 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:754 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:754-762 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:719-727 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:126 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:126-134 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:126-134 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CustomSchemeResponse.swift:22 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CustomSchemeResponse.swift:22-30 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/CustomSchemeResponse.swift:22-30 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CustomSchemeResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/CustomSchemeResponse.swift` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift:19-27 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsPromptResponse.swift:19-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsPromptResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/Size2D.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/Size2D.swift:19-27 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/Size2D.swift:19-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/Size2D.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/Size2D.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:12-20 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/NSColor.swift:12-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UIColor.swift:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceResponse.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceResponse.swift:19-27 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebResourceResponse.swift:19-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebResourceResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertChallenge.swift:13 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertChallenge.swift:13-21 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ClientCertChallenge.swift:13-21 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ClientCertChallenge.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ClientCertChallenge.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustChallenge.swift:13 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustChallenge.swift:13-21 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ServerTrustChallenge.swift:13-21 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustChallenge.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ServerTrustChallenge.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:58 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:58-66 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:58-66 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3383 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3383-3391 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2665-2673 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 9 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×33

Duplicated block (11 lines × 2) dev_packages/generators/lib/src/supported_platforms_generator.dart:188 — dev_packages/generators/lib/src/supported_platforms_generator.dart:188-198 | dev_packages/generators/lib/src/supported_platforms_generator.dart:274-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2871 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2871-2881 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3174-3184 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 119 separate duplicated blocks between them, totalling at least 2751 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2854 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2854-2864 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2782-2792 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:3285 — flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:3285-3295 | flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:3728-3738 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:283 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:283-293 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/TrustedWebActivity.java:47-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:65 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:65-75 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:83-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:94` calls `cancel` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobController.java:76` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:437 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:437-447 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:448-458 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:437` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:628 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:628-638 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:654-664 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:628` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:794 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:794-804 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:820-830 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:101 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:101-111 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:90-100 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:846 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:846-856 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:379-389 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:846` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1436 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1436-1446 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:805-815 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1436` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:27 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:27-37 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift:27-37 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:70 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:70-80 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:70-80 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:127 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:127-137 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:127-137 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:175 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:175-185 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:175-185 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1119 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1119-1129 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1072-1082 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1227 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1227-1237 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1180-1190 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) REDACTED:23 — REDACTED:23-33 | REDACTED:23-33 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/DownloadStartRequest.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/DownloadStartRequest.swift:19-29 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/DownloadStartRequest.swift:19-29 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/DownloadStartRequest.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/DownloadStartRequest.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsConfirmResponse.swift:25 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsConfirmResponse.swift:25-35 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsConfirmResponse.swift:25-35 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsConfirmResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsConfirmResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift:16 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift:16-26 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessage.swift:16-26 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessage.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:26 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:26-36 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionManager.swift:26-36 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:52 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:52-62 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionManager.swift:52-62 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:52` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustAuthResponse.swift:13 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustAuthResponse.swift:13-23 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ServerTrustAuthResponse.swift:13-23 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ServerTrustAuthResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ServerTrustAuthResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 8 more in this group — see findings.md.

X3 · Exception handling · Swallowed exception (empty catch) · ×33

Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:716 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:690 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1630 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:207 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:213 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageChannel.java:156 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1848 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2238 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2267 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:160 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:166 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1828 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1338 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1835 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1545 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:160 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:166 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_public_key.dart:41 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_extension.dart:32 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_extension.dart:46 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_extension.dart:57 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 8 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×32

Duplicated block (8 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2847 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2847-2854 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1059-1066 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 58 separate duplicated blocks between them, totalling at least 765 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2838 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2838-2845 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1050-1057 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 58 separate duplicated blocks between them, totalling at least 765 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/SslCertificateExt.java:28 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/SslCertificateExt.java:28-35 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/SslCertificateExt.java:38-45 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1265 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1265-1272 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1328-1335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717-724 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1322-1329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:584 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:584-591 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:595-602 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:197 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:197-204 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:196-203 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:206 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:206-213 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:205-212 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:782 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:782-789 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:808-815 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1874 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1874-1881 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1163-1170 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3064 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3064-3071 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2275-2282 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3064` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3104 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3104-3111 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2315-2322 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3476 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3476-3483 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2745-2752 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:55 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:55-62 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:55-62 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1101 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1101-1108 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1054-1061 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:33 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:33-40 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift:32-39 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PlatformUtil.swift` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PlatformUtil.swift:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:75 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:75-82 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:75-82 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift:26 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift:26-33 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthenticationChallenge.swift:26-33 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthenticationChallenge.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:23-30 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:35-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:26 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:26-33 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:44-51 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:26` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionResponse.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionResponse.swift:19-26 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PermissionResponse.swift:19-26 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PermissionResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:121 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:121-128 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:121-128 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:190 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:190-197 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:119-126 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/LeakAvoider.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/LeakAvoider.swift:14-21 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/LeakAvoider.swift:14-21 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/LeakAvoider.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/LeakAvoider.swift` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1002 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1002-1009 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:537-544 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 7 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×30

Duplicated block (13 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:191 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:191-203 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:121-133 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_android/lib/src/cookie_manager.dart:110 — flutter_inappwebview_android/lib/src/cookie_manager.dart:110-122 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:130-142 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2635 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2635-2647 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2607-2619 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_linux/lib/src/http_auth_credentials_database.dart:127 — flutter_inappwebview_linux/lib/src/http_auth_credentials_database.dart:127-139 | flutter_inappwebview_linux/lib/src/http_auth_credentials_database.dart:143-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:676 — flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:676-688 | flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:913-925 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:282 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:282-294 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:283-295 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:494 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:494-506 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:505-517 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:494` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:568 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:568-580 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:579-591 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:568` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:767 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:767-779 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:793-805 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:767` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:858 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:858-870 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:391-403 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:940 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:940-952 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:475-487 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1740 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1740-1752 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1074-1086 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1740` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2342 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2342-2354 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1620-1632 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2342` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3182 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3182-3194 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2394-2406 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:844 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:844-856 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:797-809 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:63 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:63-75 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift:61-73 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:175 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:175-187 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:104-116 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionSettings.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionSettings.swift:12-24 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionSettings.swift:12-24 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionSettings.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionSettings.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobManager.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobManager.swift:14-26 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PrintJob/PrintJobManager.swift:14-26 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PrintJob/PrintJobManager.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionRequest.swift:16 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionRequest.swift:16-28 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PermissionRequest.swift:16-28 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PermissionRequest.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PermissionRequest.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslCertificate.swift:17 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslCertificate.swift:17-29 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/SslCertificate.swift:17-29 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslCertificate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/SslCertificate.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:437 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:437-449 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:453-465 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:584 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:584-596 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:972-984 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:598 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:598-610 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:517-529 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:885 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:885-897 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:946-958 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 5 more in this group — see findings.md.

D3 · God Classes · TooManyMethods · ×29

TooManyMethods: PlatformInAppWebViewController flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:68 — TooManyMethods — 162 methods. The bar is 30 methods; this is 132 over it, 5.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebViewController flutter_inappwebview/lib/src/in_app_webview/in_app_webview_controller.dart:12 — TooManyMethods — 159 methods. The bar is 30 methods; this is 129 over it, 5.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppBrowser flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart:16 — TooManyMethods — 129 methods. The bar is 30 methods; this is 99 over it, 4.30× the bar. Most of these members implement src.PlatformInAppBrowserEvents (96 of 129 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: AndroidInAppWebViewController flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:45 — TooManyMethods — 122 methods. The bar is 30 methods; this is 92 over it, 4.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowsInAppWebViewController flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:47 — TooManyMethods — 119 methods. The bar is 30 methods; this is 89 over it, 3.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IOSInAppWebViewController flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:47 — TooManyMethods — 116 methods. The bar is 30 methods; this is 86 over it, 3.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebView flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:12 — TooManyMethods — 115 methods. The bar is 30 methods; this is 85 over it, 3.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LinuxInAppWebViewController flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:43 — TooManyMethods — 107 methods. The bar is 30 methods; this is 77 over it, 3.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MacOSInAppWebViewController flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:46 — TooManyMethods — 107 methods. The bar is 30 methods; this is 77 over it, 3.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PlatformInAppBrowserEvents flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart:736 — TooManyMethods — 96 methods. The bar is 30 methods; this is 66 over it, 3.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebView flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:12 — TooManyMethods — 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebView flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:119 — TooManyMethods — 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebPlatformInAppWebViewController flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:41 — TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebViewPlatform flutter_inappwebview_platform_interface/lib/src/inappwebview_platform.dart:43 — TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AndroidInAppWebViewPlatform flutter_inappwebview_android/lib/src/inappwebview_platform.dart:20 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppWebViewChromeClient flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:74 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebViewChannelDelegate flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:69 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IOSInAppWebViewPlatform flutter_inappwebview_ios/lib/src/inappwebview_platform.dart:16 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MacOSInAppWebViewPlatform flutter_inappwebview_macos/lib/src/inappwebview_platform.dart:14 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LinuxInAppWebViewPlatform flutter_inappwebview_linux/lib/src/inappwebview_platform.dart:18 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowsInAppWebViewPlatform flutter_inappwebview_windows/lib/src/inappwebview_platform.dart:16 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebViewChannelDelegate flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:12 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebViewChannelDelegate flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:12 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ChromeSafariBrowser flutter_inappwebview/lib/src/chrome_safari_browser/chrome_safari_browser.dart:8 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UserContentController flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/UserContentController.java:29 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
+ 4 more in this group — see findings.md.

D3 · God Classes · ClassTooLong · ×27

ClassTooLong: WindowsInAppWebViewController flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:47 — ClassTooLong — 2624 significant lines (blank, comment-only and punctuation-only lines excluded), 119 methods. The bar is 400 significant lines; this is 2224 over it, 6.56× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AndroidInAppWebViewController flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:45 — ClassTooLong — 2400 significant lines (blank, comment-only and punctuation-only lines excluded), 122 methods. The bar is 400 significant lines; this is 2000 over it, 6.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: IOSInAppWebViewController flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:47 — ClassTooLong — 2358 significant lines (blank, comment-only and punctuation-only lines excluded), 116 methods. The bar is 400 significant lines; this is 1958 over it, 5.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MacOSInAppWebViewController flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:46 — ClassTooLong — 2298 significant lines (blank, comment-only and punctuation-only lines excluded), 107 methods. The bar is 400 significant lines; this is 1898 over it, 5.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PlatformInAppWebViewController flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:68 — ClassTooLong — 2284 significant lines (blank, comment-only and punctuation-only lines excluded), 162 methods. The bar is 400 significant lines; this is 1884 over it, 5.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebView flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:12 — ClassTooLong — 2274 significant lines (blank, comment-only and punctuation-only lines excluded), 115 methods. The bar is 400 significant lines; this is 1874 over it, 5.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebViewSettings_ flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:49 — ClassTooLong — 1867 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 1467 over it, 4.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebView flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:12 — ClassTooLong — 1833 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods. The bar is 400 significant lines; this is 1433 over it, 4.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LinuxInAppWebViewController flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:43 — ClassTooLong — 1735 significant lines (blank, comment-only and punctuation-only lines excluded), 107 methods. The bar is 400 significant lines; this is 1335 over it, 4.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PlatformWebViewCreationParams flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_webview.dart:24 — ClassTooLong — 1531 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 1131 over it, 3.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebViewChannelDelegate flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:69 — ClassTooLong — 1031 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 631 over it, 2.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebResourceErrorType_ flutter_inappwebview_platform_interface/lib/src/types/web_resource_error_type.dart:6 — ClassTooLong — 1004 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 604 over it, 2.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PlatformInAppBrowserEvents flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart:736 — ClassTooLong — 996 significant lines (blank, comment-only and punctuation-only lines excluded), 96 methods. The bar is 400 significant lines; this is 596 over it, 2.49× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebViewChannelDelegate flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:12 — ClassTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 501 over it, 2.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebViewChromeClient flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:74 — ClassTooLong — 884 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 484 over it, 2.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExchangeableObjectGenerator dev_packages/generators/lib/src/exchangeable_object_generator.dart:43 — ClassTooLong — 877 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 477 over it, 2.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebViewChannelDelegate flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:12 — ClassTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 472 over it, 2.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HeadlessInAppWebView flutter_inappwebview/lib/src/in_app_webview/headless_in_app_webview.dart:12 — ClassTooLong — 869 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 469 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebView flutter_inappwebview/lib/src/in_app_webview/in_app_webview.dart:18 — ClassTooLong — 862 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 462 over it, 2.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebPlatformInAppWebViewController flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:41 — ClassTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 372 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebViewSettings flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java:28 — ClassTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 269 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebViewClientCompat flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:59 — ClassTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 135 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppWebViewClient flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:60 — ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 113 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppBrowser flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart:16 — ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 129 methods. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InAppBrowserWebViewController flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:13 — ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 34 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
+ 2 more in this group — see findings.md.

D3 · God Classes · FileTooLong · ×27

FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 2653 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: WindowsInAppWebViewController (51-3502). The bar is 500 significant lines; this is 2153 over it, 5.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 2427 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: AndroidInAppWebViewController (49-3227). The bar is 500 significant lines; this is 1927 over it, 4.85× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 2385 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: IOSInAppWebViewController (51-3178). The bar is 500 significant lines; this is 1885 over it, 4.77× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/platform_inappwebview_controller.dart flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart — FileTooLong — 2340 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: PlatformInAppWebViewController (86-4745). The bar is 500 significant lines; this is 1840 over it, 4.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 2326 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: MacOSInAppWebViewController (50-3093). The bar is 500 significant lines; this is 1826 over it, 4.65× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: InAppWebView/InAppWebView.swift flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift — FileTooLong — 2277 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: InAppWebView (12-3596). The bar is 500 significant lines; this is 1777 over it, 4.55× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_settings.dart flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart — FileTooLong — 2107 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: InAppWebViewSettings_ (62-3518). The bar is 500 significant lines; this is 1607 over it, 4.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: InAppWebView/InAppWebView.swift flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift — FileTooLong — 1836 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: InAppWebView (12-2851). The bar is 500 significant lines; this is 1336 over it, 3.67× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 1762 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: LinuxInAppWebViewController (47-2358). The bar is 500 significant lines; this is 1262 over it, 3.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/platform_webview.dart flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_webview.dart — FileTooLong — 1559 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: PlatformWebViewCreationParams (41-2783). The bar is 500 significant lines; this is 1059 over it, 3.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/InAppWebView.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java — FileTooLong — 1551 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1051 over it, 3.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: in_app_browser/platform_in_app_browser.dart flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart — FileTooLong — 1340 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: PlatformInAppBrowserEvents (745-2470). The bar is 500 significant lines; this is 840 over it, 2.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: webview/WebViewChannelDelegate.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java — FileTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: WebViewChannelDelegate (69-1387). The bar is 500 significant lines; this is 593 over it, 2.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: types/web_resource_error_type.dart flutter_inappwebview_platform_interface/lib/src/types/web_resource_error_type.dart — FileTooLong — 1008 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: WebResourceErrorType_ (8-1505). The bar is 500 significant lines; this is 508 over it, 2.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/InAppWebViewChromeClient.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java — FileTooLong — 950 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: InAppWebViewChromeClient (74-1384). The bar is 500 significant lines; this is 450 over it, 1.90× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/exchangeable_object_generator.dart dev_packages/generators/lib/src/exchangeable_object_generator.dart — FileTooLong — 908 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ExchangeableObjectGenerator (43-1185). The bar is 500 significant lines; this is 408 over it, 1.82× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: InAppWebView/WebViewChannelDelegate.swift flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: WebViewChannelDelegate (12-1248). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview.dart flutter_inappwebview/lib/src/in_app_webview/in_app_webview.dart — FileTooLong — 884 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: InAppWebView (21-911). The bar is 500 significant lines; this is 384 over it, 1.77× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/headless_in_app_webview.dart flutter_inappwebview/lib/src/in_app_webview/headless_in_app_webview.dart — FileTooLong — 877 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: HeadlessInAppWebView (15-944). The bar is 500 significant lines; this is 377 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: InAppWebView/WebViewChannelDelegate.swift flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift — FileTooLong — 875 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: WebViewChannelDelegate (12-1211). The bar is 500 significant lines; this is 375 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/in_app_webview_controller.dart flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: WebPlatformInAppWebViewController (45-1133). The bar is 500 significant lines; this is 295 over it, 1.59× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/InAppWebViewSettings.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java — FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: InAppWebViewSettings (28-741). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: web_storage/platform_web_storage.dart flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart — FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: in_app_webview/InAppWebViewClientCompat.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java — FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: InAppWebViewClientCompat (59-848). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: in_app_webview/InAppWebViewClient.java flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java — FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: InAppWebViewClient (60-822). The bar is 500 significant lines; this is 67 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
+ 2 more in this group — see findings.md.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×26

Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/cookie_manager.dart:147 — flutter_inappwebview_android/lib/src/cookie_manager.dart:147-181 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:293-340 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:293-340 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:172-211 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:79 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:79-97 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:78-96 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:78-96 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:68-86 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2320 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2320-2330 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2293-2303 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1852-1862 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2300-2310 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2378 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2378-2386 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2351-2359 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2358-2366 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2699-2707 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2395 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2395-2401 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2368-2374 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2375-2381 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2716-2722 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2403 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2403-2409 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2376-2382 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2383-2389 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2724-2730 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2468 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2468-2484 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2441-2457 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2448-2464 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2789-2805 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:79 — flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:79-87 | flutter_inappwebview_ios/lib/src/print_job/print_job_controller.dart:75-83 | flutter_inappwebview_macos/lib/src/print_job/print_job_controller.dart:68-76 | flutter_inappwebview_windows/lib/src/print_job/print_job_controller.dart:59-67 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3054 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3054-3061 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2209-2216 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2982-2989 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3316-3323 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:158 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:158-207 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:291-325 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:371-398 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:400-427 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:178 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:178-186 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:737-745 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:774-783 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1200-1208 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:57 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:57-88 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:119-148 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:640-727 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:666-753 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:933 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:933-942 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1172-1181 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1288-1297 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1307-1316 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:223 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:223-266 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:309-354 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:409-458 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:530-575 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:268 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:268-305 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:356-405 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:460-526 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:577-626 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1479 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1479-1508 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1510-1542 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:836-865 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:867-899 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3449 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3449-3474 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:58-97 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2718-2743 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:58-97 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19-85 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20-712 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19-85 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:20-685 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:792 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:792-803 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:818-829 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:753-764 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:775-786 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146-187 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:189-221 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:144-185 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:187-219 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:223 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:223-250 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:252-282 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:221-244 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:246-272 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:23-32 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift:23-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift:23-32 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsAlertResponse.swift:23-32 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2591 — flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2591-2599 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2601-2609 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2761-2769 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2771-2779 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:597 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:597-637 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:351-372 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:374-409 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:431-470 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:966 — flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:966-988 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:759-781 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:493-515 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:1246-1264 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
+ 1 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×22

Duplicated block (14 lines × 2) flutter_inappwebview_android/lib/src/cookie_manager.dart:204 — flutter_inappwebview_android/lib/src/cookie_manager.dart:204-217 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:239-252 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:97 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:97-110 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:99-112 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_certificate.dart:166 — flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_certificate.dart:166-179 | flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_certificate.dart:210-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:264 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:264-277 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:263-276 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:112 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:112-125 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:111-124 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:136 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:136-149 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionChannelDelegate.swift:89-102 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionChannelDelegate.swift` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:395 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:395-408 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:79-92 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1635 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1635-1648 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:969-982 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1885 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1885-1898 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1174-1187 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1901 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1901-1914 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1190-1203 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3449 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3449-3462 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2718-2731 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3449` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:119 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:119-132 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift:114-127 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:32 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:32-45 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift:32-45 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift:29 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift:29-42 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsPromptResponse.swift:29-42 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsPromptResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsPromptResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:85 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:85-98 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift:85-98 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ChannelDelegate.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ChannelDelegate.swift:14-27 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ChannelDelegate.swift:14-27 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/ChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/ChannelDelegate.swift` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CreateWindowAction.swift:17 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CreateWindowAction.swift:17-30 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/CreateWindowAction.swift:17-30 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/CreateWindowAction.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/CreateWindowAction.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:569 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:569-582 | flutter_inappwebview/example/lib/screens/webview_tester_screen.dart:73-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:160 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:160-173 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:174-187 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:879 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:879-892 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1151-1164 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:308 — flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:308-321 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:753-766 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:583 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:583-596 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:485-498 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×21

Duplicated block (12 lines × 2) flutter_inappwebview_android/lib/src/cookie_manager.dart:147 — flutter_inappwebview_android/lib/src/cookie_manager.dart:147-158 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:172-183 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:68 — flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:68-79 | flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart:66-77 — before extracting anything, compare `flutter_inappwebview_android/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` and `flutter_inappwebview_ios/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:97 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:97-108 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:114-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:97` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:828 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:828-839 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:362-373 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:828` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:840` calls `replaceGestureHandlerIfNeeded` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:374` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1108 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1108-1119 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:583-594 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1122 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1122-1133 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:597-608 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1448 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1448-1459 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:817-828 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1448` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1649 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1649-1660 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:983-994 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1649` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3436 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3436-3447 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2705-2716 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3463 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3463-3474 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2732-2743 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3463` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32-43 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:32-43 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139-150 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:139-150 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JavaScriptHandlerFunctionData.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JavaScriptHandlerFunctionData.swift:23-34 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JavaScriptHandlerFunctionData.swift:23-34 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JavaScriptHandlerFunctionData.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JavaScriptHandlerFunctionData.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WindowIdJS.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WindowIdJS.swift:14-25 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/WindowIdJS.swift:14-25 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WindowIdJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/WindowIdJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebView.swift:68 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebView.swift:68-79 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebView.swift:67-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:203 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:203-214 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:710-721 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:567 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:567-578 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:694-705 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:449 — flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:449-460 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:473-484 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:286 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:286-297 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:152-163 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:654 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:654-665 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:588-599 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) flutter_inappwebview/example/lib/widgets/webview/javascript_console_widget.dart:96 — flutter_inappwebview/example/lib/widgets/webview/javascript_console_widget.dart:96-107 | flutter_inappwebview/example/lib/widgets/webview/user_script_tester_widget.dart:80-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×20

Duplicated block (15 lines × 2) flutter_inappwebview_android/lib/src/cookie_manager.dart:184 — flutter_inappwebview_android/lib/src/cookie_manager.dart:184-198 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:214-228 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2619 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2619-2633 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2591-2605 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2883 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2883-2897 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1877-1891 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 77 separate duplicated blocks between them, totalling at least 1350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1001 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1001-1015 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1044-1058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1001` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1016` calls `getFileChooserIntent`, `createChooser` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1059` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:70 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:70-84 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:70-84 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:26 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:26-40 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:26-40 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:42 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:42-56 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift:42-56 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessInAppWebViewManager.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:145 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:145-159 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:134-148 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:667 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:667-681 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:653-667 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:667` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:47 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:47-61 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift:45-59 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift:12-26 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift:12-26 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/CallAsyncJavaScriptBelowIOS14WrapperJS.swift:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:143 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:143-157 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:143-157 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift:35 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift:35-49 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessage.swift:35-49 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessage.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessage.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:624 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:624-638 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:651-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:695 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:695-709 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1089-1103 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:726 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:726-740 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1122-1136 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:971 — flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:971-985 | flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart:367-381 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:591 — flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:591-605 | flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:608-622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/widgets/webview/event_console_widget.dart:94 — flutter_inappwebview/example/lib/widgets/webview/event_console_widget.dart:94-108 | flutter_inappwebview/example/lib/widgets/webview/network_monitor_widget.dart:68-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1546 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1546-1560 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:766-780 — before extracting anything, compare `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` and `flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×16

Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:314 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:314-325 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:312-323 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:313-324 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:305-316 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:306-317 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:332-343 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:422 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:422-431 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:416-425 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:420-429 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:409-418 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:400-409 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:443-452 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:447 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:447-462 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:441-456 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:448-462 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:434-449 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:425-440 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:468-483 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206-1804 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:207-1784 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198-1199 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:207-1791 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:112-309 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207-2070 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2024 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2024-2069 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2004-2049 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2097-2142 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2011-2056 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:444-489 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2344-2389 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2071 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2071-2096 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2051-2076 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1214-1230 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2058-2083 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:491-516 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2391-2416 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2362 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2362-2376 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2335-2349 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1589-1601 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2342-2356 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:720-734 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2683-2697 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2649 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2649-2717 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2621-2689 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2218-2286 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2549-2617 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:829-897 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2876-2944 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3170 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3170-3179 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3121-3130 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1468-1477 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3036-3045 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1074-1083 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3444-3453 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:98 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:100-109 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:98-107 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:109 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:111-129 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:109-127 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:139 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:141-175 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:139-173 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:114 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:114-179 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:101-143 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1031-1422 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:88-135 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:90-132 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:559-791 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:184 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:184-197 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:172-185 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:691-704 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:524-537 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:638-651 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:514-527 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:562 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:562-596 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:768-818 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:723-771 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:539-592 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:689-730 | flutter_inappwebview/example/lib/screens/webview_tester_screen.dart:65-100 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) flutter_inappwebview_android/example/lib/main.dart:54 — flutter_inappwebview_android/example/lib/main.dart:54-188 | flutter_inappwebview_ios/example/lib/main.dart:52-182 | flutter_inappwebview_linux/example/lib/main.dart:274-386 | flutter_inappwebview_macos/example/lib/main.dart:32-157 | flutter_inappwebview_web/example/lib/main.dart:31-145 | flutter_inappwebview_windows/example/lib/main.dart:259-653 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.

D15 · Churn × Complexity Hotspots · Hotspot · ×12

Hotspot: flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207 — flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 514 in WindowsInAppWebViewController._handleMethod at line 207. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198 — flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 303 in LinuxInAppWebViewController._handleMethod at line 198. 2 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/providers/test_runner.dart flutter_inappwebview/example/lib/providers/test_runner.dart:337 — flutter_inappwebview/example/lib/providers/test_runner.dart changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in TestRunner._executeCustomStep at line 337. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/providers/test_runner.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:113 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in _MethodTesterWidgetState._buildMethodCategories at line 113. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dev_packages/generators/lib/src/exchangeable_object_generator.dart dev_packages/generators/lib/src/exchangeable_object_generator.dart:45 — dev_packages/generators/lib/src/exchangeable_object_generator.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 176 in ExchangeableObjectGenerator.generateForAnnotatedElement at line 45. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- dev_packages/generators/lib/src/exchangeable_object_generator.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dev_packages/generators/lib/src/exchangeable_enum_generator.dart dev_packages/generators/lib/src/exchangeable_enum_generator.dart:47 — dev_packages/generators/lib/src/exchangeable_enum_generator.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in ExchangeableEnumGenerator.generateForAnnotatedElement at line 47. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- dev_packages/generators/lib/src/exchangeable_enum_generator.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:1091 — flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in _CustomTestStepDialogState._buildAction at line 1091. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1264 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in _ServiceControllersScreenState._buildWebViewEnvironmentSection at line 1264. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart:577 — flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in _ParameterDialogState._buildField at line 577. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart:187 — flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ProfileSelectorCard._buildEnvironmentProfileRow at line 187. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:620 — flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in _SupportMatrixScreenState._buildApiRow at line 620. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: flutter_inappwebview_platform_interface/lib/src/content_blocker.dart flutter_inappwebview_platform_interface/lib/src/content_blocker.dart:153 — flutter_inappwebview_platform_interface/lib/src/content_blocker.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ContentBlockerTrigger.toMap at line 153. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-11-12..2026-02-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-12 14:47:56 +01:00' --until='2026-02-10 14:47:56 +01:00' --full-history --no-merges -- flutter_inappwebview_platform_interface/lib/src/content_blocker.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×12

Duplicated block (18 lines × 2) flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:123 — flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:123-140 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:125-142 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:23 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:23-40 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/CustomSchemeHandler.swift:23-40 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/CustomSchemeHandler.swift` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/CustomSchemeHandler.swift:23` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:31 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:31-48 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:25-42 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:807 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:807-824 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:343-360 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:807` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:920 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:920-937 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:455-472 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:440 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:440-457 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:414-431 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:440` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:99 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:99-116 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift:99-116 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:99` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/PrintJS.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/PrintJS.swift:14-31 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/PrintJS.swift:14-31 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/PrintJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/PrintJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) REDACTED:60 — REDACTED:60-77 | REDACTED:60-77 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:138 — flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:138-155 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:208-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:254 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:254-271 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:120-137 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:622 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:622-639 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:653-670 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (7 lines × 5) · ×12

Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2151 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2151-2157 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2131-2137 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2138-2144 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:571-577 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2471-2477 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2196 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2196-2202 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2176-2182 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1927-1933 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2183-2189 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2516-2522 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2782 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2782-2788 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2756-2762 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2684-2690 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:994-1000 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3017-3023 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3149 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3149-3155 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3106-3112 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1489-1495 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3021-3027 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3429-3435 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:58 — flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:58-64 | flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart:58-64 | flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:58-64 | flutter_inappwebview_macos/lib/src/web_message/web_message_port.dart:58-64 | flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart:58-64 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:292 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:292-298 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:291-297 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:301-307 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:290-296 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:301-307 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:300 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:300-306 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:299-305 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:309-315 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:298-304 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:309-315 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:308 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:308-314 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:307-313 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:317-323 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:306-312 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:317-323 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:316 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:316-322 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:315-321 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:325-331 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:314-320 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:325-331 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2262 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2262-2268 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2235-2241 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2242-2248 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:654-660 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2582-2588 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2332 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2332-2338 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2305-2311 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2312-2318 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:690-696 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2653-2659 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2957 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2957-2963 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2942-2948 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1739-1745 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2870-2876 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3129-3135 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×12

Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewFactory.swift:37 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewFactory.swift:37-56 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewFactory.swift:37-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewFactory.swift:37` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1360 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1360-1379 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:740-759 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947-2966 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2158-2177 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:53 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:53-72 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift:53-72 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannel.swift:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:48 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:48-67 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:48-67 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobChannelDelegate.swift:32 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobChannelDelegate.swift:32-51 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PrintJob/PrintJobChannelDelegate.swift:23-42 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PrintJob/PrintJobChannelDelegate.swift` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PrintJob/PrintJobChannelDelegate.swift:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/BaseCallbackResult.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/BaseCallbackResult.swift:12-31 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/BaseCallbackResult.swift:12-31 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/BaseCallbackResult.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/BaseCallbackResult.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserChannelDelegate.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserChannelDelegate.swift:12-31 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserChannelDelegate.swift:12-36 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserChannelDelegate.swift` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowBlurEventJS.swift:15 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowBlurEventJS.swift:15-34 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnWindowBlurEventJS.swift:15-34 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowBlurEventJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnWindowBlurEventJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowFocusEventJS.swift:15 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowFocusEventJS.swift:15-34 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnWindowFocusEventJS.swift:15-34 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnWindowFocusEventJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnWindowFocusEventJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:563 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:563-582 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:951-970 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:81 — flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:81-100 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:166-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×11

Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/cookie_manager.dart:198 — flutter_inappwebview_android/lib/src/cookie_manager.dart:198-202 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:372-376 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:372-376 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/cookie_manager.dart:216 — flutter_inappwebview_android/lib/src/cookie_manager.dart:216-220 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:411-415 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:411-415 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/cookie_manager.dart:222 — flutter_inappwebview_android/lib/src/cookie_manager.dart:222-226 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:417-421 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:417-421 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2593 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2593-2597 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2550-2554 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2543-2547 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3048 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3048-3052 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3076-3080 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1864-1868 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:67 — flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:67-71 | flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:154-158 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:156-160 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/proxy_controller.dart:85 — flutter_inappwebview_android/lib/src/proxy_controller.dart:85-89 | flutter_inappwebview_ios/lib/src/proxy_controller.dart:85-89 | flutter_inappwebview_macos/lib/src/proxy_controller.dart:84-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2985 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2985-2989 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2913-2917 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3247-3251 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2998 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2998-3002 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2926-2930 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3260-3264 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3011 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3011-3015 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2939-2943 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3273-3277 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3071 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3071-3075 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:195-199 | flutter_inappwebview_linux/lib/src/proxy_controller/proxy_controller.dart:81-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×11

Duplicated block (6 lines × 4) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:376 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:376-381 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:188-193 | flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:167-172 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:169-174 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2388 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2388-2393 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2361-2366 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2368-2373 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2709-2714 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2411 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2411-2416 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2384-2389 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2391-2396 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2732-2737 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3039 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3039-3044 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2189-2194 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2967-2972 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3301-3306 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 1329 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:179 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:179-184 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:738-743 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:775-780 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1201-1206 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:781` calls `put` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:185` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:47 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:47-52 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:67-72 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:83-88 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:119-124 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1667 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1667-1672 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1723-1728 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1001-1006 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1057-1062 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1667` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1694 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1694-1699 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1703-1708 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1028-1033 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1037-1042 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1694` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:47 — flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:47-52 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:67-72 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:83-88 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:119-124 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:859 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:859-864 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1219-1224 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:812-817 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1172-1177 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:16 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:16-21 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift:16-21 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift:16-21 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsAlertResponse.swift:16-21 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×9

Duplicated block (22 lines × 2) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:319 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:319-340 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:314-335 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 173 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:68 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:68-89 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionController.swift:38-59 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionController.swift` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2298 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2298-2319 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1576-1597 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19-40 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19-40 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:24 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift:24-45 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift:22-43 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyWebStorageManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyWebStorageManager.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:158 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:158-179 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:158-179 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:206 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:206-227 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:206-227 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:51 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:51-72 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift:51-72 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/UserScript.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/UserScript.swift:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:811 — flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:811-832 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:662-683 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 275 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13 lines × 5) · ×9

Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:433 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:433-445 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:427-439 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:420-432 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:411-423 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:454-466 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:418 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:418-430 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:357-369 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:290-302 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:351-363 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:365-377 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:373 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:373-385 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:374-386 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:439-451 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:381-393 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:419-431 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:486 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:486-498 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:487-499 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:290-302 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:494-506 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:532-544 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1416 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1416-1428 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1417-1429 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:681-693 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1424-1436 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1520-1532 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2277 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2277-2289 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2250-2262 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2257-2269 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:669-681 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2597-2609 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2340 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2340-2352 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2313-2325 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2320-2332 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:698-710 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2661-2673 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2799 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2799-2811 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2777-2789 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2705-2717 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1011-1023 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3038-3050 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2921 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2921-2933 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2906-2918 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1761-1773 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2834-2846 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3151-3163 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 3) · ×9

Duplicated block (6 lines × 3) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:231 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:231-236 | flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:253-258 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:159-164 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) flutter_inappwebview_android/lib/src/cookie_manager.dart:103 — flutter_inappwebview_android/lib/src/cookie_manager.dart:103-108 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:124-129 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:124-129 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) flutter_inappwebview_android/lib/src/proxy_controller.dart:78 — flutter_inappwebview_android/lib/src/proxy_controller.dart:78-83 | flutter_inappwebview_ios/lib/src/proxy_controller.dart:78-83 | flutter_inappwebview_macos/lib/src/proxy_controller.dart:77-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2991 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2991-2996 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2919-2924 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3253-3258 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3004 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3004-3009 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2932-2937 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3266-3271 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3099 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3099-3104 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3014-3019 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3422-3427 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717-722 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:859-864 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1322-1327 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:717` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:19-24 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:28-33 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:46-51 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1664 — flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1664-1669 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1727-1732 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1788-1793 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (5 lines × 4) · ×9

Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/cookie_manager.dart:93 — flutter_inappwebview_android/lib/src/cookie_manager.dart:93-97 | flutter_inappwebview_android/lib/src/cookie_manager.dart:194-198 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:108-112 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:224-228 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:162 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:162-166 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:161-165 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:161-165 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:151-155 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2456 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2456-2460 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2429-2433 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2436-2440 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2777-2781 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2462 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2462-2466 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2435-2439 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2442-2446 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2783-2787 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2539 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2539-2543 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2510-2514 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1534-1538 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2858-2862 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3036 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3036-3040 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3025-3029 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2953-2957 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3287-3291 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2964 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2964-2968 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1269-1273 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2892-2896 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3226-3230 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 1329 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:73 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:73-77 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:88-92 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:105-109 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:122-126 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1700 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1700-1704 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1738-1742 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1034-1038 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1072-1076 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1700` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (5 lines × 6) · ×9

Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1813 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1813-1817 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1793-1797 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1208-1212 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1800-1804 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:318-322 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2079-2083 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2159 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2159-2163 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2139-2143 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1263-1267 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2146-2150 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:579-583 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2479-2483 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2165 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2165-2169 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2145-2149 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1275-1279 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2152-2156 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:585-589 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2485-2489 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2177 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2177-2181 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2157-2161 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1281-1285 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2164-2168 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:591-595 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2497-2501 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2212 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2212-2216 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2192-2196 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1305-1309 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2199-2203 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:604-608 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2532-2536 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2218 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2218-2222 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2198-2202 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1299-1303 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2205-2209 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:610-614 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2538-2542 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2551 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2551-2555 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2522-2526 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1423-1427 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2523-2527 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:823-827 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2870-2874 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2757 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2757-2761 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2729-2733 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1577-1581 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2657-2661 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:937-941 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2984-2988 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2763 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2763-2767 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2735-2739 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1583-1587 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2663-2667 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:943-947 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2990-2994 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (35 lines × 2) · ×8

Duplicated block (35 lines × 2) flutter_inappwebview_ios/lib/src/cookie_manager.dart:378 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:378-412 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:378-412 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:75 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:75-109 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:74-108 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (35 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1916 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1916-1950 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1205-1239 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2689 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2689-2723 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1900-1934 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:19-53 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift:19-53 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListenerChannelDelegate.swift` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:480 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:480-514 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:454-488 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:480` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:85 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:85-119 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:84-118 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:906 — flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:906-940 | flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:943-977 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×8

Duplicated block (21 lines × 2) flutter_inappwebview_android/lib/src/cookie_manager.dart:77 — flutter_inappwebview_android/lib/src/cookie_manager.dart:77-97 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:92-112 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2557 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2557-2577 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2528-2548 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnLoadResourceJS.swift:29 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnLoadResourceJS.swift:29-49 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnLoadResourceJS.swift:29-49 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OnLoadResourceJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OnLoadResourceJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:21 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:21-41 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:21-41 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:54 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:54-74 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift:54-74 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:54` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:27 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:27-47 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:27-47 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:99 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:99-119 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:99-119 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:671 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:671-691 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1065-1085 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×8

Duplicated block (16 lines × 2) dev_packages/generators/lib/src/supported_platforms_generator.dart:168 — dev_packages/generators/lib/src/supported_platforms_generator.dart:168-183 | dev_packages/generators/lib/src/supported_platforms_generator.dart:254-269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:326 — flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:326-341 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:327-342 — before extracting anything, compare `flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:217 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:217-232 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:216-231 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:760 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:760-775 | flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:819-834 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:149 — flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:149-164 | flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:177-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:560 — flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:560-575 | flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:590-605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:768 — flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:768-783 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:815-830 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart:106 — flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart:106-121 | flutter_inappwebview/example/lib/widgets/common/profile_selector_card.dart:196-211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (31 lines × 2) · ×7

Duplicated block (31 lines × 2) flutter_inappwebview_ios/lib/src/cookie_manager.dart:88 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:88-118 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:88-118 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessWebViewChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessWebViewChannelDelegate.swift:19-49 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessWebViewChannelDelegate.swift:19-49 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/HeadlessInAppWebView/HeadlessWebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/HeadlessInAppWebView/HeadlessWebViewChannelDelegate.swift` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2060 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2060-2090 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1340-1370 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2267 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2267-2297 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1545-1575 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WebMessageListenerJS.swift:12 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WebMessageListenerJS.swift:12-42 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/WebMessageListenerJS.swift:12-42 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/WebMessageListenerJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/WebMessageListenerJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:768 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:768-798 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:723-753 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:49 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:49-79 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:65-95 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×7

Duplicated block (17 lines × 2) dev_packages/generators/lib/src/supported_platforms_generator.dart:206 — dev_packages/generators/lib/src/supported_platforms_generator.dart:206-222 | dev_packages/generators/lib/src/supported_platforms_generator.dart:288-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:747 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:747-763 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:773-789 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:747` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserManager.swift:28 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserManager.swift:28-44 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserManager.swift:26-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:704 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:704-720 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:294-310 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:704` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:157 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:157-173 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:157-173 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:157` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) flutter_inappwebview/example/lib/widgets/common/method_card.dart:114 — flutter_inappwebview/example/lib/widgets/common/method_card.dart:114-130 | flutter_inappwebview/example/lib/widgets/common/method_card.dart:220-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart:624 — flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart:624-640 | flutter_inappwebview/example/lib/widgets/common/parameter_dialog.dart:652-668 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13 lines × 3) · ×7

Duplicated block (13 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2579 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2579-2591 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2569-2581 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2529-2541 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:173 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:173-185 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:173-185 | flutter_inappwebview_web/lib/src/cookie_manager.dart:160-172 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:343 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:343-355 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:343-355 | flutter_inappwebview_web/lib/src/cookie_manager.dart:275-287 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) flutter_inappwebview_ios/lib/src/print_job/print_job_controller.dart:54 — flutter_inappwebview_ios/lib/src/print_job/print_job_controller.dart:54-66 | flutter_inappwebview_macos/lib/src/print_job/print_job_controller.dart:54-66 | flutter_inappwebview_windows/lib/src/print_job/print_job_controller.dart:45-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (13 lines × 3) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1072 — flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1072-1084 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1104-1116 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1137-1149 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:293 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:293-305 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:393-405 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:614-626 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:293` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:727 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:727-739 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:1085-1097 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1123-1135 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9 lines × 4) · ×7

Duplicated block (9 lines × 4) flutter_inappwebview_android/lib/src/cookie_manager.dart:151 — flutter_inappwebview_android/lib/src/cookie_manager.dart:151-159 | flutter_inappwebview_android/lib/src/cookie_manager.dart:189-197 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:176-184 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:219-227 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2378 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2378-2386 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2351-2359 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2358-2366 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2699-2707 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2470 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2470-2478 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2443-2451 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2450-2458 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2791-2799 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:79 — flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:79-87 | flutter_inappwebview_ios/lib/src/print_job/print_job_controller.dart:75-83 | flutter_inappwebview_macos/lib/src/print_job/print_job_controller.dart:68-76 | flutter_inappwebview_windows/lib/src/print_job/print_job_controller.dart:59-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (9 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:70 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:70-78 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:130-138 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:666-674 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:692-700 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:934 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:934-942 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1173-1181 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1289-1297 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1308-1316 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `GeolocationPermissionsShowPromptCallback` in one and `FormResubmissionCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1927 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1927-1935 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1972-1980 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1216-1224 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1261-1269 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1927` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `decisionHandler` to `@escaping (WKNavigationActionPolicy) -> Void` in one and `@escaping (WKNavigationResponsePolicy) -> Void` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (6 lines × 5) · ×7

Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:263 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:263-268 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:262-267 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:272-277 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:261-266 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:272-277 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2965 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2965-2970 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2950-2955 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2878-2883 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:955-960 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3212-3217 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2972 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2972-2977 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2957-2962 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2885-2890 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:962-967 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3219-3224 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3157 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3157-3162 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3114-3119 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1461-1466 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3029-3034 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3437-3442 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:66 — flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:66-71 | flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart:66-71 | flutter_inappwebview_linux/lib/src/web_message/web_message_port.dart:66-71 | flutter_inappwebview_macos/lib/src/web_message/web_message_port.dart:66-71 | flutter_inappwebview_windows/lib/src/web_message/web_message_port.dart:66-71 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) flutter_inappwebview_android/lib/src/web_message/web_message_listener.dart:180 — flutter_inappwebview_android/lib/src/web_message/web_message_listener.dart:180-185 | flutter_inappwebview_ios/lib/src/web_message/web_message_listener.dart:179-184 | flutter_inappwebview_linux/lib/src/web_message/web_message_listener.dart:175-180 | flutter_inappwebview_macos/lib/src/web_message/web_message_listener.dart:179-184 | flutter_inappwebview_windows/lib/src/web_message/web_message_listener.dart:176-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (6 lines × 5) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1816 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1816-1821 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1861-1866 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1977-1982 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1150-1155 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1266-1271 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1816` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×7

Duplicated block (19 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/UserContentController.java:201 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/UserContentController.java:201-219 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/UserContentController.java:283-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:50 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:50-68 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:50-68 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:319 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:319-337 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:324-342 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:106 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:106-124 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:106-124 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:229 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:229-247 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:229-247 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:77 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift:77-95 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift:77-95 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/PluginScript.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/PluginScript.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1680 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1680-1698 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:899-917 — before extracting anything, compare `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` and `flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×7

Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/types/sandbox.dart:22 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/types/sandbox.dart:36 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/oid.dart:114 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/key_usage.dart:24 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_identifier.dart:19 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_identifier.dart:97 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_distinguished_names.dart:30 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (25 lines × 2) · ×6

Duplicated block (25 lines × 2) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1583 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1583-1607 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:897-921 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 77 separate duplicated blocks between them, totalling at least 1350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:26 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:26-50 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:63-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:161 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:161-185 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:150-174 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:161` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1672 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1672-1696 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1006-1030 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1672` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) REDACTED:35 — REDACTED:35-59 | REDACTED:35-59 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OriginalViewPortMetaTagContentJS.swift:15 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OriginalViewPortMetaTagContentJS.swift:15-39 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OriginalViewPortMetaTagContentJS.swift:15-39 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/OriginalViewPortMetaTagContentJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/OriginalViewPortMetaTagContentJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10 lines × 5) · ×6

Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:352 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:352-361 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:351-360 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:361-370 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:350-359 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:361-370 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:484 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:484-493 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:419-428 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:352-361 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:413-422 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:427-436 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:433 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:433-442 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:434-443 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:931-940 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:441-450 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:479-488 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:388 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:388-397 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:387-396 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:397-406 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:386-395 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:397-406 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:87 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:87-96 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:87-96 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:87-96 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:87-96 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:87-96 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:185 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:185-194 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:185-194 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:185-194 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:185-194 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:185-194 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×6

Duplicated block (10 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2866 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2866-2875 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2850-2859 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2778-2787 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:47 — flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:47-56 | flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart:47-56 | flutter_inappwebview_macos/lib/src/web_message/web_message_port.dart:47-56 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2829 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2829-2838 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2757-2766 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3090-3099 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2818 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2818-2827 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2746-2755 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3079-3088 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:699 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:699-708 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:939-948 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1093-1102 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) flutter_inappwebview_android/example/lib/main.dart:87 — flutter_inappwebview_android/example/lib/main.dart:87-96 | flutter_inappwebview_ios/example/lib/main.dart:83-92 | flutter_inappwebview_macos/example/lib/main.dart:62-71 — before extracting anything, compare `flutter_inappwebview_android/example/lib/main.dart` and `flutter_inappwebview_ios/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 4) · ×6

Duplicated block (7 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:99 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:99-105 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:98-104 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:98-104 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:88-94 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2395 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2395-2401 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2368-2374 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2375-2381 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2716-2722 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2403 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2403-2409 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2376-2382 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2383-2389 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2724-2730 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2204 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2204-2210 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2184-2190 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2191-2197 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2524-2530 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3454 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3454-3460 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:70-76 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2723-2729 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:70-76 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:68` calls `NSError` and `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3453` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:24 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift:24-30 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/JsAlertResponse.swift:24-30 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift:24-30 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/JsAlertResponse.swift:24-30 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthResponse.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthResponse.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 3) · ×6

Duplicated block (7 lines × 3) flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:73 — flutter_inappwebview_android/lib/src/web_message/web_message_port.dart:73-79 | flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart:73-79 | flutter_inappwebview_macos/lib/src/web_message/web_message_port.dart:73-79 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_message/web_message_port.dart` and `flutter_inappwebview_ios/lib/src/web_message/web_message_port.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3017 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3017-3023 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2945-2951 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3279-3285 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3031 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3031-3037 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2959-2965 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3293-3299 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3046 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3046-3052 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2974-2980 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3308-3314 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:180 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:180-186 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:739-745 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1202-1208 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:85 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:85-91 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:102-108 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:119-125 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×6

Duplicated block (28 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:641 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:641-668 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:667-694 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:641` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:93 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:93-120 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:93-120 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:626 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:626-653 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:232-259 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:626` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:231` calls `addPluginScript`, `ON_SCROLL_CHANGED_EVENT_JS_PLUGIN_SCRIPT` and `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:625` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (28 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1593 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1593-1620 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:932-959 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:39 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:39-66 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift:39-66 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:50 — flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:50-77 | flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:84-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D17 · Explicit Debt · TodoComment · ×5

TodoComment flutter_inappwebview/example/integration_test/chrome_safari_browser/sf_safari_view_controller.dart:26 — // TODO: this test takes a lot of time to complete. Tested on iOS 16.0. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment flutter_inappwebview/example/lib/screens/category_screen.dart:92 — // TODO: Execute test in Phase 3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InputAwareWebView.java:221 — // TODO (ALexVincent525): Currently only prompt has been tested, still needs more test cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:210 — // TODO: remove when Flutter fixes this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2632 — // TODO: remove when Flutter fixes this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×5

Members sharing a duplicated core (10 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:222 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:222-247 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2110-2149 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:221-246 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2090-2129 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:231-256 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:220-245 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2097-2136 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:530-569 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:231-256 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2430-2469 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:334 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:334-350 | flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:363-381 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:333-349 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:362-380 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:343-359 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:372-390 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:332-348 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:361-379 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:343-359 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:372-390 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:78 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:78-108 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:119-149 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:80-109 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:120-150 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:76-106 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:117-147 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:79-109 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:120-150 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:82-112 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:123-153 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2486 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2486-2500 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2502-2516 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2459-2473 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2475-2489 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2466-2480 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2482-2496 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:784-798 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:800-814 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2807-2821 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2823-2837 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:157 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:157-182 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:145-170 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:664-689 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:482-507 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:611-636 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:531-556 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:291-316 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:382-407 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1492-1515 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:657-680 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×5

Duplicated block (26 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:212 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:212-237 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:140-165 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:182 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:182-207 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:300-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:182` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:235 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:235-260 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:234-259 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1517 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1517-1542 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:874-899 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1517` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:89 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:89-114 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:97-122 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23 lines × 2) · ×5

Duplicated block (23 lines × 2) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:294 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:294-316 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:289-311 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 173 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:34 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:34-56 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindTextHighlightJS.swift:34-56 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindTextHighlightJS.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:599 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:599-621 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:548-570 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:123 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:123-145 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:132-154 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:994 — flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:994-1016 | flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:1019-1041 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (17 lines × 5) · ×5

Duplicated block (17 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:124 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:124-140 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:123-139 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:125-141 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:118-134 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:125-141 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:334 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:334-350 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:333-349 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:343-359 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:332-348 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:343-359 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:813 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:813-829 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:814-830 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:477-493 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:821-837 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:875-891 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:851 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:851-867 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:852-868 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:515-531 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:859-875 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:913-929 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2243 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2243-2259 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2216-2232 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2223-2239 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:635-651 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2563-2579 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10 lines × 6) · ×5

Duplicated block (10 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:422 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:422-431 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:416-425 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:420-429 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:409-418 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:400-409 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:443-452 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2087 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2087-2096 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2067-2076 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1221-1230 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2074-2083 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:507-516 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2407-2416 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3170 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3170-3179 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3121-3130 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1468-1477 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3036-3045 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1074-1083 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3444-3453 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:98 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:98-107 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:100-109 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:98-107 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:146 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:146-155 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:134-143 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:192-201 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:80-89 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:162-171 | flutter_inappwebview/example/lib/screens/webview_tester_screen.dart:1454-1463 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9 lines × 5) · ×5

Duplicated block (9 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:324 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:324-332 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:323-331 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:333-341 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:322-330 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:333-341 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206-214 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:207-215 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198-206 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:112-120 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207-215 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:54 — flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:54-62 | flutter_inappwebview_ios/lib/src/find_interaction/find_interaction_controller.dart:54-62 | flutter_inappwebview_linux/lib/src/find_interaction/find_interaction_controller.dart:52-60 | flutter_inappwebview_macos/lib/src/find_interaction/find_interaction_controller.dart:54-62 | flutter_inappwebview_windows/lib/src/find_interaction/find_interaction_controller.dart:54-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (9 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:114 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:114-122 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:113-121 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:115-123 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:108-116 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:115-123 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3061 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3061-3069 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3089-3097 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3004-3012 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1095-1103 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3412-3420 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 4) · ×5

Duplicated block (8 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:120 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:120-127 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:119-126 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:119-126 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:109-116 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:135 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:135-142 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:134-141 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:134-141 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:124-131 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) flutter_inappwebview_ios/lib/src/cookie_manager.dart:111 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:111-118 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:365-372 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:111-118 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:365-372 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3054 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3054-3061 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2209-2216 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2982-2989 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3316-3323 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 1329 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2592 — flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2592-2599 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2602-2609 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2762-2769 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2772-2779 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (6 lines × 6) · ×5

Duplicated block (6 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1806 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1806-1811 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1786-1791 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1201-1206 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1793-1798 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:311-316 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2072-2077 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2189 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2189-2194 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2169-2174 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1920-1925 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2176-2181 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:597-602 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2509-2514 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2270 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2270-2275 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2243-2248 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1396-1401 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2250-2255 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:662-667 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2590-2595 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2354 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2354-2360 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2327-2333 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1603-1608 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2334-2340 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:712-718 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2675-2681 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2532 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2532-2537 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2503-2508 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1775-1780 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2510-2515 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:816-821 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2851-2856 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 5) · ×5

Duplicated block (5 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1819 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1819-1823 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1799-1803 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1311-1315 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1806-1810 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2085-2089 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2171 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2171-2175 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2151-2155 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1287-1291 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2158-2162 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2491-2495 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2183 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2183-2187 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2163-2167 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1293-1297 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2170-2174 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2503-2507 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2292 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2292-2296 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2265-2269 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2272-2276 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:684-688 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2612-2616 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2901 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2901-2905 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2886-2890 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2814-2818 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:949-953 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3206-3210 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 4) · ×4

Duplicated block (18 lines × 4) flutter_inappwebview_android/lib/src/cookie_manager.dart:164 — flutter_inappwebview_android/lib/src/cookie_manager.dart:164-181 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:323-340 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:323-340 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:194-211 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1007 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1007-1024 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1008-1025 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:575-592 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1015-1032 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1016 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1016-1033 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1017-1034 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1024-1041 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1089-1106 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1050 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1050-1067 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1051-1068 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:618-635 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1058-1075 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 5) · ×4

Duplicated block (16 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:188 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:188-203 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:187-202 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:197-212 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:186-201 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:197-212 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:205 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:205-220 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:204-219 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:214-229 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:203-218 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:214-229 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:159 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:159-174 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:160-175 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:157-172 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:160-175 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:163-178 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:446 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:446-461 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:447-462 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:943-958 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:454-469 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:492-507 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×4

Duplicated block (13–14 lines × 2) dev_packages/generators/lib/src/exchangeable_object_generator.dart:837 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:837-850 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:928-940 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–14 lines × 2) flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:818 — flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:818-831 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:756-768 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13–14 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:566 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:566-578 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:467-480 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) flutter_inappwebview/example/lib/widgets/webview/event_console_widget.dart:35 — flutter_inappwebview/example/lib/widgets/webview/event_console_widget.dart:35-47 | flutter_inappwebview/example/lib/widgets/webview/javascript_console_widget.dart:59-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (12 lines × 4) · ×4

Duplicated block (12 lines × 4) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:322 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:322-333 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:250-261 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:317-328 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:333-344 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:255 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:255-266 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:343-354 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:447-458 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:564-575 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1656 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1656-1667 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1138-1149 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:992-1003 | flutter_inappwebview/example/lib/widgets/common/event_log_card.dart:55-67 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:977 — flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:977-988 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:770-781 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:504-515 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:1253-1264 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart` and `flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12 lines × 3) · ×4

Duplicated block (12 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2230 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2230-2241 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:622-633 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2550-2561 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 58 separate duplicated blocks between them, totalling at least 765 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3063 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3063-3074 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2991-3002 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3325-3336 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:352 — flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:352-363 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:413-424 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:427-438 — before extracting anything, compare `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:134 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:134-145 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:670-681 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:696-707 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 5) · ×4

Duplicated block (11 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2098 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2098-2108 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2078-2088 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2085-2095 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:518-528 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2418-2428 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2298 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2298-2308 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2271-2281 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2278-2288 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:969-979 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2618-2628 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:210 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:210-220 | flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:358-368 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:255-265 | flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:74-84 | flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:394-404 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:287 — flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:287-297 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:494-504 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:966-976 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:987-997 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:1026-1036 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (11 lines × 4) · ×4

Duplicated block (11 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:150 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:150-160 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:149-159 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:149-159 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:139-149 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2320 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2320-2330 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2293-2303 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1852-1862 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2300-2310 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45-55 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:518-528 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45-55 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:492-502 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:793 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:793-803 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:819-829 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:754-764 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:776-786 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `JsAlertCallback` in one and `JsConfirmCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (27 lines × 2) · ×4

Duplicated block (27 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:212 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:212-238 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:60-86 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:211` calls `get_JAVASCRIPT_BRIDGE_NAME` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:59` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (27 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:113 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:113-139 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:102-128 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:113` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1754 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1754-1780 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1088-1114 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1991 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1991-2017 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1280-1306 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1991` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D2 · Cognitive Complexity · InAppWebView.injectJavascriptFileFromUrl (cognitive 22) · ×3

InAppWebView.injectJavascriptFileFromUrl (cognitive 22) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1264 — InAppWebView.injectJavascriptFileFromUrl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.injectJavascriptFileFromUrl (cognitive 22) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1666 — InAppWebView.injectJavascriptFileFromUrl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.injectJavascriptFileFromUrl (cognitive 22) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1000 — InAppWebView.injectJavascriptFileFromUrl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.injectCSSFileFromUrl (cognitive 19) · ×3

InAppWebView.injectCSSFileFromUrl (cognitive 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1326 — InAppWebView.injectCSSFileFromUrl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.injectCSSFileFromUrl (cognitive 19) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1721 — InAppWebView.injectCSSFileFromUrl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.injectCSSFileFromUrl (cognitive 19) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1055 — InAppWebView.injectCSSFileFromUrl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Change coupling · ×3

Change coupling: web_support.js ↔ in_app_web_view_web_element.dart flutter_inappwebview_web/lib/assets/web/web_support.js:1 — `flutter_inappwebview_web/lib/assets/web/web_support.js` and `flutter_inappwebview_web/lib/web/in_app_web_view_web_element.dart` change together 80% of the time (12 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `d45532d1` [web] replace iframeId with iframe.id; `1e315f0e` [web] fix web callbacks; `27686054` updated tests (at that commit the files were still `lib/assets/web/web_support.js` and `lib/src/web/in_app_web_view_web_element.dart`) — run `git show` on any of them.
Change coupling: chrome_safari_browser.dart ↔ pull_to_refresh_controller.dart flutter_inappwebview/lib/src/chrome_safari_browser/chrome_safari_browser.dart:1 — `flutter_inappwebview/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a623ee71` Throw an error if any controller is used after being disposed, create… (at that commit the files were still `lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`); `78abd773` updated README, fixed swift Util getUrlAsset and getAbsPathAsset, fix… (at that commit the files were still `lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`); `45c3652b` merged fix(ios): invoke onBrowserCreated when viewDidLoad is called w… (at that commit the files were still `lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`) — run `git show` on any of them.
Change coupling: in_app_webview_controller.dart ↔ pull_to_refresh_controller.dart flutter_inappwebview/lib/src/in_app_webview/in_app_webview_controller.dart:1 — `flutter_inappwebview/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview/lib/src/pull_to_refresh/pull_to_refresh_controller.dart` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a623ee71` Throw an error if any controller is used after being disposed, create… (at that commit the files were still `lib/src/in_app_webview/in_app_webview_controller.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`); `78abd773` updated README, fixed swift Util getUrlAsset and getAbsPathAsset, fix… (at that commit the files were still `lib/src/in_app_webview/in_app_webview_controller.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`); `45c3652b` merged fix(ios): invoke onBrowserCreated when viewDidLoad is called w… (at that commit the files were still `lib/src/in_app_webview/in_app_webview_controller.dart` and `lib/src/pull_to_refresh/pull_to_refresh_controller.dart`) — run `git show` on any of them.

D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×3

Members sharing a duplicated core (8 members, 50+ identical tokens) dev_packages/generators/lib/src/exchangeable_object_generator.dart:972 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:972-993 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:995-1016 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1048-1069 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1071-1092 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1094-1115 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1117-1138 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1140-1161 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1163-1184 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:99 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:99-118 | flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:150-160 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:98-117 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:149-159 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:98-117 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:149-159 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:88-107 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:139-149 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:994 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:994-1011 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1026-1043 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1058-1075 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1171-1188 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:947-964 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:979-996 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1011-1028 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1124-1141 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.

D4 · Code Duplication · Duplicated block (38 lines × 2) · ×3

Duplicated block (38 lines × 2) flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:599 — flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:599-636 | flutter_inappwebview_windows/lib/src/in_app_webview/custom_platform_view.dart:464-501 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (38 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952-1989 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1241-1278 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (38 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionChannelDelegate.swift:19-56 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionChannelDelegate.swift:19-56 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionChannelDelegate.swift` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (37 lines × 2) · ×3

Duplicated block (37 lines × 2) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:230 — flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:230-266 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:313-349 — before extracting anything, compare `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (37 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:516 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:516-552 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:490-526 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:516` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (37 lines × 2) flutter_inappwebview_ios/example/lib/main.dart:84 — flutter_inappwebview_ios/example/lib/main.dart:84-120 | flutter_inappwebview_macos/example/lib/main.dart:63-99 — before extracting anything, compare `flutter_inappwebview_ios/example/lib/main.dart` and `flutter_inappwebview_macos/example/lib/main.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (29 lines × 2) · ×3

Duplicated block (29 lines × 2) flutter_inappwebview_ios/lib/src/cookie_manager.dart:344 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:344-372 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:344-372 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslError.swift:14 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslError.swift:14-42 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/SslError.swift:14-42 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/SslError.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/SslError.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:204 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:204-232 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:249-277 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3

Duplicated block (24 lines × 2) dev_packages/generators/lib/src/util.dart:61 — dev_packages/generators/lib/src/util.dart:61-84 | dev_packages/generators/lib/src/util.dart:147-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:68 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift:68-91 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift:68-91 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebViewManager.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1492 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1492-1515 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:657-680 — before extracting anything, compare `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` and `flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22 lines × 3) · ×3

Duplicated block (22 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:163 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:163-184 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:164-185 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:164-185 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 3) flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:117 — flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:117-138 | flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart:117-138 | flutter_inappwebview_windows/lib/src/web_storage/web_storage_manager.dart:117-138 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart` and `flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:381 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:381-402 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:501-522 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:602-623 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:523` calls `setView` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:403` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (21 lines × 3) · ×3

Duplicated block (21 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3206 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3206-3226 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3157-3177 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3072-3092 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 3) flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:134 — flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:134-154 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:127-147 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:134-154 — before extracting anything, compare `flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 263 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 3) flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:558 — flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:558-578 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:376-396 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:409-429 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart` and `flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×3

Duplicated block (17 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:392 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:392-408 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:392-408 | flutter_inappwebview_web/lib/src/cookie_manager.dart:314-330 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2866 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2866-2882 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2794-2810 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3186-3202 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:228 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:228-244 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:314-330 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:535-551 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:228` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `response` to `JsAlertResponse` in one and `JsConfirmResponse` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (15 lines × 5) · ×3

Duplicated block (15 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1034 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1034-1048 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1035-1049 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:602-616 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1042-1056 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1118-1132 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1056 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1056-1070 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1057-1071 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:624-638 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1064-1078 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1160-1174 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1206 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1206-1220 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1207-1221 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:409-423 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1214-1228 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1310-1324 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14 lines × 5) · ×3

Duplicated block (14 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1013 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1013-1026 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1014-1027 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:581-594 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1021-1034 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1086-1099 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2935 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2935-2948 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2920-2933 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1717-1730 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2848-2861 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3107-3120 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 5) flutter_inappwebview_android/lib/src/web_message/web_message_channel.dart:105 — flutter_inappwebview_android/lib/src/web_message/web_message_channel.dart:105-118 | flutter_inappwebview_ios/lib/src/web_message/web_message_channel.dart:97-110 | flutter_inappwebview_linux/lib/src/web_message/web_message_channel.dart:97-110 | flutter_inappwebview_macos/lib/src/web_message/web_message_channel.dart:97-110 | flutter_inappwebview_windows/lib/src/web_message/web_message_channel.dart:106-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.

D4 · Code Duplication · Duplicated block (13 lines × 6) · ×3

Duplicated block (13 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:347 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:347-359 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:345-357 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:343-355 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:338-350 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:339-351 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:365-377 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:447 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:447-459 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:441-453 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:448-460 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:434-446 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:425-437 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:468-480 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2057 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2057-2069 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2037-2049 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2130-2142 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2044-2056 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:477-489 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2377-2389 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13 lines × 4) · ×3

Duplicated block (13 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:106 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:106-118 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:105-117 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:105-117 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:95-107 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:481 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:481-493 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:416-428 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:410-422 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:424-436 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1633 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1633-1645 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1115-1127 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:856-868 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:969-981 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12 lines × 6) · ×3

Duplicated block (12 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:314 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:314-325 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:312-323 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:313-324 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:305-316 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:306-317 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:332-343 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1608 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1608-1619 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1588-1599 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:957-968 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1595-1606 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:265-276 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1832-1843 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 6) flutter_inappwebview_ios/lib/src/cookie_manager.dart:247 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:247-258 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:277-288 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:247-258 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:277-288 | flutter_inappwebview_web/lib/src/cookie_manager.dart:205-216 | flutter_inappwebview_web/lib/src/cookie_manager.dart:235-246 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12 lines × 5) · ×3

Duplicated block (12 lines × 5) flutter_inappwebview_android/lib/src/cookie_manager.dart:183 — flutter_inappwebview_android/lib/src/cookie_manager.dart:183-194 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:342-353 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:342-353 | flutter_inappwebview_web/lib/src/cookie_manager.dart:274-285 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:213-224 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:193 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:193-204 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:185-196 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:194-205 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 5) flutter_inappwebview_android/lib/src/platform_util.dart:17 — flutter_inappwebview_android/lib/src/platform_util.dart:17-28 | flutter_inappwebview_ios/lib/src/platform_util.dart:17-28 | flutter_inappwebview_macos/lib/src/platform_util.dart:17-28 | flutter_inappwebview_web/lib/src/platform_util.dart:17-28 | flutter_inappwebview_windows/lib/src/platform_util.dart:27-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.

D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3

Duplicated block (11 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2491 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2491-2501 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2498-2508 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2839-2849 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:64 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:64-74 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:660-670 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:686-696 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerManager.java:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) flutter_inappwebview/example/lib/models/environment_setting_definition.dart:35 — flutter_inappwebview/example/lib/models/environment_setting_definition.dart:35-45 | flutter_inappwebview/example/lib/models/setting_definition.dart:30-40 | flutter_inappwebview/example/lib/widgets/test_automation/custom_test_step_dialog.dart:858-868 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

D4 · Code Duplication · Duplicated block (10 lines × 4) · ×3

Duplicated block (10 lines × 4) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:292 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:292-301 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:228-237 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:287-296 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:311-320 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart` and `flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:189 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:189-198 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:307-316 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:380-389 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:409-418 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:189` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:225 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:225-234 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:255-264 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:223-232 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:249-258 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:236` calls `host` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:233` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3

Duplicated block (9 lines × 3) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2769 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2769-2777 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2741-2749 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2669-2677 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:828 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:828-836 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:849-857 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1004-1012 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:828` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `JsAlertCallback` in one and `JsConfirmCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:891 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:891-899 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1154-1162 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1348-1356 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:891` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `JsBeforeUnloadCallback` in one and `SafeBrowsingHitCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (8 lines × 5) · ×3

Duplicated block (8 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:249 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:249-256 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:248-255 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:258-265 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:247-254 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:258-265 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2224 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2224-2231 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2204-2211 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2211-2218 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:616-623 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2544-2551 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2862 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2862-2869 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2846-2853 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1343-1350 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2774-2781 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3165-3172 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (40 lines × 2) · ×3

Duplicated block (40 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:155 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:155-194 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:154-193 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (40 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:451 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:451-490 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:462-501 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:451` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (40 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:58 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:58-97 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:58-97 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (36 lines × 2) · ×3

Duplicated block (36 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:309 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:309-344 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:318-353 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:127 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:127-162 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:127-162 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (36 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:955 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:955-990 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:490-525 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (41 lines × 2) · ×3

Duplicated block (41 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3139 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3139-3179 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2351-2391 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45-85 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45-85 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:28 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:28-68 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptFetchRequestJS.swift:28-68 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptFetchRequestJS.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (33 lines × 2) · ×3

Duplicated block (33 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:181 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:181-213 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:142-174 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2231 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2231-2263 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1511-1543 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2231` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1080 — flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1080-1112 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:934-966 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 275 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (30 lines × 2) · ×3

Duplicated block (30 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:404 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:404-433 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:378-407 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/EnableViewportScaleJS.swift:15 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/EnableViewportScaleJS.swift:15-44 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/EnableViewportScaleJS.swift:15-44 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/EnableViewportScaleJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/EnableViewportScaleJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (30 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/SupportZoomJS.swift:15 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/SupportZoomJS.swift:15-44 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/SupportZoomJS.swift:15-44 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/SupportZoomJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/SupportZoomJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×3

Duplicated block (14–15 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:711 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:711-724 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1106-1120 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–15 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:612 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:612-625 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:531-545 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14–15 lines × 2) flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:86 — flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:86-100 | flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:409-422 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D1 · Cyclomatic Complexity · CredentialDatabase.handle (cyclomatic 47) · ×2

CredentialDatabase.handle (cyclomatic 47) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22 — CredentialDatabase.handle has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CredentialDatabase.handle (cyclomatic 47) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:21 — CredentialDatabase.handle has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · WebMessageListener.isOriginAllowed (cyclomatic 37) · ×2

WebMessageListener.isOriginAllowed (cyclomatic 37) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139 — WebMessageListener.isOriginAllowed has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebMessageListener.isOriginAllowed (cyclomatic 37) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:139 — WebMessageListener.isOriginAllowed has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebMessageListener.assertOriginRulesValid (cyclomatic 26) · ×2

WebMessageListener.assertOriginRulesValid (cyclomatic 26) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32 — WebMessageListener.assertOriginRulesValid has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebMessageListener.assertOriginRulesValid (cyclomatic 26) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:32 — WebMessageListener.assertOriginRulesValid has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.webView (cyclomatic 22) · ×2

InAppWebView.webView (cyclomatic 22) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952 — InAppWebView.webView has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InAppWebView.webView (cyclomatic 22) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1241 — InAppWebView.webView has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebMessageChannelChannelDelegate.handle (cyclomatic 19) · ×2

WebMessageChannelChannelDelegate.handle (cyclomatic 19) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — WebMessageChannelChannelDelegate.handle has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
WebMessageChannelChannelDelegate.handle (cyclomatic 19) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — WebMessageChannelChannelDelegate.handle has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · FlutterWebViewController.load (cyclomatic 17) · ×2

FlutterWebViewController.load (cyclomatic 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:145 — FlutterWebViewController.load has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlutterWebViewController.load (cyclomatic 17) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:134 — FlutterWebViewController.load has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · InAppWebView.userContentController (cognitive 149) · ×2

InAppWebView.userContentController (cognitive 149) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947 — InAppWebView.userContentController has cognitive complexity 149 (threshold 15). Drivers by points: if/else 37 (107 pts), boolean chains 21, ternaries 3 (11 pts), match/switch 2 (7 pts), loops 1 (3 pts) (nesting depth added 85). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
InAppWebView.userContentController (cognitive 149) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2158 — InAppWebView.userContentController has cognitive complexity 149 (threshold 15). Drivers by points: if/else 37 (107 pts), boolean chains 21, ternaries 3 (11 pts), match/switch 2 (7 pts), loops 1 (3 pts) (nesting depth added 85). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · CredentialDatabase.handle (cognitive 86) · ×2

CredentialDatabase.handle (cognitive 86) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22 — CredentialDatabase.handle has cognitive complexity 86 (threshold 15). Drivers by points: if/else 14 (38 pts), loops 11 (31 pts), boolean chains 16, match/switch 1 (nesting depth added 44). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CredentialDatabase.handle (cognitive 86) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:21 — CredentialDatabase.handle has cognitive complexity 86 (threshold 15). Drivers by points: if/else 14 (38 pts), loops 11 (31 pts), boolean chains 16, match/switch 1 (nesting depth added 44). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · WebMessageListener.isOriginAllowed (cognitive 60) · ×2

WebMessageListener.isOriginAllowed (cognitive 60) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139 — WebMessageListener.isOriginAllowed has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 22, if/else 7 (17 pts), ternaries 4 (12 pts), error handling 2 (8 pts), loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebMessageListener.isOriginAllowed (cognitive 60) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:139 — WebMessageListener.isOriginAllowed has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 22, if/else 7 (17 pts), ternaries 4 (12 pts), error handling 2 (8 pts), loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebMessageListener.assertOriginRulesValid (cognitive 59) · ×2

WebMessageListener.assertOriginRulesValid (cognitive 59) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32 — WebMessageListener.assertOriginRulesValid has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (48 pts), boolean chains 10, loops 1 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WebMessageListener.assertOriginRulesValid (cognitive 59) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:32 — WebMessageListener.assertOriginRulesValid has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (48 pts), boolean chains 10, loops 1 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WebMessageChannelChannelDelegate.handle (cognitive 38) · ×2

WebMessageChannelChannelDelegate.handle (cognitive 38) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — WebMessageChannelChannelDelegate.handle has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 3 (9 pts), boolean chains 6, loops 1 (4 pts), match/switch 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WebMessageChannelChannelDelegate.handle (cognitive 38) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageChannelChannelDelegate.swift:19 — WebMessageChannelChannelDelegate.handle has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 3 (9 pts), boolean chains 6, loops 1 (4 pts), match/switch 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · InAppWebView.webView (cognitive 35) · ×2

InAppWebView.webView (cognitive 35) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952 — InAppWebView.webView has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 11 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.webView (cognitive 35) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1241 — InAppWebView.webView has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 11 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MyCookieManager.getCookies (cognitive 25) · ×2

MyCookieManager.getCookies (cognitive 25) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:146 — MyCookieManager.getCookies has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), ternaries 1 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MyCookieManager.getCookies (cognitive 25) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:144 — MyCookieManager.getCookies has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), ternaries 1 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · Util.normalizeIPv6 (cognitive 23) · ×2

Util.normalizeIPv6 (cognitive 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167 — Util.normalizeIPv6 has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), ternaries 2 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Util.normalizeIPv6 (cognitive 23) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:96 — Util.normalizeIPv6 has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), ternaries 2 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FlutterWebViewController.load (cognitive 23) · ×2

FlutterWebViewController.load (cognitive 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:145 — FlutterWebViewController.load has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlutterWebViewController.load (cognitive 23) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:134 — FlutterWebViewController.load has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebMessagePort.postMessage (cognitive 23) · ×2

WebMessagePort.postMessage (cognitive 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebMessagePort.swift:58 — WebMessagePort.postMessage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebMessagePort.postMessage (cognitive 23) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebMessagePort.swift:58 — WebMessagePort.postMessage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebViewChromeClient.startPickerIntent (cognitive 19) · ×2

InAppWebViewChromeClient.startPickerIntent (cognitive 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:998 — InAppWebViewChromeClient.startPickerIntent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (InAppWebViewChromeClient.startPickerIntent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
InAppWebViewChromeClient.startPickerIntent (cognitive 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1040 — InAppWebViewChromeClient.startPickerIntent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (InAppWebViewChromeClient.startPickerIntent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · InAppWebView.enablePluginScriptAtRuntime (cognitive 19) · ×2

InAppWebView.enablePluginScriptAtRuntime (cognitive 19) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1431 — InAppWebView.enablePluginScriptAtRuntime has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppWebView.enablePluginScriptAtRuntime (cognitive 19) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:800 — InAppWebView.enablePluginScriptAtRuntime has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppBrowserWebViewController.initLoad (cognitive 18) · ×2

InAppBrowserWebViewController.initLoad (cognitive 18) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:181 — InAppBrowserWebViewController.initLoad has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppBrowserWebViewController.initLoad (cognitive 18) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:142 — InAppBrowserWebViewController.initLoad has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FlutterWebViewController.makeInitialLoad (cognitive 18) · ×2

FlutterWebViewController.makeInitialLoad (cognitive 18) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:101 — FlutterWebViewController.makeInitialLoad has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FlutterWebViewController.makeInitialLoad (cognitive 18) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:90 — FlutterWebViewController.makeInitialLoad has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · MyCookieManager.setCookie (cognitive 17) · ×2

MyCookieManager.setCookie (cognitive 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:85 — MyCookieManager.setCookie has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MyCookieManager.setCookie (cognitive 17) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:84 — MyCookieManager.setCookie has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ProxyRule.toProxyConfiguration (cognitive 17) · ×2

ProxyRule.toProxyConfiguration (cognitive 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:142 — ProxyRule.toProxyConfiguration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, ternaries 3 (5 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProxyRule.toProxyConfiguration (cognitive 17) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:142 — ProxyRule.toProxyConfiguration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, ternaries 3 (5 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D4 · Code Duplication · Near-duplicate member pair (40 shared lines) · ×2

Near-duplicate member pair (40 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771-841 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:324-374 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (40 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:139-185 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:139-185 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (9 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:188 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:188-195 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobChannelDelegate.java:68-75 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:753-760 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:951-958 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:984-991 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1014-1021 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1057-1064 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1135-1142 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1191-1198 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:714 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:714-878 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:880-1011 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:1013-1183 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:1185-1288 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:820-980 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1031-1151 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1153-1262 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1264-1508 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1510-1600 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.

D4 · Code Duplication · Duplicated block (40 lines × 5) · ×2

Duplicated block (40 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:385 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:385-424 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:386-425 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:640-679 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:393-432 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:431-470 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (40 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2110 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2110-2149 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2090-2129 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2097-2136 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:530-569 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2430-2469 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (36 lines × 5) · ×2

Duplicated block (36 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:247 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:247-282 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:248-283 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:332-367 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:255-290 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:273-308 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (36 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:289 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:289-324 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:290-325 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:376-411 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:297-332 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:315-350 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (34 lines × 5) · ×2

Duplicated block (34 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:151 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:151-184 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:150-183 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:156-189 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:149-182 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:156-189 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1985 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1985-2018 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1965-1998 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2058-2091 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1972-2005 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2274-2307 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (24 lines × 5) · ×2

Duplicated block (24 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:336 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:336-359 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:337-360 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:227-250 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:344-367 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:362-385 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2071 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2071-2094 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2051-2074 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2058-2081 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:491-514 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2391-2414 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22 lines × 5) · ×2

Duplicated block (22 lines × 5) flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:64 — flutter_inappwebview_android/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_ios/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_linux/lib/src/find_interaction/find_interaction_controller.dart:62-83 | flutter_inappwebview_macos/lib/src/find_interaction/find_interaction_controller.dart:64-85 | flutter_inappwebview_windows/lib/src/find_interaction/find_interaction_controller.dart:64-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (22 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2815 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2815-2836 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2795-2816 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2723-2744 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1027-1048 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3056-3077 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (19 lines × 5) · ×2

Duplicated block (19 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:363 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:363-381 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:362-380 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:372-390 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:361-379 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:372-390 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:831 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:831-849 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:832-850 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:495-513 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:839-857 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:893-911 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (19 lines × 4) · ×2

Duplicated block (19 lines × 4) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:79 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:79-97 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:78-96 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:78-96 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:68-86 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1028 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1028-1046 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1029-1047 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:596-614 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1036-1054 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (19 lines × 3) · ×2

Duplicated block (19 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:80 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:80-98 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:80-98 | flutter_inappwebview_web/lib/src/cookie_manager.dart:83-101 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 3) flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:140 — flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:140-158 | flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart:140-158 | flutter_inappwebview_windows/lib/src/web_storage/web_storage_manager.dart:140-158 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart` and `flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14 lines × 3) · ×2

Duplicated block (14 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2970 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2970-2983 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2898-2911 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3232-3245 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) flutter_inappwebview_platform_interface/lib/src/content_blocker.dart:156 — flutter_inappwebview_platform_interface/lib/src/content_blocker.dart:156-169 | flutter_inappwebview_platform_interface/lib/src/content_blocker.dart:172-185 | flutter_inappwebview_platform_interface/lib/src/content_blocker.dart:188-201 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2

Duplicated block (11–12 lines × 2) dev_packages/generators/lib/src/exchangeable_object_generator.dart:757 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:757-768 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:780-790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:112 — flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:112-123 | flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart:96-106 — before extracting anything, compare `flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart` and `flutter_inappwebview_ios/lib/src/chrome_safari_browser/chrome_safari_browser.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×2

Duplicated block (8–9 lines × 2) dev_packages/generators/lib/src/exchangeable_object_generator.dart:689 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:689-696 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:708-716 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:1223 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:1223-1230 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1711-1719 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 8) · ×2

Duplicated block (5 lines × 8) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:101 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:101-105 | flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:152-156 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:100-104 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:151-155 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:100-104 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:151-155 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:90-94 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:141-145 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 8) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:129 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:129-133 | flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:144-148 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:128-132 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:143-147 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:128-132 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:143-147 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:118-122 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:133-137 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 7) · ×2

Duplicated block (5 lines × 7) flutter_inappwebview_android/lib/src/cookie_manager.dart:212 — flutter_inappwebview_android/lib/src/cookie_manager.dart:212-216 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2281-2286 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2254-2259 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2261-2266 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:673-678 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:247-251 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2601-2606 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 7) flutter_inappwebview_android/lib/src/cookie_manager.dart:212 — flutter_inappwebview_android/lib/src/cookie_manager.dart:212-217 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2102-2106 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2082-2086 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2089-2093 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:522-526 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:247-252 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2422-2426 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_windows/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9 lines × 6) · ×2

Duplicated block (9 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3181 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:3181-3189 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:3132-3140 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1479-1487 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:3047-3055 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1085-1093 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3455-3463 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 6) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:129 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:129-137 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:129-137 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:129-137 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:129-137 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:131-139 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:129-137 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (70 lines × 2) · ×2

Duplicated block (70 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:361 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:361-430 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:372-441 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (70 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092-2161 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1372-1441 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (51 lines × 2) · ×2

Duplicated block (51 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:677 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:677-727 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:703-753 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:677` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (51 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindElementsAtPointJS.swift:28 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindElementsAtPointJS.swift:28-78 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindElementsAtPointJS.swift:28-78 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindElementsAtPointJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindElementsAtPointJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindElementsAtPointJS.swift:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (49 lines × 2) · ×2

Duplicated block (49 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2379 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2379-2427 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1674-1722 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (49 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2531 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2531-2579 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1803-1851 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (43 lines × 2) · ×2

Duplicated block (43 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2971 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2971-3013 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2182-2224 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2971` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (43 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:25 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:25-67 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:24-66 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (34 lines × 2) · ×2

Duplicated block (34 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2654 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2654-2687 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1865-1898 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2654` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (34 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceRequest.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceRequest.swift:19-52 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebResourceRequest.swift:19-52 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WebResourceRequest.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/WebResourceRequest.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×2

Duplicated block (8–10 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebViewFlutterPlugin.swift:43 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebViewFlutterPlugin.swift:43-52 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebViewFlutterPlugin.swift:43-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebViewFlutterPlugin.swift:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebViewFlutterPlugin.swift:53` calls `ChromeSafariBrowserManager` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebViewFlutterPlugin.swift:51` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–10 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:799 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:799-806 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:832-841 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (48 lines × 2) · ×2

Duplicated block (48 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/ConsoleLogJS.swift:17 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/ConsoleLogJS.swift:17-64 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/ConsoleLogJS.swift:17-64 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/ConsoleLogJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/ConsoleLogJS.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/ConsoleLogJS.swift:17` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (48 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:307 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:307-354 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:353-400 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×2

Duplicated block (10–11 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1645 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1645-1654 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1127-1136 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:981-990 | flutter_inappwebview/example/lib/widgets/common/event_log_card.dart:43-53 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 4) flutter_inappwebview/example/lib/screens/support_matrix/platform_comparison_screen.dart:560 — flutter_inappwebview/example/lib/screens/support_matrix/platform_comparison_screen.dart:560-569 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:159-169 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1544-1554 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:764-774 — before extracting anything, compare `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` and `flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×2

Sync-over-async blocking REDACTED:216 — `fs.statSync` in `app.get("/test-download-file")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:217 — `fs.readFileSync` in `app.get("/test-download-file")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 42) · ×2

Complex function (anonymous) (cyclomatic 29, cognitive 42) flutter_inappwebview_web/lib/assets/web/web_support.js:47 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 29, cognitive 42) web_support/src/index.ts:73 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function setSettings (cyclomatic 21, cognitive 42) · ×2

Complex function setSettings (cyclomatic 21, cognitive 42) flutter_inappwebview_web/lib/assets/web/web_support.js:296 — setSettings has cyclomatic complexity 21 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function setSettings (cyclomatic 21, cognitive 42) web_support/src/index.ts:352 — setSettings has cyclomatic complexity 21 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function getSize (cyclomatic 12, cognitive 13) · ×2

Complex function getSize (cyclomatic 12, cognitive 13) flutter_inappwebview_web/lib/assets/web/web_support.js:638 — getSize has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getSize (cyclomatic 12, cognitive 13) web_support/src/index.ts:704 — getSize has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

X18 · Disposal-pattern correctness · Owned disposable field is never released · ×2

Owned disposable field is never released flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:139 — `CustomPlatformViewController` carries a disposal duty — it declares its own release — and it creates `_cursorStreamController` itself (line 139, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_cursorStreamController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_cursorStreamController.close();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released flutter_inappwebview_windows/lib/src/in_app_webview/custom_platform_view.dart:114 — `CustomPlatformViewController` carries a disposal duty — it declares its own release — and it creates `_cursorStreamController` itself (line 114, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_cursorStreamController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_cursorStreamController.close();` in `dispose()` before `super.dispose()`.

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2

Untrusted text written into markup unescaped flutter_inappwebview_web/lib/assets/web/web_support.js:487 — `source` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped web_support/src/index.ts:550 — `source` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

D1 · Cyclomatic Complexity · WindowsInAppWebViewController._handleMethod (cyclomatic 514) · ×1

WindowsInAppWebViewController._handleMethod (cyclomatic 514) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207 — WindowsInAppWebViewController._handleMethod has cyclomatic complexity 514 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AndroidInAppWebViewController._handleMethod (cyclomatic 437) · ×1

AndroidInAppWebViewController._handleMethod (cyclomatic 437) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206 — AndroidInAppWebViewController._handleMethod has cyclomatic complexity 437 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MacOSInAppWebViewController._handleMethod (cyclomatic 432) · ×1

MacOSInAppWebViewController._handleMethod (cyclomatic 432) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:207 — MacOSInAppWebViewController._handleMethod has cyclomatic complexity 432 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · IOSInAppWebViewController._handleMethod (cyclomatic 431) · ×1

IOSInAppWebViewController._handleMethod (cyclomatic 431) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:207 — IOSInAppWebViewController._handleMethod has cyclomatic complexity 431 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · LinuxInAppWebViewController._handleMethod (cyclomatic 303) · ×1

LinuxInAppWebViewController._handleMethod (cyclomatic 303) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198 — LinuxInAppWebViewController._handleMethod has cyclomatic complexity 303 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebViewChannelDelegate.onMethodCall (cyclomatic 198) · ×1

WebViewChannelDelegate.onMethodCall (cyclomatic 198) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:81 — WebViewChannelDelegate.onMethodCall has cyclomatic complexity 198 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.setSettings (cyclomatic 195) · ×1

InAppWebView.setSettings (cyclomatic 195) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:830 — InAppWebView.setSettings has cyclomatic complexity 195 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.setSettings (cyclomatic 193) · ×1

InAppWebView.setSettings (cyclomatic 193) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1031 — InAppWebView.setSettings has cyclomatic complexity 193 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebViewChannelDelegate.handle (cyclomatic 177) · ×1

WebViewChannelDelegate.handle (cyclomatic 177) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20 — WebViewChannelDelegate.handle has cyclomatic complexity 177 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ExchangeableObjectGenerator.generateForAnnotatedElement (cyclomatic 176) · ×1

ExchangeableObjectGenerator.generateForAnnotatedElement (cyclomatic 176) dev_packages/generators/lib/src/exchangeable_object_generator.dart:45 — ExchangeableObjectGenerator.generateForAnnotatedElement has cyclomatic complexity 176 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebViewChannelDelegate.handle (cyclomatic 167) · ×1

WebViewChannelDelegate.handle (cyclomatic 167) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:20 — WebViewChannelDelegate.handle has cyclomatic complexity 167 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.setSettings (cyclomatic 112) · ×1

InAppWebView.setSettings (cyclomatic 112) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:559 — InAppWebView.setSettings has cyclomatic complexity 112 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ExchangeableEnumGenerator.generateForAnnotatedElement (cyclomatic 85) · ×1

ExchangeableEnumGenerator.generateForAnnotatedElement (cyclomatic 85) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:47 — ExchangeableEnumGenerator.generateForAnnotatedElement has cyclomatic complexity 85 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.prepare (cyclomatic 72) · ×1

InAppWebView.prepare (cyclomatic 72) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:258 — InAppWebView.prepare has cyclomatic complexity 72 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.userContentController (cyclomatic 72) · ×1

InAppWebView.userContentController (cyclomatic 72) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2158 — InAppWebView.userContentController has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.userContentController (cyclomatic 71) · ×1

InAppWebView.userContentController (cyclomatic 71) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947 — InAppWebView.userContentController has cyclomatic complexity 71 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebPlatformInAppWebViewController._handleMethod (cyclomatic 64) · ×1

WebPlatformInAppWebViewController._handleMethod (cyclomatic 64) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:112 — WebPlatformInAppWebViewController._handleMethod has cyclomatic complexity 64 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppBrowserWebViewController.setSettings (cyclomatic 57) · ×1

InAppBrowserWebViewController.setSettings (cyclomatic 57) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:494 — InAppBrowserWebViewController.setSettings has cyclomatic complexity 57 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ContentBlockerHandler.checkUrl (cyclomatic 53) · ×1

ContentBlockerHandler.checkUrl (cyclomatic 53) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerHandler.java:53 — ContentBlockerHandler.checkUrl has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ExchangeableObjectGenerator.getFromMapValue (cyclomatic 51) · ×1

ExchangeableObjectGenerator.getFromMapValue (cyclomatic 51) dev_packages/generators/lib/src/exchangeable_object_generator.dart:751 — ExchangeableObjectGenerator.getFromMapValue has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.webView (cyclomatic 50) · ×1

InAppWebView.webView (cyclomatic 50) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092 — InAppWebView.webView has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.webView (cyclomatic 49) · ×1

InAppWebView.webView (cyclomatic 49) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1372 — InAppWebView.webView has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · SupportedPlatformsGenerator.generateForAnnotatedElement (cyclomatic 47) · ×1

SupportedPlatformsGenerator.generateForAnnotatedElement (cyclomatic 47) dev_packages/generators/lib/src/supported_platforms_generator.dart:20 — SupportedPlatformsGenerator.generateForAnnotatedElement has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ExchangeableObjectGenerator.getToMapValue (cyclomatic 44) · ×1

ExchangeableObjectGenerator.getToMapValue (cyclomatic 44) dev_packages/generators/lib/src/exchangeable_object_generator.dart:884 — ExchangeableObjectGenerator.getToMapValue has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.printCurrentPage (cyclomatic 40) · ×1

InAppWebView.printCurrentPage (cyclomatic 40) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2435 — InAppWebView.printCurrentPage has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.prepare (cyclomatic 37) · ×1

InAppWebView.prepare (cyclomatic 37) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:377 — InAppWebView.prepare has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebViewManager.onMethodCall (cyclomatic 33) · ×1

InAppWebViewManager.onMethodCall (cyclomatic 33) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/InAppWebViewManager.java:51 — InAppWebViewManager.onMethodCall has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AndroidChromeSafariBrowser._handleMethod (cyclomatic 30) · ×1

AndroidChromeSafariBrowser._handleMethod (cyclomatic 30) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:80 — AndroidChromeSafariBrowser._handleMethod has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ASN1DERDecoder.parse (cyclomatic 30) · ×1

ASN1DERDecoder.parse (cyclomatic 30) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart:13 — ASN1DERDecoder.parse has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ChromeCustomTabsSettings.parse (cyclomatic 30) · ×1

ChromeCustomTabsSettings.parse (cyclomatic 30) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:51 — ChromeCustomTabsSettings.parse has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · InAppBrowserWebViewController.prepareWebView (cyclomatic 30) · ×1

InAppBrowserWebViewController.prepareWebView (cyclomatic 30) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:233 — InAppBrowserWebViewController.prepareWebView has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ChromeCustomTabsChannelDelegate.onMethodCall (cyclomatic 28) · ×1

ChromeCustomTabsChannelDelegate.onMethodCall (cyclomatic 28) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:32 — ChromeCustomTabsChannelDelegate.onMethodCall has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ServiceWorkerChannelDelegate.onMethodCall (cyclomatic 28) · ×1

ServiceWorkerChannelDelegate.onMethodCall (cyclomatic 28) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerChannelDelegate.java:35 — ServiceWorkerChannelDelegate.onMethodCall has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppBrowserWindow.prepare (cyclomatic 28) · ×1

InAppBrowserWindow.prepare (cyclomatic 28) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWindow.swift:60 — InAppBrowserWindow.prepare has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppBrowserActivity.setSettings (cyclomatic 27) · ×1

InAppBrowserActivity.setSettings (cyclomatic 27) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:491 — InAppBrowserActivity.setSettings has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · FindInteractionChannelDelegate.handle (cyclomatic 27) · ×1

FindInteractionChannelDelegate.handle (cyclomatic 27) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:19 — FindInteractionChannelDelegate.handle has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AndroidHeadlessInAppWebView._inferInitialSettings (cyclomatic 26) · ×1

AndroidHeadlessInAppWebView._inferInitialSettings (cyclomatic 26) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368 — AndroidHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · AndroidInAppWebViewWidget._inferInitialSettings (cyclomatic 26) · ×1

AndroidInAppWebViewWidget._inferInitialSettings (cyclomatic 26) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:432 — AndroidInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.observeValue (cyclomatic 26) · ×1

InAppWebView.observeValue (cyclomatic 26) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771 — InAppWebView.observeValue has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppBrowserActivity.onCreateOptionsMenu (cyclomatic 25) · ×1

InAppBrowserActivity.onCreateOptionsMenu (cyclomatic 25) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:256 — InAppBrowserActivity.onCreateOptionsMenu has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebMessageListener.isOriginAllowed (cyclomatic 25) · ×1

WebMessageListener.isOriginAllowed (cyclomatic 25) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:189 — WebMessageListener.isOriginAllowed has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · IOSHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) · ×1

IOSHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:366 — IOSHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · IOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24) · ×1

IOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:371 — IOSInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · LinuxHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) · ×1

LinuxHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:370 — LinuxHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · LinuxInAppWebViewWidget._inferInitialSettings (cyclomatic 24) · ×1

LinuxInAppWebViewWidget._inferInitialSettings (cyclomatic 24) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:304 — LinuxInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · MacOSHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) · ×1

MacOSHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:359 — MacOSHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · MacOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24) · ×1

MacOSInAppWebViewWidget._inferInitialSettings (cyclomatic 24) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:365 — MacOSInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WindowsHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) · ×1

WindowsHeadlessInAppWebView._inferInitialSettings (cyclomatic 24) flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:393 — WindowsHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WindowsInAppWebViewWidget._inferInitialSettings (cyclomatic 24) · ×1

WindowsInAppWebViewWidget._inferInitialSettings (cyclomatic 24) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:379 — WindowsInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WebMessageListener.assertOriginRulesValid (cyclomatic 24) · ×1

WebMessageListener.assertOriginRulesValid (cyclomatic 24) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:124 — WebMessageListener.assertOriginRulesValid has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · URLRequest.init (cyclomatic 23) · ×1

URLRequest.init (cyclomatic 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/URLRequest.swift:12 — URLRequest.init has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppBrowserWindow.setSettings (cyclomatic 23) · ×1

InAppBrowserWindow.setSettings (cyclomatic 23) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWindow.swift:302 — InAppBrowserWindow.setSettings has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.prepare (cyclomatic 23) · ×1

InAppWebView.prepare (cyclomatic 23) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:78 — InAppWebView.prepare has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · LinuxInAppWebViewController.getFavicons (cyclomatic 22) · ×1

LinuxInAppWebViewController.getFavicons (cyclomatic 22) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1935 — LinuxInAppWebViewController.getFavicons has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.rebuildActionMode (cyclomatic 22) · ×1

InAppWebView.rebuildActionMode (cyclomatic 22) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1662 — InAppWebView.rebuildActionMode has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebViewClient.shouldInterceptRequest (cyclomatic 22) · ×1

InAppWebViewClient.shouldInterceptRequest (cyclomatic 22) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:640 — InAppWebViewClient.shouldInterceptRequest has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebViewClientCompat.shouldInterceptRequest (cyclomatic 22) · ×1

InAppWebViewClientCompat.shouldInterceptRequest (cyclomatic 22) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:666 — InAppWebViewClientCompat.shouldInterceptRequest has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.printCurrentPage (cyclomatic 22) · ×1

InAppWebView.printCurrentPage (cyclomatic 22) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3225 — InAppWebView.printCurrentPage has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AndroidInAppWebViewController.getFavicons (cyclomatic 21) · ×1

AndroidInAppWebViewController.getFavicons (cyclomatic 21) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864 — AndroidInAppWebViewController.getFavicons has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · IOSInAppWebViewController.getFavicons (cyclomatic 21) · ×1

IOSInAppWebViewController.getFavicons (cyclomatic 21) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1844 — IOSInAppWebViewController.getFavicons has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MacOSInAppWebViewController.getFavicons (cyclomatic 21) · ×1

MacOSInAppWebViewController.getFavicons (cyclomatic 21) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1851 — MacOSInAppWebViewController.getFavicons has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WindowsInAppWebViewController.getFavicons (cyclomatic 21) · ×1

WindowsInAppWebViewController.getFavicons (cyclomatic 21) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2153 — WindowsInAppWebViewController.getFavicons has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppBrowserActivity.onCreate (cyclomatic 21) · ×1

InAppBrowserActivity.onCreate (cyclomatic 21) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:89 — InAppBrowserActivity.onCreate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · createFlutterInAppWebView · ×1

createFlutterInAppWebView::setSettings (cyclomatic 21) flutter_inappwebview_web/lib/assets/web/web_support.js:296 — createFlutterInAppWebView::setSettings has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Util.getParameterSupportedDocs (cyclomatic 20) · ×1

Util.getParameterSupportedDocs (cyclomatic 20) dev_packages/generators/lib/src/util.dart:107 — Util.getParameterSupportedDocs has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PullToRefreshChannelDelegate.onMethodCall (cyclomatic 20) · ×1

PullToRefreshChannelDelegate.onMethodCall (cyclomatic 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/pull_to_refresh/PullToRefreshChannelDelegate.java:27 — PullToRefreshChannelDelegate.onMethodCall has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.printCurrentPage (cyclomatic 20) · ×1

InAppWebView.printCurrentPage (cyclomatic 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1467 — InAppWebView.printCurrentPage has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MyCookieManager.getCookies (cyclomatic 20) · ×1

MyCookieManager.getCookies (cyclomatic 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:209 — MyCookieManager.getCookies has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.preWKWebViewConfiguration (cyclomatic 20) · ×1

InAppWebView.preWKWebViewConfiguration (cyclomatic 20) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:655 — InAppWebView.preWKWebViewConfiguration has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebView.onScrollChanged (cyclomatic 20) · ×1

InAppWebView.onScrollChanged (cyclomatic 20) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2589 — InAppWebView.onScrollChanged has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CredentialDatabaseHandler.onMethodCall (cyclomatic 19) · ×1

CredentialDatabaseHandler.onMethodCall (cyclomatic 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:45 — CredentialDatabaseHandler.onMethodCall has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InAppWebViewFlutterPlugin.onDetachedFromEngine (cyclomatic 19) · ×1

InAppWebViewFlutterPlugin.onDetachedFromEngine (cyclomatic 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/InAppWebViewFlutterPlugin.java:122 — InAppWebViewFlutterPlugin.onDetachedFromEngine has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.observeValue (cyclomatic 19) · ×1

InAppWebView.observeValue (cyclomatic 19) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:324 — InAppWebView.observeValue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Util.getSupportedDocs (cyclomatic 18) · ×1

Util.getSupportedDocs (cyclomatic 18) dev_packages/generators/lib/src/util.dart:38 — Util.getSupportedDocs has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WebPlatformHeadlessInAppWebView._inferInitialSettings (cyclomatic 18) · ×1

WebPlatformHeadlessInAppWebView._inferInitialSettings (cyclomatic 18) flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:360 — WebPlatformHeadlessInAppWebView._inferInitialSettings has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · WebPlatformInAppWebViewWidget._inferInitialSettings (cyclomatic 18) · ×1

WebPlatformInAppWebViewWidget._inferInitialSettings (cyclomatic 18) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview.dart:346 — WebPlatformInAppWebViewWidget._inferInitialSettings has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · ChromeCustomTabsActivity.prepareCustomTabs (cyclomatic 18) · ×1

ChromeCustomTabsActivity.prepareCustomTabs (cyclomatic 18) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:269 — ChromeCustomTabsActivity.prepareCustomTabs has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebView.preWKWebViewConfiguration (cyclomatic 18) · ×1

InAppWebView.preWKWebViewConfiguration (cyclomatic 18) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:261 — InAppWebView.preWKWebViewConfiguration has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · _CustomPlatformViewState._buildInner (cyclomatic 17) · ×1

_CustomPlatformViewState._buildInner (cyclomatic 17) flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:472 — _CustomPlatformViewState._buildInner has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · InAppWebViewSettings.getRealSettings (cyclomatic 17) · ×1

InAppWebViewSettings.getRealSettings (cyclomatic 17) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java:611 — InAppWebViewSettings.getRealSettings has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: InAppWebViewSettings.parse (cyclomatic 106) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · PullToRefreshChannelDelegate.handle (cyclomatic 17) · ×1

PullToRefreshChannelDelegate.handle (cyclomatic 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PullToRefresh/PullToRefreshChannelDelegate.swift:20 — PullToRefreshChannelDelegate.handle has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · NSAttributedString.fromMap (cyclomatic 17) · ×1

NSAttributedString.fromMap (cyclomatic 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:12 — NSAttributedString.fromMap has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · X509Extension.generalName (cyclomatic 16) · ×1

X509Extension.generalName (cyclomatic 16) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_extension.dart:97 — X509Extension.generalName has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · JsPromptResponse.equals (cyclomatic 16) · ×1

JsPromptResponse.equals (cyclomatic 16) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsPromptResponse.java:103 — JsPromptResponse.equals has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · 2.run (cyclomatic 16) · ×1

2.run (cyclomatic 16) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/JavaScriptBridgeInterface.java:112 — 2.run has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · WindowsInAppWebViewController._handleMethod (cognitive 875) · ×1

WindowsInAppWebViewController._handleMethod (cognitive 875) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:207 — WindowsInAppWebViewController._handleMethod has cognitive complexity 875 (threshold 15). Drivers by points: if/else 272 (587 pts), boolean chains 217, ternaries 17 (56 pts), loops 3 (9 pts), error handling 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 363). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AndroidInAppWebViewController._handleMethod (cognitive 747) · ×1

AndroidInAppWebViewController._handleMethod (cognitive 747) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:206 — AndroidInAppWebViewController._handleMethod has cognitive complexity 747 (threshold 15). Drivers by points: if/else 244 (519 pts), boolean chains 184, ternaries 11 (35 pts), error handling 1 (3 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 304). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MacOSInAppWebViewController._handleMethod (cognitive 739) · ×1

MacOSInAppWebViewController._handleMethod (cognitive 739) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:207 — MacOSInAppWebViewController._handleMethod has cognitive complexity 739 (threshold 15). Drivers by points: if/else 242 (514 pts), boolean chains 181, ternaries 11 (35 pts), error handling 1 (3 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 301). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · IOSInAppWebViewController._handleMethod (cognitive 738) · ×1

IOSInAppWebViewController._handleMethod (cognitive 738) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:207 — IOSInAppWebViewController._handleMethod has cognitive complexity 738 (threshold 15). Drivers by points: if/else 241 (513 pts), boolean chains 181, ternaries 11 (35 pts), error handling 1 (3 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 301). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LinuxInAppWebViewController._handleMethod (cognitive 506) · ×1

LinuxInAppWebViewController._handleMethod (cognitive 506) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:198 — LinuxInAppWebViewController._handleMethod has cognitive complexity 506 (threshold 15). Drivers by points: if/else 153 (331 pts), boolean chains 127, ternaries 9 (33 pts), loops 3 (9 pts), error handling 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 211). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ExchangeableObjectGenerator.generateForAnnotatedElement (cognitive 383) · ×1

ExchangeableObjectGenerator.generateForAnnotatedElement (cognitive 383) dev_packages/generators/lib/src/exchangeable_object_generator.dart:45 — ExchangeableObjectGenerator.generateForAnnotatedElement has cognitive complexity 383 (threshold 15). Drivers by points: if/else 92 (220 pts), ternaries 17 (74 pts), boolean chains 67, loops 11 (22 pts) (nesting depth added 196). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.setSettings (cognitive 284) · ×1

InAppWebView.setSettings (cognitive 284) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1031 — InAppWebView.setSettings has cognitive complexity 284 (threshold 15). Drivers by points: if/else 114 (185 pts), boolean chains 84, loops 3 (9 pts), error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 81). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebViewChannelDelegate.onMethodCall (cognitive 278) · ×1

WebViewChannelDelegate.onMethodCall (cognitive 278) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:81 — WebViewChannelDelegate.onMethodCall has cognitive complexity 278 (threshold 15). Drivers by points: if/else 124 (218 pts), boolean chains 25, ternaries 7 (18 pts), error handling 4 (12 pts), loops 1 (4 pts), match/switch 1 (nesting depth added 116). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebViewChannelDelegate.handle (cognitive 235) · ×1

WebViewChannelDelegate.handle (cognitive 235) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20 — WebViewChannelDelegate.handle has cognitive complexity 235 (threshold 15). Drivers by points: if/else 113 (198 pts), boolean chains 22, error handling 3 (8 pts), loops 1 (4 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 94). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebViewChannelDelegate.handle (cognitive 228) · ×1

WebViewChannelDelegate.handle (cognitive 228) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:20 — WebViewChannelDelegate.handle has cognitive complexity 228 (threshold 15). Drivers by points: if/else 107 (192 pts), boolean chains 21, error handling 3 (8 pts), loops 1 (4 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 94). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.setSettings (cognitive 218) · ×1

InAppWebView.setSettings (cognitive 218) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:830 — InAppWebView.setSettings has cognitive complexity 218 (threshold 15). Drivers by points: if/else 102 (119 pts), boolean chains 90, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 22). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · ExchangeableEnumGenerator.generateForAnnotatedElement (cognitive 184) · ×1

ExchangeableEnumGenerator.generateForAnnotatedElement (cognitive 184) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:47 — ExchangeableEnumGenerator.generateForAnnotatedElement has cognitive complexity 184 (threshold 15). Drivers by points: if/else 51 (124 pts), boolean chains 28, ternaries 5 (17 pts), loops 6 (15 pts) (nesting depth added 94). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ContentBlockerHandler.checkUrl (cognitive 170) · ×1

ContentBlockerHandler.checkUrl (cognitive 170) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/content_blocker/ContentBlockerHandler.java:53 — ContentBlockerHandler.checkUrl has cognitive complexity 170 (threshold 15). Drivers by points: if/else 27 (111 pts), loops 6 (26 pts), boolean chains 15, ternaries 1 (8 pts), error handling 2 (7 pts), match/switch 1 (3 pts) (nesting depth added 118). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.setSettings (cognitive 157) · ×1

InAppWebView.setSettings (cognitive 157) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:559 — InAppWebView.setSettings has cognitive complexity 157 (threshold 15). Drivers by points: if/else 64 (102 pts), boolean chains 46, error handling 1 (3 pts), loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.webView (cognitive 115) · ×1

InAppWebView.webView (cognitive 115) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092 — InAppWebView.webView has cognitive complexity 115 (threshold 15). Drivers by points: if/else 36 (73 pts), boolean chains 13, loops 2 (12 pts), match/switch 3 (9 pts), error handling 1 (4 pts), ternaries 1 (4 pts) (nesting depth added 59). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ExchangeableObjectGenerator.getFromMapValue (cognitive 110) · ×1

ExchangeableObjectGenerator.getFromMapValue (cognitive 110) dev_packages/generators/lib/src/exchangeable_object_generator.dart:751 — ExchangeableObjectGenerator.getFromMapValue has cognitive complexity 110 (threshold 15). Drivers by points: if/else 35 (54 pts), ternaries 15 (45 pts), boolean chains 11 (nesting depth added 49). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.webView (cognitive 110) · ×1

InAppWebView.webView (cognitive 110) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1372 — InAppWebView.webView has cognitive complexity 110 (threshold 15). Drivers by points: if/else 35 (68 pts), boolean chains 13, loops 2 (12 pts), match/switch 3 (9 pts), error handling 1 (4 pts), ternaries 1 (4 pts) (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.printCurrentPage (cognitive 104) · ×1

InAppWebView.printCurrentPage (cognitive 104) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2435 — InAppWebView.printCurrentPage has cognitive complexity 104 (threshold 15). Drivers by points: if/else 42 (97 pts), boolean chains 7 (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ExchangeableObjectGenerator.getToMapValue (cognitive 101) · ×1

ExchangeableObjectGenerator.getToMapValue (cognitive 101) dev_packages/generators/lib/src/exchangeable_object_generator.dart:884 — ExchangeableObjectGenerator.getToMapValue has cognitive complexity 101 (threshold 15). Drivers by points: ternaries 19 (62 pts), if/else 20 (30 pts), boolean chains 9 (nesting depth added 53). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · SupportedPlatformsGenerator.generateForAnnotatedElement (cognitive 101) · ×1

SupportedPlatformsGenerator.generateForAnnotatedElement (cognitive 101) dev_packages/generators/lib/src/supported_platforms_generator.dart:20 — SupportedPlatformsGenerator.generateForAnnotatedElement has cognitive complexity 101 (threshold 15). Drivers by points: if/else 30 (77 pts), boolean chains 12, loops 4 (8 pts), ternaries 1 (4 pts) (nesting depth added 54). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ASN1DERDecoder.parse (cognitive 89) · ×1

ASN1DERDecoder.parse (cognitive 89) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart:13 — ASN1DERDecoder.parse has cognitive complexity 89 (threshold 15). Drivers by points: if/else 26 (52 pts), error handling 3 (15 pts), ternaries 2 (11 pts), loops 3 (10 pts), boolean chains 1 (nesting depth added 54). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.prepare (cognitive 87) · ×1

InAppWebView.prepare (cognitive 87) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:258 — InAppWebView.prepare has cognitive complexity 87 (threshold 15). Drivers by points: if/else 55 (64 pts), boolean chains 17, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · WebPlatformInAppWebViewController._handleMethod (cognitive 85) · ×1

WebPlatformInAppWebViewController._handleMethod (cognitive 85) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:112 — WebPlatformInAppWebViewController._handleMethod has cognitive complexity 85 (threshold 15). Drivers by points: if/else 26 (50 pts), boolean chains 19, ternaries 4 (12 pts), error handling 1 (3 pts), match/switch 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppBrowserWebViewController.setSettings (cognitive 79) · ×1

InAppBrowserWebViewController.setSettings (cognitive 79) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:494 — InAppBrowserWebViewController.setSettings has cognitive complexity 79 (threshold 15). Drivers by points: if/else 40 (52 pts), boolean chains 27 (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · InAppBrowserWindow.prepare (cognitive 76) · ×1

InAppBrowserWindow.prepare (cognitive 76) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWindow.swift:60 — InAppBrowserWindow.prepare has cognitive complexity 76 (threshold 15). Drivers by points: if/else 31 (69 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.prepare (cognitive 71) · ×1

InAppWebView.prepare (cognitive 71) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:377 — InAppWebView.prepare has cognitive complexity 71 (threshold 15). Drivers by points: if/else 32 (63 pts), boolean chains 4, loops 1 (4 pts) (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppBrowserWebViewController.prepareWebView (cognitive 65) · ×1

InAppBrowserWebViewController.prepareWebView (cognitive 65) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:233 — InAppBrowserWebViewController.prepareWebView has cognitive complexity 65 (threshold 15). Drivers by points: if/else 21 (48 pts), boolean chains 9, loops 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · FindInteractionChannelDelegate.handle (cognitive 54) · ×1

FindInteractionChannelDelegate.handle (cognitive 54) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:19 — FindInteractionChannelDelegate.handle has cognitive complexity 54 (threshold 15). Drivers by points: if/else 30 (53 pts), match/switch 1 (nesting depth added 23). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · InAppWebView.printCurrentPage (cognitive 53) · ×1

InAppWebView.printCurrentPage (cognitive 53) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1467 — InAppWebView.printCurrentPage has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (41 pts), match/switch 1 (5 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.observeValue (cognitive 51) · ×1

InAppWebView.observeValue (cognitive 51) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:771 — InAppWebView.observeValue has cognitive complexity 51 (threshold 15). Drivers by points: if/else 19 (43 pts), boolean chains 8 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.preWKWebViewConfiguration (cognitive 48) · ×1

InAppWebView.preWKWebViewConfiguration (cognitive 48) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:655 — InAppWebView.preWKWebViewConfiguration has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (34 pts), loops 3 (10 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · Util.getParameterSupportedDocs (cognitive 47) · ×1

Util.getParameterSupportedDocs (cognitive 47) dev_packages/generators/lib/src/util.dart:107 — Util.getParameterSupportedDocs has cognitive complexity 47 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 3 (9 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AndroidChromeSafariBrowser._handleMethod (cognitive 46) · ×1

AndroidChromeSafariBrowser._handleMethod (cognitive 46) flutter_inappwebview_android/lib/src/chrome_safari_browser/chrome_safari_browser.dart:80 — AndroidChromeSafariBrowser._handleMethod has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (35 pts), ternaries 2 (5 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 28). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · ChromeCustomTabsChannelDelegate.onMethodCall (cognitive 46) · ×1

ChromeCustomTabsChannelDelegate.onMethodCall (cognitive 46) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:32 — ChromeCustomTabsChannelDelegate.onMethodCall has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (34 pts), boolean chains 5, error handling 1 (3 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · InAppWebViewManager.onMethodCall (cognitive 45) · ×1

InAppWebViewManager.onMethodCall (cognitive 45) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/InAppWebViewManager.java:51 — InAppWebViewManager.onMethodCall has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (40 pts), ternaries 2 (4 pts), match/switch 1 (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · MyCookieManager.getCookies (cognitive 44) · ×1

MyCookieManager.getCookies (cognitive 44) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:209 — MyCookieManager.getCookies has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (24 pts), error handling 2 (10 pts), ternaries 2 (6 pts), loops 2 (4 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LinuxInAppWebViewController.getFavicons (cognitive 43) · ×1

LinuxInAppWebViewController.getFavicons (cognitive 43) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1935 — LinuxInAppWebViewController.getFavicons has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppBrowserActivity.onCreateOptionsMenu (cognitive 42) · ×1

InAppBrowserActivity.onCreateOptionsMenu (cognitive 42) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:256 — InAppBrowserActivity.onCreateOptionsMenu has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (30 pts), ternaries 3 (7 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebMessageListener.assertOriginRulesValid (cognitive 42) · ×1

WebMessageListener.assertOriginRulesValid (cognitive 42) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:124 — WebMessageListener.assertOriginRulesValid has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 9, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.observeValue (cognitive 42) · ×1

InAppWebView.observeValue (cognitive 42) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:324 — InAppWebView.observeValue has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 5 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · createFlutterInAppWebView · ×1

createFlutterInAppWebView::setSettings (cognitive 42) flutter_inappwebview_web/lib/assets/web/web_support.js:296 — createFlutterInAppWebView::setSettings has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (39 pts), boolean chains 2, error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AndroidInAppWebViewController.getFavicons (cognitive 41) · ×1

AndroidInAppWebViewController.getFavicons (cognitive 41) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864 — AndroidInAppWebViewController.getFavicons has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · IOSInAppWebViewController.getFavicons (cognitive 41) · ×1

IOSInAppWebViewController.getFavicons (cognitive 41) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1844 — IOSInAppWebViewController.getFavicons has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · MacOSInAppWebViewController.getFavicons (cognitive 41) · ×1

MacOSInAppWebViewController.getFavicons (cognitive 41) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1851 — MacOSInAppWebViewController.getFavicons has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WindowsInAppWebViewController.getFavicons (cognitive 41) · ×1

WindowsInAppWebViewController.getFavicons (cognitive 41) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2153 — WindowsInAppWebViewController.getFavicons has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebViewClient.shouldInterceptRequest (cognitive 41) · ×1

InAppWebViewClient.shouldInterceptRequest (cognitive 41) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:640 — InAppWebViewClient.shouldInterceptRequest has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (21 pts), error handling 6 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebViewClientCompat.shouldInterceptRequest (cognitive 41) · ×1

InAppWebViewClientCompat.shouldInterceptRequest (cognitive 41) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:666 — InAppWebViewClientCompat.shouldInterceptRequest has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (21 pts), error handling 6 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.preWKWebViewConfiguration (cognitive 39) · ×1

InAppWebView.preWKWebViewConfiguration (cognitive 39) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:261 — InAppWebView.preWKWebViewConfiguration has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 2 (7 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppBrowserActivity.setSettings (cognitive 38) · ×1

InAppBrowserActivity.setSettings (cognitive 38) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:491 — InAppBrowserActivity.setSettings has cognitive complexity 38 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 8 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebMessageListener.isOriginAllowed (cognitive 38) · ×1

WebMessageListener.isOriginAllowed (cognitive 38) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageListener.java:189 — WebMessageListener.isOriginAllowed has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (10 pts), ternaries 4 (10 pts), error handling 2 (5 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.prepare (cognitive 37) · ×1

InAppWebView.prepare (cognitive 37) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:78 — InAppWebView.prepare has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.printCurrentPage (cognitive 35) · ×1

InAppWebView.printCurrentPage (cognitive 35) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3225 — InAppWebView.printCurrentPage has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 5 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ServiceWorkerChannelDelegate.onMethodCall (cognitive 33) · ×1

ServiceWorkerChannelDelegate.onMethodCall (cognitive 33) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/service_worker/ServiceWorkerChannelDelegate.java:35 — ServiceWorkerChannelDelegate.onMethodCall has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 8, match/switch 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.hitTest (cognitive 33) · ×1

InAppWebView.hitTest (cognitive 33) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:242 — InAppWebView.hitTest has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (5 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · CredentialDatabaseHandler.onMethodCall (cognitive 32) · ×1

CredentialDatabaseHandler.onMethodCall (cognitive 32) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/credential_database/CredentialDatabaseHandler.java:45 — CredentialDatabaseHandler.onMethodCall has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 3 (10 pts), boolean chains 1, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppBrowserActivity.onCreate (cognitive 32) · ×1

InAppBrowserActivity.onCreate (cognitive 32) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:89 — InAppBrowserActivity.onCreate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (24 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PullToRefreshChannelDelegate.handle (cognitive 31) · ×1

PullToRefreshChannelDelegate.handle (cognitive 31) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PullToRefresh/PullToRefreshChannelDelegate.swift:20 — PullToRefreshChannelDelegate.handle has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (30 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · ASN1DERDecoder.getContentLength (cognitive 30) · ×1

ASN1DERDecoder.getContentLength (cognitive 30) flutter_inappwebview_platform_interface/lib/src/x509_certificate/asn1_decoder.dart:134 — ASN1DERDecoder.getContentLength has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 2 (8 pts), loops 1 (4 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · AndroidHeadlessInAppWebView._inferInitialSettings (cognitive 28) · ×1

AndroidHeadlessInAppWebView._inferInitialSettings (cognitive 28) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368 — AndroidHeadlessInAppWebView._inferInitialSettings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 13 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · AndroidInAppWebViewWidget._inferInitialSettings (cognitive 28) · ×1

AndroidInAppWebViewWidget._inferInitialSettings (cognitive 28) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:432 — AndroidInAppWebViewWidget._inferInitialSettings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 13 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · InAppWebView.rebuildActionMode (cognitive 28) · ×1

InAppWebView.rebuildActionMode (cognitive 28) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1662 — InAppWebView.rebuildActionMode has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 3 (4 pts), ternaries 3, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.canPerformAction (cognitive 28) · ×1

InAppWebView.canPerformAction (cognitive 28) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:322 — InAppWebView.canPerformAction has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · Util.getSupportedDocs (cognitive 27) · ×1

Util.getSupportedDocs (cognitive 27) dev_packages/generators/lib/src/util.dart:38 — Util.getSupportedDocs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebViewSettings.getRealSettings (cognitive 27) · ×1

InAppWebViewSettings.getRealSettings (cognitive 27) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java:611 — InAppWebViewSettings.getRealSettings has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · IOSHeadlessInAppWebView._inferInitialSettings (cognitive 26) · ×1

IOSHeadlessInAppWebView._inferInitialSettings (cognitive 26) flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:366 — IOSHeadlessInAppWebView._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · IOSInAppWebViewWidget._inferInitialSettings (cognitive 26) · ×1

IOSInAppWebViewWidget._inferInitialSettings (cognitive 26) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:371 — IOSInAppWebViewWidget._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · LinuxHeadlessInAppWebView._inferInitialSettings (cognitive 26) · ×1

LinuxHeadlessInAppWebView._inferInitialSettings (cognitive 26) flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:370 — LinuxHeadlessInAppWebView._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · LinuxInAppWebViewWidget._inferInitialSettings (cognitive 26) · ×1

LinuxInAppWebViewWidget._inferInitialSettings (cognitive 26) flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:304 — LinuxInAppWebViewWidget._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · MacOSHeadlessInAppWebView._inferInitialSettings (cognitive 26) · ×1

MacOSHeadlessInAppWebView._inferInitialSettings (cognitive 26) flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:359 — MacOSHeadlessInAppWebView._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · MacOSInAppWebViewWidget._inferInitialSettings (cognitive 26) · ×1

MacOSInAppWebViewWidget._inferInitialSettings (cognitive 26) flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:365 — MacOSInAppWebViewWidget._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · WindowsHeadlessInAppWebView._inferInitialSettings (cognitive 26) · ×1

WindowsHeadlessInAppWebView._inferInitialSettings (cognitive 26) flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:393 — WindowsHeadlessInAppWebView._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · WindowsInAppWebViewWidget._inferInitialSettings (cognitive 26) · ×1

WindowsInAppWebViewWidget._inferInitialSettings (cognitive 26) flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:379 — WindowsInAppWebViewWidget._inferInitialSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 12 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · ChromeCustomTabsSettings.parse (cognitive 26) · ×1

ChromeCustomTabsSettings.parse (cognitive 26) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsSettings.java:51 — ChromeCustomTabsSettings.parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (7 pts), match/switch 2 (6 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PullToRefreshChannelDelegate.onMethodCall (cognitive 26) · ×1

PullToRefreshChannelDelegate.onMethodCall (cognitive 26) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/pull_to_refresh/PullToRefreshChannelDelegate.java:27 — PullToRefreshChannelDelegate.onMethodCall has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · WebMessagePort.postMessage (cognitive 26) · ×1

WebMessagePort.postMessage (cognitive 26) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebMessagePort.java:64 — WebMessagePort.postMessage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 1 (3 pts), ternaries 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FindInteractionChannelDelegate.handle (cognitive 26) · ×1

FindInteractionChannelDelegate.handle (cognitive 26) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionChannelDelegate.swift:19 — FindInteractionChannelDelegate.handle has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (25 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · InAppBrowserWindow.setSettings (cognitive 26) · ×1

InAppBrowserWindow.setSettings (cognitive 26) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWindow.swift:302 — InAppBrowserWindow.setSettings has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 11 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · WebPlatformInAppWebViewController.getFavicons (cognitive 25) · ×1

WebPlatformInAppWebViewController.getFavicons (cognitive 25) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:353 — WebPlatformInAppWebViewController.getFavicons has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ChromeSafariBrowserManager.handle (cognitive 25) · ×1

ChromeSafariBrowserManager.handle (cognitive 25) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/SafariViewController/ChromeSafariBrowserManager.swift:26 — ChromeSafariBrowserManager.handle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · FlutterWebViewFactory.create (cognitive 24) · ×1

FlutterWebViewFactory.create (cognitive 24) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/FlutterWebViewFactory.java:28 — FlutterWebViewFactory.create has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.onScrollChanged (cognitive 24) · ×1

InAppWebView.onScrollChanged (cognitive 24) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2589 — InAppWebView.onScrollChanged has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 11 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · URLRequest.init (cognitive 24) · ×1

URLRequest.init (cognitive 24) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/URLRequest.swift:12 — URLRequest.init has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16, boolean chains 6, loops 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · WKUserContentController.sync (cognitive 24) · ×1

WKUserContentController.sync (cognitive 24) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/WKUserContentController.swift:91 — WKUserContentController.sync has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 4 (10 pts), boolean chains 1 (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · ActionBroadcastReceiver.onReceive (cognitive 23) · ×1

ActionBroadcastReceiver.onReceive (cognitive 23) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ActionBroadcastReceiver.java:18 — ActionBroadcastReceiver.onReceive has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (21 pts), boolean chains 2 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · 2.run (cognitive 23) · ×1

2.run (cognitive 23) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/JavaScriptBridgeInterface.java:112 — 2.run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (4 pts), ternaries 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppBrowserWebViewController.viewDidLoad (cognitive 23) · ×1

InAppBrowserWebViewController.viewDidLoad (cognitive 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:114 — InAppBrowserWebViewController.viewDidLoad has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.prepareAndAddUserScripts (cognitive 23) · ×1

InAppWebView.prepareAndAddUserScripts (cognitive 23) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:596 — InAppWebView.prepareAndAddUserScripts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WebViewAssetLoaderExt.fromMap (cognitive 22) · ×1

WebViewAssetLoaderExt.fromMap (cognitive 22) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebViewAssetLoaderExt.java:36 — WebViewAssetLoaderExt.fromMap has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebViewSettings.getRealSettings (cognitive 22) · ×1

InAppWebViewSettings.getRealSettings (cognitive 22) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebViewSettings.swift:123 — InAppWebViewSettings.getRealSettings has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (22 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HeadlessInAppWebView.dispose (cognitive 21) · ×1

HeadlessInAppWebView.dispose (cognitive 21) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:129 — HeadlessInAppWebView.dispose has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WebMessageChannel.postMessageForInAppWebView (cognitive 21) · ×1

WebMessageChannel.postMessageForInAppWebView (cognitive 21) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/web_message/WebMessageChannel.java:93 — WebMessageChannel.postMessageForInAppWebView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 1 (3 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.prepareAndAddUserScripts (cognitive 21) · ×1

InAppWebView.prepareAndAddUserScripts (cognitive 21) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:206 — InAppWebView.prepareAndAddUserScripts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (21 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ChromeCustomTabsActivity.prepareCustomTabs (cognitive 20) · ×1

ChromeCustomTabsActivity.prepareCustomTabs (cognitive 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsActivity.java:269 — ChromeCustomTabsActivity.prepareCustomTabs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ProxyManager.setProxyOverride (cognitive 20) · ×1

ProxyManager.setProxyOverride (cognitive 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/proxy/ProxyManager.java:69 — ProxyManager.setProxyOverride has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · JsPromptResponse.equals (cognitive 20) · ×1

JsPromptResponse.equals (cognitive 20) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsPromptResponse.java:103 — JsPromptResponse.equals has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 8, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · _CustomPlatformViewState._buildInner (cognitive 19) · ×1

_CustomPlatformViewState._buildInner (cognitive 19) flutter_inappwebview_linux/lib/src/in_app_webview/custom_platform_view.dart:472 — _CustomPlatformViewState._buildInner has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 3, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · FlutterWebView.makeInitialLoad (cognitive 19) · ×1

FlutterWebView.makeInitialLoad (cognitive 19) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/FlutterWebView.java:91 — FlutterWebView.makeInitialLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Util.getDataDetectorTypeString (cognitive 19) · ×1

Util.getDataDetectorTypeString (cognitive 19) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:94 — Util.getDataDetectorTypeString has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · X509Extension.generalName (cognitive 18) · ×1

X509Extension.generalName (cognitive 18) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_extension.dart:97 — X509Extension.generalName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), error handling 2 (5 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HeadlessInAppWebView.prepare (cognitive 18) · ×1

HeadlessInAppWebView.prepare (cognitive 18) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessInAppWebView.java:48 — HeadlessInAppWebView.prepare has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · TracingControllerChannelDelegate.onMethodCall (cognitive 18) · ×1

TracingControllerChannelDelegate.onMethodCall (cognitive 18) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/tracing/TracingControllerChannelDelegate.java:29 — TracingControllerChannelDelegate.onMethodCall has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 1 (3 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · WebResourceResponseExt.equals (cognitive 18) · ×1

WebResourceResponseExt.equals (cognitive 18) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/WebResourceResponseExt.java:137 — WebResourceResponseExt.equals has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 7, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebViewFlutterPlugin.onDetachedFromEngine (cognitive 18) · ×1

InAppWebViewFlutterPlugin.onDetachedFromEngine (cognitive 18) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/InAppWebViewFlutterPlugin.java:122 — InAppWebViewFlutterPlugin.onDetachedFromEngine has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · X509PublicKey.encoded (cognitive 17) · ×1

X509PublicKey.encoded (cognitive 17) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_public_key.dart:28 — X509PublicKey.encoded has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WebPlatformHeadlessInAppWebView._inferInitialSettings (cognitive 17) · ×1

WebPlatformHeadlessInAppWebView._inferInitialSettings (cognitive 17) flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:360 — WebPlatformHeadlessInAppWebView._inferInitialSettings has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · WebPlatformInAppWebViewWidget._inferInitialSettings (cognitive 17) · ×1

WebPlatformInAppWebViewWidget._inferInitialSettings (cognitive 17) flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview.dart:346 — WebPlatformInAppWebViewWidget._inferInitialSettings has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · FindInteractionChannelDelegate.onMethodCall (cognitive 17) · ×1

FindInteractionChannelDelegate.onMethodCall (cognitive 17) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/find_interaction/FindInteractionChannelDelegate.java:25 — FindInteractionChannelDelegate.onMethodCall has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · MyCookieManager.deleteCookies (cognitive 17) · ×1

MyCookieManager.deleteCookies (cognitive 17) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/MyCookieManager.java:327 — MyCookieManager.deleteCookies has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.longPressGestureDetected (cognitive 17) · ×1

InAppWebView.longPressGestureDetected (cognitive 17) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:187 — InAppWebView.longPressGestureDetected has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · InAppBrowserWebViewController.viewDidLoad (cognitive 17) · ×1

InAppBrowserWebViewController.viewDidLoad (cognitive 17) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:88 — InAppBrowserWebViewController.viewDidLoad has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · InAppWebView.takeScreenshot (cognitive 17) · ×1

InAppWebView.takeScreenshot (cognitive 17) flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:412 — InAppWebView.takeScreenshot has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · X509Certificate.decodeToDER (cognitive 16) · ×1

X509Certificate.decodeToDER (cognitive 16) flutter_inappwebview_platform_interface/lib/src/x509_certificate/x509_certificate.dart:69 — X509Certificate.decodeToDER has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HeadlessWebViewChannelDelegate.onMethodCall (cognitive 16) · ×1

HeadlessWebViewChannelDelegate.onMethodCall (cognitive 16) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessWebViewChannelDelegate.java:25 — HeadlessWebViewChannelDelegate.onMethodCall has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · InAppBrowserActivity.prepareView (cognitive 16) · ×1

InAppBrowserActivity.prepareView (cognitive 16) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserActivity.java:220 — InAppBrowserActivity.prepareView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PrintJobChannelDelegate.onMethodCall (cognitive 16) · ×1

PrintJobChannelDelegate.onMethodCall (cognitive 16) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobChannelDelegate.java:29 — PrintJobChannelDelegate.onMethodCall has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · MyCookieManager.deleteCookie (cognitive 16) · ×1

MyCookieManager.deleteCookie (cognitive 16) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:223 — MyCookieManager.deleteCookie has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FindInteractionController.findNext (cognitive 16) · ×1

FindInteractionController.findNext (cognitive 16) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionController.swift:105 — FindInteractionController.findNext has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InAppWebView.takeScreenshot (cognitive 16) · ×1

InAppWebView.takeScreenshot (cognitive 16) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:879 — InAppWebView.takeScreenshot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · NSAttributedString.fromMap (cognitive 16) · ×1

NSAttributedString.fromMap (cognitive 16) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/NSAttributedString.swift:12 — NSAttributedString.fromMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D22 · Internal API Consistency · Duplicate operation with inconsistent naming and signature. 'evaluateJavaScript' and 'evaluateJavascript' differ only by case (camelCase vs PascalCase for the method name), which is a common source of confusion in Swift/ObjC interop. Furthermore, the 'evaluateJavascript' variant drops the Error parameter from the completion handler, implying different error handling semantics or a legacy wrapper, creating ambiguity for the caller. · ×1

Duplicate operation with inconsistent naming and signature. 'evaluateJavaScript' and 'evaluateJavascript' differ only by case (camelCase vs PascalCase for the method name), which is a common source of confusion in Swift/ObjC interop. Furthermore, the 'evaluateJavascript' variant drops the Error parameter from the completion handler, implying different error handling semantics or a legacy wrapper, creating ambiguity for the caller. — Remove 'evaluateJavascript'. Standardize on 'evaluateJavaScript' with a consistent signature that includes error handling. (signatures: InAppWebView.evaluateJavaScript(String, completionHandler: ((Any?, Error?) -> Void)?) | InAppWebView.evaluateJavascript(String, completionHandler: ((Any?) -> Void)?))

D22 · Internal API Consistency · Duplicate operation with inconsistent signatures. Two methods named 'close' exist · ×1

Duplicate operation with inconsistent signatures. Two methods named 'close' exist: one with an optional completion handler and one without. This forces the caller to guess which overload is appropriate or handle the lack of callback in the no-arg version, violating the principle of least surprise. — Unify into a single method 'close(completionHandler: (() -> Void)? = nil)' or provide distinct names like 'closeAsync' and 'closeSync' if the behavior is fundamentally different. (signatures: InAppBrowserWebViewController.close(completion: (() -> Void)?) | InAppBrowserWebViewController.close())

D22 · Internal API Consistency · Conflicting lifecycle management. 'disposeAndGetFlutterWebView' implies a transition of ownership/state, while 'dispose' has an overloaded version with a boolean flag and a no-arg version. The intent of 'disposeWebView · ×1

Conflicting lifecycle management. 'disposeAndGetFlutterWebView' implies a transition of ownership/state, while 'dispose' has an overloaded version with a boolean flag and a no-arg version. The intent of 'disposeWebView: Bool' is unclear compared to the explicit 'disposeAndGet...' method. It is unclear if 'dispose()' is a no-op or performs a default action. — Clarify the lifecycle. If 'disposeAndGetFlutterWebView' is the primary path for headless views, remove the ambiguous 'dispose(disposeWebView: Bool)' overload or rename it to clearly indicate it is a partial cleanup. (signatures: HeadlessInAppWebView.disposeAndGetFlutterWebView(withFrame: CGRect): FlutterWebViewController? | HeadlessInAppWebView.dispose(disposeWebView: Bool) | HeadlessInAppWebView.dispose())

D22 · Internal API Consistency · Inconsistent navigation API surface. 'InAppWebView' uses a single 'goBackOrForward(steps · ×1

Inconsistent navigation API surface. 'InAppWebView' uses a single 'goBackOrForward(steps: Int)' method, while 'InAppBrowserWebViewController' provides separate 'goBack()' and 'goForward()' methods. This forces developers to remember different APIs for similar concepts depending on the specific controller type. — Standardize on a single navigation API pattern across all web view controllers, e.g., 'goBack()' and 'goForward()' or a unified 'navigate(steps: Int)'. (signatures: InAppWebView.goBackOrForward(steps: Int) | InAppBrowserWebViewController.goBackOrForward(steps: Int) | InAppBrowserWebViewController.goBack() | InAppBrowserWebViewController.goForward())

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

D35 · Change Coupling · Change-coupling hub · ×1

Change-coupling hub: in_app_browser.dart → chrome_safari_browser.dart, headless_in_app_webview.dart, in_app_webview.dart flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart — `flutter_inappwebview/lib/src/in_app_browser/in_app_browser.dart` changes together with 3 other files — `flutter_inappwebview/lib/src/chrome_safari_browser/chrome_safari_browser.dart`, `flutter_inappwebview/lib/src/in_app_webview/headless_in_app_webview.dart`, `flutter_inappwebview/lib/src/in_app_webview/in_app_webview.dart` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.

D4 · Code Duplication · Near-duplicate member family (11 members, 29 shared lines) · ×1

Near-duplicate member family (11 members, 29 shared lines) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368-415 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:432-479 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:366-409 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:371-414 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:370-413 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:304-347 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:359-402 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:365-408 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:360-393 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:393-436 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:379-422 — These 11 members are variants of one another: a block of 29 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.

D4 · Code Duplication · Near-duplicate member family (8 members, 11 shared lines) · ×1

Near-duplicate member family (8 members, 11 shared lines) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:120 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:120-133 | flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:135-148 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:119-132 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:134-147 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:119-132 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:134-147 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:109-122 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:124-137 — These 8 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.

D4 · Code Duplication · Near-duplicate member family (6 members, 52 shared lines) · ×1

Near-duplicate member family (6 members, 52 shared lines) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864-2018 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1844-1998 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1935-2091 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1851-2005 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:353-438 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2153-2307 — These 6 members are variants of one another: a block of 52 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.

D4 · Code Duplication · Near-duplicate member family (6 members, 28 shared lines) · ×1

Near-duplicate member family (6 members, 28 shared lines) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:327 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:327-366 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:325-364 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:326-368 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:318-357 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:319-358 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:345-391 — These 6 members are variants of one another: a block of 28 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.

D4 · Code Duplication · Near-duplicate member family (4 members, 22 shared lines) · ×1

Near-duplicate member family (4 members, 22 shared lines) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:292 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:292-340 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:228-266 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:287-335 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:311-349 — These 4 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (4 members, 11 shared lines) · ×1

Near-duplicate member family (4 members, 11 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1666 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1666-1714 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1721-1752 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1000-1048 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1055-1086 — These 4 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (3 members, 26 shared lines) · ×1

Near-duplicate member family (3 members, 26 shared lines) flutter_inappwebview_android/lib/src/cookie_manager.dart:75 — flutter_inappwebview_android/lib/src/cookie_manager.dart:75-108 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:78-129 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:78-129 — These 3 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.

D4 · Code Duplication · Near-duplicate member pair (184 shared lines) · ×1

Near-duplicate member pair (184 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2947-3194 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2158-2406 — These two members are variants of one another: 184 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (126 shared lines) · ×1

Near-duplicate member pair (126 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22-162 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:21-162 — These two members are variants of one another: 126 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (54 shared lines) · ×1

Near-duplicate member pair (54 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:167-224 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:96-153 — These two members are variants of one another: 54 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (43 shared lines) · ×1

Near-duplicate member pair (43 shared lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:32-80 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:32-80 — These two members are variants of one another: 43 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Edited copy of a member (135 corresponding lines) · ×1

Edited copy of a member (135 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:28 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:28-162 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptFetchRequestJS.swift:28-162 — These two members are one piece of code written twice and then edited apart: 135 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1

Edited copy of a member (15 corresponding lines) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:126 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/ProxyManager.swift:126-140 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/ProxyManager.swift:126-140 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1

Edited copy of a member (18 corresponding lines) flutter_inappwebview_android/lib/src/cookie_manager.dart:183 — flutter_inappwebview_android/lib/src/cookie_manager.dart:183-202 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:213-237 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×1

Edited copy of a member (7 corresponding lines) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java:170 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserManager.java:170-204 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/FlutterWebView.java:43-83 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (14 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:154 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:154-194 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:360-447 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:450-506 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:510-580 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:595-638 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:746-779 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:153-193 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:371-458 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:461-517 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:521-591 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:609-664 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:772-805 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:23-57 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:60-94 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.

D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (12 members, 50+ identical tokens) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2430 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2430-2441 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2443-2454 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2403-2414 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2416-2427 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1551-1562 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1564-1575 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2410-2421 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2423-2434 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:748-759 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:761-772 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2751-2762 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2764-2775 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.

D4 · Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (11 members, 50+ identical tokens) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1782 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1782-1826 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1828-1871 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1916-1950 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1952-2017 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2092-2319 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2689-2723 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1116-1160 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1205-1239 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1241-1306 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1372-1597 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1900-1934 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.

D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (7 members, 50+ identical tokens) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:825 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:825-836 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:846-857 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:867-879 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:889-899 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1001-1012 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1152-1162 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1346-1356 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.

D4 · Code Duplication · Duplicated block (373 lines × 4) · ×1

Duplicated block (373 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:407 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:407-779 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:408-780 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:415-787 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:453-825 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (296 lines × 4) · ×1

Duplicated block (296 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1057 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1057-1352 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1058-1353 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1065-1360 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1161-1456 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (155 lines × 4) · ×1

Duplicated block (155 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:858 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:858-1012 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:859-1013 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:866-1020 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:920-1074 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (112 lines × 5) · ×1

Duplicated block (112 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1659 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1659-1770 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1639-1750 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1008-1119 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1646-1757 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1883-1994 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (93 lines × 4) · ×1

Duplicated block (93 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1376 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1376-1468 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1377-1469 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1384-1476 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1480-1572 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (69 lines × 6) · ×1

Duplicated block (69 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2649 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2649-2717 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2621-2689 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2218-2286 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2549-2617 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:829-897 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2876-2944 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (53 lines × 5) · ×1

Duplicated block (53 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1512 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1512-1564 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1513-1565 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:851-903 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1520-1572 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1616-1668 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (48 lines × 5) · ×1

Duplicated block (48 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1880 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1880-1927 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1860-1907 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1867-1914 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:369-416 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2169-2216 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (47 lines × 5) · ×1

Duplicated block (47 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1611 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1611-1657 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1591-1637 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:960-1006 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1598-1644 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1835-1881 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (42 lines × 4) · ×1

Duplicated block (42 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:777 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:777-818 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:778-819 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:785-826 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:839-880 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (39–40 lines × 5) · ×1

Duplicated block (39–40 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1346 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1346-1385 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1347-1386 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:713-751 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1354-1393 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1450-1489 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (40 lines × 3) · ×1

Duplicated block (40 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:131 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:131-170 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:131-170 | flutter_inappwebview_web/lib/src/cookie_manager.dart:118-157 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (37 lines × 5) · ×1

Duplicated block (37 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2719 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2719-2755 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2691-2727 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2619-2655 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:899-935 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2946-2982 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (37 lines × 4) · ×1

Duplicated block (37 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:820 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:820-856 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:821-857 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:828-864 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:882-918 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (37 lines × 3) · ×1

Duplicated block (37 lines × 3) flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:79 — flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart:79-115 | flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart:79-115 | flutter_inappwebview_windows/lib/src/web_storage/web_storage_manager.dart:79-115 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_storage/web_storage_manager.dart` and `flutter_inappwebview_macos/lib/src/web_storage/web_storage_manager.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (35 lines × 6) · ×1

Duplicated block (35 lines × 6) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:139 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:139-173 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:141-175 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:139-173 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (33 lines × 6) · ×1

Duplicated block (33 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2024 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2024-2056 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2004-2036 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2097-2129 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2011-2043 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:444-476 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2344-2376 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (33 lines × 5) · ×1

Duplicated block (33 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1929 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1929-1961 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1909-1941 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2002-2034 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1916-1948 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2218-2250 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (32 lines × 6) · ×1

Duplicated block (32 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1773 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1773-1804 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1753-1784 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1168-1199 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1760-1791 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:278-309 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2039-2070 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (31 lines × 10) · ×1

Duplicated block (31 lines × 10) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:373 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:373-403 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:437-467 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:371-401 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:376-406 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:375-405 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:309-339 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:364-394 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:370-400 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:398-428 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:384-414 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (31 lines × 5) · ×1

Duplicated block (31 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:207 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:207-237 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:208-238 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:199-229 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:215-245 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:208-238 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (31 lines × 3) · ×1

Duplicated block (31 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:233 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:233-263 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:233-263 | flutter_inappwebview_web/lib/src/cookie_manager.dart:191-221 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (4–28 lines × 3) · ×1

Duplicated block (4–28 lines × 3) flutter_inappwebview_android/lib/src/cookie_manager.dart:160 — flutter_inappwebview_android/lib/src/cookie_manager.dart:160-163 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:293-320 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:293-320 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (27 lines × 6) · ×1

Duplicated block (27 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1920 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1920-1946 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1900-1926 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1993-2019 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1907-1933 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:409-435 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2209-2235 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (26 lines × 5) · ×1

Duplicated block (26 lines × 5) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:222 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:222-247 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:221-246 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:231-256 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:220-245 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:231-256 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1

Duplicated block (26 lines × 3) flutter_inappwebview_ios/lib/src/cookie_manager.dart:266 — flutter_inappwebview_ios/lib/src/cookie_manager.dart:266-291 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:266-291 | flutter_inappwebview_web/lib/src/cookie_manager.dart:224-249 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/cookie_manager.dart` and `flutter_inappwebview_macos/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 414 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (25 lines × 6) · ×1

Duplicated block (25 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1864-1888 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1844-1868 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1935-1959 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1851-1875 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:353-377 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2153-2177 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (24–25 lines × 5) · ×1

Duplicated block (24–25 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1825 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1825-1848 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1805-1828 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1812-1835 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:324-348 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2114-2137 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23 lines × 6) · ×1

Duplicated block (23 lines × 6) flutter_inappwebview_android/lib/src/cookie_manager.dart:123 — flutter_inappwebview_android/lib/src/cookie_manager.dart:123-145 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:209-231 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:428-450 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:209-231 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:428-450 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:148-170 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (21–23 lines × 5) · ×1

Duplicated block (21–23 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1396 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1396-1416 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1397-1417 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:758-780 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1404-1424 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1500-1520 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23 lines × 5) · ×1

Duplicated block (23 lines × 5) flutter_inappwebview_android/lib/src/web_message/web_message_listener.dart:91 — flutter_inappwebview_android/lib/src/web_message/web_message_listener.dart:91-113 | flutter_inappwebview_ios/lib/src/web_message/web_message_listener.dart:90-112 | flutter_inappwebview_linux/lib/src/web_message/web_message_listener.dart:88-110 | flutter_inappwebview_macos/lib/src/web_message/web_message_listener.dart:90-112 | flutter_inappwebview_windows/lib/src/web_message/web_message_listener.dart:89-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.

D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1

Duplicated block (22–23 lines × 2) dev_packages/generators/lib/src/supported_platforms_generator.dart:125 — dev_packages/generators/lib/src/supported_platforms_generator.dart:125-146 | dev_packages/generators/lib/src/supported_platforms_generator.dart:222-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (21 lines × 5) · ×1

Duplicated block (21 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1963 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1963-1983 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1943-1963 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:2036-2056 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1950-1970 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2252-2272 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (21 lines × 4) · ×1

Duplicated block (21 lines × 4) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1035 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1035-1055 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1036-1056 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1043-1063 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1119-1139 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (20 lines × 5) · ×1

Duplicated block (20 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:460 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:460-479 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:461-480 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:456-475 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:468-487 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:506-525 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (19 lines × 6) · ×1

Duplicated block (19 lines × 6) flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:109 — flutter_inappwebview_android/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_linux/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_macos/lib/src/web_storage/web_storage.dart:109-127 | flutter_inappwebview_web/lib/src/web_storage/web_storage.dart:111-129 | flutter_inappwebview_windows/lib/src/web_storage/web_storage.dart:109-127 — before extracting anything, compare `flutter_inappwebview_android/lib/src/web_storage/web_storage.dart` and `flutter_inappwebview_ios/lib/src/web_storage/web_storage.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 8) · ×1

Duplicated block (18 lines × 8) dev_packages/generators/lib/src/exchangeable_object_generator.dart:976 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:976-993 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:999-1016 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1052-1069 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1075-1092 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1098-1115 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1121-1138 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1144-1161 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:1167-1184 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (18 lines × 5) · ×1

Duplicated block (18 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:357 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:357-374 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:358-375 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:262-279 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:365-382 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:403-420 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1

Duplicated block (18 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1573 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1573-1590 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1580-1597 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1676-1693 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16–17 lines × 10) · ×1

Duplicated block (16–17 lines × 10) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:92 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:92-108 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:134-149 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:93-109 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:135-150 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:90-106 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:132-147 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:93-109 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:135-150 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:96-112 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:138-153 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 11) · ×1

Duplicated block (16 lines × 11) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:395 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:395-410 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:459-474 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:393-408 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:398-413 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:397-412 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:331-346 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:386-401 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:392-407 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:377-392 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:420-435 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:406-421 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 6) · ×1

Duplicated block (16 lines × 6) flutter_inappwebview_android/lib/src/cookie_manager.dart:75 — flutter_inappwebview_android/lib/src/cookie_manager.dart:75-90 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:78-93 | flutter_inappwebview_linux/lib/src/cookie_manager/cookie_manager.dart:48-63 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:78-93 | flutter_inappwebview_web/lib/src/cookie_manager.dart:81-96 | flutter_inappwebview_windows/lib/src/cookie_manager.dart:90-105 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1

Duplicated block (14–16 lines × 2) dev_packages/generators/lib/src/exchangeable_object_generator.dart:527 — dev_packages/generators/lib/src/exchangeable_object_generator.dart:527-542 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:656-669 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (14–15 lines × 6) · ×1

Duplicated block (14–15 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:327 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:327-340 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:325-338 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:327-341 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:318-331 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:319-332 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:345-358 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–15 lines × 6) · ×1

Duplicated block (13–15 lines × 6) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2362 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2362-2376 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2335-2349 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1589-1601 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2342-2356 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:720-734 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2683-2697 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (11–15 lines × 2) · ×1

Duplicated block (11–15 lines × 2) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:289 — dev_packages/generators/lib/src/exchangeable_enum_generator.dart:289-299 | dev_packages/generators/lib/src/exchangeable_enum_generator.dart:313-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1

Duplicated block (13–14 lines × 3) dev_packages/generators/lib/src/supported_platforms_generator.dart:121 — dev_packages/generators/lib/src/supported_platforms_generator.dart:121-133 | dev_packages/generators/lib/src/supported_platforms_generator.dart:218-231 | dev_packages/generators/lib/src/supported_platforms_generator.dart:300-313 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1

Duplicated block (12–14 lines × 2) dev_packages/generators/lib/src/exchangeable_enum_generator.dart:134 — dev_packages/generators/lib/src/exchangeable_enum_generator.dart:134-145 | dev_packages/generators/lib/src/exchangeable_object_generator.dart:177-190 — before extracting anything, compare `dev_packages/generators/lib/src/exchangeable_enum_generator.dart` and `dev_packages/generators/lib/src/exchangeable_object_generator.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13 lines × 11) · ×1

Duplicated block (13 lines × 11) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:368-380 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart:432-444 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:366-378 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:371-383 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:370-382 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview.dart:304-316 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:359-371 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:365-377 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:360-372 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:393-405 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview.dart:379-391 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13 lines × 10) · ×1

Duplicated block (13 lines × 10) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2488 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2488-2500 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2504-2516 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2461-2473 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2477-2489 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2468-2480 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2484-2496 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:786-798 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:802-814 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2809-2821 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2825-2837 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10 lines × 12) · ×1

Duplicated block (10 lines × 12) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2432 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2432-2441 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2445-2454 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2405-2414 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2418-2427 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1553-1562 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1566-1575 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2412-2421 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2425-2434 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:750-759 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:763-772 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2753-2762 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2766-2775 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9–10 lines × 10) · ×1

Duplicated block (9–10 lines × 10) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:337 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:337-345 | flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:365-374 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:336-344 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:364-373 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:346-354 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:374-383 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:335-343 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:363-372 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:346-354 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:374-383 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8–10 lines × 8) · ×1

Duplicated block (8–10 lines × 8) flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:334 — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:334-342 | flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart:332-340 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart:294-303 | flutter_inappwebview_linux/lib/src/in_app_webview/headless_in_app_webview.dart:334-341 | flutter_inappwebview_macos/lib/src/in_app_webview/headless_in_app_webview.dart:325-333 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview.dart:289-298 | flutter_inappwebview_web/lib/src/in_app_webview/headless_in_app_webview.dart:326-334 | flutter_inappwebview_windows/lib/src/in_app_webview/headless_in_app_webview.dart:352-360 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1

Duplicated block (8–9 lines × 5) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2892 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2892-2899 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2876-2884 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1886-1893 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2804-2812 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3196-3204 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 12) · ×1

Duplicated block (8 lines × 12) flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2253 — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2253-2260 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2283-2290 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2226-2233 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2256-2263 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1387-1394 | flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1408-1415 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2233-2240 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2263-2270 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:645-652 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:675-682 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2573-2580 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2603-2610 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 131 separate duplicated blocks between them, totalling at least 2931 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6–7 lines × 10) · ×1

Duplicated block (6–7 lines × 10) flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:238 — flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart:238-243 | flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:2131-2137 | flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart:237-242 | flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2111-2117 | flutter_inappwebview_linux/lib/src/in_app_browser/in_app_browser.dart:247-252 | flutter_inappwebview_macos/lib/src/in_app_browser/in_app_browser.dart:236-241 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2118-2124 | flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:551-557 | flutter_inappwebview_windows/lib/src/in_app_browser/in_app_browser.dart:247-252 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:2451-2457 — before extracting anything, compare `flutter_inappwebview_android/lib/src/in_app_browser/in_app_browser.dart` and `flutter_inappwebview_ios/lib/src/in_app_browser/in_app_browser.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (4–7 lines × 7) · ×1

Duplicated block (4–7 lines × 7) flutter_inappwebview_android/lib/src/cookie_manager.dart:98 — flutter_inappwebview_android/lib/src/cookie_manager.dart:98-101 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:113-119 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:367-373 | flutter_inappwebview_ios/lib/src/cookie_manager.dart:407-413 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:113-119 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:367-373 | flutter_inappwebview_macos/lib/src/cookie_manager.dart:407-413 — before extracting anything, compare `flutter_inappwebview_android/lib/src/cookie_manager.dart` and `flutter_inappwebview_ios/lib/src/cookie_manager.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 8) · ×1

Duplicated block (6 lines × 8) flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:122 — flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:122-127 | flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart:137-142 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:121-126 | flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart:136-141 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:121-126 | flutter_inappwebview_macos/lib/src/http_auth_credentials_database.dart:136-141 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:111-116 | flutter_inappwebview_windows/lib/src/http_auth_credentials_database.dart:126-131 — before extracting anything, compare `flutter_inappwebview_android/lib/src/http_auth_credentials_database.dart` and `flutter_inappwebview_ios/lib/src/http_auth_credentials_database.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 9) · ×1

Duplicated block (6 lines × 9) flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:89 — flutter_inappwebview_android/lib/src/print_job/print_job_controller.dart:89-94 | flutter_inappwebview_ios/lib/src/print_job/print_job_controller.dart:85-90 | flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart:160-165 | flutter_inappwebview_linux/lib/src/webview_environment/webview_environment.dart:148-153 | flutter_inappwebview_macos/lib/src/print_job/print_job_controller.dart:78-83 | flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart:162-167 | flutter_inappwebview_windows/lib/src/print_job/print_job_controller.dart:69-74 | flutter_inappwebview_windows/lib/src/web_notification/web_notification_controller.dart:95-100 | flutter_inappwebview_windows/lib/src/webview_environment/webview_environment.dart:172-177 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/web_authentication_session/web_authenticate_session.dart` and `flutter_inappwebview_macos/lib/src/web_authentication_session/web_authenticate_session.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1

Duplicated block (8 lines × 3) flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2764 — flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:2764-2771 | flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:2692-2699 | flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:3025-3032 — before extracting anything, compare `flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart` and `flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart` as WHOLE FILES: this scan already matched 143 separate duplicated blocks between them, totalling at least 3029 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (51–55 lines × 2) · ×1

Duplicated block (51–55 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:118 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:118-172 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:176-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:173` calls `FLAG_VARIABLE_FOR_INTERCEPT_ONLY_ASYNC_AJAX_REQUESTS_JS_SOURCE`, `FLAG_VARIABLE_FOR_SHOULD_INTERCEPT_AJAX_REQUEST_JS_SOURCE`, `FLAG_VARIABLE_FOR_ON_AJAX_READY_STATE_CHANGE` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:227` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (53 lines × 2) · ×1

Duplicated block (53 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:511 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:511-563 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:522-574 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:511` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (43–45 lines × 2) · ×1

Duplicated block (43–45 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:252 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:252-294 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:302-346 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:295` calls `get_JAVASCRIPT_BRIDGE_NAME` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:347` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×1

Duplicated block (35–36 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:60 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:60-95 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:135-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:170` calls `JAVASCRIPT_UTIL_VAR_NAME` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:96` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1

Duplicated block (33–34 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:259 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:259-291 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:127-160 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (30–31 lines × 3) · ×1

Duplicated block (30–31 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:272 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:272-302 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:136-165 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:218-248 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:272` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:135` calls `JAVASCRIPT_UTIL_VAR_NAME` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:271` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×1

Duplicated block (29–30 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:123 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:123-151 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/JavaScriptBridgeJS.java:175-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1

Duplicated block (17–19 lines × 2) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:249 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java:249-265 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java:98-116 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptAjaxRequestJS.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/plugin_scripts_js/InterceptFetchRequestJS.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1

Duplicated block (17 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:275 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:275-291 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:370-386 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:490-506 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:591-607 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:275` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1

Duplicated block (8–10 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1294 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1294-1301 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1306-1313 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1330-1339 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1330` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1340` calls `replaceAll` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1301` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1

Duplicated block (9–10 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:269 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:269-278 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:357-365 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:578-586 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (8 lines × 14) · ×1

Duplicated block (8 lines × 14) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:182 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:182-189 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:435-442 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:494-501 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:568-575 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:626-633 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:767-774 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:181-188 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:446-453 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:505-512 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:579-586 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:652-659 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:793-800 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:45-52 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:82-89 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 642 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:182` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClient.java:179` calls `allowShouldOverrideUrlLoading` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewRenderProcessClient.java:41` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1

Duplicated block (8 lines × 7) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:826 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:826-833 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:847-854 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:868-875 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:890-897 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1002-1009 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1153-1160 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1347-1354 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `JsAlertCallback` in one and `JsConfirmCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:877` calls `put` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:835` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (7 lines × 9) · ×1

Duplicated block (7 lines × 9) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:189 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:189-195 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/print_job/PrintJobChannelDelegate.java:69-75 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:754-760 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:952-958 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:985-991 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1015-1021 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1058-1064 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1136-1142 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1192-1198 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (3–5 lines × 4) · ×1

Duplicated block (3–5 lines × 4) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsAlertResponse.java:74 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsAlertResponse.java:74-76 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:87-91 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java:87-91 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsPromptResponse.java:112-116 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsPromptResponse.java:117` calls `equals` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:91` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (3–5 lines × 3) · ×1

Duplicated block (3–5 lines × 3) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:97 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:97-101 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java:97-101 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsPromptResponse.java:125-127 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsConfirmResponse.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/types/JsBeforeUnloadResponse.java:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (6 lines × 15) · ×1

Duplicated block (6 lines × 15) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:142 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:142-147 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:149-154 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:156-161 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:171-176 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:207-212 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/headless_in_app_webview/HeadlessWebViewChannelDelegate.java:59-64 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserChannelDelegate.java:18-23 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/in_app_browser/InAppBrowserChannelDelegate.java:33-38 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/pull_to_refresh/PullToRefreshChannelDelegate.java:111-116 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:796-801 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:803-808 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:810-815 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:918-923 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:944-949 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1358-1363 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (7 lines × 11) · ×1

Duplicated block (7 lines × 11) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:163 — flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:163-169 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:214-220 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:222-228 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:230-236 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java:238-244 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:960-966 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:968-974 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:976-982 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1041-1047 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1049-1055 | flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1183-1189 — before extracting anything, compare `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/chrome_custom_tabs/ChromeCustomTabsChannelDelegate.java` and `flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (93 lines × 2) · ×1

Duplicated block (93 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:206 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:206-298 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:203-295 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (69 lines × 2) · ×1

Duplicated block (69 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2162 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2162-2230 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1442-1510 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2162` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (66 lines × 2) · ×1

Duplicated block (66 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:86 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:86-151 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:86-151 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (65 lines × 2) · ×1

Duplicated block (65 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20-84 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:20-84 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (58 lines × 2) · ×1

Duplicated block (58 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:19 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:19-76 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionChannelDelegate.swift:19-76 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/FindInteraction/FindInteractionChannelDelegate.swift` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/FindInteraction/FindInteractionChannelDelegate.swift:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1

Duplicated block (46 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2451 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2451-2496 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1738-1783 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1

Duplicated block (44 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:82 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift:82-125 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift:82-125 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebMessage/WebMessageListener.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebMessage/WebMessageListener.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (36 lines × 3) · ×1

Duplicated block (36 lines × 3) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1791 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1791-1826 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1836-1871 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1125-1160 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1791` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (1–33 lines × 11) · ×1

Duplicated block (1–33 lines × 11) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3026 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3026-3058 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3059-3059 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3072-3072 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3086-3086 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3103-3103 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2237-2269 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2270-2270 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2283-2283 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2297-2297 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2314-2314 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2344-2344 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3026` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3058` calls `data` and `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3059` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1

Duplicated block (32 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:153 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:153-184 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:153-184 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:153` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1

Duplicated block (27–28 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22-48 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:21-48 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (2–25 lines × 4) · ×1

Duplicated block (2–25 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1484 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1484-1508 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1515-1516 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:841-865 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:872-873 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1484` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1484` calls `substring`, `NSRange` and `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1515` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1

Duplicated block (23–24 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:121 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:121-144 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:120-142 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (23 lines × 4) · ×1

Duplicated block (23 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:155 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:155-177 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:196-218 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:153-175 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:194-216 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (17 lines × 8) · ×1

Duplicated block (17 lines × 8) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:995 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:995-1011 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1027-1043 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1059-1075 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1172-1188 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:948-964 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:980-996 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1012-1028 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1125-1141 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 709 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `ReceivedHttpAuthRequestCallback` in one and `ReceivedServerTrustAuthRequestCallback` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (3–14 lines × 3) · ×1

Duplicated block (3–14 lines × 3) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3089 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3089-3102 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2300-2313 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:2341-2343 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:3089` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (2–14 lines × 4) · ×1

Duplicated block (2–14 lines × 4) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:188 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:188-189 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:211-224 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:117-118 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift:140-153 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Util.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Util.swift:211` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (10–11 lines × 6) · ×1

Duplicated block (10–11 lines × 6) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:153 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:153-163 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/FlutterWebViewController.swift:115-125 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1363-1372 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift:109-119 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/FlutterWebViewController.swift:104-114 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:743-752 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppBrowser/InAppBrowserWebViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppBrowser/InAppBrowserWebViewController.swift:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1

Duplicated block (11 lines × 6) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2156 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2156-2166 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2225-2235 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2292-2302 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1436-1446 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1505-1515 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1570-1580 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2156` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (7 lines × 8) · ×1

Duplicated block (7 lines × 8) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2161 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2161-2167 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2230-2236 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2297-2303 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2705-2711 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1441-1447 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1510-1516 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1575-1581 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1916-1922 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (6–7 lines × 5) · ×1

Duplicated block (6–7 lines × 5) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:24 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:24-29 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/SafariViewController/ChromeSafariBrowserManager.swift:26-32 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/WebAuthenticationSession/WebAuthenticationSessionManager.swift:25-31 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift:23-28 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/WebAuthenticationSession/WebAuthenticationSessionManager.swift:25-31 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/MyCookieManager.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/MyCookieManager.swift:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (6–7 lines × 3) · ×1

Duplicated block (6–7 lines × 3) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift:25 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift:25-31 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/URLAuthenticationChallenge.swift:11-16 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthenticationChallenge.swift:25-31 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/Types/HttpAuthenticationChallenge.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/Types/HttpAuthenticationChallenge.swift:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1

Duplicated block (6 lines × 10) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1932 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1932-1937 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2161-2166 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2230-2235 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2297-2302 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:2705-2710 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1221-1226 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1441-1446 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1510-1515 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1575-1580 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1916-1921 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1932` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (5–6 lines × 6) · ×1

Duplicated block (5–6 lines × 6) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:64 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:64-69 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:80-85 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift:116-121 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:64-68 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:80-84 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift:116-120 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/CredentialDatabase.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/CredentialDatabase.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (2–5 lines × 3) · ×1

Duplicated block (2–5 lines × 3) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1783 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1783-1787 | flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1832-1833 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1117-1121 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift` as WHOLE FILES: this scan already matched 85 separate duplicated blocks between them, totalling at least 1539 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1783` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1832` calls `escaping` and `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1783` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (127 lines × 2) · ×1

Duplicated block (127 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:57 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:57-183 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindTextHighlightJS.swift:57-183 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/FindTextHighlightJS.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/FindTextHighlightJS.swift:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (80 lines × 2) · ×1

Duplicated block (80 lines × 2) flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:81 — flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:81-160 | flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptFetchRequestJS.swift:81-160 — before extracting anything, compare `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift` and `flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/PluginScriptsJS/InterceptFetchRequestJS.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/PluginScriptsJS/InterceptFetchRequestJS.swift:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Near-duplicate member family (4 members, 62 shared lines) · ×1

Near-duplicate member family (4 members, 62 shared lines) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1632 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1632-1709 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1114-1191 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:968-1045 | flutter_inappwebview/example/lib/widgets/common/event_log_card.dart:26-109 — These 4 members are variants of one another: a block of 62 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member pair (80 shared lines) · ×1

Near-duplicate member pair (80 shared lines) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:49 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:49-145 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:65-154 — These two members are variants of one another: 80 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (55 shared lines) · ×1

Near-duplicate member pair (55 shared lines) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:613 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:613-691 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1007-1085 — These two members are variants of one another: 55 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (45 shared lines) · ×1

Near-duplicate member pair (45 shared lines) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1629 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1629-1709 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:850-928 — These two members are variants of one another: 45 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1

Edited copy of a member (51 corresponding lines) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:299 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:299-362 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:345-408 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (13 members, 50+ identical tokens) flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:811 — flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:811-878 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:880-932 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:934-975 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:977-1013 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1015-1069 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:662-733 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:735-769 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:771-799 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:801-853 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:743-785 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:787-886 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:888-934 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:936-964 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.

D4 · Code Duplication · Duplicated block (61–62 lines × 2) · ×1

Duplicated block (61–62 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:237 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:237-297 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:282-343 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (47 lines × 3) · ×1

Duplicated block (47 lines × 3) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1632 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1632-1678 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1114-1160 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:968-1014 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (34 lines × 4) · ×1

Duplicated block (34 lines × 4) flutter_inappwebview_android/example/lib/main.dart:137 — flutter_inappwebview_android/example/lib/main.dart:137-170 | flutter_inappwebview_ios/example/lib/main.dart:134-167 | flutter_inappwebview_macos/example/lib/main.dart:109-142 | flutter_inappwebview_web/example/lib/main.dart:97-130 — before extracting anything, compare `flutter_inappwebview_android/example/lib/main.dart` and `flutter_inappwebview_ios/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (29–31 lines × 2) · ×1

Duplicated block (29–31 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:314 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:314-342 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:180-210 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (26 lines × 8) · ×1

Duplicated block (26 lines × 8) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:157 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:157-182 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:145-170 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:664-689 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:482-507 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:611-636 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:531-556 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:291-316 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:382-407 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22–26 lines × 2) · ×1

Duplicated block (22–26 lines × 2) flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:159 — flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:159-180 | flutter_inappwebview/example/lib/screens/webview_tester_screen.dart:604-629 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_tester_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22–25 lines × 2) · ×1

Duplicated block (22–25 lines × 2) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1371 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1371-1392 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1412-1436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1

Duplicated block (24–25 lines × 2) flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1741 — flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1741-1765 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:682-705 — before extracting anything, compare `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` and `flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (24 lines × 6) · ×1

Duplicated block (24 lines × 6) flutter_inappwebview_android/example/lib/main.dart:158 — flutter_inappwebview_android/example/lib/main.dart:158-181 | flutter_inappwebview_ios/example/lib/main.dart:155-178 | flutter_inappwebview_linux/example/lib/main.dart:349-372 | flutter_inappwebview_macos/example/lib/main.dart:130-153 | flutter_inappwebview_web/example/lib/main.dart:118-141 | flutter_inappwebview_windows/example/lib/main.dart:623-646 — before extracting anything, compare `flutter_inappwebview_android/example/lib/main.dart` and `flutter_inappwebview_ios/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (24 lines × 4) · ×1

Duplicated block (24 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1669 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1669-1692 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1151-1174 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:1005-1028 | flutter_inappwebview/example/lib/widgets/common/event_log_card.dart:69-92 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1

Duplicated block (23 lines × 3) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:773 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:773-795 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:728-750 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:544-566 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1

Duplicated block (21–22 lines × 2) flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:556 — flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:556-577 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:696-716 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (20–22 lines × 2) · ×1

Duplicated block (20–22 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:504 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:504-523 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:827-848 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:140 — flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:140-157 | flutter_inappwebview/example/lib/screens/webview_tester_screen.dart:563-581 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_tester_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 9) · ×1

Duplicated block (18 lines × 9) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:725 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:725-742 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:891-908 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:1024-1041 | flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:1196-1213 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:831-848 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1042-1059 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1164-1181 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1277-1294 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1521-1538 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1

Duplicated block (17–18 lines × 2) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:629 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:629-646 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:1023-1039 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15–16 lines × 5) · ×1

Duplicated block (15–16 lines × 5) flutter_inappwebview_android/example/lib/main.dart:54 — flutter_inappwebview_android/example/lib/main.dart:54-69 | flutter_inappwebview_ios/example/lib/main.dart:52-66 | flutter_inappwebview_linux/example/lib/main.dart:274-289 | flutter_inappwebview_macos/example/lib/main.dart:32-46 | flutter_inappwebview_web/example/lib/main.dart:31-45 — before extracting anything, compare `flutter_inappwebview_android/example/lib/main.dart` and `flutter_inappwebview_ios/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1

Duplicated block (16 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1694 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:1694-1709 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1176-1191 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:1030-1045 | flutter_inappwebview/example/lib/widgets/common/event_log_card.dart:94-109 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1

Duplicated block (16 lines × 3) flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:323 — flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:323-338 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:381-396 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:427-442 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1

Duplicated block (15–16 lines × 2) flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:638 — flutter_inappwebview/example/lib/utils/controller_methods_registry.dart:638-652 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:571-586 — before extracting anything, compare `flutter_inappwebview/example/lib/utils/controller_methods_registry.dart` and `flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14–15 lines × 4) · ×1

Duplicated block (14–15 lines × 4) flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:271 — flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:271-285 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:564-577 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:382-395 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:415-428 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart` and `flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14 lines × 6) · ×1

Duplicated block (14 lines × 6) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:184 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:184-197 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:172-185 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:691-704 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:524-537 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:638-651 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:514-527 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–14 lines × 6) · ×1

Duplicated block (13–14 lines × 6) flutter_inappwebview_android/example/lib/main.dart:63 — flutter_inappwebview_android/example/lib/main.dart:63-75 | flutter_inappwebview_ios/example/lib/main.dart:60-72 | flutter_inappwebview_linux/example/lib/main.dart:283-295 | flutter_inappwebview_macos/example/lib/main.dart:40-52 | flutter_inappwebview_web/example/lib/main.dart:39-51 | flutter_inappwebview_windows/example/lib/main.dart:270-283 — before extracting anything, compare `flutter_inappwebview_android/example/lib/main.dart` and `flutter_inappwebview_ios/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×1

Duplicated block (13–14 lines × 4) flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:208 — flutter_inappwebview/example/lib/screens/settings_editor_screen.dart:208-220 | flutter_inappwebview/example/lib/screens/support_matrix/support_matrix_screen.dart:355-368 | flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart:253-265 | flutter_inappwebview/example/lib/widgets/test_automation/method_selector_widget.dart:391-404 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/settings_editor_screen.dart` and `flutter_inappwebview/example/lib/screens/webview_environment_settings_editor_screen.dart` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 475 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12 lines × 10) · ×1

Duplicated block (12 lines × 10) flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:164 — flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart:164-175 | flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:152-163 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:671-682 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:489-500 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:618-629 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:538-549 | flutter_inappwebview/example/lib/screens/storage/http_auth_screen.dart:298-309 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:389-400 | flutter_inappwebview/example/lib/widgets/webview/method_tester_widget.dart:1498-1509 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:663-674 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (11 lines × 13) · ×1

Duplicated block (11 lines × 13) flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:812 — flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:812-822 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:881-891 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:935-945 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:978-988 | flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart:1016-1026 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:663-673 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:736-746 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:772-782 | flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart:802-812 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:744-754 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:788-798 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:889-899 | flutter_inappwebview/example/lib/screens/browsers/inapp_browser_screen.dart:937-947 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/browsers/chrome_safari_browser_screen.dart` and `flutter_inappwebview/example/lib/screens/browsers/headless_webview_screen.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 275 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1

Duplicated block (10–11 lines × 2) flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:597 — flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:597-606 | flutter_inappwebview/example/lib/widgets/webview/static_method_tester_widget.dart:735-745 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1

Duplicated block (8–9 lines × 4) flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:602 — flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart:602-609 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:356-363 | flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart:383-391 | flutter_inappwebview/example/lib/screens/storage/web_storage_screen.dart:436-443 — before extracting anything, compare `flutter_inappwebview/example/lib/screens/advanced/service_controllers_screen.dart` and `flutter_inappwebview/example/lib/screens/storage/cookie_manager_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×1

Duplicated block (7–8 lines × 3) flutter_inappwebview/example/lib/screens/support_matrix/platform_comparison_screen.dart:456 — flutter_inappwebview/example/lib/screens/support_matrix/platform_comparison_screen.dart:456-463 | flutter_inappwebview/example/lib/screens/test_automation/test_configuration_screen.dart:741-747 | flutter_inappwebview/example/lib/screens/test_automation/test_runner_screen.dart:950-956 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

P1 · CI/CD gates · No CI gate on code changes · ×1

No CI gate on code changes — A workflow is configured, but none of the repository's 3 workflows (`REDACTED`, `no-response.yaml`, `REDACTED`) runs on a code change (no `push` or `pull_request` trigger) or checks the code out — so nothing here builds or tests a change before it merges. This is automation for the repository's ISSUES AND HOUSEKEEPING, not a gate on its code: a pull request can land without anything having compiled or run it. The rows about missing build and test steps are deliberately not reported beside this one, because there is no pipeline for them to be missing from — adding the gate is one action, not three.

R1 · Type Safety · Type Safety · ×1

Type Safety — 2 typed · 4 plain JS — the untyped files are flutter_inappwebview_web/lib/assets/web/web_support.js, test_node_server/client.js, REDACTED, test_node_server/public/js/main.js. 0 production file(s) opt out entirely with @ts-nocheck · 7 @ts-ignore suppression(s).

R10 · Code Duplication · Duplicated block with local edits (659 matched lines × 2 locations) · ×1

Duplicated block with local edits (659 matched lines × 2 locations) flutter_inappwebview_web/lib/assets/web/web_support.js:24 — flutter_inappwebview_web/lib/assets/web/web_support.js:24 · web_support/src/index.ts:43 — the two spans are one implementation copied and then locally edited — 4013 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1

Duplicated block (10 lines × 2 locations) web_support/src/index.ts:186 — web_support/src/index.ts:186 · web_support/src/index.ts:198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R3 · Large Files · web_support/src/index.ts · ×1

web_support/src/index.ts: 719 lines of code web_support/src/index.ts:1 — web_support/src/index.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · flutter_inappwebview_web/lib/assets/web/web_support.js · ×1

flutter_inappwebview_web/lib/assets/web/web_support.js: 691 lines of code flutter_inappwebview_web/lib/assets/web/web_support.js:1 — flutter_inappwebview_web/lib/assets/web/web_support.js has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R6 · Tooling · No test, lint or typecheck script · ×1

No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

R8 · Dependency Hygiene · Unused dependency 'https' · ×1

Unused dependency 'https' — Declared in test_node_server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

Minor — 451 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×403

Orphaned file flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/InAppWebView.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_webview.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/in_app_browser/platform_in_app_browser.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebView.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/WebViewChannelDelegate.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/types/web_resource_error_type.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewChromeClient.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/WebViewChannelDelegate.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_macos/macos/flutter_inappwebview_macos/Sources/flutter_inappwebview_macos/InAppWebView/WebViewChannelDelegate.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file dev_packages/generators/lib/src/exchangeable_object_generator.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/mime_type_resolver.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview/lib/src/in_app_webview/headless_in_app_webview.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/chrome_safari_browser/platform_chrome_safari_browser.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview/lib/src/in_app_webview/in_app_webview.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_web/lib/src/in_app_webview/in_app_webview_controller.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewSettings.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/platform_cookie_manager.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_platform_interface/lib/src/web_storage/platform_web_storage.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/in_app_webview/InAppWebViewClientCompat.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 378 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart:376 — `(params.onDownloadStartRequest != null || params.onDownloadStarting != null) && settings.useOnDownloadStart == null` appears character-identically in 11 files — flutter_inappwebview_android/lib/src/in_app_webview/headless_in_app_webview.dart, flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview.dart, flutter_inappwebview_ios/lib/src/in_app_webview/headless_in_app_webview.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:718 — `(webviewParams != null && (webviewParams!.androidOnScaleChanged != null || webviewParams!.onZoomScaleChanged != null)) || _inAppBrowserEvent…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:386 — `(webviewParams != null && (webviewParams!.onDownloadStart != null || webviewParams!.onDownloadStartRequest != null || webviewParams!.onDownl…` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1073 — `(webviewParams != null && (webviewParams!.onFindResultReceived != null || (webviewParams!.findInteractionController != null && webviewParams…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:684 — `(webviewParams != null && (webviewParams!.onFormResubmission != null || webviewParams!.androidOnFormResubmission != null)) || _inAppBrowserE…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:498 — `(webviewParams != null && (webviewParams!.onGeolocationPermissionsShowPrompt != null || webviewParams!.androidOnGeolocationPermissionsShowPr…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:870 — `(webviewParams != null && (webviewParams!.onJsBeforeUnload != null || webviewParams!.androidOnJsBeforeUnload != null)) || _inAppBrowserEvent…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:427 — `(webviewParams != null && (webviewParams!.onLoadResourceWithCustomScheme != null || webviewParams!.onLoadResourceCustomScheme != null)) || _…` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1252 — `(webviewParams != null && (webviewParams!.onNavigationResponse != null || webviewParams!.iosOnNavigationResponse != null)) || _inAppBrowserE…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1130 — `(webviewParams != null && (webviewParams!.onPermissionRequest != null || webviewParams!.androidOnPermissionRequest != null)) || _inAppBrowse…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1461 — `(webviewParams != null && (webviewParams!.onPrintRequest != null || webviewParams!.onPrint != null)) || _inAppBrowserEventHandler != null` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:237 — `(webviewParams != null && (webviewParams!.onReceivedError != null || webviewParams!.onLoadError != null)) || _inAppBrowserEventHandler != nu…` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:279 — `(webviewParams != null && (webviewParams!.onReceivedHttpError != null || webviewParams!.onLoadHttpError != null)) || _inAppBrowserEventHandl…` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:752 — `(webviewParams != null && (webviewParams!.onReceivedIcon != null || webviewParams!.androidOnReceivedIcon != null)) || _inAppBrowserEventHand…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:945 — `(webviewParams != null && (webviewParams!.onReceivedLoginRequest != null || webviewParams!.androidOnReceivedLoginRequest != null)) || _inApp…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:779 — `(webviewParams != null && (webviewParams!.onReceivedTouchIconUrl != null || webviewParams!.androidOnReceivedTouchIconUrl != null)) || _inApp…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:652 — `(webviewParams != null && (webviewParams!.onRenderProcessGone != null || webviewParams!.androidOnRenderProcessGone != null)) || _inAppBrowse…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:620 — `(webviewParams != null && (webviewParams!.onRenderProcessResponsive != null || webviewParams!.androidOnRenderProcessResponsive != null)) || …` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:588 — `(webviewParams != null && (webviewParams!.onRenderProcessUnresponsive != null || webviewParams!.androidOnRenderProcessUnresponsive != null))…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:905 — `(webviewParams != null && (webviewParams!.onSafeBrowsingHit != null || webviewParams!.androidOnSafeBrowsingHit != null)) || _inAppBrowserEve…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1292 — `(webviewParams != null && (webviewParams!.shouldAllowDeprecatedTLS != null || webviewParams!.iosShouldAllowDeprecatedTLS != null)) || _inApp…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:555 — `(webviewParams != null && (webviewParams!.shouldInterceptRequest != null || webviewParams!.androidShouldInterceptRequest != null)) || _inApp…` appears character-identically in 4 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1696 — `(webviewParams != null && webviewParams!.onAjaxProgress != null) || _inAppBrowserEventHandler != null` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1672 — `(webviewParams != null && webviewParams!.onAjaxReadyStateChange != null) || _inAppBrowserEventHandler != null` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart:1514 — `(webviewParams != null && webviewParams!.onCameraCaptureStateChanged != null) || _inAppBrowserEventHandler != null` appears character-identically in 5 files — flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_linux/lib/src/in_app_webview/in_app_webview_controller.dart, flutter_inappwebview_macos/lib/src/in_app_webview/in_app_webview_controller.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

X7 · Silent fallback defaults · Silent fallback default in catch · ×6

Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:161 — `_getCoreWebViewFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:175 — `_getBrowserFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:192 — `_getStorageFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:211 — `_getControllerFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:223 — `_getMessagingFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch flutter_inappwebview/example/lib/screens/platform_info_screen.dart:235 — `_getAdvancedFeatures` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.

D34 · Knowledge Freshness · Most significant orphaned file · ×3

Most significant orphaned file flutter_inappwebview_platform_interface/lib/src/in_app_webview/platform_inappwebview_controller.dart:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file flutter_inappwebview_platform_interface/lib/src/in_app_webview/in_app_webview_settings.dart:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.

AX6 · Interface segregation · Fat interface · ×2

Fat interface: InAppWebView (26 required operations) web_support/src/types.ts:12 — `InAppWebView` declares 26 required operations: `disableContextMenuHandler`, `prepare`, `setSettings`, `reload`, `goBack`, `goForward`, `goBackOrForward`, `evaluateJavascript`, `stopLoading`, `getUrl`, `getTitle`, `injectJavascriptFileFromUrl`, `injectCSSCode`, `injectCSSFileFromUrl`, `scrollTo`, `scrollBy`, `printCurrentPage`, `getContentHeight`, `getContentWidth`, `getSelectedText`, `getScrollX`, `getScrollY`, `isSecureContext`, `canScrollVertically`, `canScrollHorizontally`, `getSize`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: InAppWebViewInterface (90 abstract methods) flutter_inappwebview_android/android/src/main/java/com/pichillilorenzo/flutter_inappwebview_android/webview/InAppWebViewInterface.java:30 — `InAppWebViewInterface` declares 90 abstract methods: `addWebMessageListener`, `callAsyncJavaScript`, `canGoBack`, `canGoBackOrForward`, `canGoForward`, `canScrollHorizontally`, `canScrollVertically`, `clearAllCache`, `clearFocus`, `clearHistory`, `clearMatches`, `clearSslPreferences`, `createCompatWebMessageChannel`, `createWebMessageChannel`, `disposeWebMessageChannels`, `disposeWebMessageListeners`, `evaluateJavascript`, `findAllAsync`, `findNext`, `getCertificate`, `getChannelDelegate`, `getContentHeight`, `getContentHeight`, `getContentWidth`, `getContext`, `getContextMenu`, `getCopyBackForwardList`, `getCustomSettings`, `getCustomSettingsMap`, `getHitTestResult`, `getHitTestResult`, `getInAppBrowserDelegate`, `getOriginalUrl`, `getPlugin`, `getProgress`, `getScrollX`, `getScrollY`, `getSelectedText`, `getTitle`, `getUrl`, and 50 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 90 declarations carry 86 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 86 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 5 of 15 project(s) overshoot their size bounds, lowering Project Cohesion to 3.8/10. The most over is `flutter_inappwebview_platform_interface` (42711 LoC, 423 module-visible types across 18 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 406 of 406 significant files have no living knowledge — the codebase as a whole is dormant, not 406 separate risks. Counted over 406 of the 971 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

M2 · Architecture documentation · No architecture diagram/doc · ×1

No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

M3 · Folder & project structure · No src/ separation · ×1

No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

P10 · Library API & versioning · Large public API surface · ×1

Large public API surface — 1158/1277 types (91%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 2956 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: flutter_inappwebview_platform_interface/lib/src/in_app_localhost_server.dart:96 — `HttpServer.bind(`.

S1 · Web-Security Posture · No inbound request validation detected · ×1

No inbound request validation detected — No handler of this repository's Dart server answers 400, 413 or 422 (`Response.badRequest`, `HttpStatus.badRequest`, `statusCode = 400`) and no validation package (luthor, acanthis, ez_validator, json_schema, …) is imported — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: flutter_inappwebview_platform_interface/lib/src/in_app_localhost_server.dart:96 — `HttpServer.bind(`.

X5 · Nullable reference types · Null assertions (`!`) reduce the null safety score · ×1

Null assertions (`!`) reduce the null safety score — ~26.6 `!` null assertions per 1k Dart product lines — 2671 across the 100392 line(s) of the 550 Dart file(s) read (generated, test and example code not counted; a file opted out with a `// @dart=` comment below 2.12 counts once). Densest: flutter_inappwebview_windows/lib/src/in_app_webview/in_app_webview_controller.dart (516), flutter_inappwebview_android/lib/src/in_app_webview/in_app_webview_controller.dart (463), flutter_inappwebview_ios/lib/src/in_app_webview/in_app_webview_controller.dart (457). Each one tells the analyzer to trust the author about null and becomes a `Null check operator used on a null value` the first time the author is wrong.

Minor — 1 finding(s)

D12 · Dependency Hygiene · Outdated · ×1

Outdated: swift-collections — `swift-collections` is resolved at 1.3.0, but 1.7.4 is the newest release tagged on https://github.com/apple/swift-collections.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-collections` reaches this one with no change to Package.swift.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b939d75b902d4855a5863afc6904f2ed/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b939d75b902d4855a5863afc6904f2ed/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	15	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	1	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/InAppWebView/InAppWebView.swift`, `flutter_inappwebview_ios/ios/flutter_inappwebview_ios/Sources/flutter_inappwebview_ios/SafariViewController/ChromeSafariBrowserManager.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a1690b-85f0-790a-ad00-62cb44754cdb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 43% · Weak · gated by D2, R1, R3 ·

At a glance — Architecture · 93% · Adequate · gated by D26 ·

At a glance — Maturity · 39% · Weak · gated by D34, M2 ·

At a glance — Readiness · 32% · Weak · gated by D13, R6, P1, P3 ·

At a glance — Security · 71% · Strong ·

At a glance — Performance · 70% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts