AppCode 2016.2 Help

Diagnosing Problems with Subversion Integration

On this page:


If any problem occurs with Subversion integration, feel free to contact our support. To facilitate detecting, locating, and resolving your problems, provide detailed information regarding your Subversion integration with AppCode. This topic lists the necessary information and explains how you can retrieve it.

The following data is usually required to diagnose Subversion problems:

  • The AppCode version and the build number.
  • The operating system used.

VCS and its general settings

The version control system used in your project or in its parts and the general version control settings applied to your project are specified on the Version Control page of the Settings/Preferences dialog.

Subversion settings

Subversion-specific settings are configured on the Subversion page, under the Version Control node of the Settings/Preferences dialog.

The format of the local working copy

The working copy format is the Subversion format in compliance with which the working copy was created. To view the format of a working copy, choose View | Tool Windows | Version Control on the main menu. In the Version Control tool window that opens, switch to the Subversion Working Copies Information tab.

Parent folders of the branches used

To view the configuration of branches, in the Subversion Working Copies Information tab of the Version Control tool window, click the Configure Branches link.

Enabling svnkit logging

If data saved in the AppCode logs is not sufficient to solve the problem and the problem is related to the communication protocol or authentication, enable svnkit logging, reproduce the problem, and attach the idea.log.

To enable svnkit logging, add -Djavasvn.log=true as described here:

See Also

Last modified: 20 July 2016