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

[Meta] Xcode 13.0 Support #12778

Closed
dalexsoto opened this issue Sep 20, 2021 · 156 comments
Closed

[Meta] Xcode 13.0 Support #12778

dalexsoto opened this issue Sep 20, 2021 · 156 comments
Labels
iOS Issues affecting Xamarin.iOS macOS Issues affecting Xamarin.Mac
Milestone

Comments

@dalexsoto
Copy link
Member

dalexsoto commented Sep 20, 2021

🚨 Update ⚠️

Hello All!

We have what we believe is the final build for Xcode 13 Support

Thank you for your patience!

The macios team!


Apple released Xcode 13.0 on September 20, 2021 we are working to get our Xcode 13 support release out in the meantime if you use Xamarin we recommend you to not upgrade to Xcode 13 just yet and keep using Xcode 12.5.

If you updated to Xcode 13, you have 3 options:

  1. You can download Xcode 12.5 from the downloads page in the Apple Developer Portal and continue to use it.
  2. If you need to keep Xcode 13 but want to use our current stable d16-10 bits you will need to install the following in you macOS machine
  3. Use a build from our xcode13-ios branch, this is where our next stable release is coming out and it includes all the iOS 15 SDKs APIs, that said we are still ironing it out.

We will keep this issue updated as we go to have the final builds declared.

Thank you for your patience!

The macios team!

@dalexsoto dalexsoto added macOS Issues affecting Xamarin.Mac iOS Issues affecting Xamarin.iOS labels Sep 20, 2021
@dalexsoto dalexsoto added this to the Future milestone Sep 20, 2021
@dalexsoto dalexsoto pinned this issue Sep 20, 2021
@Hackmodford
Copy link

Hackmodford commented Sep 21, 2021

Is there a rough ETA for this? Is it a matter of day(s), week(s)?

@dalexsoto
Copy link
Member Author

dalexsoto commented Sep 21, 2021

Days :) we are working around the clock for this. You can in te meantime follow the work on our xcode13-ios branch and install the latest build that is close to be our release candidate xamarin.ios-15.0.0.0.pkg

@npagare
Copy link

npagare commented Sep 21, 2021

Hi @dalexsoto, thank you for the update and the guidance.

Will the xamarin.ios-15.0.0.0.pkg work with both VS 2019.11.x and VS 2022 preview 4+ ?

@dalexsoto
Copy link
Member Author

@IoTFier In theory yes, this is Xamarin.iOS pre .NET 6 so it should be continued to be supported until the .NET 6 SDKs are GA.

@nabilakhlaque
Copy link

Days :) we are working around the clock for this. You can in te meantime follow the work on our xcode13-ios branch and install the latest build that is close to be our release candidate xamarin.ios-15.0.0.0.pkg

Doesnt work for me with Visual Studio Enterprise 19.11.3, I keep getting this message:

The Xamarin.iOS SDK version '15.0.0.0' that is installed on the Mac is not compatible with this version of Visual Studio. Would you like us to install Xamarin.iOS '14.20.0.25' for you? This will overwrite any other existing Xamarin.iOS installation on your Mac.

@praeclarum
Copy link
Contributor

praeclarum commented Sep 21, 2021

I have tried xamarin.ios-15.0.0.0.pkg but cannot deploy to devices. It says "Deploying" but nothing appears in the pad.

=== Visual Studio Community 2019 for Mac ===

Version 8.10.9 (build 3)
Installation UUID: 99635f05-cd0f-4705-b99b-2d921ff95a68
	GTK+ 2.24.23 (Raleigh theme)
	Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638)

	Package version: 612000140

=== Mono Framework MDK ===

Runtime:
	Mono 6.12.0.140 (2020-02/51d876a041e) (64-bit)
	Package version: 612000140

=== Roslyn (Language Service) ===

3.10.0-4.21269.26+029847714208ebe49668667c60ea5b0a294e0fcb

=== NuGet ===

Version: 5.9.0.7134

=== Apple Developer Tools ===

Xcode 13.0 (19234)
Build 13A233

=== Xamarin.Mac ===

Version: 7.14.0.24 (Visual Studio Community)
Hash: c4b89cddb
Branch: d16-10
Build date: 2021-06-15 22:03:00-0400

=== Xamarin.iOS ===

Version: 15.0.0.0 (Visual Studio Community)
Hash: ea8c82574
Branch: xcode13-ios
Build date: 2021-09-21 00:43:25-0400

=== Build Information ===

Release ID: 810090003
Git revision: 156eb53c9c668cb7ff4311ae3d1dab894549848b
Build date: 2021-09-08 07:26:54-04
Build branch: release-8.10

=== Operating System ===

Mac OS X 10.16.0
Darwin 21.0.0 Darwin Kernel Version 21.0.0
    Mon Aug  2 00:18:13 PDT 2021
    root:xnu-8019.30.9~9/RELEASE_ARM64_T8101 x86_64

@KraigM
Copy link

KraigM commented Sep 21, 2021

I have tried xamarin.ios-15.0.0.0.pkg but cannot deploy to devices. It says "Deploying" but nothing appears in the pad.

I also tried this build of Xamarin.iOS. I can't even get it to find/deploy to simulators. It builds for "Generic Simulator" fine but says I don't have any simulators installed.

Visual Studio Professional 2019 for Mac
Version 8.10.9 (build 3)
Installation UUID: 47f6d95a-0f4e-491e-9290-8de3d010e6f7
	GTK+ 2.24.23 (Raleigh theme)
	Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638)

	Package version: 612000140

Mono Framework MDK
Runtime:
	Mono 6.12.0.140 (2020-02/51d876a041e) (64-bit)
	Package version: 612000140

Roslyn (Language Service)
3.10.0-4.21269.26+029847714208ebe49668667c60ea5b0a294e0fcb

NuGet
Version: 5.9.0.7134

.NET Core SDK
SDK: /usr/local/share/dotnet/sdk/5.0.401/Sdks
SDK Versions:
	5.0.401
	5.0.400
	5.0.302
	5.0.301
	5.0.203
	5.0.202
	5.0.201
	5.0.103
	5.0.102
	5.0.101
	5.0.100
	5.0.100-rc.2.20479.15
	3.1.413
	3.1.412
	3.1.411
	3.1.410
	3.1.409
	3.1.408
	3.1.407
	3.1.406
	3.1.405
	3.1.404
	3.1.403
	3.1.402
	3.1.401
	3.1.302
	3.1.301
	3.1.300
	3.1.201
	3.1.200
	3.1.101
	3.0.100
	2.2.402
	2.1.811
	2.1.810
	2.1.809
	2.1.701
MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/Current/bin/Sdks

.NET Core Runtime
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
	5.0.10
	5.0.9
	5.0.8
	5.0.7
	5.0.6
	5.0.5
	5.0.4
	5.0.3
	5.0.2
	5.0.1
	5.0.0
	5.0.0-rc.2.20475.5
	3.1.19
	3.1.18
	3.1.17
	3.1.16
	3.1.15
	3.1.14
	3.1.13
	3.1.12
	3.1.11
	3.1.10
	3.1.9
	3.1.8
	3.1.7
	3.1.6
	3.1.5
	3.1.4
	3.1.3
	3.1.2
	3.1.1
	3.0.0
	2.2.7
	2.1.23
	2.1.22
	2.1.21
	2.1.20
	2.1.19
	2.1.18
	2.1.17
	2.1.15
	2.1.13
	2.1.12

.NET Core 3.1 SDK
SDK: 3.1.413

Xamarin.Profiler
Version: 1.6.12.29
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

Updater
Version: 11

Xamarin.Android
Version: 11.3.0.4 (Visual Studio Professional)
Commit: xamarin-android/d16-10/ae14caf
Android SDK: /Users/kraigm/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.4 (API level 19)
		6.0 (API level 23)
		7.1 (API level 25)
		8.1 (API level 27)

SDK Tools Version: 26.1.1
SDK Platform Tools Version: 31.0.3
SDK Build Tools Version: 30.0.2

Build Information: 
Mono: b4a3858
Java.Interop: xamarin/java.interop/d16-10@f39db25
ProGuard: Guardsquare/proguard/v7.0.1@912d149
SQLite: xamarin/sqlite/3.35.4@85460d3
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-10@c5732a0

Microsoft OpenJDK for Mobile
Java SDK: /Users/kraigm/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Android SDK Manager
Version: 16.10.0.13
Hash: 1b81df5
Branch: remotes/origin/d16-10
Build date: 2021-08-12 20:43:52 UTC

Android Device Manager
Version: 16.10.0.15
Hash: 89dcc0b
Branch: remotes/origin/d16-10
Build date: 2021-08-12 20:44:10 UTC

Apple Developer Tools
Xcode 13.0 (19234)
Build 13A233

Xamarin.Mac
Version: 7.14.0.24 (Visual Studio Professional)
Hash: c4b89cddb
Branch: d16-10
Build date: 2021-06-15 22:03:00-0400

Xamarin.iOS
Version: 15.0.0.0 (Visual Studio Professional)
Hash: ea8c82574
Branch: xcode13-ios
Build date: 2021-09-21 00:43:25-0400

Xamarin Designer
Version: 16.10.0.119
Hash: 36a2d986f
Branch: remotes/origin/d16-10
Build date: 2021-06-02 19:41:34 UTC

Build Information
Release ID: 810090003
Git revision: 156eb53c9c668cb7ff4311ae3d1dab894549848b
Build date: 2021-09-08 07:26:54-04
Build branch: release-8.10

Operating System
Mac OS X 10.16.0
Darwin 20.6.0 Darwin Kernel Version 20.6.0
    Wed Jun 23 00:26:31 PDT 2021
    root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64

Enabled user installed extensions
NuGet Package Management Extensions 0.27
NuGet Package Explorer 0.6

@IchKannDenken
Copy link

I also have tried xamarin.ios-15.0.0.0.pkg. But I cannot deploy to my iphone with the error message: "An error occurred while executing MTouch"

Microsoft Visual Studio Enterprise 2019
Version 16.11.3
VisualStudio.16.Release/16.11.3+31702.278
Microsoft .NET Framework
Version 4.8.04161

@rolfbjarne
Copy link
Member

Thanks for the testing! We've identified an issue and a fix is in progress (#12801).

We'll update this issue when an updated package is available.

@CleverSoftwarePoland
Copy link

I also have tried xamarin.ios-15.0.0.0.pkg. But I cannot deploy to my iphone with the error message: "An error occurred while executing MTouch"

Microsoft Visual Studio Enterprise 2019
Version 16.11.3
VisualStudio.16.Release/16.11.3+31702.278
Microsoft .NET Framework
Version 4.8.04161

Same problem, "An error occurred while executing MTouch"

@TrevorBond2020
Copy link

Option 2 worked for me. Visual Studio 2019 Mac Community 8.10.9 (build 3)
xamarin.mac-7.14.0.27.pkg
xamarin.ios-14.20.0.27.pkg

All simulators back and at iOS 15. Running on device on iOS 15.0

Many thanks for all your hard work

@fschneider1509
Copy link

fschneider1509 commented Sep 22, 2021

Option 2 worked for me. Visual Studio 2019 Mac Community 8.10.9 (build 3)
xamarin.mac-7.14.0.27.pkg
xamarin.ios-14.20.0.27.pkg

All simulators back and at iOS 15. Running on device on iOS 15.0

Many thanks for all your hard work

@TrevorBond2020
Where did you get the xamarin.ios-14.20.0.27.pkg? I can only see the version 14.20.0.24.

@TrevorBond2020
Copy link

Option 2 worked for me. Visual Studio 2019 Mac Community 8.10.9 (build 3)
xamarin.mac-7.14.0.27.pkg
xamarin.ios-14.20.0.27.pkg
All simulators back and at iOS 15. Running on device on iOS 15.0
Many thanks for all your hard work

@TrevorBond2020
Where did you get the xamarin.ios-14.20.0.27.pkg? I can only see the version 14.20.0.24.

At top of this page ...

Apple released Xcode 13.0 on September 20, 2021 we are working to get our Xcode 13 support release out in the meantime if you use Xamarin we recommend you to not upgrade to Xcode 13 just yet and keep using Xcode 12.5.

If you updated to Xcode 13, you have 3 options:

You can download Xcode 12.5 from the downloads page in the Apple Developer Portal and continue to use it.
If you need to keep Xcode 13 but want to use our current stable d16-10 bits you will need to install the following in you macOS machine
xamarin.ios-14.20.0.27.pkg
xamarin.mac-7.14.0.27.pkg
Use a build from our xcode13-ios branch, this is where our next stable release is coming out and it includes all the iOS 15 SDKs APIs, that said we are still ironing it out.
xamarin.ios-15.0.0.0.pkg

@lukiller
Copy link

The second solution worked for me on VS 8.10.9, Xcode 13 and iOS 15. I only installed xamarin.ios-14.20.0.27.pkg package.
Thank you guys! I was in the middle of a code fix when Xcode decided to upgrade by itself without asking.

@MarcelWolterbeek
Copy link

The second solution worked for me on VS 16.11.3 (Windows), Xcode 13 and iOS 15. I only installed xamarin.ios-14.20.0.27.pkg (iOS dev only).

When connection I get the message "The Xamarin.iOS SDK version '14.20.0.27' that is installed on the Mac is not compatible with this version of Visual Studio. Would you like us to install Xamarin.iOS '14.20.0.25' for you? This will overwrite any other existing Xamarin.iOS installation on your Mac."

When I click Cancel, connecting continues and the simulators are back in the list.

@nschoenberg
Copy link

Can confirm downgrade to xcode 12.5.1 worked for me on two machines.

@johnybaryah
Copy link

Can confirm downgrade to xcode 12.5.1 worked for me on two machines.

Are you able to deploy the build from xcode 12.5 to an iOS 15 device?

@dalexsoto
Copy link
Member Author

Hello all, we have a new release candidate build for Xcode 13 Support

Please give this a try and let us know how it goes!

With ❤️ to you all,

  • The macios team!

@osniel
Copy link

osniel commented Sep 22, 2021

I tried xamarin.ios-15.0.0.3.pkg and it worked well with the simulator and an iPhone 😄
Using VS 8.10.9 (build 3), Xcode 13 and iOS 15.

@kozw
Copy link

kozw commented Sep 22, 2021

iOS 15 simulators seem to work well, device not so much. Got the following error while launching my app:

error: Unregistered icall 'System.RuntimeTypeHandle:GetAssembly (System.RuntimeType)'

=================================================================
	Native stacktrace:
=================================================================
	0x1099085ac - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_dump_native_crash_info
	0x1098fe724 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_handle_native_crash
	0x109907af4 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : sigabrt_signal_handler
	0x1dc9bfd50 - /usr/lib/system/libsystem_platform.dylib : <redacted>
	0x1dc9d68d8 - /usr/lib/system/libsystem_pthread.dylib : pthread_kill
	0x18d48d0c0 - /usr/lib/system/libsystem_c.dylib : abort
	0x1087a2fe0 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : xamarin_find_protocol_wrapper_type
	0x1098d55ec - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : monoeg_g_logv_nofree
	0x1098d563c - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : monoeg_g_log
	0x10990a3e0 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_resolve_patch_target
	0x1098e3ce0 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_aot_plt_resolve
	0x109912c68 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_aot_plt_trampoline
	0x103a8968c - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x1032fc490 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x1032c3804 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x1032c37e4 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x105df8824 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x103a18e90 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x10990fe74 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_jit_runtime_invoke
	0x1099cbe70 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_runtime_try_invoke
	0x1099cab70 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_runtime_class_init_full
	0x10990a920 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_resolve_patch_target
	0x1098e2418 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : init_method
	0x1098e3464 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : load_method
	0x1098e2c98 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_aot_get_method
	0x10990b164 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_jit_compile_method_with_opt
	0x10990fb90 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_jit_runtime_invoke
	0x1099cbe70 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_runtime_try_invoke
	0x1099cdd98 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Frameworks/Mono.framework/Mono : mono_runtime_invoke
	0x1087ae438 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : xamarin_localized_string_format_9
	0x1087a30f8 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : xamarin_find_protocol_wrapper_type
	0x1087b377c - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : xamarin_localized_string_format_9
	0x102fdc814 - /private/var/containers/Bundle/Application/00000000-0000-0000-0000-000000000000/Test.app/Test : sqlite3_sleep
	0x109480190 - Unknown


=================================================================
	Managed Stacktrace:
=================================================================
	  at <unknown> <0xffffffff>
	  at System.RuntimeTypeHandle:GetAssembly <0x0005f>
	  at System.RuntimeType:GetRuntimeAssembly <0x00013>
	  at System.RuntimeType:get_Assembly <0x00013>
	  at Foundation.NSObject:.cctor <0x00023>
	  at System.Object:runtime_invoke_dynamic <0x0010f>
=================================================================

@dalexsoto
Copy link
Member Author

@kozw thanks for the report, can I ask you to make a new bug report and if possible attach a test case for this? Thank you!

@tamifist
Copy link

That works! Thanks @dalexsoto!

@kozw
Copy link

kozw commented Sep 22, 2021

Issue created. Looks like there is an issue with application extensions

@WongWeiLoon
Copy link

Xamarin ios 15.0.0.6, iOS 15, listviews are a bit under their normal location. I found this issue on only iOS 15 devices/simulators. Take a look:
image

Hey @ShadowOfPhantom, have you managed to fix this ?

@ShadowOfPhantom
Copy link

ShadowOfPhantom commented Oct 1, 2021

Xamarin ios 15.0.0.6, iOS 15, listviews are a bit under their normal location. I found this issue on only iOS 15 devices/simulators. Take a look:
image

Hey @ShadowOfPhantom, have you managed to fix this ?

Hi! Yes, here is the solution
But I recommend to wait for update that will be available ~ on October 13 with bug fixes, because current version has a lot of bugs, it’s a really bad idea to use it in production

@t9mike
Copy link

t9mike commented Oct 1, 2021

The table section issue is not a bug. Just Apple change present since first iOS15 Betas. https://twitter.com/chockenberry/status/1405679018909655044?lang=en.

@kurtblondin
Copy link

kurtblondin commented Oct 1, 2021

Does anyone has issue with their app published to TestFlight ? I updated my Visual Studio for mac. My app runs fine with the debug and release version but, when I open my app on TestFlight, it crashes when opening. The build I made with the previous version of VS is working perfectly fine. Tested on iPhone XR iOS 14.8 and iPhone 12 Pro iOS 15.

@mikeks
Copy link

mikeks commented Oct 1, 2021

Any updates for VS for Windows? I have VS 2019 16.11.3 and it says "The Xamarin.iOS SDK version '15.0.0.6' that is installed on the Mac is not compatible with this version of Visual Studio.". Thanks.

@npagare
Copy link

npagare commented Oct 1, 2021

Any updates for VS for Windows? I have VS 2019 16.11.3 and it says "The Xamarin.iOS SDK version '15.0.0.6' that is installed on the Mac is not compatible with this version of Visual Studio.". Thanks.

Hi @mikeks,

Refer to this workaround I posted at this #12778 (comment)
Hope it works for you.

@mackayn
Copy link

mackayn commented Oct 3, 2021

@dalexsoto @IoTFier

Thanks for the workarounds, can confirm updating VS4Mac to latest stable and adding to the flag for VS2019 for Windows gets remote iOS builds to iPhone running on iOS 14.8 deploying after a few reboots and a little swearing :)

Some odd stuff in TabbedPage views though in iOS but that's an XForms issue.

@kwaclaw
Copy link

kwaclaw commented Oct 5, 2021

None of the solutions work for me:
VS 2019 16.11.3 (Windows), Mac Mini with XCode 13, iPad Mini with iOS 14.8.

This is quite inconvenient, as I am working on a high priority bug.

Attempted:

  • XCode 13, Xamarin.iOS 14.20.0.27 installed on MacMini, ignoring Xamarin.iOS warning (registry setting):
    On running in debugger: Invalid Service Error (error: 0xe8000022)
  • reverted to XCode 12.5.1:
    would not build, some AppBundle empty error
  • Tried installing Xamarin.iOS 15.0.0.6 on MacMini, is that support to work with VS2019 on Windows, because for me it doesn't
    error CS0006: Metadata file '...\Debug\NativeLibrary.dll' could not be found

@ahoke-cr
Copy link

ahoke-cr commented Oct 5, 2021

@kwaclaw I am able to build just fine using VS 2019 16.11.3 (Windows), Mac mini with XCode 13, and iPhone XS (or any simulator) while my Mac mini has Xamarin SDK 15.0.0.6 installed. You could try cleaning the Mac build cache which usually fixes the odd issue.

@grriffin
Copy link

grriffin commented Oct 5, 2021

I am able to build VS for Windows fine now, using Xamarin SDK 15.0.0.6 on my Mac. However, if I use new features included in the latest Xamarin.iOS SDK like SectionHeaderTopPadding on a UITableView then Visual Studio reports that this property doesn't exist. I guess the Xamarin.iOS package that Visual studio uses also needs to be updated.

Is there any way around this?
Or do I have to wait for the next Visual Studio update to include new Xamarin.iOS packages?
image

@kwaclaw
Copy link

kwaclaw commented Oct 5, 2021

@ahoke-cr Thanks for the advice but cleaning the build cache did not help either. The error references a native bindings library which is the part that does not build.

@ahoke-cr
Copy link

ahoke-cr commented Oct 5, 2021

@kwaclaw that error sounds like an issue with your project, not Xamarin. If the file needs to be copied as part of the build process, ensure that it is in fact being copied to the build folder. Try to reproduce the issue with a fresh new project and perhaps that will help you narrow down the cause.

@kwaclaw
Copy link

kwaclaw commented Oct 5, 2021

@ahoke-cr Just got the new VS update for Windows (16.11.4) and the build issue is resolved.

@vitalyster
Copy link

Just got a new VS update with Xamarin.iOS 15.0.0.8 and simulators are not listed again (previously it works in 15.0.0.6)

@PredatH0r
Copy link

PredatH0r commented Oct 6, 2021

I made the mistake to update VS2019 Community Edition to Version 16.11.4, which now REQUIRES Xcode 13.
Also installed Xamarin 15.0.0.8 on both Windows and the Mac.

  • Hot-Reload is broken now with both the iOS 13.7 and 15 simulator on M1-CPU (It worked till yesterday with VS2019 16.11.3, Xcode 12.5.1, Xamarin 14.20.0.25, iOS 13.7 simulator)
  • The Xamarin Forms UI is broken in the iOS 15 simulator (the title bar on the top and Tab bar on the bottom are white-on-white with clickable links in them). The UI shows fine in a iOS 13.7 simulator.

image

@mackayn
Copy link

mackayn commented Oct 6, 2021

Seen the tab issue, that will need a Forms patch I'm guessing, don't know if an issue has been raised.

Can confirm HotReload is borked on iOS 15 sim (sigh) with latest service pack of Forms.

@haavamoa
Copy link

haavamoa commented Oct 6, 2021

Same happened to me as well @PredatH0r . Is there any way to roll back versions? I am totally stuck here.

@PredatH0r
Copy link

Unfortunately there is no way to rollback VS2019 Community. Microsoft only offers downgrades for the Professional and Enterprise versions: https://docs.microsoft.com/en-us/visualstudio/releases/2019/history

So I'm stuck with VS2019 16.11.4 and Xcode 13 now.

With a small code Change in AppDelegate.cs I can at least make the Title bar and Tab bar visible again.
For unknown reasons though, as soon as I set a ScrollEdgeAppearance (with out without explicit BackgroundColor), the ForegroundColor will be black, ignoring the value from XAML or any attempt to set a value in code through either ScrollEdgeAppearance or StandardAppearance. I'm giving up on this now.

    public override bool FinishedLaunching(UIApplication app, NSDictionary options)
    {
      global::Xamarin.Forms.Forms.Init();
      LoadApplication(new App());

      if (UIDevice.CurrentDevice.CheckSystemVersion(15, 0))
      {
        var textColor = UIColor.Red;

        UINavigationBar.Appearance.ScrollEdgeAppearance = new UINavigationBarAppearance() { BackgroundColor = UIColor.FromRGB(33, 150, 234) };
        UINavigationBar.Appearance.ScrollEdgeAppearance.TitleTextAttributes.ForegroundColor = textColor; // will be ignored and Title is ALLWAYS black

        UITabBar.Appearance.ScrollEdgeAppearance = new UITabBarAppearance { BackgroundColor = UIColor.FromRGB(33, 150, 234) };
      }

      return base.FinishedLaunching(app, options);
    }

@GTCLive
Copy link

GTCLive commented Oct 6, 2021

The negligence level reigning in that software provider team is now beyond comprehensible. Obviously some sort of internal sabotage going on. Are MS executives/shareholders aware of this situation and investigating into this recurrent issue?

@WongWeiLoon
Copy link

WongWeiLoon commented Oct 6, 2021

Unfortunately there is no way to rollback VS2019 Community. Microsoft only offers downgrades for the Professional and Enterprise versions: https://docs.microsoft.com/en-us/visualstudio/releases/2019/history

So I'm stuck with VS2019 16.11.4 and Xcode 13 now.

With a small code Change in AppDelegate.cs I can at least make the Title bar and Tab bar visible again. For unknown reasons though, as soon as I set a ScrollEdgeAppearance (with out without explicit BackgroundColor), the ForegroundColor will be black, ignoring the value from XAML or any attempt to set a value in code through either ScrollEdgeAppearance or StandardAppearance. I'm giving up on this now.

public override bool FinishedLaunching(UIApplication app, NSDictionary options)
{
  global::Xamarin.Forms.Forms.Init();
  LoadApplication(new App());

  if (UIDevice.CurrentDevice.CheckSystemVersion(15, 0))
  {
    var textColor = UIColor.Red;

    UINavigationBar.Appearance.ScrollEdgeAppearance = new UINavigationBarAppearance() { BackgroundColor = UIColor.FromRGB(33, 150, 234) };
    UINavigationBar.Appearance.ScrollEdgeAppearance.TitleTextAttributes.ForegroundColor = textColor; // will be ignored and Title is ALLWAYS black

    UITabBar.Appearance.ScrollEdgeAppearance = new UITabBarAppearance { BackgroundColor = UIColor.FromRGB(33, 150, 234) };
  }

  return base.FinishedLaunching(app, options);
}

@PredatH0r , I encountered similar issue for TabBar in iOS15, you can refer to this solution. I believe you can implement the similar idea for your Title Bar. Good Luck

@GreatBarrier86
Copy link

GreatBarrier86 commented Oct 6, 2021

The negligence level reigning in that software provider team is now beyond comprehensible. Obviously some sort of internal sabotage going on. Are MS executives/shareholders aware of this situation and investigating into this recurrent issue?

Lighten up, Francis.

@PredatH0r
Copy link

PredatH0r commented Oct 6, 2021

I finally have a working solution (for the Navigation/Title and Tab bars):

In AppDelegate.cs of the iOS project:

    public override bool FinishedLaunching(UIApplication app, NSDictionary options)
    {
      global::Xamarin.Forms.Forms.Init();
      LoadApplication(new App());

      if (UIDevice.CurrentDevice.CheckSystemVersion(15, 0))
      {
        var textColor = UIColor.White;
        var backColor = UIColor.FromRGB(33, 150, 234);

        var stringAttributes = new UIStringAttributes { ForegroundColor = textColor };
        UINavigationBar.Appearance.ScrollEdgeAppearance = new UINavigationBarAppearance
        {
          BackgroundColor = backColor, 
          TitleTextAttributes = stringAttributes, 
          LargeTitleTextAttributes = stringAttributes
        };
       

        UITabBar.Appearance.ScrollEdgeAppearance = new UITabBarAppearance { BackgroundColor = backColor };
      }

      return base.FinishedLaunching(app, options);
    }

Please note that the BarTintColor property seems to have no effect at all with iOS 15, regardless of Translucent=false/true.
In my app I am using GMImagePicker.Xamarin and its "NavigationBarBarTintColor" property is ignored just like my app's NavigationBar.TintColor.
But with the code snippet above in place, both my app's MainPage and the GMImagePicker now use the blue-ish BackgroundColor and the white text color I set in the code.

@GTCLive
Copy link

GTCLive commented Oct 6, 2021

Lighten up, Francis.

haha, thanks Jack. Yeah that hot rebroke huh. Was broken, got fixed, and butchered once more too often. Just about when one indeed lightens up and go shop somewhere else! Wonder what happen to equities when one finds out something is going awfully wrong within the Fortune 500's internal validation process.... step up asap @ms devs.

@drasticactions
Copy link
Member

Lighten up, Francis.

haha, thanks Jack. Yeah that hot rebroke huh. Was broken, got fixed, and butchered once more too often. Just about when one indeed lightens up and go shop somewhere else! Wonder what happen to equities when one finds out something is going awfully wrong within the Fortune 500's internal validation process.... step up asap @ms devs.

https://developercommunity.visualstudio.com/t/XAML-Hot-Reload-does-not-load-with-Xamar/1543082

A fix for this is coming soon. It broke with XCode 13 GA and worked with the previous betas and was missed just before everything shipped.

It should still work with iOS Devices, and with MAUI apps with the sim or devices.

@RTchakmakian
Copy link

Hy guys, I still can't run my app on IOS 15:

=================================================================
Native Crash Reporting

Got a segv while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

=================================================================
Native stacktrace:

0x1046990f5 - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : mono_dump_native_crash_info
0x10468d53e - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : mono_handle_native_crash
0x1046a0449 - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : mono_sigsegv_signal_handler_debug
0x7fff6bfe0d7d - /usr/lib/system/libsystem_platform.dylib : _sigtramp
0x1049d8af0 - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : ss_trampoline
0x1048aee44 - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : xamarin_invoke_objc_method_implementation
0x1048aefc8 - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : xamarin_release_trampoline
0x1048ac35d - /Users/jaxtech/Library/Developer/CoreSimulator/Devices/D4C181C6-BA5C-4704-B06C-063DF718AC0B/data/Containers/Bundle/Application/60178B5D-BA6B-43E8-9F50-00806729FA09/PlainnessiOSPhone.app/PlainnessiOSPhone : xamarin_release_managed_ref
0x108f4819c - Unknown

=================================================================
Basic Fault Address Reporting

Memory around native instruction pointer (0x7fff201803cb):0x7fff201803bb 0f 1f 44 00 00 48 85 ff 7e 63 4c 8b 17 49 89 f3 ..D..H..~cL..I..
0x7fff201803cb 45 23 5a 18 49 c1 e3 04 4d 03 5a 10 49 3b 33 75 E#Z.I...M.Z.I;3u
0x7fff201803db 0a 4d 8b 5b 08 4d 31 d3 41 ff e3 49 83 3b 01 76 .M.[.M1.A..I.;.v
0x7fff201803eb 13 49 83 c3 10 49 3b 33 75 f1 4d 8b 5b 08 4d 31 .I...I;3u.M.[.M1

=================================================================
Managed Stacktrace:

  at <unknown> <0xffffffff>
  at Foundation.NSObject:xamarin_release_managed_ref <0x000fb>
  at Foundation.NSObject:ReleaseManagedRef <0x0019a>
  at NSObject_Disposer:Drain <0x00392>
  at <Module>:runtime_invoke_void_object <0x001a8>
  at <unknown> <0xffffffff>
  at UIKit.UIApplication:UIApplicationMain <0x00254>
  at UIKit.UIApplication:Main <0x00172>
  at Plainness.iOS.Phone.Application:Main <0x00092>
  at <Module>:runtime_invoke_void_object <0x001a8>

=================================================================

@dalexsoto
Copy link
Member Author

Hello, now that Xcode 13 support is out in both VS for Windows and VS for Mac I would encourage everyone that if you find issues with anything please report them in the respective support channel so they are not lost.

I will lock this thread for a little so issues can flow to the right places. Please do not forget to fill in as much information as possible requested by the new issues templates.

Thank you all!

@xamarin xamarin locked as resolved and limited conversation to collaborators Oct 6, 2021
@rolfbjarne rolfbjarne unpinned this issue Oct 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iOS Issues affecting Xamarin.iOS macOS Issues affecting Xamarin.Mac
Projects
None yet
Development

No branches or pull requests