Fix `AccountCache` only handled first request

The app would previously crash when the UI side `AccountCache` class
sent a second request message to the service side `AccountCache` class.
The simplest way to reproduce this was to log out and log in again. This
was happening because the service side `AccountCache` actor
implementation was only handling one request and then stopping.

This is now fixed by having the actor run a loop to handle all incoming
requests.

1 files changed, 6 insertions, 6 deletions

diff --git a/android/src/main/kotlin/net/mullvad/mullvadvpn/service/endpoint/AccountCache.kt b/android/src/main/kotlin/net/mullvad/mullvadvpn/service/endpoint/AccountCache.kt
index 74cdc3f11f..50f0f5940c 100644
--- a/android/src/main/kotlin/net/mullvad/mullvadvpn/service/endpoint/AccountCache.kt
+++ b/android/src/main/kotlin/net/mullvad/mullvadvpn/service/endpoint/AccountCache.kt
@@ -163,12 +163,12 @@ class AccountCache(private val endpoint: ServiceEndpoint) {
 
     private fun spawnActor() = GlobalScope.actor<Command>(Dispatchers.Default, Channel.UNLIMITED) {
         try {
-            val command = channel.receive()
-
-            when (command) {
-                is Command.CreateAccount -> doCreateAccount()
-                is Command.Login -> doLogin(command.account)
-                is Command.Logout -> doLogout()
+            for (command in channel) {
+                when (command) {
+                    is Command.CreateAccount -> doCreateAccount()
+                    is Command.Login -> doLogin(command.account)
+                    is Command.Logout -> doLogout()
+                }
             }
         } catch (exception: ClosedReceiveChannelException) {
             // Command channel was closed, stop the actor