Fix validated upstream issues: LateInit handlers (#8), updateNode (#6), dep constraints (#26, #29)

[iamEtornam]

Addresses open issues from upstream hlefe/ar_flutter_plugin_2 that were validated as real bugs reproducible in this codebase. Native-only and device-specific issues are handled elsewhere or deferred (see bottom).

Fixes

🐛 LateInitializationError on session callbacks — upstream hlefe#8

ARSessionManager.onPlaneOrPointTap and onPlaneDetected were declared late (non-nullable), but _platformCallHandler guards them with if (x != null). Reading an unset late field throws LateInitializationError: Field 'onPlaneDetected' has not been initialized. — exactly the error reported. Made both nullable (matching onError), so the guards work and the callbacks are optional. Also removes two unnecessary_null_comparison analyzer warnings.

✨ Add ARObjectManager.updateNode() — upstream #6

The maintainer told users to call objectManager.updateNode(node) to sync transforms, but the method never existed. Added it — it invokes the transformationChanged platform method that the Android and iOS sides already handle, so no native change is needed.

📦 Widen permission_handler to >=11.3.1 <13.0.0 — upstream hlefe#26

Allows permission_handler 12.x (resolves to 12.0.3). All APIs used (Permission.camera, PermissionStatus.*, openAppSettings) are stable across 11→12. Widened rather than pinned so 11.x users aren't forced to upgrade.

🧹 Bump Dart SDK upper bound <3.0.0 → <4.0.0 — related to upstream hlefe#29 (hygiene)

Honest note: hlefe#29's reported symptom (incompatible with Flutter 3.35.6) did not reproduce here — pub's Dart-3 compatibility mode resolves fine against <3.0.0 on Dart 3.12. This bump removes the fragile reliance on that compat shim; it is hygiene, not a verified fix for hlefe#29's exact symptom.

Verification

• flutter analyze lib test → 0 errors; the two targeted unnecessary_null_comparison warnings are gone.
• flutter test → 3 passing, including new regression tests for Model is seen on Android but IOS is not. hlefe/ar_flutter_plugin_2#8 and Fix validated upstream issues: LateInit handlers (#8), updateNode (#6), dep constraints (#26, #29) #6.
• The Model is seen on Android but IOS is not. hlefe/ar_flutter_plugin_2#8 regression test was proven to fail against the old late declaration and pass after the fix.
• permission_handler widening and SDK bump both re-resolve cleanly via flutter pub get.
• pubspec.lock intentionally not modified (not authoritative for a plugin; regenerated on pub get).

Not included (validated + routed elsewhere / deferred)

• [android] Name from nodeNames List from onNodeTap function doesn't correspond with any name from nodes names. hlefe/ar_flutter_plugin_2#12, [android] getCameraPose() returns null value every time hlefe/ar_flutter_plugin_2#18, 'onPanEnd' and 'onRotationEnd' callbacks does not work hlefe/ar_flutter_plugin_2#16, [android] panning and rotation does not work hlefe/ar_flutter_plugin_2#24, ar_flutter_plugin_2 not compatible with Android 16KB page size devices hlefe/ar_flutter_plugin_2#32 — already covered by the replicated PRs Return nodeName instead of anchorName on Android (replicates upstream #13) #1–Android build.gradle: ARCore dep + SDK/Kotlin bumps (replicates upstream #33) #5.
• onNodeTap callback does not work at all hlefe/ar_flutter_plugin_2#15 (iOS [#" node-name quirk), Fail to load GLB from File System - Might have a FIX hlefe/ar_flutter_plugin_2#21/[Bug] 3D model not showing even after applying file:// fix + Depth & Occlusion not working hlefe/ar_flutter_plugin_2#22 (native GLB file:// / occlusion) — native-side, not verifiable without a device; deferred.
• How to configure manual control along the Z axis hlefe/ar_flutter_plugin_2#30, [Feature request] Hide nodes under planes. hlefe/ar_flutter_plugin_2#11, Cloud we achieve motion smooth when loading different animations in AR? hlefe/ar_flutter_plugin_2#23 — feature requests. Many 3d models does not render after added as node hlefe/ar_flutter_plugin_2#14, .glb Model Does Not Show After Plane Detection in AR hlefe/ar_flutter_plugin_2#17 — usage/scale, resolved by reporters.

[gemini-code-assist]

Code Review

This pull request introduces the updateNode method to ARObjectManager to synchronize node transformations with the native AR engine, resolves potential LateInitializationErrors in ARSessionManager by making event handlers nullable, updates dependency constraints in pubspec.yaml, and adds corresponding regression tests. The review feedback suggests minor improvements: using const for the MatrixValueNotifierConverter instantiation to avoid unnecessary runtime allocations, and replacing the null-assertion operator (!) with the safer, more idiomatic null-aware call operator (?.call(...)) when invoking the nullable event handlers.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Since MatrixValueNotifierConverter has a const constructor, you can instantiate it as a compile-time constant using const to avoid unnecessary runtime object allocations.

Suggested change

	MatrixValueNotifierConverter().toJson(node.transformNotifier),
	const MatrixValueNotifierConverter().toJson(node.transformNotifier),

[iamEtornam]

Done in 01450b36df05a7651d3a3de7856f299ef60089d0 — applied as suggested. Thanks!

[gemini-code-assist]

Using the null-assertion operator ! on a mutable instance field is discouraged in Dart because the field's value could theoretically change or be set to null. It is more idiomatic and safer to use the null-aware call operator ?.call(...) instead.

Suggested change

	onPlaneOrPointTap!(hitTestResults);
	onPlaneOrPointTap?.call(hitTestResults);

[iamEtornam]

Done in 01450b36df05a7651d3a3de7856f299ef60089d0 — applied as suggested. Thanks!

[gemini-code-assist]

Using the null-assertion operator ! on a mutable instance field is discouraged in Dart. It is more idiomatic and safer to use the null-aware call operator ?.call(...) instead.

Suggested change

	onPlaneDetected!(planeCountResult);
	onPlaneDetected?.call(planeCountResult);

[iamEtornam]

Done in 01450b36df05a7651d3a3de7856f299ef60089d0 — applied as suggested. Thanks!

[iamEtornam]

Review loop — ✅ clean after 2 iterations

Iteration 1 — found a BLOCKER: updateNode was async and awaited transformationChanged, but Android's handleTransformNode (ArView.kt:649) wraps its whole body in if (handlePans || handleRotation) — both default false, so it never calls result.* and an awaited call would hang forever. (The pre-existing addNode transform listener never hit this because it's fire-and-forget.)

Fix applied: made updateNode void / fire-and-forget, mirroring removeNode. Documented that on Android the transform is applied only when handlePans/handleRotation was enabled in onInitialize.

Iteration 2 — LGTM. BLOCKER resolved and confirmed against the native code. No regressions.

Accepted tradeoff (not fixed, by design): a fire-and-forget invoke can log an uncaught async error if gestures are enabled and the node is missing (NODE_NOT_FOUND). This is identical to the existing removeNode behaviour, so updateNode matches the established pattern rather than diverging. Adding .catchError was considered and rejected to avoid inconsistency + scope creep into removeNode.

Verification: flutter analyze lib test → 0 errors (targeted unnecessary_null_comparison warnings gone); flutter test → 3 passing; hlefe#8 regression test proven to fail on the old late code and pass on the fix.