I feel like I’m either missing something obvious or this is just a true limitation of lovable.
Native iOS apple sign in works fine with my bundle ID (com.yourapp.bundle)
Web needs a Services ID (com.yourapp.web)
Supabase checks the aud, so now everything has to line up depending on the flow
Since my auth settings are managed through lovable cloud, and lovable cloud only allows one client ID, I’m stuck either choosing having Apple sign in on native app or on web, I cannot get both working in harmony.
I didn’t even care about Apple Sign In on web at first, but it actually matters. If that button isn’t there, people hesitate. Especially for apps where you’re asking for any kind of commitment early. I need people to be able to persist their sessions across multiple devices.
For context, this is for a fitness app I’m building that’s more of a coach than a tracker, so if auth breaks, the whole thing falls apart before it even starts. The app is live: Goal Hour: Fitness Coach (apple and android, all build on lovable without plans to migrate off immediately soon unless I need to).
Has anyone gotten this setup to a place where they actually trust it long term?