iOS Swift SDK: WebSocket fails with TenantNotFound / -1005 — REST API works fine

realtime🟠Swift/Kotlin

Problem:
WebSocket connections to Realtime fail immediately, while REST API calls work perfectly (all 200 responses).

The first connection attempt generates a server-side TenantNotFound: Tenant not found: <project-ref> error in the Realtime logs. Subsequent reconnect attempts produce NO server-side log entries at all — as if the connection is being rejected before reaching the Realtime server.

The SDK enters a perpetual disconnect/reconnect loop logging -1005 NSURLErrorNetworkConnectionLost on every attempt.

What works:
- All REST API calls (select, insert, update, delete) — 200 responses
- Dashboard's own Realtime connection (I can see "CONNECTED TO" entries in server logs every ~10s from the dashboard)
- Auth (Google Sign-In, session restore, token refresh)

What doesn't work:
- Any WebSocket connection from the Swift SDK (both simulator and physical device)

Server-side config verified:
- Realtime enabled, public access enabled
- All tables in supabase_realtime publication
- All tables have REPLICA IDENTITY FULL
- RLS enabled with proper policies

Client setup:

 let client = SupabaseClient(
      supabaseURL: URL(string: "https://<ref>.supabase.co")!,
      supabaseKey: anonKey,
      options: SupabaseClientOptions(
          global: .init(session: customURLSession, logger: logger)
      )
  )

  // Single channel, Postgres Changes
  let ch = client.realtimeV2.channel("household-\(id)")
  let rooms = ch.postgresChange(AnyAction.self, schema: "public", table: "rooms", filter: "household_id=eq.\(id)")
  try await ch.subscribe() // fails here

 let client = SupabaseClient(
      supabaseURL: URL(string: "https://<ref>.supabase.co")!,
      supabaseKey: anonKey,
      options: SupabaseClientOptions(
          global: .init(session: customURLSession, logger: logger)
      )
  )

  // Single channel, Postgres Changes
  let ch = client.realtimeV2.channel("household-\(id)")
  let rooms = ch.postgresChange(AnyAction.self, schema: "public", table: "rooms", filter: "household_id=eq.\(id)")
  try await ch.subscribe() // fails here

Questions:
1. What causes TenantNotFound when the project exists and REST works?
2. Why would subsequent reconnect attempts not even generate server logs?
3. Is there a known issue with the Swift SDK's WebSocket transport on iOS (it uses URLSessionWebSocketTask with URLSessionConfiguration.default, ignoring the custom URLSession passed in options)?

iOS Swift SDK: WebSocket fails with TenantNotFound / -1005 — REST API works fine

realtime🟠Swift/Kotlin

 let client = SupabaseClient(
      supabaseURL: URL(string: "https://<ref>.supabase.co")!,
      supabaseKey: anonKey,
      options: SupabaseClientOptions(
          global: .init(session: customURLSession, logger: logger)
      )
  )

  // Single channel, Postgres Changes
  let ch = client.realtimeV2.channel("household-\(id)")
  let rooms = ch.postgresChange(AnyAction.self, schema: "public", table: "rooms", filter: "household_id=eq.\(id)")
  try await ch.subscribe() // fails here

 let client = SupabaseClient(
      supabaseURL: URL(string: "https://<ref>.supabase.co")!,
      supabaseKey: anonKey,
      options: SupabaseClientOptions(
          global: .init(session: customURLSession, logger: logger)
      )
  )

  // Single channel, Postgres Changes
  let ch = client.realtimeV2.channel("household-\(id)")
  let rooms = ch.postgresChange(AnyAction.self, schema: "public", table: "rooms", filter: "household_id=eq.\(id)")
  try await ch.subscribe() // fails here

iOS Swift SDK: WebSocket fails with TenantNotFound / -1005 — REST API works fine

iOS Swift SDK: WebSocket fails with TenantNotFound / -1005 — REST API works fine

Similar Threads

Similar Threads

Similar Threads