When building Xamarin.Firebase.iOS.Core, Xamarin.Firebase.iOS.CloudMessaging and Xamarin.Firebase.iOS.InstanceID with a recent Xamarin.iOS versions, a lot of "...pcm: No such file or directory" warnings occur. This is an example of what they look like:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(3,3): Warning: warning: /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/C/org.llvm.clang.runner/ModuleCache/1XLCWWLE22H9C/FirebaseInstanceID-3I51ZS0UOAE71.pcm: No such file or directory
We reproduced this with the following Xamarin.iOS and XCode versions:
The current Xamarin.iOS version 15.4.0.0, and XCode 13.2.1.
The current Xamarin.iOS version 15.4.0.0, and XCode 13.1.
The previous Xamarin.iOS version 15.2.0.17, and XCode 13.1
We reproduced by building a Xamarin.Forms app with the following NuGet package versions:
The warnings do not appear with Xamarin.iOS 14.20.0.24 and XCode 12.5.1
With packages versions Xamarin.Firebase.iOS.Core 5.2.0, Xamarin.Firebase.iOS.CloudMessaging 3.1.2, Xamarin.Firebase.iOS.InstanceID 3.2.1
The warnings seem to be related to debugging. But it's unclear to me how to address these warnings. Do they indicate that something is broken? Everything we tested with the Firebase packages seemed to work. How can we fix these warnings? It is desirable that the warnings do no occur, especially because they do not seem to have a warning number (with which the warning could be suppressed).
I'm not entirely sure if this is a bug of GoogleApisForiOSComponents or rather of Xamarin.iOS. Since we've seen this problem so far only with the Firebase NuGet packages, I assume this is a good place for this bug report.
Steps to Reproduce
Create new Xamarin.Forms solution (e.g. using the Visual Studio "Blank app" template)
Add the NuGet packages mentioned above
Add rudimentary Firebase cloud messaging implementation based on this guide.
Clean and build the solution
The example project below has been created using these steps.
Expected Behavior
No warnings occur.
Actual Behavior
A large number of "...pcm: No such file or directory" warnings occur.
With the most recent Xamarin.iOS version 15.4.0.0 and XCode 13.2.1, we observed a separate warning issue with Xamarin.Firebase.iOS.Core (and other NuGet packages). Here is the link in case the two issues are related: https://github.com/xamarin/xamarin-macios/issues/13652.
When building Xamarin.Firebase.iOS.Core, Xamarin.Firebase.iOS.CloudMessaging and Xamarin.Firebase.iOS.InstanceID with a recent Xamarin.iOS versions, a lot of "...pcm: No such file or directory" warnings occur. This is an example of what they look like:
We reproduced this with the following Xamarin.iOS and XCode versions:
We reproduced by building a Xamarin.Forms app with the following NuGet package versions:
Last known good versions:
The warnings seem to be related to debugging. But it's unclear to me how to address these warnings. Do they indicate that something is broken? Everything we tested with the Firebase packages seemed to work. How can we fix these warnings? It is desirable that the warnings do no occur, especially because they do not seem to have a warning number (with which the warning could be suppressed).
I'm not entirely sure if this is a bug of GoogleApisForiOSComponents or rather of Xamarin.iOS. Since we've seen this problem so far only with the Firebase NuGet packages, I assume this is a good place for this bug report.
Steps to Reproduce
The example project below has been created using these steps.
Expected Behavior
No warnings occur.
Actual Behavior
A large number of "...pcm: No such file or directory" warnings occur.
Environment
pcmwarnings-systeminfo.txt
Build Logs
pcmwarnings-buildlog.txt pcmwarnings-warnings.txt
Example Project
pcmwarnings.zip
Potentially related issue
With the most recent Xamarin.iOS version 15.4.0.0 and XCode 13.2.1, we observed a separate warning issue with Xamarin.Firebase.iOS.Core (and other NuGet packages). Here is the link in case the two issues are related: https://github.com/xamarin/xamarin-macios/issues/13652.