Known issues in Acquia Dev Desktop¶

Acquia Dev Desktop is incompatible with macOS Catalina¶

The current version of Acquia Dev Desktop is incompatible with macOS Catalina.

Recent Acquia Dev Desktop releases support only 64-bit versions of Windows¶

Recent versions of Acquia Dev Desktop are incompatible with 32-bit versions of the Windows operating system.

Workaround: Install the July 23, 2018 release of Acquia Dev Desktop, which supports PHP versions up to and including 7.1.12, and is available from the Acquia Dev Desktop Historical releases page.

Acquia Dev Desktop doesn’t support usernames that include non-ASCII characters¶

Workaround: Use a Windows account with a username that includes only ASCII characters.

Windows file paths must be less than 260 characters¶

The path of a file can’t be longer than the Windows maximum path length of 260 characters, which you can exceed when trying to clone an Acquia Cloud website, or pulling files or code from Acquia Cloud.

Workaround: Either install Acquia Dev Desktop and the websites directory into a shorter Windows path (for example, c:\dd or c:\sites, rather than c:\program files\dev desktop\...) or consider renaming long custom file or path names in your Acquia Cloud website.

Elevated permissions required for Microsoft Windows¶

Acquia Dev Desktop requires elevated permissions for both installation, and operation on computers running Microsoft Windows.

Apache server fails to start on Windows 8 and 10¶

Some Microsoft Windows version 8 and version 10 users have reported that Acquia Dev Desktop fails to stop and restart Apache correctly during the website installation process, which prevents installation from completing successfully.

Workaround: While Acquia corrects this issue, use one of the following two potential methods:

• On the Acquia Dev Desktop menu, click Preference, click the Config tab, and then click the Edit link next to the Apache field. This opens the httpd.conf file in Notepad. Close the file without making changes, which may allow you to create a new website.
• Before starting or restarting the application stack in Acquia Dev Desktop, use the Task Manager to end the Apache process manually.

Cloning fails if the website’s name is longer than 21 characters¶

Acquia Dev Desktop can’t make a local clone of an Acquia Cloud website if the website’s name is longer than 21 characters.

Workaround: Export your website from Acquia Cloud, and then import it as a new website that has a name that’s 21 characters or less in size. Then, you can make a local clone of the new website in Acquia Dev Desktop.

Acquia Dev Desktop may fail to regenerate correct symlink¶

Acquia Dev Desktop doesn’t regenerate the correct symlink to point to a customer’s file system if the following case is true:

• Acquia Dev Desktop generates a symlink that points to a file system, and that symlink is then checked into a customer’s codebase.

Workaround: Remove the symlink from Acquia Dev Desktop, and then deploy code without it. Acquia Dev Desktop should then regenerate the correct symlink.

Acquia Dev Desktop doesn’t support syncing with Acquia Cloud Site Factory¶

The Acquia Dev Desktop Host on Acquia Cloud or Clone from Acquia Cloud buttons work with Acquia Cloud websites only, and not with Acquia Cloud Site Factory websites.

Acquia Cloud Site Factory overwrites information in settings.php¶

The acsf-init command in Acquia Cloud Site Factory removes lines in settings.php inserted by Acquia Dev Desktop.

Workaround: Remove Acquia Dev Desktop changes to your settings.php file with git stash before executing the acsf-init command, unstashing the changes afterward.

PHP 7.3 is not available in Acquia Dev Desktop¶

Acquia Dev Desktop times out during stack start¶

You could get a timeout error (for example, Process 'MySQL database server' failed to start) while starting Acquia Dev Desktop if you have unusually large, or many databases. If this happens, you can try increasing the startTimeout, as described in Troubleshooting: Timeout during stack start.

Domain Access module requires special configuration¶

To use the Domain Access module with Acquia Dev Desktop, you must add a ServerAlias entry in the Acquia Dev Desktop Apache vhosts.conf configuration file. For details, see Using Domain Access with Acquia Dev Desktop.

Syncing fails for websites with too many files, or too large files¶

Sites hosted on Acquia Cloud may not be able to sync locally if they have too many files in one directory or extremely large files. For information about addressing files issues, see Understanding files, Proactively organizing files in subfolders, and Optimizing file paths: Organizing files in subfolders.

Acquia Dev Desktop fails to connect to Acquia Cloud from behind a firewall¶

Some users may experience connection issues or other seemingly unrelated errors when attempting to sync their Acquia Cloud websites locally or report bugs. This may be due to firewalls between your local computer and Acquia Cloud.

Workaround - Acquia recommends you whitelist *.acquia.com/ in your firewall.

Trusted Host Settings not enabled¶

Some Drupal websites show a Trusted Host Settings Not enabled message. See Protecting against HTTP HOST Header attacks (prevent your site from thinking it’s someone else) for suggestions.

Drupal 8 installation displays a fatal error¶

When attempting to install Drupal 8, the installation process displays the following fatal error:

'The service definition "renderer" does not exist.'

Workaround: Don’t supply a password when prompted for database credentials. For information about a Drupal core patch that can avoid this issue, see Exception during installation when auto creating the MySQL database with special characters on Drupal.org.