Failed to create site after updating to 1.7.0

  • Unknown's avatar
    corrysalim8256 · Member ·

    Hi everyone,

    I’m using Macbook Pro 2017 MacOS Venture 13.7.8 (22H730) Everything was fine until last night WordPress Studio prompt me to update the software to 1.7.0 and after the installation I couldn’t open the previous site that I’m working with, it also can’t create a new site.

    These error appear as a respond:

    Failed to create site
    An error occurred while creating the site. Verify your selected local path is an empty directory or an existing WordPress folder and try again. If this problem persists, please contact support.
    CLI create site failed


    And here’s the log from that:

    [2026-01-24T09:32:24.213Z][info][main] Starting new session
    [2026-01-24T09:32:24.222Z][info][main] Checking for update on app launch: https://public-api.wordpress.com/wpcom/v2/studio-app/updates?platform=darwin&studioArch=x64&version=1.7.0
    [2026-01-24T09:32:24.597Z][info][main] App version: 1.7.0
    [2026-01-24T09:32:24.599Z][info][main] Environment: production
    [2026-01-24T09:32:24.602Z][info][main] Built from commit: 1d522b29b60f3c6d44429b581aa9d1468d6bf701
    [2026-01-24T09:32:24.640Z][info][main] Local timezone: Asia/Jakarta
    [2026-01-24T09:32:24.641Z][info][main] App locale: en-US
    [2026-01-24T09:32:24.641Z][info][main] System locale: en-ID
    [2026-01-24T09:32:24.641Z][info][main] Used language: en
    [2026-01-24T09:32:24.677Z][info][main] Copying bundled WP version 6.9.0 as ‘latest’ version…
    [2026-01-24T09:32:29.702Z][info][main] Copying bundled SQLite version 2.2.16…
    [2026-01-24T09:32:29.795Z][info][main] Copying bundled SQLite command version 1.1.5…
    [2026-01-24T09:32:30.244Z][info][main] Setting Sentry user ID: 691b13a4-500f-40f6-8d73-450f99cf7101
    [2026-01-24T09:32:31.880Z][warn][main] CLI events subscriber exited unexpectedly
    [2026-01-24T09:32:31.890Z][info][main] WordPress latest folder already exists. Skipping download.
    [2026-01-24T09:32:35.845Z][info][main] Downloaded wp-cli to /Users/Corry/Library/Application Support/Studio/server-files/wp-cli.phar
    [2026-01-24T09:32:36.181Z][info][main] SQLite Command is up to date.
    [2026-01-24T09:37:26.528Z][info][main] Manually checking for update: https://public-api.wordpress.com/wpcom/v2/studio-app/updates?platform=darwin&studioArch=x64&version=1.7.0
    [2026-01-24T09:40:15.715Z][erro][main] Error occurred in handler for ‘createSite’: Error: CLI create site failed
    at CliCommandEventEmitter. (/Applications/Studio.app/Contents/Resources/app.asar/dist/main/index.js:15369:14)
    at CliCommandEventEmitter.emit (node:events:519:28)
    at CliCommandEventEmitter.emit (/Applications/Studio.app/Contents/Resources/app.asar/dist/main/index.js:15169:18)
    at ChildProcess. (/Applications/Studio.app/Contents/Resources/app.asar/dist/main/index.js:15236:20)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1101:16)
    at Socket. (node:internal/child_process:456:11)
    at Socket.emit (node:events:519:28)
    at Pipe. (node:net:346:12)
    [2026-01-24T09:40:15.727Z][erro][ren1] Failed to create site
    [2026-01-24T10:05:39.837Z][info][main] App is terminating



    What I have tried so far but now working:
    – Create a new local path
    – Waiting for GitHub 403 rate limit over
    – Turn off my VPN
    – Remove some folder so that the Studio can install it again when starting up

    – Clean uninstall and install it again using a fresh studio-darwin-x64-v1.7.0.dmg dowloaded from Studio website.

    I also tried this:

    ➜  ~ ls ~/Library/Application Support/Studio/server-files

    sqlite-command              wordpress-versions

    sqlite-database-integration wp-cli.phar

    ➜  ~ php ~/Library/Application Support/Studio/server-files/wp-cli.phar –info

    zsh: command not found: php

    And now installing php but somehow it never finish so I try to consult in here.
    Thank you

  • Unknown's avatar
    corrysalim8256 · Member ·

    Bug Report: Trace Trap / SIGTRAP Crashes on Intel Macs (macOS 13 Ventura)

    Environment

    • Hardware : Intel x86_64
    • OS : macOS Ventura 13.7.8
    • Studio Version : 1.7.0 (Bundled with Node v22.20.0)
      The Problem After the auto-update to version 1.7.0, WordPress Studio becomes completely unusable on Intel-based Macs. Any attempt to create a site, start a site, or even run studio site list in the CLI results in a trace trap (SIGTRAP) crash.

    Root Cause Analysis The crash occurs within the V8 engine of the bundled Node.js v22 binary. Specifically, it fails during memory allocation/permission setting in the Sparkplug (Baseline) and RegExp compilers.

    • Primary Error : Check failed: 12 == (*__error()) (ENOMEM/Permission error).
    • Stack Trace Location : v8::internal::baseline::BaselineCompiler::Build and v8::internal::RegExpMacroAssemblerX64::GetCode .
    • Reason : Node 22’s JIT compilers attempt to set memory permissions (executable/writeable) in a way that is blocked by the security/memory management layer of macOS Ventura on Intel architecture.

    How We Overcame This (Step-by-Step)

    To fix this, we had to bypass the bundled “poisoned” Node binary and force Studio to use a stable system Node.

    1. Verification of Architecture We confirmed the binary was the correct architecture but crashing anyway:
    file "/Applications/Studio.app/Contents/Resources/bin/node"
    # Result: Mach-O 64-bit executable x86_64
    1. Attempting Node Flags (Failed) We tried disabling the crashing compilers via NODE_OPTIONS=”–no-sparkplug” . This failed because:
    • The internal studio-cli.sh script explicitly runs unset NODE_OPTIONS .
    • Packaged Electron apps often ignore NODE_OPTIONS for security reasons.
    1. The Solution: Binary Hot-Swapping We successfully resolved the issue by physically replacing the bundled Node 22 binary with a symlink to a stable system Node (v20 or v18), which handles Intel memory permissions correctly.

    The Fix Script:

    # Backup the crashing bundled node
    sudo mv /Applications/Studio.app/Contents/Resources/bin/node /Applications/Studio.
    app/Contents/Resources/bin/node.bak
    # Symlink the working system node into the app
    sudo ln -s $(which node) /Applications/Studio.app/Contents/Resources/bin/node
    # Update the launcher script to ensure it respects the link
    # (Ensuring CONTENTS_DIR and CLI_SCRIPT paths are preserved)
    1. Site Re-Registration Because the Application Support/Studio data was cleared during troubleshooting, we had to re-register the existing site directory:
    studio site create --path /path/to/existing-site
    studio site start

    Recommendations for the Studio Team

    1. Node Version Compatibility : Re-evaluate the stability of bundling Node 22 for Intel/Ventura users. A downgrade to Node 20 LTS for the Intel build may resolve this.
    2. Graceful Failover : If the bundled PHP-WASM worker fails with a trace trap , provide a meaningful error message instead of a generic “Failed to start site.”
    3. CLI Script Flexibility : Modify studio-cli.sh to allow users to override the Node binary path via an environment variable (e.g., STUDIO_NODE_PATH ) without needing to sudo into the app bundle.
Log in or create an account to reply