Skip to main content

Troubleshooting FAQs

Solutions to the most common problems you might encounter.

Installation Issues

Try these steps:
  1. Check you have macOS 15.1 or later
  2. Right-click the app, choose “Open” to bypass Gatekeeper
  3. Go to System Settings → Privacy & Security → Allow Nativeline
  4. Restart your Mac and try again
  5. Re-download from nativeline.ai
If Xcode install gets stuck:
  1. Check internet connection
  2. Ensure at least 30GB free space
  3. Restart Nativeline — it should resume
  4. Check System Settings → Software Update for pending updates
  5. Try installing Xcode manually from App Store, then reopen Nativeline
You need macOS 15.1 (Sequoia) or later.To update:
  1. System Settings → General → Software Update
  2. Download and install the latest macOS
  3. Some older Macs may not support macOS 15
Check Apple’s compatibility list for your Mac model.
Nativeline + Xcode requires about 30GB.To free space:
  1. Empty Trash
  2. Delete old Downloads
  3. Use Storage Management (Apple menu → About This Mac → Storage → Manage)
  4. Remove unused apps
  5. Clear system caches

Building Issues

If the app won’t build:
  1. Check the error message in the build output
  2. Let the AI try to fix it (up to 3 attempts)
  3. Describe the error to the AI in your own words
  4. Try: /planclear to reset and start fresh
  5. As last resort, create a new project and rebuild
See our Debugging Guide for detailed steps.
When automatic fixing fails after 3 attempts:
  1. A Continue Fixing card appears in the chat
  2. Optionally add more context in your message
  3. Click Continue Fixing to let the AI try again
  4. If still failing, describe the problem differently
  5. Try: “Let’s try a completely different approach”
The simulator is embedded in the right side of the Build tab for iPhone and iPad apps. If it’s not appearing:
  1. Make sure the build succeeded (check for errors in chat)
  2. Wait a moment — first launch takes 30-60 seconds
  3. Restart Nativeline and rebuild
  4. Check that Xcode is installed
Mac apps run natively in their own window — there’s no simulator for Mac.
To reset the embedded Simulator:
  1. In Simulator: Device → Erase All Content and Settings
  2. Wait for reset to complete
  3. Click “Run App” in Nativeline
  4. Fresh build should install
This clears all cached app data.
Common causes:
  • Missing permission descriptions (add in Settings → Permissions)
  • Invalid initial state
  • Missing data the app expects
Debug:
  1. Check build output for crash log
  2. Tell the AI: “The app crashes on launch. Here’s the error: [paste error]”
  3. The AI will analyze and fix
After AI makes changes:
  1. Wait for the AI to finish completely
  2. Look for “Run App” button or wait for auto-run
  3. Watch for build output
  4. Check Simulator after build succeeds
If still not appearing, erase Simulator content and rebuild.

AI Issues

Tips for better results:
  1. Be more specific — include details
  2. Break into smaller requests
  3. Try rephrasing your request
  4. Share a screenshot of what you want
  5. Say “That’s not right, I wanted X instead”
See Prompt Writing Workshop for techniques.
When AI is stuck in a loop:
  1. Type /planclear to clear the current plan
  2. Say “Let’s try a completely different approach”
  3. Be more specific about what’s wrong
  4. Break the task into smaller pieces
  5. Provide examples or reference images
Sometimes the AI reports completion but nothing was actually created, and the plan stays active (not checked off).To fix this:
  1. Type /planclear to clear the stuck plan
  2. Re-request the feature with different wording
  3. The AI will start fresh and complete the task
This can happen occasionally when the AI misinterprets the request. Rephrasing usually resolves it.
Possible reasons:
  • Complex request taking time
  • Server load (try again later)
  • Large project context being processed
The AI shows a loading indicator while working. Complex tasks take more time.
You’ve used your monthly bit allocation.Options:
  • Wait for monthly reset
  • Upgrade to a higher plan
Check your usage in Settings → Account.

Account Issues

Try these steps:
  1. Verify email address is correct
  2. Check for 8-digit code in spam folder
  3. Click “Resend Code” and wait 2-3 minutes
  4. Try a different email address
  5. Contact support@nativeline.ai
Email issues:
  1. Check spam/junk folder
  2. Wait 2-3 minutes (can be delayed)
  3. Add nativeline.ai to your contacts
  4. Click “Resend Code” in the app
  5. Try a different email (Gmail, iCloud work well)
If you paid but don’t have access:
  1. Close and reopen Nativeline
  2. Go to Settings → Account → Restore Purchases
  3. Check the subscription is active in your Apple ID settings
  4. Wait a few minutes and try again
  5. Contact support with your receipt

Toolkit Issues

If typing # doesn’t open the Toolkit popover:
  1. Make sure you type # at the beginning of a word in the chat input
  2. The popover should appear with Assets and Data sections
  3. If nothing happens, try deleting and retyping #
  4. Restart Nativeline if the issue persists
If your asset appears as an orange chip but the AI ignores it:
  1. Make sure you describe what the AI should do with the file
  2. Be specific: “Use this image as the app background” not just “here’s an image”
  3. Check the file format is supported (see Toolkit)
  4. Try removing the chip and re-attaching the file
Each # command supports specific formats:
  • #image — PNG, JPEG, GIF, HEIC, TIFF, BMP, SVG
  • #font — TTF, OTF
  • #data — JSON, CSV
  • #sound — MP3, WAV, AIFF
  • #video — MOV, MP4
  • #lottie — JSON (Lottie format)
  • #3d — USDZ, Reality
#color opens a color picker, not a file picker.

Publishing Issues

Common causes:
  1. Check internet connection
  2. Verify Apple Developer account is connected
  3. Ensure Bundle ID matches App Store Connect
  4. Check for missing app icon (1024x1024)
  5. Try resetting signing certificates in Settings
See TestFlight Troubleshooting for more.
Apple processing can take 10-30 minutes, sometimes longer.If longer than 2 hours:
  1. Check Apple System Status
  2. Upload a new build with incremented number
  3. Wait up to 24 hours before contacting Apple
Handle rejection:
  1. Read the rejection reason carefully
  2. Fix each issue mentioned
  3. Upload new build if code changes needed
  4. Reply in Resolution Center
  5. Resubmit for review
See Review Guidelines to avoid common rejections.
If DMG export fails:
  1. Make sure your Apple Developer account is connected
  2. Check that code signing certificates are valid
  3. Ensure the app builds successfully first
  4. Try again — notarization can sometimes time out
  5. Check internet connection (notarization requires Apple’s servers)
See DMG Export Guide for the full process.

Performance Issues

To improve performance:
  1. Close other heavy applications
  2. Restart Nativeline
  3. Restart your Mac
  4. Check Activity Monitor for resource usage
  5. Ensure enough free storage (at least 10GB)
Building apps uses significant CPU. This is normal, but:
  1. Work in a well-ventilated area
  2. Close unnecessary apps
  3. Take breaks between heavy build sessions
  4. Check that fans are working (Activity Monitor)
Speed up builds:
  1. Close other applications
  2. Quit and reopen Nativeline occasionally
  3. First build is always slowest
  4. Incremental builds are faster

Still Stuck?

Check the Guides

Contact Support

Email: support@nativeline.ai Include:
  • What you were doing
  • What happened
  • What you expected
  • Any error messages
  • Screenshots if helpful

Join the Community

  • Discord — Get help from other users
  • Search for similar issues others have solved
  • Share your solution to help others

Building Apps

AI and building questions

Toolkit

Asset and # command questions

Technical

Code and Swift questions

Publishing

TestFlight and App Store