Migrate client state off ObjectBox to Radiance

[atavism]

Resolves https://github.com/getlantern/engineering/issues/2944

This PR replaces Flutter local DB/local storage reads for user, plans, split-tunneling, private servers, and selected server location with Riverpod providers backed by lantern-core/Radiance APIs (with Go-side on-disk caching)

[jigar-f]

@atavism I think this pretty big change, did we remove obejctbox completly? I thought we were just removing private server stuff.

• With this change, now every time we need adda new local state, we need to add an ffi method and a platform channel against it, before we just did with object box, only one method.
• With this, now it goes to flutter->ffi/platfomchannel-> go aginest flutter->done

Correct if I'm wrong, I have not looked in detail.

[atavism]

@jigar-f Yes, I went ahead and fully removed ObjectBox in this PR. If Radiance is our source of truth for persistent state (user, selected server, split tunneling, etc.), I think we’re better off not keeping a separate Flutter DB. I get the concern about extra FFI/platform-channel calls, but we can keep the surface area small with a few get/set endpoints (and core caching) instead of duplicating state...Does that sound reasonable?

[atavism]

For instance, we could expose getAppState / updateAppState instead of one API per field

[jigar-f]

Agreed, Radiance should definitely be the source for VPN-related functionality. That said, I don’t think Radiance needs to care whether a user has a plan or not, or whether the user is shown an intro, etc. That logic can probably live elsewhere — though I don’t have a strong opinion against it.

I think we should take the time to test everything thoroughly and make sure all flows are working as expected before merging.
Did you get a chance to test all flows, especially auth and purchase?

[jigar-f]

@atavism, sorry, I know thisis on me. I will start reviewing this soon, caught up on someother stuff.

[atavism]

No worries, thanks @jigar-f!

[DelaLantern]

@atavism - is this still awaiting your review?

[jigar-f]

@atavism Created PR for follow-up changes #8509 take look when you get chance

[atavism]

@jigar-f Did you do some testing? Lmk if/when you're comfortable merging this. Thanks!

[jigar-f]

@atavism I did a bit of testing, so far it looks good. Still, I like to test a bit more payment stuff, maybe give it 2 more days.

[Copilot]

Pull request overview

This PR migrates Flutter-side user/session-related state off of the local ObjectBox DB and onto Riverpod providers backed by lantern-core/Radiance APIs (with Go-side caching), while also adding new private-server and split-tunneling bridging methods across Dart ⇄ native ⇄ Go.

Changes:

• Removes ObjectBox (deps, generated plugin registrants, entities/mappers) and introduces a SharedPreferences-backed LocalStorageService for lightweight cached settings.
• Refactors multiple features (plans, server location selection, private servers, split tunneling, user/home) to consume Riverpod providers sourced from lantern-core instead of local DB reads.
• Adds new private-server and split-tunnel APIs across Go core, FFI exports, and native method-channel handlers.

Reviewed changes

Copilot reviewed 114 out of 119 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
pubspec.yaml / pubspec.lock	Removes ObjectBox deps; adds shared_preferences as a direct dependency.
lib/core/services/local_storage_service.dart	New SharedPreferences cache wrapper replacing DB reads for settings/plans/location/dev-mode.
lib/core/services/injection_container.dart	Switches LocalStorageService to async GetIt singleton registration.
lib/lantern/lantern_platform_service.dart	Adds split-tunnel + private-server methods and enabled-apps snapshot refresh logic.
ios/Runner/Handlers/MethodHandler.swift / android/.../MethodHandler.kt / macos/.../MethodHandler.swift	Adds/updates method-channel plumbing for new core APIs.
lib/features/private_server/manage_private_server.dart	Updates private-server UI to use available servers from core and adds share-key caching.

Comments suppressed due to low confidence (1)

ios/Runner/Handlers/MethodHandler.swift:193

• The iOS method channel only adds deletePrivateServerByName, but Dart now calls getSplitTunnelItems / getSplitTunnelState (and private-server rename once implemented) via LanternPlatformService. Without adding these cases to the iOS handler, iOS will hit FlutterMethodNotImplemented/MissingPlugin errors at runtime when split-tunneling screens load. Please add the missing method cases and wire them to the new MobileGetSplitTunnelItems, MobileGetSplitTunnelStateJSON, and MobileUpdatePrivateServerName / MobileDeletePrivateServerByName APIs as appropriate.

      case "deletePrivateServerByName":
        guard let name: String = self.decodeValue(from: call.arguments, result: result) else {
          return
        }
        self.deletePrivateServerByName(result: result, name: name)

      // Server Selection
      case "getLanternAvailableServers":
        self.getLanternAvailableServers(result: result)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.