# Broken App Diagnosis (Lovable, Bolt, v0, Replit) (`evocative_kumquat/broken-app-diagnosis`) Actor

GitHub repo URL in, plain-English diagnosis out. Clones the app, installs and builds it in a clean environment, renders it in a headless browser, and reports exactly what is broken and why: missing env vars, dependency conflicts, build blockers, white screens, leaked keys, SPA routing gaps.

- **URL**: https://apify.com/evocative\_kumquat/broken-app-diagnosis.md
- **Developed by:** [Dylan Caponi](https://apify.com/evocative_kumquat) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / complete app diagnosis report

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Broken App Diagnosis for AI-Built Apps

Your Lovable, Bolt, v0, or Replit app worked in the tool, then broke the moment it left: blank screen after deploy, build errors, "works for me but not for anyone else". This Actor tells you exactly what is wrong, in plain English, in a few minutes.

Give it a public GitHub repo URL. It will:

1. **Clone your app** into a clean, isolated environment (nothing from your machine, no stored logins, no env vars).
2. **Check the code statically**: missing `.env.example`, env vars your code needs but never documents, config modules that crash before React mounts, possible secret keys committed to client code, missing SPA rewrite config that 404s your routes after deploy.
3. **Install dependencies** with lifecycle scripts disabled, and classify failures (the classic `ERESOLVE` conflict AI tools create gets a specific explanation).
4. **Build the production bundle** and pinpoint blockers like `Cannot find module`, which usually means the AI used a package it never declared.
5. **Actually run your app** with a stack-aware runtime check, catching the "builds fine, ships a white screen" failure class:
   - Vite/SPA builds render in a headless browser and we measure whether your UI actually mounts.
   - Next.js apps boot with `next start` and get fetched over HTTP, so server crashes on startup, 500s, and "Application error" pages are caught.
   - Node/Express servers (and fastify, koa, hono) boot with `npm start`; we detect crash-on-boot, servers that never start listening, and error responses.

### Why a clean environment matters

Most "it broke after export" problems are invisible on the machine that grew the app, because that machine has the env vars, the logins, and the node\_modules that make it work. This Actor reproduces what a new user, a fresh deploy, or a collaborator actually experiences. That is where your bug lives.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `repoUrl` | string | Public GitHub repository, e.g. `https://github.com/owner/repo` |

### Output

- A ranked, plain-English markdown report in the run's key-value store (`OUTPUT`), worst problems first, each with what it means and how it gets fixed.
- A structured summary row in the dataset: blocker, risk, and note counts plus the verdict, so you can wire this into automations.

### What it covers

- Lovable, Bolt.new, and v0 exports (Vite + React + Supabase stacks get extra checks)
- Replit apps pushed to GitHub, including the fullstack template (Vite client + Express server)
- Any Vite, Next.js, or Node/Express JavaScript/TypeScript project with a standard install/build/start flow

Repos that are private, deleted, or not JavaScript projects fail fast with a clear message.

### Who built this

Built by [Vibe Code Rescue](https://dylancaponi.github.io/vibe-code-rescue/), a service that fixes broken AI-built apps. The same engine powers our free diagnosis intake; if the report finds something you want fixed rather than explained, that is what we do.

# Actor input Schema

## `repoUrl` (type: `string`):

Public GitHub repository of the app, e.g. https://github.com/owner/repo or just owner/repo. Works for Lovable and Bolt exports, v0 apps, Replit apps pushed to GitHub, and any Vite or Next.js project.

## Actor input object example

```json
{
  "repoUrl": "https://github.com/owner/my-lovable-app"
}
```

# Actor output Schema

## `report` (type: `string`):

The full plain-English diagnosis report as a markdown document, stored under the OUTPUT key of the run's key-value store.

## `summary` (type: `string`):

One dataset row per diagnosis with the verdict and counts of blockers, risks, and notes, plus the full report text.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "repoUrl": "https://github.com/hypestyle1/hypestyle-launchpad"
};

// Run the Actor and wait for it to finish
const run = await client.actor("evocative_kumquat/broken-app-diagnosis").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "repoUrl": "https://github.com/hypestyle1/hypestyle-launchpad" }

# Run the Actor and wait for it to finish
run = client.actor("evocative_kumquat/broken-app-diagnosis").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "repoUrl": "https://github.com/hypestyle1/hypestyle-launchpad"
}' |
apify call evocative_kumquat/broken-app-diagnosis --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,evocative_kumquat/broken-app-diagnosis"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3owhscqlxUf9KRe2d/builds/9FJy5TREBg5gQYxcL/openapi.json