Diagnosing Problems with Subversion Integration
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
- Subversion settings
- The format of the local working copy
- The parent folders of the branches used
- AppCode log
- AppCode.log with svnkit logging enabled
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 Preferences dialog box.
The format of the local working copy
The format of a working copy is the Subversion format in compliance with which the working copy was created. To view the format of a working copy, choose Version Control tool window that opens, switch to the Subversion Working Copies Information tab.on the main menu. In the
The 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.
To open the folder with AppCode logs, choose.
Enabling svnkit logging
If the data saved in the AppCode logs is not sufficient to solve the problem and the problem is
related to communication protocol or authentication,
enablesvnkit logging, reproduce the problem, and attach the
To enable svnkit logging, add
as described here: