Integration App "Install" fails with generic connectivity error — app never contacted

App: Pinky (01KSMSPEHFS9P0A30MTJNQTR67), owner erikvanmaanen@gmail.com

Steps to reproduce:

1. Create an Integration App with External Integration capability (Webhook URL, optional Setup Completed URL, App Home URL all configured and publicly reachable).

2. From the app's own App Details page (app.omi.me/my-apps/<app_id>), click Install.

3. Request fails immediately with: 400 {"detail":"This app is currently unavailable due to connectivity issues. The developer has been notified."}

What I've ruled out:

- All configured URLs (Webhook, Setup Completed, App Home, .well-known/omi-tools.json manifest) verified publicly reachable (200) at the exact moment of each failed install.

- Disabled External Integration entirely (no URLs configured at all) - install still fails identically.

- Toggled the app to Public and back - no change, fails identically either way.

- Installed a different, existing public app (Google Drive) from the same account in the same session - succeeds instantly, no errors. So this isn't an account-wide outage.

- Checked my own server's access logs (every inbound request logged with method/path/timestamp) for the exact timestamps of two separate failed Install attempts - zero requests of any kind arrived from Omi's backend in that window. So the "connectivity issues" check fails before any outbound call is even attempted - it isn't actually testing connectivity to my app.

Conclusion: looks like a bug in the install/validation path for a newly-created, never-installed Integration App, independent of app config, public/private status, or actual reachability.

Could someone check the install logs for app 01KSMSPEHFS9P0A30MTJNQTR67 around 2026-08-10T12:52:46Z and 2026-08-10T12:53:41Z UTC to see what's actually failing server-side? Happy to provide more detail.