The MAUI Blazor doesn't work on iOS 16.2 arm64 simulator #12124
Comments
jsuarezruiz
added
area-blazor
|
@gdar91 can you please try this scenario with a MAUI app (not Blazor) and see if that works? Thanks! |
|
Hi @gdar91. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
`2022-12-16 08:33:37.962221+0800 MauiApp1[21635:318266] SecTaskLoadEntitlements failed error=22 cs_flags=200, pid=21635 ` |
ghost
added
s/needs-attention
|
I think the only way you could test iOS 16.2 is if you're using Xcode 14.2, which was just released and is not supported by the currently shipping iOS SDKs. What version of Xcode are you running? |
|
My Xcode Version 14.2 (14C18) |
|
I have the same issue, working on every iOS version but not on 16.2, only a blank page is shown :/ |
|
Thanks for your feedback, @Shineway02 and @Murkrow02. Could you please check if the issue reproduces on a MAUI project (NOT Blazor) with a normal webview? |
MackinnonBuck
added
s/needs-info
|
Hi @gdar91. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
I tried creating a blank MAUI (not blazor) project and added a simple web view.
|
ghost
added
s/needs-attention
|
This instead is what happens on 16.2 and 16.0 (running the same application, simple blank starting project for Blazor MAUI) This is the full log on iOS 16.2: xcrun simctl launch --stdout=/dev/ttys000 --stderr=/dev/ttys001 --terminate-running-process 89F0F764-8997-41E7-AB8B-866E61CBBF8D com.companyname.mauicacca -monodevelop-port 10000 |
|
I have the same issue. It started when I upgraded macOS to 13.1, Visual Studio for Mac to 17.4.2 and XCode to 14.2 My MAUI Blazor project runs ok on MacCatalyst, but on every iOS 16.2 simulator I only see a blank white screen. Is there any way I could get it working again? |
|
@Jinjinov The current net7.0-ios SDK does not support Xcode 14.2. It would be best if you downgraded back to Xcode 14.1 until it receives support. This issue could be related to underlying issues within the SDK that needs to be addressed. |
|
@drasticactions do you know of another tracking issue for the SDK issue that you're suspicious of? |
mkArtakMSFT
removed
the
s/needs-attention
|
confirmed that downgrading to 16.1 is working |
|
Also it only affects me on Simulator somehow. Testing on real iPhone works though it sucks because I can no longer use Simulator to take screenshots for the App Store. Will check if downloading lower Simulator image version (without XCode) works. UPDATE: doesn't work. VS can't see those simulators. |
|
Is there an estimation ot ETA of when .NET 7 sdk will work with xCode 14.2? |
|
Though shows blank UI on iOS 16.2 emulators, app works fine on actual device iPhone 13, iOS 16.3. Using Xcode 14.2, Maui Blazor "hello world" with Maui 7.0.59, .NET 7.0.2, MS.iOS 16.2.1007 Is the problem in the 16.2 simulators and simply need a fix in Xcode to bump and release an Xcode 14.3 with iOS 16.3 simulators? Fred |
|
I am pretty sure the latest VS for Mac works only with XCode 14.2 (I don't know about the Windows connection thing, I could never get it to work for me so I just use VS for Mac). So here's how it was after I updated to the latest VS for Mac:
So what it means:
Hope these problems can be fixed soon. |
|
This also makes it impossible to upload apps for review, since the Blazor apps also crashes in the simulator during review. "We were unable to review your app as it crashed on launch." A fix would be greatly appreciated :-) |
|
Can confirm with @hakonn , now 16.2 simulator simply shows blank screen, while trying to manually install the app through drag-and-drop to older simulators (16.0) would just crash on startup. We have no problem with review though since it runs fine on real devices. It's still an issue that needs to be fixed I believe. |
|
They seriously need to review their Xamarin MAUI compilation pipeline and maybe allocate more brainpower for it. Even if they say the GA is there, you can’t depend on it, because when you actually try to use it in production, lots of issues and blockers pop up. |
|
why is microsoft so quiet about this? It is a serious bug and we get no information on the progress. Meanwhile they're bashing the drum for hybrid razor on all plattforms. I'm really frustrated - feels like the bad old Xamarin days. And 5 seconds after I wrote this, I got it working on the 16.0 simulator ... didn't work a couple of days ago.... I did get a new OSX update just 2 days ago, maybe that fixed something! |
|
Can anyone reproduce this on an intel machine, or does it only happen on M1/M2 macs? |
|
Pretty sure that changed by the recent Visual Studio 2022 for Mac v17.4.5 (VS2022 on Windows has a similar update):
Update: after updating VS for Mac to the latest version, I can manually install the Debug build on Simulator 16.0 and run apps without crashing. |
I can confirm it's only a M1/M2 bug, working fine on my Intel machine. Still an issue if Apple reviewers use Apple silicon (very likely) |
AFAIK reviewers use actual devices, and this issue only happens in the simulator. Does the problem still occur when using <PropertyGroup>
<RuntimeIdentifier>iossimulator-arm64</RuntimeIdentifier>
</PropertyGroup> |
|
Can confirm, we have many iOS apps successfully published and passed reviews without any issue (no |
If the I really hope this issue gets resolved soon. Apple already released Xcode 14.3 beta and MAUI doesn't even support 14.2 correctly, which was released over two months ago. |
It seems you're using a third-party native library that doesn't support arm64 in the simulator.
This is a bit complicated to investigate, because Apple's web view rendering is remoted into a different process, and the problem is that this other process crashes. I wouldn't be surprised if this turns out to be a bug in the iOS simulator, because realistically nothing we do should be able to crash this other rendering process. |
We've tested this a bit, and it seems that this is the solution. At some point we'll change the default to build for iossimulator-arm64 when using an ARM64 Mac, but this won't be until .NET 8 at least (it's a rather major change, and it also means a lot of third-party libraries need to add support for iossimulator-arm64 as well - as evidenced by this previous comment). In the meantime it's possible to add this yourself to the project file. |
|
I can confirm this fixed it for us. |
|
Here is a solution that handles a few more scenarios (from dotnet/macios#17841 (comment)). Add this to the csproj: <PropertyGroup>
<_OSArchitecture>$([System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture)</_OSArchitecture>
<_TargetPlatformIdentifier>$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)'))</_TargetPlatformIdentifier>
<RuntimeIdentifier Condition="'$(_TargetPlatformIdentifier)' == 'ios' And '$(_OSArchitecture)' == 'Arm64' And ('$(_iOSRuntimeIdentifier)' == 'iossimulator-x64' Or ('$(_iOSRuntimeIdentifier)' == '' And '$(RuntimeIdentifier)' == ''))">iossimulator-arm64</RuntimeIdentifier>
</PropertyGroup>
|
|
Unfortunately, this still didn't fix it for us. It fails with the following error: Any idea why this happens? |
|
Neither of the workarounds above work for me. I have a slightly unconventional scenario where the blazor webview is in a separate MAUI class library. I tried adding both Here is the log of the simulator: https://pastebin.com/raw/07wuQiBE This is very annoying to deal with because I am forced to downgrade to .net 7.0.100 and ios workload 16.1 to be able to still use Xcode 16.1 |
Did you try to use the old iOS 16.1 simulator on Xcode 14.2 (iOS 16.2)? Edit: |
this is works fine, xcode 14.2 |
My guess is that the native sqlite library you're using doesn't contain an arm64 version for the simulator (it's trying to link in an arm64 version for device, which won't work). You'll need an updated version of the sqlite library. |
davidortinau
changed the title
|
The RuntimeIdentifier workaround worked for me. I am glad that the workaround provided a path forward, but it still leaves me feeling that MAUI is in chaos right now. |
|
The problem with this issue is that Apple is using arm64 simulators and does not want to validate working application. |
|
@foximoxi I got it through the verification process by stating in the test notes that they should test it on intel simulators or real hardware and referencing this issue. |
|
Because we have a workaround for this issue (adding the RID), I'm going to close this. There's an issue open to track changing the default, if you are interested in following that progress. Feel free to comment here or create a new issue if you think we've missed something. |
and others
Description
After upgrading to iOS 16.2, MAUI Blazor projects started crashing. This applies to devices and simulators.
Steps to Reproduce
Link to public reproduction project repository
https://github.com/dotnet/maui
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 16.2
Did you find any workaround?
See these comments:
Relevant log output
No response
The text was updated successfully, but these errors were encountered: