Known issues in Acquia Dev Desktop

This page describes known issues in Acquia Dev Desktop. For more information, see Troubleshooting. If you find a problem that isn't listed on this page, see Reporting issues, feature requests, and bugs for information about how to let us know.

  • Incompatible with Drupal 8.4.0 and greater

    The following issues affect attempts to use Drupal 8.4.0 and greater with Acquia Dev Desktop:

    • Acquia Dev Desktop includes Drush version 8.1.10, but does not include Drush version 8.1.14 (which is required by Drupal versions 8.4.0 and greater).
    • If you execute composer update for a website, Composer will also attempt to update the Doctrine library to a version that requires PHP 7.1, which is incompatible with Acquia Dev Desktop.
  • Incompatible with PHP 7.1

    Acquia Dev Desktop includes PHP version 7.0, but does not include PHP 7.1.

  • Included PHP 7 and Xdebug issues
    Xdebug may not work properly with the included version of PHP 7. You can download an updated version of Xdebug here.
  • Timeout 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.
  • Acquia Dev Desktop cannot 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 is 21 characters or less. Then you can make a local clone of the new website in Acquia Dev Desktop.

  • Domain Access module requires special configuration

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

  • Acquia Dev Desktop does not support usernames that include non-ASCII characters

    This limitation does not apply to the Mac version of Acquia Dev Desktop. On Windows, use a Windows account with a username that includes only ASCII characters.

  • On Windows, the path of a file cannot be longer than the Windows maximum path length of 260 characters

    This limitation does not apply to the Mac version of Acquia Dev Desktop. You can experience this issue when trying to clone an Acquia Cloud website, or pulling files or code down 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.

  • Problems syncing with large websites
    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 About files, Proactively organizing files in subfolders, and Optimizing file paths: Organizing files in subfolders.
  • Acquia Dev Desktop does not support syncing with Acquia Cloud Site Factory
    Acquia Dev Desktop's Host on Acquia Cloud or Clone from Acquia Cloud buttons work only with Acquia Cloud websites, and not with Acquia Cloud Site Factory websites.
  • Acquia Cloud Site Factory overwrites Acquia Dev Desktop's 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's changes to your settings.php file with git stash before executing the acsf-init command, unstashing the changes afterward.

  • Acquia Cloud connection issues when using Acquia Dev Desktop 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 that you whitelist *.acquia.com/ in your firewall.
  • 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.
  • 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 is 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 - Do not 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.

Contact supportStill need assistance? Contact Acquia Support