This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 43%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
I have an application that I have deployed to an ios device that is now showing a black screen after the splash screen is loaded. I am running the latest xcode, vs versions and the project is targeting .net 9. What should I be looking for as a possible cause of this?
Regards,
Daniel
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWZ%3C/text%3E%3C/svg%3E)
I want to double-check that the VS version is 17.12.4 and the Xcode version is 16.2, right? What's the iOS version of your device? On your physical device, right? Or on a simulator? Do you call any methods when the app is launching? Could you create an empty project and then see if the screen is black and test if the issue only occurs on your current project?
After testing, the screen is black when running on simulators (works on physical device), please let me know if it's the same behavior as yours.
Hello Wenyan
VS is 17.12.4
Xcode is 16.2
iOS version of device is 17.6.1
My project is targeting .net 9
I am not calling any methods while the app is launching. An empty test project works fine on the device.
The output windows is reporting the following problems:
Loaded assembly: /private/var/mobile/Containers/Data/Application/888257B4-14BA-4EB6-8B0A-1E56C3096CFB/Documents/ChronicleMobileApp.content/System.Runtime.InteropServices.JavaScript.dll [External]
[0:] Failed to force load assembly /var/mobile/Containers/Data/Application/888257B4-14BA-4EB6-8B0A-1E56C3096CFB/Documents/ChronicleMobileApp.content/System.Runtime.InteropServices.JavaScript.dll. Type:System.Runtime.InteropServices.JavaScript.JSExportAttribute. Exception: 'System.Runtime.InteropServices.JavaScript is not supported on this platform.'. Callstack: ' at System.Runtime.InteropServices.JavaScript.JSExportAttribute..ctor()
at System.Object.InvokeStub_JSExportAttribute..ctor(Object , Object , IntPtr* )
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)'
Loaded assembly: /private/var/mobile/Containers/Data/Application/888257B4-14BA-4EB6-8B0A-1E56C3096CFB/Documents/ChronicleMobileApp.content/HtmlAgilityPack.dll [External]
2025-01-22 11:31:07.689 Xamarin.PreBuilt.iOS[669:61172] Could not resolve assembly System.Runtime.InteropServices.JavaScript.resources, Version=9.0.0.0, Culture=en, PublicKeyToken=null. Details: Could not load file or assembly '/var/mobile/Containers/Data/Application/888257B4-14BA-4EB6-8B0A-1E56C3096CFB/Documents/ChronicleMobileApp.content/System.Runtime.InteropServices.JavaScript.resources.dll' or one of its dependencies.
Thanks for your help
Daniel
An empty test project works fine on the device.
I understand this issue only occurs on your current project.
The error occurs on System.Runtime.InteropServices.JavaScript.dll. Is your project a Blazor app?
Hi Wenyan
It is not a blazor app. I am using a webview so I guess that is why System.Runtime.InteropServices.JavaScript.dll is being included in the project. Could a Java security restriction be the cause of such behavior?
Regards,
Daniel
After a bit of digging would you recommend using a storyboard to see if that is what iOS is missing?
It turns out that this black screen issue was caused by an incorrectly configured ios cert/profile issue that got introduced when I upgraded to .net 9.
Glad you solved the problem, I converted the comment to answer, thanks for your sharing.