UrgisoftAI-built apps

AI-built apps ยท November 2026

Convert a Lovable app to iOS: three routes, the steps, and seven things that break it or get it rejected

Short answer: Lovable builds web apps, not native ones. Its own FAQ answers the question "native iOS or Android app?" with "Not as native apps" and names two ways onto a phone: make the published app installable from the browser (a PWA), or wrap it with a tool such as Capacitor outside Lovable and submit that to the App Store or Play Store. The wrapping itself is an afternoon. What takes the time is what comes after: login that stops working inside the wrapper, and Apple's review. Both are below, with the fix for each.

Pick your route first

RouteWhat people getWhat you needGood when
1. Home-screen app (PWA)They open your site in Safari and choose Share, Add to Home Screen. It gets an icon and opens full screen.Nothing to buy. No Mac, no review.You want it on phones this week, or your users are a known group you can send a link to.
2. Capacitor wrapperA real app in the App Store that shows your web app inside a native shell, and can use the camera, push notifications and other phone features through plugins.A Mac with Xcode, an Apple Developer Program membership (99 USD a year), your code on GitHub.You need to be found in the App Store, or need phone features.
3. Rebuild as a native appA separate app written for phones (React Native or Swift), using the same Supabase backend.A developer and weeks, not days. Lovable does not generate React Native projects.The phone app is the product and the web app is the side door.

If you are not sure, start with route 1. It costs nothing, and everything you fix for it (speed on phones, layout on a small screen, login) is needed for route 2 anyway.

Route 2, step by step

  1. Get the code out of Lovable. Connect the project to GitHub (Lovable creates a new repository from the project and keeps it in sync), then clone it to the Mac. In its folder: npm install, then npm run build. The build must finish without errors and leave a dist folder.
  2. Add Capacitor.
    npm i @capacitor/core
    npm i -D @capacitor/cli
    npx cap init
    npm i @capacitor/ios
    npx cap add ios
    When npx cap init asks for the web folder, answer dist (Lovable projects are built with Vite, which writes there). It is saved as webDir in the Capacitor config file.
  3. Copy the web app in and open Xcode.
    npm run build
    npx cap sync
    npx cap open ios
    Run the first two lines again after every change to the web app: sync copies the built files into the iOS project, it does not build them.
  4. Run it on your own iPhone first. In Xcode choose your team under Signing, plug the phone in and press Run. Sign up, log out, log in, pay, upload: everything a user does. Most of the seven problems below show up here, before Apple sees anything.
  5. Send it to Apple. In Xcode: Product, Archive, then upload to App Store Connect. Try it through TestFlight with a few people, fill in the store page (screenshots, privacy details, a privacy policy address), and submit for review.

Versions, from Capacitor's own setup page: Capacitor 8 needs Node 22 or higher, macOS, and Xcode 26.0 or higher. For Android the same steps use @capacitor/android and Android Studio; Google Play charges a one-time 25 USD, and a personal account created after November 13, 2023 must first run a closed test with at least 12 testers for 14 days.

Seven things that break it or get it rejected

  1. A white screen when the app opens. Usually the wrapper has no web app in it, or an old one. Check that webDir says dist, that npm run build ran before npx cap sync, and that the build did not fail quietly. Then look at the real error: with the app running from Xcode, open Safari on the Mac, Develop menu, your iPhone, and read the first red line in the Console.
    If the web app also shows a blank page in a normal browser, fix that first: six causes of a blank page.
  2. "Sign in with Google" stops working inside the app. Google does not allow its sign-in page to run inside an app's embedded web view; it answers with an error such as disallowed_useragent. The fix is to open the sign-in in the phone's own browser (or use a native sign-in plugin) and come back to the app through a link the app owns, and to add that return address to the allowed redirect addresses in Supabase. Email and password sign-in is not affected.
    More on redirect addresses: login and Supabase errors.
  3. Rejected as "a repackaged website" (guideline 4.2). Apple's words: an app "should include features, content, and UI that elevate it beyond a repackaged website." A wrapper that only shows the site is the classic case. Before you submit, make it behave like an app: no browser-style header or footer links, a layout that fits the notch and the home bar, a sensible screen when the phone is offline, and at least one thing the phone adds (notifications, camera, share sheet) if it fits what the app does.
  4. Google or Facebook login without a second option (guideline 4.8). An app that uses a third-party or social login for its main account must also offer an equivalent login service with the privacy features Apple lists there. Sign in with Apple is the usual way to meet it. Read the guideline for its exceptions.
  5. No way to delete the account (guideline 5.1.1(v)). "If your app supports account creation, you must also offer account deletion within the app." A "write to support" line is not enough: add a Delete account button that really removes the user and their data.
  6. Selling digital features with Stripe (guideline 3.1.1). Apple's rule is that unlocking features or content inside the app (subscriptions, premium content, a full version) goes through its in-app purchase. Section 3.1 also lists what is paid for another way, such as goods and services used outside the app, and the rules differ by country and have changed more than once, so read section 3.1 as it stands on the day you submit. This one is worth knowing before you build, not after a rejection.
  7. The reviewer cannot get in, or it crashes (guideline 2.1). Apple rejects apps that "crash or exhibit obvious technical problems," and submissions must be final versions, without placeholder text. If the app needs a login, give the reviewer a working demo account in the review notes, make sure the reviewer does not land on a private or invite-only screen, and test on a real phone on mobile data, not only on Wi-Fi.

Check it like a reviewer before you submit

On a real iPhone, with the app installed through TestFlight: (1) delete the app, install it again and sign up as a brand-new user. (2) Log out and back in with every sign-in button you show. (3) Do the main task from start to finish, payment included. (4) Turn on airplane mode and open the app: it should say it is offline, not show a white screen. (5) Find Delete account and use it on the test user. If all five hold, the seven problems above are not in your app.

This is a checklist, not a study: we have not counted how often each problem happens, and no checklist can promise that Apple approves an app. Read on November 21, 2026: Lovable's FAQ (web apps, the two routes, GitHub sync), Capacitor's documentation (the commands and versions), Apple's App Review Guidelines (2.1, 3.1.1, 4.2, 4.8, 5.1.1) and Apple's and Google's own pages for the fees and the testing rule. The rest (the white screen, Google sign-in inside a web view, the demo account, testing as a new user) is general engineering practice. Apple, Google and Lovable change their rules and menus often, so check their pages if something here does not match what you see. Urgisoft is not affiliated with Lovable, Apple, Google or Capacitor.

Other problems

A blank page after publishing: six causes. Login and Supabase errors: seven causes. Stripe payments not working: seven causes. Six security checks you can run yourself. Deploy to Vercel or Netlify. Base44 bug fixing. Replit app bug fixing. Fix AI-generated code: seven common problems. Slow on phones? Our demo shop, measured before and after: 14.5 s to 1.4 s. Not sure which problem you have? A ten-minute check.

Want the web app fixed first?

A wrapper shows your web app exactly as it is, so a bug on the web is a bug in the App Store. We fix apps made with Lovable, Bolt, Base44, Replit, Cursor and other AI builders: the blank screen, the login that fails, the payment that never arrives, the page that is slow on a phone, and we tell you in plain words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from $150. No fix, no charge. We never ask for your password. Your Apple developer account and the store submission stay in your hands.

See the gig on Fiverr