Skip to content

Add a note to the Bitcode workaround #9037

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.

Sign up for GitHub

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

Merged
MariaShaposhnikova merged 1 commit into from
Feb 11, 2025
Merged

Add a note to the Bitcode workaround #9037

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions ...nt/en/docs/refguide/mobile/introduction-to-mobile-technologies/native-mobile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,13 @@ To address the issue, there are one of three things you can do:

#### Workaround {#bitcode-workaround}

Apply the following changes to the native mobile project in "ios/Podfile" file in the "post_install" block (ref https://stackoverflow.com/questions/79022303/asset-validation-failed-nslocalizedrecoverysuggestion-invalid-executable-the-e/79022687):
{{% alert color="info" %}}

In the workaround below, there might be paths (files) missing depending on the exact version of Studio Pro you are using. If the build process fails, Studio Pro shows you problematic paths that need to be added to the list.

{{% /alert %}}

Apply the following changes to the native mobile project in "ios/Podfile" file in the "post_install" block (For more information, see [Asset validation failed, NSLocalizedRecoverySuggestion=Invalid Executable](https://stackoverflow.com/questions/79022303/asset-validation-failed-nslocalizedrecoverysuggestion-invalid-executable-the-e/79022687)):

@MariaShaposhnikova MariaShaposhnikova Feb 11, 2025

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note for @ConnorLand , in our style guide it says: For static links (to external websites), deep-link the name of the site/page (do not include full URL as the link text unless you want to emphasize how the URL is written).
Also for cross-referencing:
Use these phrases consistently when cross-referencing:
“For more information,…” + “…see {doc}.”
“For details on…,” + “…see {doc}.”

So I have changed the external link text.


```
bitcode_strip_path = `xcrun --find bitcode_strip`.chop!
Expand All @@ -59,4 +65,5 @@ bitcode_strip_path = `xcrun --find bitcode_strip`.chop!
framework_paths.each do |framework_relative_path|
strip_bitcode_from_framework(bitcode_strip_path, framework_relative_path)
end
```
```