No actionable comments were generated in the recent review. 🎉

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@coderabbitai full review

Please focus on AndroidX/Material/coroutines compatibility with compileSdk 35, the WorkManager 2.9 Configuration.Provider property migration in SagerNet.kt, and any API breaks. Note: dependency versions were specifically chosen to stay compileSdk-35-compatible (avoided releases requiring compileSdk 36). kryo intentionally held (serialization). Both debug and release builds pass on the builder.

#!/bin/bash
set -euo pipefail

echo "=== app/build.gradle.kts ==="
cat app/build.gradle.kts

echo ""
echo "=== SagerNet.kt (search) ==="
fd -i "SagerNet.kt" --exec cat {}

echo ""
echo "=== WorkManager Configuration.Provider usage ==="
rg -n "Configuration" --type kotlin -C 5

echo ""
echo "=== coroutines usage patterns ==="
rg -n "coroutines\|GlobalScope\|CoroutineScope\|Dispatchers" --type kotlin -C 2 | head -80

echo ""
echo "=== navigation safe-args or NavController usage ==="
rg -n "NavController\|navigate\|findNavController\|NavigationUI" --type kotlin -C 2 | head -60

echo ""
echo "=== WorkManager enqueue/getConfiguration usage ==="
rg -n "WorkManager\|WorkRequest\|getWorkManagerConfiguration\|workManagerConfiguration" --type kotlin -C 3 | head -80

@hawkff: Full review completed. Here are my findings.

Review: build: update AndroidX, Material, Gson, coroutines, guava, desugar

✅ WorkManager 2.9 — Configuration.Provider Migration (SagerNet.kt)

The migration is correct and complete.

// WorkManager ≤ 2.8 (old — method)
override fun getWorkManagerConfiguration(): WorkConfiguration { … }

// WorkManager ≥ 2.9 (new — property, as implemented)
override val workManagerConfiguration: WorkConfiguration
    get() = WorkConfiguration.Builder()
        .setDefaultProcessName("${BuildConfig.APPLICATION_ID}:bg")
        .build()

Additional correctness notes:

• Import alias (import androidx.work.Configuration as WorkConfiguration) cleanly resolves the name clash with android.content.res.Configuration used on Lines 9, 107, and 129. No ambiguity.
• work-runtime-ktx and work-multiprocess are both pinned to 2.9.1 — version parity is required and is present. ✅
• setDefaultProcessName("${BuildConfig.APPLICATION_ID}:bg") correctly matches the isBgProcess check (process.endsWith(":bg")) in onCreate(). ✅

✅ compileSdk 35 Compatibility — All Bumps

✅ No SafeArgs / Navigation API Break

No SafeArgs plugin is declared in the plugins {} block (com.android.application, kotlin-android, ksp, kotlin-parcelize only). Navigation 2.8's new type-safe @Serializable route API is opt-in; @IdRes-based navigate() remains fully supported. No action needed.

✅ Fragment 1.8.5 — Predictive Back Compatibility

MainActivity already uses onBackPressedDispatcher.addCallback {} (the modern pattern) with no legacy override fun onBackPressed(). Fragment 1.8's predictive back integration is fully compatible. ✅

✅ Coroutines 1.8.1

DEBUG_PROPERTY_NAME and DEBUG_PROPERTY_VALUE_ON (used in SagerNet.onCreate()) remain stable public API in 1.8.1. No removals or deprecation breaks relevant to this codebase.

⚠️ Advisory: Gson 2.11.0 — Default Float Serialization Behavior Change

Gson 2.10+ changed the default behavior: NaN and ±Infinity are no longer serialized without explicitly enabling them via GsonBuilder().serializeSpecialFloatingPointValues(). If any profile data, subscription parsing, or config export code passes NaN/Infinity through a default Gson() instance, it will now throw IllegalArgumentException at runtime instead of silently encoding a non-standard JSON token.

This won't be caught by the build but could surface in runtime profile handling. It is worth scanning Gson instantiation sites for Gson() vs GsonBuilder() usage. Since kryo is intentionally held for profile serialization, the blast radius is limited — but subscription/config JSON paths may use Gson directly.

Summary

The PR is well-scoped and the only item requiring attention is the Gson advisory above.

Re: Gson 2.11.0 NaN/Infinity advisory — assessed, no change needed.

Both central Gson instances (JavaUtil.gson and SingBoxOptions.gsonSingbox) and the ad-hoc Gson() uses (V2RayFmt VMess QR) only ever serialize VPN config values: ports, timeouts, mbps, packet sizes, UUIDs, strings — all finite integers/doubles parsed from JSON/YAML/URI subscription input. There is no code path that produces Float.NaN or +/-Infinity to serialize, so the Gson 2.10+ stricter default cannot be triggered here. Adding serializeSpecialFloatingPointValues() would be defensive code for an input that cannot occur. Documented as an accepted no-op.

Profile persistence uses kryo (intentionally held), not Gson, so profile data is unaffected.