xcrun -find bitcode_strip is running every time I deploy locally to an iPad

[dsancho]

Description

The problem is that every time I want to debug my application on the iPad, it takes like 30 minutes to run the command xcrun -find bitcode_strip for GoogleMobileAds library. The think is that this library already has been striped and running this command does nothing.

First time I can understand that it is needed to do this process for /XamarinBuildDownloadCache/FAdM-8.13.0/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.xcframework/ios-arm64_armv7/GoogleMobileAds.framework/GoogleMobileAds but the generated file can be used for subsequent compilations.

I asked GPT and answered to put this in my project

<_StripBitcodeFromFrameworksMasterDependsOnTargets Condition="'$(OS)'=='Windows_NT'">_StripBitcodeFromFrameworksOnWindows</_StripBitcodeFromFrameworksMasterDependsOnTargets>

BUT did not work.

Steps to Reproduce

1. Create a new MAUI iOS project
2. Add any package that references Xamarin.Google.iOS.MobileAds (8.13.0.3). For example, Plugin.MauiMTAdmob
3. You need an Apple developer account, and the device added to a profile for this application.
4. Try to debug in a connected device

Link to public reproduction project repository

No response

Version with bug

9.0.0-preview.7.24407.4

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Bitcode is deprecated when publishing app to appstore MAUI in 7.0.200-preview.22628.1 (#12863), similarity score: 0.76
• How to disable bitcode strip in Plugin.Firebase in .net 7. It causing issue in iOS in .net MAUI, unable to make release build. (#12993), similarity score: 0.75
• How to disable bitcode strip for Google Sign In ? (#12631), similarity score: 0.74
• How to disable bitcode strip for Google Sign In ? (#12663), similarity score: 0.74
• .NET 8 iOS app build error when using Xamarin.Firebase.iOS.Core NuGet: bitcode_strip: missing argument(s) (#19946), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[dsancho]

I have found a workaround that is to comment the following lines from Xamarin.Google.iOS.MobileAds.targets (in the nuget package folder)

<ItemGroup Condition="('$(OutputType)'!='Library' OR '$(IsAppExtension)'=='True')">
    <_FrameworkNamesToStripBitcode Include="GoogleMobileAds" />
  </ItemGroup>

but the ideal is that somehow, visual studio was able know that the file in the XamarinBuildDownloadCache has been already striped.

[drasticactions]

@rolfbjarne Would this be an SDK issue?

[rolfbjarne]

This is probably a bug in the Xamarin.Google.iOS.MobileAds NuGet, but if you could get an MSBuild binlog I should be able to confirm what's going on.

[dsancho]

This happens to other packages too. It will happen for any package that needs to be striped.

[QianaJiao]

Hi, @dsancho I noticed that you also debug to the local iOS device, and using xcframework resource, so it may be the same as #23829 (comment)

[rolfbjarne]

Hi, @dsancho I noticed that you also debug to the local iOS device, and using xcframework resource, so it may be the same as #23829 (comment)

No, it's not (xcframeworks work fine with Hot Restart, I've created a PR to update the documentation).

[dotnet-policy-service]

Hi @dsancho. 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.

[dotnet-policy-service]

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.