Deploy & App Stores

How to Publish a Lovable App on the Apple App Store (Step-by-Step Guide)

You can publish a Lovable app on the Apple App Store by syncing it to GitHub, wrapping the React + Vite build in Capacitor, building and signing it in Xcode on a Mac, testing through TestFlight and submitting it in App Store Connect. The hard part is not the build: it is making the app feel native enough to clear Apple's guideline 4.2 and getting Supabase auth, privacy labels and account deletion right.

neooutput editorial team 6 min read Auf Deutsch lesen

What does a Lovable app need before it can become an iOS app?

It needs to live in a Git repository you control, because the iOS project has to be generated and maintained outside Lovable's editor. Use Lovable's GitHub sync so every change you make in Lovable lands in a repo you can clone locally.

Lovable projects are React + Vite + TypeScript with Tailwind and shadcn/ui, which is good news: Vite produces a static bundle in the dist folder, exactly what Capacitor expects as its web directory. Most of the work is configuration, not rewriting.

  • An Apple Developer Program membership (99 USD per year), ideally enrolled as an organization if the app represents a company
  • A Mac with a current Xcode, or a cloud build service such as Codemagic or EAS if you have no Mac
  • Your Lovable project connected to GitHub with two-way sync enabled
  • Production Supabase keys and redirect URLs that work outside the browser

How do you wrap a Lovable project with Capacitor?

Add Capacitor to the cloned repo, point it at the Vite output and generate a native iOS project. Keep the Capacitor files committed so Lovable's sync does not fight with them; Lovable only edits the web source.

Bundle the web build inside the app rather than loading your lovable.app URL remotely. A remote URL works technically, but it is the fastest route to a 4.2 rejection and it breaks when the device is offline.

  1. Clone the GitHub repo and run npm install
  2. Install @capacitor/core, @capacitor/cli and @capacitor/ios, then run npx cap init with a reverse-domain bundle ID such as com.yourcompany.yourapp
  3. Set webDir to dist in capacitor.config.ts
  4. Run npm run build, then npx cap add ios and npx cap sync ios
  5. Open the project with npx cap open ios and set your team, bundle ID and version in Xcode
  6. Repeat build and npx cap sync every time you pull new changes from Lovable

How do you make Supabase auth work inside the iOS app?

Email and password login usually works immediately, but OAuth providers such as Google need a deep link back into the app instead of a browser redirect to your web domain. Register a custom URL scheme or Universal Link, add it to Supabase's allowed redirect URLs, and handle the callback with Capacitor's App plugin.

If you offer Google, Facebook or another third-party login, Apple's guideline 4.8 requires an equivalent privacy-friendly option, which in practice means adding Sign in with Apple. Supabase supports Apple as a provider, so you enable it in the Supabase dashboard, create a Services ID and key in your Apple Developer account and use a native Apple sign-in plugin for the smoothest flow.

  • Store sessions with Capacitor Preferences or secure storage rather than relying only on browser localStorage
  • Implement in-app account deletion: Apple requires it for any app that lets users create an account (guideline 5.1.1)
  • Test login on a real iPhone, not just the simulator

How do you avoid an Apple guideline 4.2 rejection with a Lovable app?

Add genuine native value so the app is more than your website in a frame. Reviewers look at whether the app behaves like an app: native navigation, offline handling, device features and no browser chrome.

Lovable makes it easy to iterate on UI, so use it to build mobile-first layouts: a bottom tab bar, safe-area padding for the notch and home indicator, and no hover-dependent interactions.

  • Push notifications via Capacitor Push Notifications and APNs
  • Native share sheet, haptics, camera or photo picker where they fit the use case
  • An offline screen instead of a blank WebView when there is no connection
  • Native splash screen and app icon in all required sizes
  • Remove marketing pages, cookie banners and links to web pricing from the app build

How do you test with TestFlight and submit in App Store Connect?

Archive the app in Xcode, upload it to App Store Connect and distribute it via TestFlight before you ever press submit. Internal testers on your team get builds almost immediately; external testers require a short Beta App Review first.

For the real submission, fill out the privacy nutrition labels honestly. A typical Lovable app collects at least email addresses and user IDs through Supabase, plus anything you store in your tables. If you use analytics or error tracking, those SDKs must be declared too, and third-party SDKs may need to ship a privacy manifest.

  1. Create the app record in App Store Connect with the same bundle ID
  2. Product > Archive in Xcode, then Distribute App to App Store Connect
  3. Add testers in TestFlight and fix what they find
  4. Complete privacy labels, age rating, screenshots for the required iPhone sizes and a support URL
  5. Provide a demo account in the review notes if the app requires login
  6. Submit for review and answer reviewer questions quickly in Resolution Center

What are the most common pitfalls with Lovable apps on iOS?

Most rejections and bugs come from web assumptions that do not hold inside WKWebView. Plan a day of iPhone-specific QA before your first submission.

Watch for file uploads that rely on desktop pickers, links that open external pages inside the app instead of Safari, and Stripe checkout for digital goods: selling digital content or subscriptions in an iOS app generally requires Apple's In-App Purchase under guideline 3.1.1.

  • Hard-coded localhost or preview URLs left in environment variables
  • Viewport zoom on input focus because font sizes are below 16px
  • Stale web bundle because npx cap sync was skipped after a Lovable change

When should you get help instead of doing it yourself?

If your app has payments, complex auth or a deadline, an experienced team saves weeks of trial and error with Apple review. Our AI Code Engineers at neooutput take Lovable projects from GitHub to TestFlight and the App Store, and if you prefer a no-code route, our sister product WebViewGold wraps web apps into native iOS apps with native features built in.

Either way, keep Lovable as your fast UI workshop and treat the native shell as a stable, version-controlled layer on top.

Frequently asked questions

Can I publish a Lovable app to the App Store without a Mac?

Yes, with a cloud build service such as Codemagic or Expo's EAS that runs macOS build machines for you. You still need an Apple Developer account and you will manage signing certificates in the cloud service. A Mac remains the most convenient option for debugging.

Does Lovable have a one-click App Store export?

Lovable focuses on web apps, so the usual route is GitHub sync plus Capacitor or a WebView wrapper. Check Lovable's current features, but plan for a native build step outside the editor.

Will Apple reject my Lovable app as a website wrapper?

It can under guideline 4.2 if it only shows your website. Bundling the web build locally and adding native features like push notifications, offline handling and native sharing significantly improves your chances, though approval is never guaranteed.

Do I need Sign in with Apple?

If you offer third-party or social logins such as Google, Apple requires an equivalent privacy-focused login option, which most teams solve with Sign in with Apple. Apps with only their own email login typically do not need it.

All insights