-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install app on device when adding FirebaseAnalyticsOnDeviceConversion
via SPM
#10126
Comments
I found a few problems with this issue:
|
Thanks for the report. It's being tracked internally at b/242914978 |
@gbrixey can you share your project? We suspect this issue occurs when SPM links a static dependency into your app target and then extraneously bundles it into your app bundle as well. The bundled library is unsigned, which causes errors when deploying to device (unsigned bundles can run fine on simulator). |
@morganchen12 sure, I was able to reproduce the issue with a simple test project: FirebaseSPMTest.zip |
Thanks @gbrixey, the culprit seems to be
I haven't figured out how to remove this copy command without excluding |
@htcgh and the Analytics team have identified a fix. I tested a prerelease binary with your test project and it built successfully. We should have this out in the next release. |
Should be fixed in 9.6.0 that released today. |
[REQUIRED] Step 1: Describe your environment
13.4.1 (13F100)
9.4.1
Swift Package Manager
FirebaseAnalyticsOnDeviceConversion
iOS
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
FirebaseAnalyticsOnDeviceConversion
to the app target.See the full text of the error message here.
This error only appears when running the app on a physical device; there is no such error when running on simulator.
This issue is similar to another one that was reported and closed recently: #9938. The repro steps are slightly different for me, as I am using SPM and I am not attempting to embed
FirebaseAnalyticsOnDeviceConversion
. The Firebase SDK version is also different.The text was updated successfully, but these errors were encountered: