Robin North

Mirror recently changed `NetworkConnection` to no longer implement the `IDisposable` interface and instead just clean up directly on disconnection (see https://github.com/vis2k/Mirror/pull/1179), so `LiteNetLib4MirrorNetworkManager` should just need to call `conn.Disconnect();` now.

This Mirror change was reverted recently (see https://github.com/vis2k/Mirror/commit/4cc4279d7ddeaf61fe300b3dc420143e63942f1f), so this issue can be closed once the transport is updated to work with the latest Mirror release (7.2.1 at the time...

This could also potentially be combined with the Xcode project manipulation functionality from #11.

@vailshnast you should be able to move the settings file that's created by default at `Assets/SuperUnityBuild` to wherever you like in your folder structure, including to a path like `Assets/Plugins/SuperUnityBuild`....

Hey @tycobbb, thanks for this. I do need to take a look into it some more, as whilst SuperUnityBuild (should) currently support pointing the settings instance at an asset at...

Hi @3ternal, thanks for reporting this. I'll take a look into it, but it sounds like your suggestion might be the right way to go.

@nickfourtimes do you have your filter configuration set to match 'Any' or 'All' conditions? 'Any' is the default, and that would explain the behaviour you're seeing. 

Finally had some time to look into this further @nickfourtimes, and it seems that 'Single Run' BuildActions are *always* run once per build and ignore any filters that are configured...

Hey @mfdeveloper, SuperUnityBuild's CLI is currently just a single command, but it could already be used in a CI/CD environment: https://github.com/superunitybuild/buildtool/wiki/Command-Line-Interface What it's lacking is reporting errors or any of...

@skaggspa thanks for the report, I believe I have seen the same behaviour in 2021.1.15f on a project I'm working on, will try and find some time to investigate more...