[Bug] iOS Build crashing on second launch when made with Xcode 15.3

[jayantjha23]

Description

iOS app build with Xcode 15.3 crashes on second launch after debugging I found that it is stucking in firebase code
var task = FirebaseMessaging.GetTokenAsync();
Build is working fine when made with Xcode 14.

Reproducing the issue

Make iOS Build with Xcode 15.3 .
Unity Version-2021.3.28f1
firebase version -9.6.0
step to reproduce
1.try to get token from firebase using var task = FirebaseMessaging.GetTokenAsync();
2. get instance id from firebase using var task=FirebaseAnalytics.GetAnalyticsInstanceIdAsync();

Firebase Unity SDK Version

9.6.0

Unity editor version

2021.3.28f1

Installation Method

.unitypackage

Problematic Firebase Component(s)

All

Other Firebase Component(s) in use

No response

Additional SDKs you are using

No response

Targeted Platform(s)

Apple Platforms

Unity editor platform

Mac

Scripting Runtime

IL2CPP

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

Relevant Log Output

No response

If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

👀 Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[paulinon]

Hi @jayantjha23,

Does updating the Firebase SDK to its latest version make any difference? If it doesn't, could you provide the full stack trace being returned so we can identify what's causing this to happen?

[google-oss-bot]

Hey @jayantjha23. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@jayantjha23 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.