Removed unused coroutinescope from the RoomLifeCycleManager, added mi…

…ssing

attach suspending method

chat-android/src/main/java/com/ably/chat/RoomLifecycleManager.kt

@@ -2,8 +2,6 @@ package com.ably.chat
 
 import io.ably.lib.types.ErrorInfo
 import io.ably.lib.util.Log.LogHandler
-import kotlinx.coroutines.CoroutineScope
-import kotlinx.coroutines.Dispatchers
 import io.ably.lib.realtime.Channel as AblyRealtimeChannel
 
 /**
@@ -85,15 +83,6 @@ class RoomLifecycleManager
      */
     private val _logger: LogHandler? = logger
 
-    /**
-     * sequentialCoroutineScope is to ensure the integrity and atomicity of operations that affect the room status, such as
-     * attaching, detaching, and releasing the room. It makes sure that we don't have multiple operations happening
-     * at once which could leave us in an inconsistent state.
-     * It is used as a CoroutineContext for with [kotlinx.coroutines.selects.select] statement.
-     * See [Kotlin Dispatchers](https://kt.academy/article/cc-dispatchers) for more information.
-     */
-    private val sequentialCoroutineScope = CoroutineScope(Dispatchers.Default.limitedParallelism(1))
-
     /**
      * This flag indicates whether some sort of controlled operation is in progress (e.g. attaching, detaching, releasing).
      *
@@ -115,4 +104,8 @@ class RoomLifecycleManager
         }
         // TODO - [CHA-RL4] set up room monitoring here
     }
+
+    suspend fun attach() {
+        TODO("Not yet implemented")
+    }
 }

chat-android/src/main/java/com/ably/chat/RoomStatus.kt

@@ -212,7 +212,7 @@ class DefaultStatus(private val logger: LogHandler?) : InternalRoomStatus, RoomS
     }
 
     fun setStatus(status: RoomLifecycle, error: ErrorInfo? = null) {
-        val newStatus = object :NewRoomStatus {
+        val newStatus = object : NewRoomStatus {
             override val status: RoomLifecycle = status
             override val error: ErrorInfo? = error
         }