Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.2.0b8
Issue ID
949497
Regression
No
Manifest.json is not tracked by VCS plug-in
When using P4V as a source control, the Unity Editor integration doesn't pick up on changes made to the manifest.json file contained on the project root.
1. Enable P4V,
2. Start Unity Editor,
3. Navigate to Project Settings on the EDIT menu
4. Select EDITOR from the list (note that this will open a settings panel on the Inspector window)
5. On the version control section select Perforce
6. Edit the values with the ones that reflect the values of your P4V setup
7. If successful, notice that files are now tracked
8. Navigate to the local Unity project.
9 Find and edit manifest.json.
10. Notice that upon changing the manifest file, that this one doesn't appear on the "incoming" changes in the VCS plug-in.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment