mirror of https://github.com/ospab/ostp.git
ospab
2092f6c716
Traced the whole traffic-counter pipeline (Dart -> MethodChannel -> Kotlin -> JNI -> Bridge) end to end; it's architecturally identical to the working desktop implementation, so no code-level bug was found. Previously a getMetrics exception was only reported as a PlatformException that Dart swallows with a bare debugPrint, invisible in the in-app log viewer users actually have access to. Now it's also written to the native log buffer via OstpClientSdk.addLog, so if the counter breaks again the actual cause (exception vs. genuinely-zero atomics) shows up in View Logs instead of requiring adb. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle.kts | ||
| proguard-rules.pro | ||