This PR bumps the minimum supported platforms to:

  platforms: [
    .macOS(.v10_15),
    .iOS(.v13),
    .watchOS(.v6),
    .tvOS(.v13),
  ],

That make's it possible to remove the Starscream dependency.

This is definitely an edge case, but something I think that is important.

The realtime-swift package cannot be imported into Swift Playgrounds 4 because of the dependency on StarScream. realtime-swift can already run with StarScream removed since an implementation of the Transport protocol using standard iOS libraries exists. Please see my fork for a working repo that can import into Swift Playgrounds 4: https://github.com/YeomansIII/realtime-swift

Through my research, these Supabase Swift libraries (postgrest-swift, storage-swift, gotrue-swift) are some of the only 100% Swift packages that can actually be imported into Swift Playgrounds 4, which allows developers to create iOS apps directly on iPadOS without a Mac computer. This was important for me, because I was looking for a no-code backend like Firebase to use for my iOS app I am developing in Swift Playgrounds 4. Firebase and numerous other similar platforms were not able to be imported into Swift Playgrounds 4 because the packages contain Objective-C or other incompatible code/settings.

While I know that removing the StarScream dependency allows importing into Swift Playgrounds 4, I do not know if this is an actual solution or what the potential solution might be to get the main realtime-swift repo working with Swift Playgrounds.

So I would like to open up that discussion here.

I love the project

Im running into a when setting up a channel listener on a table with public schema.

Currently, I can only receive data from my supabase DB if I'm using realtime:*, but whenever set a specific table with the schema set public:

channel(.table("Media", schema: "public"))

the listener returns no data and after the socket opens, it emits a Close Event shortly after. I made sure all of my tables were public and also replicated as per the requirements for real-time setup.

Thanks you for the help!

not sure if it's a side effect of CLib change from swift-nio

sample app here https://github.com/wweevv-johndpope/DemoBazel/tree/gotrue-swift

table is simple structure

    struct TestClass: Codable {
        var id: Int?
    }

I'm definitely on the right instance. pqxcxltwoifmxcmhghzf

client connects successfully - I attempt to move subscription into the onOpen block - but no joy.

   let rt = RealtimeClient(endPoint: "https://pqxcxltwoifmxcmhghzf.supabase.co/realtime/v1", params: ["apikey": supabaseKey])
        rt.connect()
        rt.onOpen {
           
            let allUsersUpdateChanges =  rt.channel(.all)//rt.channel(.table("test", schema: "public"))
            allUsersUpdateChanges.on(.all) { message in
                print(message)
            }
            allUsersUpdateChanges.subscribe()
        }
        self.realtimeClient = rt

https://github.com/daltoniam/Starscream/pull/844

this prevents xcframeworks being spat out https://github.com/supabase-community/supabase-swift/issues/38

Hello,

I might be doing something totally off but having a hard time connecting to the server. I am getting an error of "Could not connect to the server."

Heres what I am trying:

var client = RealtimeClient(endPoint: "https://pkx....supabase.co/realtime/v1", params: ["apikey": "eyJhb..."])

A few questions.

1. Should use https and not wss in the url?
2. Should the url end in supabase.io or supabase.co?

Apply the usual Swift pattern to the API: Event and Topic are now proper Swift Enum. Limit the current implementation to the effectively supported features. Extend the tests to ensure the patterns are right. Add the subscription part to the README for ease of introduction to the framework.

Add FoundationNetworking if available. This is allowing Linux platforms to compile the framework, since the migration of URL-related function to the FoundationNetworking framework.

I created this PR in favor of #4 . Thanks @lmick002 for addressing it, I've just added a few minor things on top of it, such as:

1. Refactoring ChannelTopic type for using RawRepresentable.
2. Add unit tests for testing the ChannelTopic init from the rawValue string.

Fixes #3

What kind of change does this PR introduce?

Fix availability check for URLSessionTransport.

What is the current behavior?

The current availability check consider only macOS versions.

What is the new behavior?

Availability check now consider macOS, iOS, tvOS and watchOS versions.