In iphone 16 (ios 18) Splash screen showing black

[chinni-nag]

Description

In iphone 16 (ios 18) Splash screen showing black

Steps to Reproduce

Added required code for splash screen can able to see in iphone 13 and Android but not in iphone 16

Link to public reproduction project repository

No response

Version with bug

8.0.82 SR8.2

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

No response

Affected platforms

iOS

Affected platform versions

Ios 18

Did you find any workaround?

No response

Relevant log output

No response

[similar-issues-ai[bot]]

We've found some similar issues:

• #20171 , similarity score: 82%
• #16945 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[chinni-nag]

Hello, Please add one splash screen the test app run in the simulator i.e. iphone 16 (ios 18).

[ninachen03]

Could you try to Add the following to PropertyGroup in the csproj. it may dup of https://github.com/xamarin/xamarin-macios/issues/18469

<EnableCodeSigning>true</EnableCodeSigning>
<CodesignRequireProvisioningProfile>true</CodesignRequireProvisioningProfile>
<DisableCodesignVerification>true</DisableCodesignVerification>

[chinni-nag]

@ninachen03 getting below error while building the app

/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk.net8.0_18.0/18.0.8303/tools/msbuild/iOS/Xamarin.Shared.targets(1835,3): error : Could not find any available provisioning profiles for AppicontestApp on iOS.

[jfversluis]

When running on the iPhone 13 Simulator, what version of iOS do you target there?

Also iOS 18?

As of iOS 16.4, the Simulators now require signed builds to show the splash screen, also see: https://github.com/xamarin/xamarin-macios/issues/19430

More on how to do that is explained here: https://learn.microsoft.com/dotnet/maui/ios/deployment/publish-cli

The easiest way to test is by deploying to a physical device because that is always a signed build.

Can you confirm if that does show it correctly?

[dotnet-policy-service[bot]]

Hi @chinni-nag. 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.

[jfversluis]

@rolfbjarne is this a new variation we know of?

[rolfbjarne]

@rolfbjarne is this a new variation we know of?

No, this looks like the codesigning in the simulator issue.

[dotnet-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.