How a Swapped Argument Order Killed Our Supabase iOS Connection (Silently)
SupabaseClient got the URL and anon key swapped. Swift compiled it without complaint. Everything failed silently. The fix was one line.
Everything that doesn't fit a bucket yet.
SupabaseClient got the URL and anon key swapped. Swift compiled it without complaint. Everything failed silently. The fix was one line.
Supabase's batch upsert silently turns missing keys into NULLs — which bypasses your schema defaults and can quietly discard your data. error === n
If you're demoing a Supabase-backed iOS app live, add a guest mode with hardcoded data. Eighty lines of Swift buys you a demo that runs in airplane