Missing weak symbol

[brian-smith723]

First off, thank you for creating this package.

I've installed Jc.GMA.iOS and Jc.UMP.iOS. The package works only on a simulator. When I run it on a physical device I get the following error:

2025-08-24 13:00:01.098 XXXXX[5239:539416] [Firebase/Crashlytics] Version 11.0.0
2025-08-24 13:00:01.125 XXXXX[5239:539416] Plugin.Firebase initialized with the following settings:
2025-08-24 13:00:01.125 XXXXX[5239:539416] [CrossFirebaseSettings: IsAnalyticsEnabled=True,IsAuthEnabled=True,IsCloudMessagingEnabled=True,IsCrashlyticsEnabled=False,IsDynamicLinksEnabled=True,IsFirestoreEnabled=True,IsFunctionsEnabled=True,IsRemoteConfigEnabled=True,IsStorageEnabled=True]
2025-08-24 13:00:02.143 XXXXX[5239:539477] Warning: observer object was not disposed manually with Dispose()
2025-08-24 13:00:02.143 XXXXX[5239:539477] Warning: observer object was not disposed manually with Dispose()
Failed to look up symbolic reference at 0x1031a8447 - offset 99065 - symbol symbolic _____Sg ScP in /private/var/containers/Bundle/Application/69270111-8FD1-445E-8F85-E2AA3AB7CD6E/XXXXXX/XXXX - pointer at 0x1031c0740 is likely a reference to a missing weak symbol

The app starts and then crashes during the splash screen.

What am I missing? Is there a conflict with Plugin.Firebase ?

I don't know how to solve this issue.

[jcsawyer]

I'm not entirely sure what might be causing this. This does smell like it may be related to #49 if you wanted to try the workaround there?

[OMendozaG]

I’m pretty sure this is the same issue, because after the splash, one of the first things to run is probably GAM.SharedInstance.init.

Just try changing the minimum version in your csproj.

<SupportedOSPlatformVersion>15.0</SupportedOSPlatformVersion> <TargetPlatformMinVersion>15.0</TargetPlatformMinVersion>

[brian-smith723]

@OMendozaG I updated the target platform for iOS and it worked. Thank you!

[Picao84]

I’m pretty sure this is the same issue, because after the splash, one of the first things to run is probably GAM.SharedInstance.init.

Just try changing the minimum version in your csproj.

<SupportedOSPlatformVersion>15.0</SupportedOSPlatformVersion> <TargetPlatformMinVersion>15.0</TargetPlatformMinVersion>

Where do you put this exactly? Did you clone this repo and added that to the csproj? Or did you add this to your own project csproj?

[OMendozaG]

I’m pretty sure this is the same issue, because after the splash, one of the first things to run is probably GAM.SharedInstance.init.
Just try changing the minimum version in your csproj.
<SupportedOSPlatformVersion>15.0</SupportedOSPlatformVersion> <TargetPlatformMinVersion>15.0</TargetPlatformMinVersion>

Where do you put this exactly? Did you clone this repo and added that to the csproj? Or did you add this to your own project csproj?

In your own project, simply find MinimumOSVersion and SupportedOSPlatformVersion and change it to 15 or greatter.

[Picao84]

Actually that is not a fix because your app is going to crash on iOS versions under 18.4! The issue is here: https://stackoverflow.com/questions/79573379/after-upgrading-from-xcode-14-0-to-xcode-16-3-my-swiftui-project-failed-to-run

Something changed with Xcode 16.4 that is causing this issue and the fix seems to be on the LinkerFlags.

[Picao84]

Nevermind, they are actually two different things. Sorry about that, but hopefully might be useful too if you experience problems with XCode 16.3+!

[YasarYY]

Hi. out of curiosity, I performed some trials to choose a stable combination of versions.

• Project uses Avalonia version 11.3.7, on net9.0
• .NET SDK at Mac (osx 15.6) is version 9.0.305, ios workload is version 18.5.9219/9.0.100
• Used simulator device is iOS 18.6
• Used physical device is iOS 18.6.2
• For changing minimum iOS version, I only altered <SupportedOSPlatformVersion> (didn't add <TargetPlatformMinVersion>)

+-----------------+-------------------+-------------------+
|                 | .NET 9 not incl.  | .NET 9 incl.      |
|   SupportedOS   | with packages:    | with packages:    |
| PlatformVersion | Jc.GMA.iOS 12.2.2 | Jc.GMA.iOS 12.2.3 |
|                 | Jc.UMP.iOS 2.7.3  | Jc.UMP.iOS 2.7.4  |
+-----------------+-------------------+-------------------+
|      13.0       | sim OK            | sim OK            |
|                 | phy CRASHED       | phy CRASHED       |
+-----------------+-------------------+-------------------+
|      14.0       | sim OK            | sim OK            |
|                 | phy CRASHED       | phy CRASHED       |
+-----------------+-------------------+-------------------+
|      15.0       | sim OK            | sim OK            |
|                 | phy OK            | phy OK            |
+-----------------+-------------------+-------------------+

As previously determined, inclusion of .NET 9 has nothing to do with this. So, #47 seems having no effect on this issue. I'll go with SupportedOSPlatformVersion set to 15.0.

And, thoughts? I have absolutely no idea about what's happening here 😅 Unfortunately, I cannot add anything to what has already been said.

[jcsawyer]

Thanks for the interesting investigation @YasarYY
I'm honestly not entirely sure what the cause was here. But I suspect some combination of Xcode/Microsoft/Google shenanigans as this definitely did work at one point.

Either way, I should probably get around to adding in platform support annotations somewhere (if poss) to help analysers highlight the required supported version as I'm not sure on how I could fix this issue at its root when I can't be certain of the cause

[jcsawyer]

Given I'm not entirely sure there's a whole lot I can do from this package, I am adding in a compiler warning to this package that prompts a consumer to update the supported os version to a minimum of 15.0.

This means iPhone 6 and lower is no longer supported as far as I can tell. I suspect this isn't far out of Apple's own support timeline anyway.

Please let me know if there's anything else you think I might be able to do to close this one out.

[YasarYY]

Well, the most reasonable closure to this issue seems what you are planning to do. I cannot think of anything else, since it seems the cause of this problem is not about this package, but some later emerged incompatibility between MS/Apple APIs.

About Apple's support timeline, iPhone 6 received its last security update at January 23, 2023, on iOS 12.5.7 [1]. And iOS 12 is no longer unsupported [2]. (Next iPhone, iPhone 6s, is currently on iOS 15.8.5 and is receiving security updates.)

So, giving package users a compiler warning seems a good way to walkaround this beyond-our-control issue.

[1] https://en.wikipedia.org/wiki/List_of_iPhone_models
[2] https://en.wikipedia.org/wiki/IOS_12