Skip to content
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

Asset validation failed due to bitcode in OMSDK_Teadstv.framework, TeadsSDK.framework #251

Open
dailydmello opened this issue Oct 7, 2024 · 7 comments
Assignees

Comments

@dailydmello
Copy link

dailydmello commented Oct 7, 2024

Description

During the app upload process to App Store Connect, we encountered multiple asset validation errors related to frameworks in our project containing bitcode. The error messages indicate that the OMSDK_Teadstv.framework, TeadsSDK.framework, and OMSDK_Adsbynimbus.framework all contain bitcode, causing the upload to fail with the following error code:

[09:55:30]: [ContentDelivery.Uploader.600003B901C0] Asset validation failed (90482) Invalid Executable. The executable 'theScore.app/Frameworks/OMSDK_Adsbynimbus.framework/OMSDK_Adsbynimbus' contains bitcode. (ID: 36dd9f67-d030-4f41-85a2-a8ebdd5d2799) [09:55:30]: [ContentDelivery.Uploader.600003B901C0] Asset validation failed (90482) Invalid Executable. The executable 'theScore.app/Frameworks/OMSDK_Teadstv.framework/OMSDK_Teadstv' contains bitcode. (ID: dc7f61a6-8dee-4af7-ac87-bd36379c43a1) [09:55:30]: [ContentDelivery.Uploader.600003B901C0] Asset validation failed (90482) Invalid Executable. The executable 'theScore.app/Frameworks/TeadsSDK.framework/TeadsSDK' contains bitcode. (ID: 780a6298-c148-47af-8a4f-8a81cd597993)

Impact:

This issue is blocking our ability to upload the app to the App Store. Bitcode is deprecated for iOS submissions, and it needs to be removed from these frameworks.

Steps to Reproduce:

  • Attempt to upload an iOS application to App Store Connect with the mentioned frameworks integrated.
  • Observe the asset validation errors during the fastlane upload process

Expected Behavior:

The upload process should succeed without any validation errors related to bitcode.

##Actual Behavior:
The upload process fails due to bitcode in OMSDK_Teadstv.framework, TeadsSDK.framework, and OMSDK_Adsbynimbus.framework.

Possible Solution:

Please provide a version of the frameworks that does not include bitcode, in line with the recent changes from Apple’s deprecation of bitcode for App Store submissions.

Environment

Fastlane version: 2.223.1
Xcode version: Xcode 16.0
Framework version: 5.1.3
macOS: 14.7 (23H124)

@github-richard-depierre
Copy link
Contributor

Hi @dailydmello,

Thank you for bringing this issue to our attention. We are aware of the asset validation errors related to bitcode in the OMSDK_Teadstv.framework, TeadsSDK.framework, and OMSDK_Adsbynimbus.framework, and we’re currently investigating a solution.

To address the problem, we’re working on releasing SDK versions without bitcode, in line with Apple’s deprecation. We’ll provide an update as soon as we have a confirmed timeline for the bitcode-free release.

We appreciate your patience, and we’ll keep you posted on our progress.

Best regards,
Richard

@github-lucas-bon
Copy link
Contributor

Hello all, the ETA for next release fixing this issue is early next week. Anyway we are doing our best to release until Friday.

@github-richard-depierre
Copy link
Contributor

github-richard-depierre commented Oct 23, 2024

Hi @dailydmello this issue seems to be fixed in the latest release 5.1.6 please tell me if this has fixed your issue.

@v-andreipetrea
Copy link

Hi @github-richard-depierre , @github-lucas-bon,

The issue is still there for "OMSDK_Teadstv.framework". Have you tried to update the SDK?

They removed bitcode in their latest release:
Changelog for Open Measurement SDK on iOS
1.5.2 - 2024-09-26
Disable bitcode for builds.

In order to be able to submit the app in AppStore we removed bitcode from OMSDK_Teadstv.framework by running "bitcode_strip" command.

But it would be nice to have a permanent solution and avoid this workaround.

Do you have plans to release an update version of the OM SDK soon?

Thanks,
Andrei

@github-richard-depierre
Copy link
Contributor

Hello @v-andreipetrea

We are currently looking into updating the OM SDK to the latest version. We’ll keep you posted as soon as we have an updated version of the OM SDK integrated.

Thank you for your patience, and we appreciate your workaround in the meantime.

Best,
Richard

@github-lucas-bon
Copy link
Contributor

New ETA early next week.

@jonashinge
Copy link

Have the same problem. Fails using Xcode 16.1. Have to fallback to 15.4 for App Store uploads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants