Realtime does not work on iOS / iPadOS 26
I'm facing a pretty critical issue with the newest versions of iOS
I'm using a self-hosted version of Supabase-- all of my requests (specifically from devices both iPadOS and iOS using v26) seem to send CONNECT requests instead of GET requests when subscribing for real-time. This causes the connection to fail, leading to realtime just not working.
Again, my current realtime setup works fine everywhere, except on iPhone/iPad running the iOS 26 beta. It happens on all versions of the beta. I've tested this on 3 different devices, and 3 different networks, all produced the same results.
Here is a summary of my self-hosted stack:
- supabase-kong: kong (version: 2.8.1)
- supabase-studio: supabase/studio (version: 2025.06.02-sha-8f2993d)
- supabase-db: supabase/postgres (version: 17.4.1.042)
- supabase-analytics: supabase/logflare (version: 1.4.1)
- supabase-vector: timberio/vector (version: 0.28.1-alpine)
- supabase-rest: postgrest/postgrest (version: v13.0.2)
- supabase-auth: supabase/gotrue (version: v2.175.0)
- realtime-dev: supabase/realtime (version: v2.36.11)
- supabase-minio: minio/minio (version: latest)
- minio-createbucket: minio/mc (version: latest)
- supabase-storage: supabase/storage-api (version: v1.24.4)
- imgproxy: darthsim/imgproxy (version: v3.28.0)
- supabase-meta: supabase/postgres-meta (version: v0.89.3)
- supabase-edge-functions: supabase/edge-runtime (version: v1.67.4)
- supabase-supavisor: supabase/supavisor (version: 2.5.1)
Would love to know if anyone has discovered a fix for this! Thanks
I'm using a self-hosted version of Supabase-- all of my requests (specifically from devices both iPadOS and iOS using v26) seem to send CONNECT requests instead of GET requests when subscribing for real-time. This causes the connection to fail, leading to realtime just not working.
Again, my current realtime setup works fine everywhere, except on iPhone/iPad running the iOS 26 beta. It happens on all versions of the beta. I've tested this on 3 different devices, and 3 different networks, all produced the same results.
Here is a summary of my self-hosted stack:
- supabase-kong: kong (version: 2.8.1)
- supabase-studio: supabase/studio (version: 2025.06.02-sha-8f2993d)
- supabase-db: supabase/postgres (version: 17.4.1.042)
- supabase-analytics: supabase/logflare (version: 1.4.1)
- supabase-vector: timberio/vector (version: 0.28.1-alpine)
- supabase-rest: postgrest/postgrest (version: v13.0.2)
- supabase-auth: supabase/gotrue (version: v2.175.0)
- realtime-dev: supabase/realtime (version: v2.36.11)
- supabase-minio: minio/minio (version: latest)
- minio-createbucket: minio/mc (version: latest)
- supabase-storage: supabase/storage-api (version: v1.24.4)
- imgproxy: darthsim/imgproxy (version: v3.28.0)
- supabase-meta: supabase/postgres-meta (version: v0.89.3)
- supabase-edge-functions: supabase/edge-runtime (version: v1.67.4)
- supabase-supavisor: supabase/supavisor (version: 2.5.1)
Would love to know if anyone has discovered a fix for this! Thanks
