Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
1
Found in
2020.1.0a23
Issue ID
1224872
Regression
Yes
Apple File Merge not supported by Collaborate as diff tool
How to Repro:
1. Open a Collab-enabled Project in Unity 2020.1+.
2. Open the Preferences menu, go to External Tools and make sure that Apple File Merge is selected as the Revision Control Diff/Merge Tool.
3. Create small change in SampleScene.unity and save.
4. Open the Collab Window by pressing the Collab button.
5. On the modified SampleScene asset, hover over it and choose to See Differences.
Expected: Apple File Merge should open and highlight the changes made in SampleScene.unity.
Actual: Apple File Merge doesn't open, in the Collab Window there is a red error that says "Sorry, something went wrong, please try again later."
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
chachi
Jul 07, 2020 21:38
EDIT: documentation for setting up a custom Diff tool is ready here: https://docs.unity3d.com/2020.2/Documentation/Manual/Preferences.html
chachi
Jul 07, 2020 21:27
Same here. I tried setting up VSCode as my diff tool but failed to find the needed params.
Purple-Toupee
Mar 23, 2020 07:45
Additionally, I can't use a 3rd party tool because there is no documentation on how to set up the command line args. I can't tell what tokens to use to represent the file names, and leaving the command line arguments blank passes nothing.