Solve Known Version Control Issues

Last update: Edit

1 Introduction

Mendix Studio Pro contains a version control system that supports collaborating with team members. This document presents fixes that can be used when version control problems arise.

For more information and general help on version control, see the following documents:

2 Errors & Fixes

Below is a list of known errors and the steps to fix them.

2.1 Getting an Error Containing SharpSvn.SvnAuthenticationException: Proxy authentication failed

Error dialog with proxy authentication failed

This error means that Studio Pro has problems reaching the version control server because of a proxy server.

Follow these steps:

  1. Go to Edit > Preferences.
  2. Go to the Advanced tab.
  3. In the Proxy server section, change the Proxy server settings. Fill in the correct User name and Password.

    Proxy settings

2.2 Getting an Error Containing Another SharpSvn.SvnAuthenticationException

When this error occurs, sign out of Studio Pro and then log back in to resolve it.

2.3 Getting an Error with the Message Connection timed out

To solve this issue, follow these steps:

  1. Open the \Users<username>\AppData\Roaming\Subversion\servers file with any text editor.
  2. Add the text http-timeout = 5000 under the section [global].
  3. Save the file.

2.4 Getting an Error with the Message <app folder> is already locked

To solve this issue, follow these steps:

  1. Install TortoiseSVN, as suggested in System Requirements.

  2. Go to the parent directory (folder) of your app (this is the folder with the from the error message).

  3. Right-click to open the folder’s context menu and select TortoiseSVN > Clean up.

2.5 Getting an Error with the Message System.Security.Cryptography.CryptographicException: Key not valid for use in specified state

Follow these steps to remove your user settings and restart Studio Pro:

  1. Rename \Users<username>\AppData\Local\Mendix\Settings.sqlite to Settings.sqlite.old.
  2. Restart Studio Pro.

2.6 Getting an Error with the Message SharpSvn.SvnRepositoryIOException: At least one property change failed; repository is unchanged

To solve this issue, follow the steps below:

  1. Install TortoiseSVN, as suggested in System Requirements.
  1. Open the app folder via Studio Pro by selecting App > Show App Directory in Explorer.

  2. Right-click the background of the app folder and select TortoiseSVN > Properties. The Properties dialog box opens.

  3. Double-click the svn:ignore property. The Edit Properties dialog box opens.

  4. Copy all text of the Property value via Ctrl+A followed by Ctrl+C.

  5. Paste the text into a new document in Notepad++ (or another editor that understands newline conventions).

  6. In the lower right, double-click Windows (CR LF) and select Unix (LF) instead. This will change the newline type from CRLF to LF.

  7. Copy all text again.

  8. Go back to the Edit Properties dialog box.

  9. Replace the current content by pasting from the clipboard via Ctrl+A followed by Ctrl+V.

  10. Click OK to close the Edit Properties dialog box.

  11. Click OK to close the Properties dialog box.

  12. Restart Studio Pro.

You can now commit your app.

2.7 Resolving Conflicts on the svn:ignore Property

When you merge or update branches, a conflict is sometimes reported on the app folder rather than on an individual file. This usually means there is a conflict on the svn:ignore property.

In the svn:ignore property, Subversion records which files should be ignored. These are files that are on disk but should not be on Team Server.

For example, the deployment directory is necessary for running your app, but it should not be on the Team Server. Each user has their own version of the deployment folder on their hard disk.

You will need to resolve the conflict before you can commit your app to Team Server.

2.7.1 Example

In this example, we will focus on merging a branch into the main line. On the main line, the list of ignored files looks like this:

modeler-merge-marker
.mendix-cache
ResolveIgnoreConflict.mpr.lock
*.launch
ResolveIgnoreConflict.mpr.bak
node_modules

On the branch, the list looks like this:

modeler-merge-marker
.mendix-cache
ResolveIgnoreConflict.mpr.lock
*.launch
ResolveIgnoreConflict.mpr.bak
.project
.classpath
deployment

Merging the branch to the main line will result in the following information message:

To resolve a conflict on the svn:ignore property, follow these steps:

  1. Install TortoiseSVN, as suggested in System Requirements.

  2. Open the app directory in Windows File Explorer.

  3. Right-click the background of the app folder and choose TortoiseSVN > Edit Conflicts. The following pop-up window will be shown (resize the window to display all the information):

  4. Copy all the lines starting with modeler-merge-marker to the clipboard.

  5. Click Manually edit property.

  6. Double-click the svn:ignore line in the grid.

  7. Paste the previously copied lines via Ctrl+A followed by Ctrl+V.

  8. Remove the special lines that start with <<<<<<<, =======, and >>>>>>>. For this example, we end up with the following combined ignore list:

  9. Click OK and then OK again to confirm the change.

  10. Right-click the background of the app directory and choose TortoiseSVN > Edit Conflicts again.

  11. Click Resolve using local property.

You have resolved the conflict and can commit from Studio Pro.

2.8 Getting an Error with the Message SharpSvn.SvnRepositoryIOForbiddenException: Access to '/.../!svn/rvr/1/trunk' forbidden

If you get this error, try the following options:

  • In the Developer Portal, check whether the user has access to the app:
    • If they do not have access, invite them to the app
    • If they do have access, remove them from the app and add them back – this will re-sync the access rules
  • If the above does not work, make sure the WebDAV protocol is not blocked within your network. This protocol is required by Studio Pro for version control to work, but it might be blocked by your proxy server or other software like a firewall.

3 Other Problems

If the solutions here do not work for your version control problems, please submit a request to Mendix Support.

4 Read More