Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xbuild and msbuild preserves readonly file permission when copying referenced assembly. #10743

Closed
lambdageek opened this issue Sep 21, 2018 · 9 comments · Fixed by #10934

Comments

@lambdageek
Copy link
Member

@lambdageek lambdageek commented Sep 21, 2018

Found this while debugging a xamarin-macios failure using the mono-2018-08 branch.

Steps to Reproduce

  1. Download and extract attached
    Xamarin.MMP.Tests.MMPTests.RunMMPTest68.zip
  2. edit UnifiedExample.csproj to adjust the HintPath for b.dll
  3. Note that b.dll in the project is readonly.
  4. Run xbuild or msbuild (Both behave the same way)
  5. ls -l bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll

Current Behavior

Output of ls is

-r-xr-xr-x  1 alklig  staff  3072 Sep 21 11:24 bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll

Note that the result file is readonly.

Expected Behavior

-rwxr-xr-x  1 alklig  staff  3072 Sep 21 11:24 bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll

Note that the result file is readwrite.

On which platforms did you notice this

[x] macOS
[ ] Linux
[ ] Windows

Version Used:

Bad result: mono 5.16 and 5.18.

Expected result: mono 5.14

Please see xamarin/xamarin-macios#4596 (comment) for the failure in-situ. The test is called Xamarin.MMP.Tests.MMPTests.Dontlink_Allow_ReadonlyAssembly

@lambdageek

This comment has been minimized.

Copy link
Member Author

@lambdageek lambdageek commented Sep 21, 2018

/cc @radical

@marek-safar

This comment has been minimized.

Copy link
Member

@marek-safar marek-safar commented Sep 27, 2018

There is not much special in msbuild about it.

@lambdageek could you try to reproduce it with simple File.Copy BCL call?

@radical could you extract msbuild repro for it?

@lambdageek

This comment has been minimized.

Copy link
Member Author

@lambdageek lambdageek commented Sep 27, 2018

File.Copy ("x.from", "x.to", True); when x.from is readonly and x.to doesn't exist creates a readonly x.to. So just using File.Copy and not fixing up the permissions doesn't give the result that XM expects.

@radical radical self-assigned this Sep 27, 2018
@radical

This comment has been minimized.

Copy link
Member

@radical radical commented Sep 27, 2018

I'm not able to reproduce this with 5.16.05, 5.16.0.152 or 5.18.0.106 . One thing to note is that msbuild (via the Copy task) is copying b.dll only to bin/Debug/b.dll, which has the expected permissions. But the file that mentioned above, bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll, is copied by the mmp task from XI and not msbuild itself. But I'm not being able to reproduce that either.

@lambdageek should I be using a jenkins build of XI for this?

@lambdageek

This comment has been minimized.

Copy link
Member Author

@lambdageek lambdageek commented Sep 27, 2018

@radical I'm using the versions below. As far as I know, this is all released Alpha channel stuff, except for mono 5.18.0.115 which is from Jenkins.

Visual Studio Enterprise 2017 for Mac (Preview)
Version 7.8 Preview (7.8 build 408)
Installation UUID: c1b3b394-68d8-4231-92e8-47d068034506
Runtime:
	Mono 5.18.0.115 (2018-08/005c804cb2c) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)
	Xamarin.Mac 4.4.1.178 (master / eeaeb7e6)

	Package version: 518000115

NuGet
Version: 4.3.1.4445

.NET Core
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
	2.1.2
	2.1.1
	2.1.0
	2.0.7
	2.0.6
	2.0.5
SDK: /usr/local/share/dotnet/sdk/2.1.302/Sdks
SDK Versions:
	2.1.302
	2.1.301
	2.1.300
	2.1.200
	2.1.103
	2.1.4
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.18.0/lib/mono/msbuild/15.0/bin/Sdks

Xamarin.Profiler
'/Applications/Xamarin Profiler.app' not found

Apple Developer Tools
Xcode 10.0 (14320.25)
Build 10A255

Xamarin.Mac
Version: 4.8.0.22 (Visual Studio Enterprise)
Hash: bd81f1c3
Branch: 
Build date: 2018-08-24 17:10:45-0400

Xamarin.iOS
Version: 11.16.0.22 (Visual Studio Enterprise)
Hash: bd81f1c3
Branch: HEAD
Build date: 2018-08-24 17:10:45-0400

Xamarin.Android
Version: 9.1.0.17 (Visual Studio Enterprise)
Android SDK: /Users/alekseyk/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
		6.0   (API level 23)
		7.1   (API level 25)
		8.0   (API level 26)
		8.1   (API level 27)

SDK Tools Version: 26.0.2
SDK Platform Tools Version: 26.0.0
SDK Build Tools Version: 23.0.3

Java SDK: /usr
java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Android Device Manager
Version: 1.1.652.0
Hash: d9c8ea86

Xamarin Inspector
Version: 1.4.3
Hash: db27525
Branch: 1.4-release
Build date: Mon, 09 Jul 2018 21:20:18 GMT
Client compatibility: 1

Build Information
Release ID: 708000408
Git revision: 71e204ffc2fbfac5fd56710ad49746b77ce1361d
Build date: 2018-09-07 16:55:06+00
Build branch: master
Xamarin extensions: b2631e0f54e48c46f45e661017f59180fd419d73

Operating System
Mac OS X 10.14.0
Darwin 18.0.0 Darwin Kernel Version 18.0.0
    Wed Aug 22 20:13:40 PDT 2018
    root:xnu-4903.201.2~1/RELEASE_X86_64 x86_64

Enabled user installed extensions
AddinMaker 1.4.3
@radical

This comment has been minimized.

Copy link
Member

@radical radical commented Sep 27, 2018

After installing everything from the alpha channel, I am able to reproduce this. But IIUC, this is a XM/mmp issue, as I can reproduce it with just mmp (which doesn't depend on msbuild) by running it with the arguments obtained from a build:

          /verbose 
          /debug 
          /output:/private/tmp/Xamarin.MMP.Tests.MMPTests.RunMMPTest68/bin/Debug/ 
          /name:UnifiedExample 
          '/profile:Xamarin.Mac,Version=v2.0,Profile=Mobile' 
          /arch:x86_64 
          --http-message-handler=HttpClientHandler 
          /minos=10.7 
          /nolink 
          /assembly:/tmp/Xamarin.MMP.Tests.MMPTests.RunMMPTest68/b.dll 
          /assembly:/Library/Frameworks/Xamarin.Mac.framework/Versions/Current/lib/mono/Xamarin.Mac/mscorlib.dll 
          /assembly:/Library/Frameworks/Xamarin.Mac.framework/Versions/Current/lib/mono/Xamarin.Mac/System.Core.dll 
          /assembly:/Library/Frameworks/Xamarin.Mac.framework/Versions/Current/lib/mono/Xamarin.Mac/System.dll 
          /assembly:/Library/Frameworks/Xamarin.Mac.framework/Versions/Current/lib/mono/Xamarin.Mac/Xamarin.Mac.dll 
          /assembly:/tmp/Xamarin.MMP.Tests.MMPTests.RunMMPTest68/b.dll 
          /root-assembly:/private/tmp/Xamarin.MMP.Tests.MMPTests.RunMMPTest68/bin/Debug/UnifiedExample.exe 
          /sdkroot:/Applications/Xcode.app/Contents/Developer 
          --cache:/private/tmp/Xamarin.MMP.Tests.MMPTests.RunMMPTest68/obj/Debug/mmp-cache 

Steps:

  1. Write the above set of args to a temp file, like /tmp/mmp-args.rsp
  2. Build with msbuild
  3. rm bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll* # this is the file in question
  4. run /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/bin/mmp @/tmp/mmp-args.rsp
  5. ls -l bin/Debug/UnifiedExample.app/Contents/MonoBundle/b.dll

Step 5 shows the file with readonly permissions.
Maybe @jstedfast or @chamons can correct me if I'm wrong about mmp.

@radical

This comment has been minimized.

Copy link
Member

@radical radical commented Sep 27, 2018

Oh, also since the arguments have the full path to the project, unzip the project in /tmp or adjust the paths.

@lambdageek

This comment has been minimized.

Copy link
Member Author

@lambdageek lambdageek commented Sep 27, 2018

Thanks @radical. Looks like mmp has

		static void CopyFileAndRemoveReadOnly (string src, string dest) {
			File.Copy (src, dest, true);

			FileAttributes attrs = File.GetAttributes (dest);
			if ((attrs & FileAttributes.ReadOnly) == FileAttributes.ReadOnly)
				File.SetAttributes (dest, attrs & ~FileAttributes.ReadOnly);
		}

But if I just make a standalone example that calls CopyFileAndRemoveReadOnly ("x.from", "x.to") where x.from is read-only and x.to doesn't exist, the result is an x.to with rw permission. So it is something is going on with mmp.

@radical radical removed their assignment Sep 27, 2018
@lambdageek

This comment has been minimized.

Copy link
Member Author

@lambdageek lambdageek commented Sep 27, 2018

Okay, I @marek-safar I think this bug is due to mono/linker@0f78150
That change changed the linker OutputStep CopyAssembly function to use as the source the original (read-only) assembly file, not the copied over (read-write) assembly.

The following patch (for https://github.com/mono/linker) makes the test pass:

---
 linker/Linker.Steps/OutputStep.cs | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/linker/Linker.Steps/OutputStep.cs b/linker/Linker.Steps/OutputStep.cs
index 61852b7..4969ef8 100644
--- a/linker/Linker.Steps/OutputStep.cs
+++ b/linker/Linker.Steps/OutputStep.cs
@@ -213,18 +213,27 @@ namespace Mono.Linker.Steps {
 			if (source == target)
 				return;
 
-			File.Copy (source, target, true);
+			CopyFileAndRemoveReadOnly (source, target);
 
 			if (!Context.LinkSymbols)
 				return;
 
 			var mdb = source + ".mdb";
 			if (File.Exists (mdb))
-				File.Copy (mdb, target + ".mdb", true);
+				CopyFileAndRemoveReadOnly (mdb, target + ".mdb");
 
 			var pdb = Path.ChangeExtension (source, "pdb");
 			if (File.Exists (pdb))
-				File.Copy (pdb, Path.ChangeExtension (target, "pdb"), true);
+				CopyFileAndRemoveReadOnly (pdb, Path.ChangeExtension (target, "pdb"));
+		}
+
+		static void CopyFileAndRemoveReadOnly (string src, string dest) {
+			File.Copy (src, dest, true);
+
+			FileAttributes attrs = File.GetAttributes (dest);
+
+			if ((attrs & FileAttributes.ReadOnly) == FileAttributes.ReadOnly)
+				File.SetAttributes (dest, attrs & ~FileAttributes.ReadOnly);
 		}
 
 		protected virtual string GetAssemblyFileName (AssemblyDefinition assembly, string directory)
-- 
2.19.0

But I think the original commit was wrong to use the original assembly info. MMP ends up copy every assembly twice. Once during its CopyAssemblies run and once during the linker's OutputStep.

lambdageek added a commit to lambdageek/mono-linker that referenced this issue Oct 1, 2018
File.Copy will preserve permissions and create readonly files.
We should create writeable files instead.

See mono/mono#10743
marek-safar added a commit to mono/linker that referenced this issue Oct 2, 2018
File.Copy will preserve permissions and create readonly files.
We should create writeable files instead.

See mono/mono#10743
lambdageek added a commit to lambdageek/mono that referenced this issue Oct 2, 2018
Includes mono/linker@4dde7af
to fix permissions of files created by OutputStep.

Fixes mono#10743
lambdageek added a commit to lambdageek/mono that referenced this issue Oct 2, 2018
Includes mono/linker@4dde7af
to fix permissions of files created by OutputStep.

Fixes mono#10743
marek-safar added a commit to mono/linker that referenced this issue Oct 3, 2018
File.Copy will preserve permissions and create readonly files.
We should create writeable files instead.

See mono/mono#10743
marek-safar added a commit that referenced this issue Oct 3, 2018
Includes mono/linker@4dde7af
to fix permissions of files created by OutputStep.

Fixes #10743
lambdageek added a commit to xamarin/xamarin-macios that referenced this issue Oct 3, 2018
Bump mono
spouliot added a commit to xamarin/xamarin-macios that referenced this issue Dec 6, 2018
* Bump to mono:2018-06

* Bump mono

* Updates compression to work with the public span

* Bump mono

* Fixes pointer check logic in Deflater

* Bump mono

* Fixes pointer check logic in Deflater

* Bump mono

* Bump Mono

* [runtime] always use `mono_jit_set_aot_mode` (#4491)

`mono_jit_set_aot_only` is deprecated and accidentally broke with
mono/mono#7887

This should fix device tests with `mono-2018-06`

* Testing with Zoltan's patch

* Include libmono-system-native on Xamarin.Mac

* Bump Mono

Commit list for mono/mono:

* mono/mono@7bcda19 Bump llvm to release_60/fc854b8ec5873d294b80afa3e6cf6a88c5c48886. (#9786). (#9804)
* mono/mono@23e95ec Apply F# portable pdb debug fix for pinvokes & bump (#9797)
* mono/mono@295f6d3 [2018-06] [MacOS] On Mac, use the copyfile API to copy files (#9696)

Diff: mono/mono@7d5f4b6...7bcda19

* Revert 4bacab3, it doesn't fix the ios aot problems.

* Bump mono

* [tests] Adjust the MT0137 test for mcs change in behavior.

Starting with mono 5.16 mcs will now add assembly references when the assembly
is only used in attributes (this was already the case for csc in both 5.14 and
5.16, so it seems to be a compatibility change).

Adjust the MT0137 test accordingly.

* [msbuild] Fix parsing of json parser errors to handle trailing periods in the error message.

Fixes this test:

    1) Test Failure : Xamarin.iOS.Tasks.Bug60536.TestACToolTaskCatchesJsonException
         ColumnNumber
      Expected: 2
      But was:  0

* Bump mono

* [builds] Install the old llvm binaries into the LLVM36 directory and make the 32 bit builds use that.

* Bump mono

* Bump to mono:2018-08

* Initialize Dependency Injector.

* Fix typo

* Fix llvm build

* Reflect latest X509CertificateImpl changes

* Use same compile flags also for link

Linking can fail if the minimum versions are different

* Bump mono

* Bump mono

* Assembly.LoadFile accepts only absolute path

* Bump mono

* [jenkins] Don't give VSTS a fake branch. (#4667)

Something in VSTS changed, and now fake branch names don't work anymore.

So instead use real branch names (and for pull requests I've created a
'pull-request' branch we can use).

* Assembly.LoadFile accepts only absolute path

* [linker] Add new Facade (System.Threading.Tasks.Extensions).

Fixes these MTouch test failures:

    1. Xamarin.Linker.SdkTest.iOS_Unified :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

    2. Xamarin.Linker.SdkTest.tvOS :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

    3. Xamarin.Linker.SdkTest.watchOS :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

* [linker] Add new Facade (System.Threading.Tasks.Extensions).

Fixes these MTouch test failures:

    1. Xamarin.Linker.SdkTest.iOS_Unified :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

    2. Xamarin.Linker.SdkTest.tvOS :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

    3. Xamarin.Linker.SdkTest.watchOS :   Facades
      Expected:
      But was:  < "System.Threading.Tasks.Extensions" >

* [tests] Reference GuiUnit_Net_4_5 using a project reference.

This makes sure GuiUnit is built when the main project is built.

* [mono-sdks] Necessary changes to unify the LLVM provisioning for both iOS and Android. (#4732)

* Bump Mono

* [mtouch] add mixed-mode support (#4751)

* [mtouch] add --interp-mixed option

When enabling this option, mtouch will AOT compile `mscorlib.dll`.  At
runtime that means every method that wasn't AOT'd will be executed by
the runtime interpreter.

* [mtouch] Add support to --interpreter to list the assemblies to (not) interpret.

* [msbuild] Simplify interpreter code to use a single variable.

* Fix whitespace.

* [mtouch] Move mtouch-specific code to mtouch-specific file.

* [msbuild] An empty string is a valid value for 'Interpreter', so make it a non-required property.

* [mtouch] Add sanity check for aot-compiling interpreted assemblies.

* Bump Mono

* [linker] Updates SDKs facades list

* Bump mono

* [msbuild] Adds facades which might override default nuget version to framework list

The collision resolver task reads them from here https://github.com/dotnet/sdk/blob/master/src/Tasks/Common/ConflictResolution/FrameworkListReader.cs

* Bump mono to pick up hybrid suspend fixes

Pick up the 2018-08 backport (mono/mono#10551)
of mono/mono#10545

This should fix GC hangs when managed code runs on a GCD threadpool worker
thread.

* [builds] Fix target name in llvm36 provisioning

package-llvm-llvm36-32 isn't defined in external/mono/sdks/builds/llvm.mk,
but package-llvm36-llvm32 is.

* Revert "[builds] Fix target name in llvm36 provisioning"

This reverts commit b233837.

* Revert "Fix llvm build"

This reverts commit f668561.

* [mono-sdks] Necessary changes to unify the LLVM provisioning for both iOS and Android. (#4732)

* Bump mono

* Bump mono

* Revert "Use same compile flags also for link"

This reverts commit cf20539.

* Bump mono to pick up mono/mono@1a309a7

* [mmptest] System.Core doesn't depend on Mono.Posix in 2018-08

System.Core doesn't depend on Mono.Posix anymore since it's using the corefx
implementation of pipes now mono/mono@0f0e318

* Bump mono and minimum system mono

* [security]: Make `SecCertificate` work with the latest runtime code.

* Fix the `NATIVE_APPLE_CERTIFICATE` logic; it should only be defined when
  using `XAMARIN_APPLETLS` and not on watch.

* It is no longer allowed to construct `X509Certificate` from a native pointer,
  the `X509Certificate(IntPtr)` and `X509Certificate2(IntPtr)` constructors now
  throw an exception.  Use `X509CertificateImplAppl` directly instead.

* Bump mono

* Bump VSmac min version to 7.7.0.1373

To pick up the fix for https://devdiv.visualstudio.com/DevDiv/_workitems/edit/658916/
Should fix the XM classic build failures

* Revert "Bump VSmac min version to 7.7.0.1373"

This reverts commit b2686bb.

* Bump to a VSfM version that can build XM Classic projects.

* Bump mono system dependency

* Bump mono

Pick up mono/mono@1644a1a - fix for mono/mono#10743

* Bump mono

* Bump mono

* [monotouch-test] Disable X509Certificate(byte[]) tests on watchOS (#4942)

* [monotouch-test] Disable X509Certificate(byte[]) tests on watchOS

* [tests] Add TestRuntime.AssertNotWatchOS()

* fixup WatchOS build

* Bump mono

* Bump mono

* [tests] Disable link-preserve-calendar-1 until we can upgrade it to be a Unified test.

See #4596 (comment)
for reference: mono's desktop API changed, the linker behavior the test is
verifying is only expected when using XM's Mobile profile.

* Bump mono

* Revert "[monotouch-test] Disable X509Certificate(byte[]) tests on watchOS (#4942)"

This reverts commit d003a9b.

* Bump Mono.

* [security]: `NATIVE_APPLE_CERTIFICATE` should now be defined on watchOS as well.

* Mono 2018-08 requires macOS 10.9+, so Xamarin.Mac must as well.

* Bump min mono version for XM system apps.

Using a system mono < 5.18 results in a TypeLoadException:

    Could not resolve type with token 01000032 from typeref (expected class 'Mono.ISystemDependencyProvider' in assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089')

* Bump guiunit to get updated min macOS version.

Commit list for mono/guiunit:

* mono/guiunit@9f67042 Bump min macOS version to 10.9.
* mono/guiunit@0c3159a [Harness] Fix exit code of 0 being reported in case of exceptions in the harness
* mono/guiunit@9b7497c Merge pull request #15 from mono/fix-more-warnings
* mono/guiunit@a264470 Fix more warnings
* mono/guiunit@dd094e7 Merge pull request #14 from mono/fix-warnings
* mono/guiunit@b3afede Fix build warnings

Diff: mono/guiunit@1306b0d...9f67042

* [tests] More min macOS version setting to 10.9.

* Remove 10.7 & 10.8 availability attributes, since they're redundant now.

* Bump mono

* [2018-08][watchos] Use mono_dangerous_add_raw_internal_call for watchOS icalls (#5030)

* Add optional mono_dangerous_add_raw_internal_call to exports.t4

* Use mono_dangerous_add_raw_internal_call on watchOS for icall registration

Internal calls added with mono_dangerous_add_raw_internal_call run in GC Unsafe
mode under cooperative and hybrid suspend, whereas internal calls added with
mono_add_internal_call run in GC Safe mode since
mono/mono@5756ba4 in order for hybrid suspend
to be a transparent replacement for preemptive suspend (the old default).  The
icalls in GC Unsafe mode have a responsibility not to block indefinitely
without manually performing a thread state transition to GC Safe mode, and in
return they avoid a thread state transition when the icall is invoked from a
managed method.

* [mmptest] Less hardcoding.

* Bump minimum mono one that has 'mono_dangerous_add_raw_internal_call'.

* Bump mono

* Bump system mono dependency

* Fixes building mono tests

* [ImageCaptureCore] Remove redundant availability attribute.

* [mtouch] Clear the MONO_THREADS_SUSPEND environment variable before calling the AOT compiler. Works around mono/mono#11765.

Visual Studio for Mac may set MONO_THREADS_SUSPEND, and this ends up confusing
the AOT compiler when compiling for watchOS.

So unset the environment variable before calling the AOT compiler.

Works around mono/mono#11765.
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Apr 24, 2019
Bumps to mono/api-snapshot@ae01378
Bumps to mono/reference-assemblies@e5173a5
Bumps to mono/bockbuild@d30329d
Bumps to mono/boringssl@3d87996
Bumps to mono/corefx@72f7d76
Bumps to mono/corert@1b7d4a1
Bumps to mono/helix-binaries@7e893ea
Bumps to mono/illinker-test-assets@f21ff68
Bumps to mono/linker@13d864e
Bumps to mono/llvm@1aaaaa5 [mono]
Bumps to mono/llvm@2c2cffe [xamarin-android]
Bumps to mono/NUnitLite@0029561
Bumps to mono/roslyn-binaries@0bbc9b4
Bumps to mono/xunit-binaries@8f6e62e

	$ git diff --shortstat 886c4901..e66c7667      # mono
        3597 files changed, 350850 insertions(+), 91128 deletions(-)
	$ git diff --shortstat 349752c464c5fc93b32e7d45825f2890c85c8b7d..2c2cffedf01e0fe266b9aaad2c2563e05b750ff4
	 240 files changed, 18562 insertions(+), 6581 deletions(-)

Context: dotnet/coreclr#22046

Fixes: CVE 2018-8292 on macOS
Fixes: http://work.devdiv.io/737323
Fixes: dotnet/corefx#33965
Fixes: dotnet/standard#642
Fixes: mono/mono#6997
Fixes: mono/mono#7326
Fixes: mono/mono#7517
Fixes: mono/mono#7750
Fixes: mono/mono#7859
Fixes: mono/mono#8360
Fixes: mono/mono#8460
Fixes: mono/mono#8766
Fixes: mono/mono#8922
Fixes: mono/mono#9418
Fixes: mono/mono#9507
Fixes: mono/mono#9951
Fixes: mono/mono#10024
Fixes: mono/mono#10030
Fixes: mono/mono#10038
Fixes: mono/mono#10448
Fixes: mono/mono#10735
Fixes: mono/mono#10735
Fixes: mono/mono#10737
Fixes: mono/mono#10743
Fixes: mono/mono#10834
Fixes: mono/mono#10837
Fixes: mono/mono#10838
Fixes: mono/mono#10863
Fixes: mono/mono#10945
Fixes: mono/mono#11020
Fixes: mono/mono#11021
Fixes: mono/mono#11021
Fixes: mono/mono#11049
Fixes: mono/mono#11091
Fixes: mono/mono#11095
Fixes: mono/mono#11123
Fixes: mono/mono#11138
Fixes: mono/mono#11146
Fixes: mono/mono#11202
Fixes: mono/mono#11214
Fixes: mono/mono#11317
Fixes: mono/mono#11326
Fixes: mono/mono#11378
Fixes: mono/mono#11385
Fixes: mono/mono#11478
Fixes: mono/mono#11479
Fixes: mono/mono#11488
Fixes: mono/mono#11489
Fixes: mono/mono#11527
Fixes: mono/mono#11529
Fixes: mono/mono#11596
Fixes: mono/mono#11603
Fixes: mono/mono#11613
Fixes: mono/mono#11623
Fixes: mono/mono#11663
Fixes: mono/mono#11681
Fixes: mono/mono#11684
Fixes: mono/mono#11693
Fixes: mono/mono#11697
Fixes: mono/mono#11779
Fixes: mono/mono#11809
Fixes: mono/mono#11858
Fixes: mono/mono#11895
Fixes: mono/mono#11898
Fixes: mono/mono#11898
Fixes: mono/mono#11965
Fixes: mono/mono#12182
Fixes: mono/mono#12193
Fixes: mono/mono#12218
Fixes: mono/mono#12235
Fixes: mono/mono#12263
Fixes: mono/mono#12307
Fixes: mono/mono#12331
Fixes: mono/mono#12362
Fixes: mono/mono#12374
Fixes: mono/mono#12402
Fixes: mono/mono#12421
Fixes: mono/mono#12461
Fixes: mono/mono#12479
Fixes: mono/mono#12479
Fixes: mono/mono#12552
Fixes: mono/mono#12603
Fixes: mono/mono#12747
Fixes: mono/mono#12831
Fixes: mono/mono#12843
Fixes: mono/mono#12881
Fixes: mono/mono#13030
Fixes: mono/mono#13284
Fixes: mono/mono#13297
Fixes: mono/mono#13455
Fixes: mono/mono#13460
Fixes: mono/mono#13478
Fixes: mono/mono#13479
Fixes: mono/mono#13522
Fixes: mono/mono#13607
Fixes: mono/mono#13610
Fixes: mono/mono#13610
Fixes: mono/mono#13639
Fixes: mono/mono#13672
Fixes: mono/mono#13834
Fixes: mono/mono#13878
Fixes: mono/mono#6352
Fixes: mono/monodevelop#6898
Fixes: xamarin/maccore#1069
Fixes: xamarin/maccore#1407
Fixes: xamarin/maccore#604
Fixes: xamarin/xamarin-macios#4984
Fixes: xamarin/xamarin-macios#5289
Fixes: xamarin/xamarin-macios#5363
Fixes: xamarin/xamarin-macios#5381
Fixes: https://issuetracker.unity3d.com/issues/editor-crashes-with-g-logv-when-entering-play-mode-with-active-flowcanvas-script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.