I have a blazor hybrid app that includes a chart. It works fine on Windows, Android and IOS but in IOS only in debug mode. As soon as i produce a release version (delivered to a local connected device) the program crashes. I can't see any specific error, just the generic blazor yellow section. I wrap the section into an ErrorBoundary but all i can see is a red section with a message "An error has occurred" ( no crash this time )
Hi Leonardo,
We have analyzed your query, and you mentioned that a Blazor hybrid app crashes on iOS. However, we don't have enough information about the specific issue you're facing, including the chart version you're using. It would be helpful if you could provide more details about the chart version you are using.
Additionally, it would be beneficial to know if you are using the MAUI framework for your hybrid app development. Knowing the environment you are working in can assist in diagnosing and resolving the crash issue more effectively. Furthermore, please provide details about the host environment.
To better assist you, it would be helpful if you could provide a demo sample that reproduces the issue you are experiencing. With a sample code or more specific details about the problem, we can offer a more accurate and timely solution.
Kindly revert us if you have any concerns.
Regards,
Gopalakrishnan Veeraraghavan
Sorry for the delay, i have created a simple project to reproduce the incident ( its the base blazor app with a sample SF chart )
leoperez77/SfHybridDemo (github.com)
Basically, the problem appears in a release version running on IOS . I dot it connecting a device via cable to the Max. It does not appear with a debug version.
:)
Regards,
Leo.
Hi Leonardo Perez,
We are analyzing your query and we will update the status within two business days(August 9th , 2023). We appreciate your patience until then.
Regards,
Gopalakrishnan Veeraraghavan
Hi Leonardo,
We are currently investigating a hybrid app crash issue that occurs when deploying the chart in an iOS device. Our investigation is being conducted in a MAUI Blazor app. However, at present, we do not have access to an iOS device to test the issue in a MAUI environment. We plan to acquire an iOS device within the next two days and will update you on the status of the issue once we have conducted the necessary tests. We appreciate your patience until then.
Regards,
Gopalakrishnan Veeraraghavan
No worries, thank you very much for your support.
Hi Leonardo,
You're welcome. Please get back to us if you need any further assistance. we will be happy to help you.
Regards,
Jayashree
Hello everyone,
Around three weeks ago, there was mention of conducting tests on iOS devices. I'm curious if there have been any updates or news regarding those tests? It would be great to hear about any progress or findings related to this topic. Looking forward to any insights you might have to share!
Leo.
Hi Leonardo,
Sorry for their inconvenience caused.
To investigate the issue of the chart crashing on iOS devices, it is necessary to have an Apple developer account in order to debug the MAUI app. However, we are currently experiencing difficulties logging into the Apple developer account for debugging purposes. We are actively working with our internal team to resolve this issue with the Apple developer account. Once the issue is resolved, we will provide an update on the status of the problem within a week.
Regards,
Gopalakrishnan Veeraraghavan
Hello guys, any news ? :)
Hi Leonardo,
Sorry for their inconvenience caused.
Currently, we are facing a crash issue in the MAUI project on iOS devices when the chart component is not included. We have experienced the Maui application crashing on an iPad device while trying to deploy the project using the Maui framework. Therefore, we have raised a ticket with Microsoft support. Currently, we are checking with Microsoft support to resolve the issue. Once the issue is resolved by Microsoft, we will investigate the crash issue related to the chart component. Please find the attached screenshots for reference.
Screenshots:
Regards,
Gopalakrishnan Veeraraghavan
Leonardo,
I am assuming you are running xcode 15 and your device is IOS17? I ask because there is a known issue with MAUI anything and IOS right now. It has something to do with some libraries that were removed in the IOS17 SDK that MAUI automatically tries to link. I have tried many things and am 100% unable to get a maui app to run in ios. From what I have read there is a release coming out next month that will fix this in .net 8 but there is supposed to be a backport to IOS 7
Hope this helps.
Brian
Brain,
Thanks for the update. We will ensure the reported scenario once .NET 8 is released as per your update. We appreciate your patience until then.
Kindly revert us if you have any other concerns.
No problem, you are very supportive. I'll keep in touch.
Thanks.
Leonardo,
Most welcome. We are always happy in assisting you.
Reviving this thread because I am experiencing the same issue now. iOS 18.5 and XCode 16.3. The Blazor hybrid maui app runs fine as a debug build, but immediately crashes as release mode. Syncfusion is the only charting library I found to work easily for a hybrid app, and I would really like to keep using it.
Thanks,
Scott C.
I wanted to add my fix for this issue. After running my issue by Gemini, found out that this issue was related to .Net Linker. Basically, iOS linker aggressively removes code it thinks is not needed to save space. Here is the fix. Add the following to the project file, adding/replacing the SyncFusion assemblies that you are using.
<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-ios|AnyCPU'">
<MtouchExtraArgs>--linkskip=Syncfusion.Blazor.Core --linkskip=Syncfusion.Blazor.Charts --linkskip=Syncfusion.Blazor.Themes --linkskip=Syncfusion.Licensing</MtouchExtraArgs>
</PropertyGroup>
Scott,
Thank you for sharing the solution. We truly appreciate you taking the time to post the update, and we’ll certainly consider it.
If you have any further questions or concerns, please don’t hesitate to reach out. We’re always happy to assist you.
Hi Leonardo Perez,
A crash like that usually hints at something in the release build getting trimmed or blocked by iOS restrictions, especially when charts or web-rendered components are involved. Sometimes people test apps with different builds on the same device, and they use tools or files from outside the official store during development. That reminded me of how many issues pop up when someone sideloads things like a Roblox, because iOS locks down anything unsigned. If your hybrid app loads any external resources in a similar way or references something not included in the release bundle, iOS can shut it down without giving a clear trace. It might help to double check the linker settings, make sure every script or asset used by the chart is included, and confirm nothing depends on a path or file that only exists in the debug environment.
Sam Konstas,
Thank you for sharing these insights. We’ll review the release build configuration and confirm that all chart-related scripts and assets are included. We’ll also check linker settings and ensure there are no references to debug-only paths or external resources that iOS might block. If needed, we’ll run tests on a clean device to rule out any sideloading-related issues.