This repository was archived by the owner on Feb 25, 2025. It is now read-only.
[iOS] Do not archive/upload Flutter.dSYM to cloud #54492
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of the following three patches, we now bundle Flutter.framework.dSYM as part of Flutter.xcframework and bundle them in the .xcarchive bundles produced by
flutter build ipa
/ Xcode Product > Archive for upload to the iOS App Store.The .dSYM bundle is now available both in the uploaded .xcarchive and in the xcframework in Flutter's internal artifact cache. For developers with CI toolchains that do additional manual handling or local archiving of .dSYMs, the dSYMs no longer need to be downloaded from cloud storage as previously detailed in
docs/Crashes.md
, but can instead be copied up from the appropriate dSYM subdirectory in the framework cache:flutter/bin/cache/artifacts/engine/ios-release/Flutter.xcframework
Issue: flutter/flutter#116493
Credo: Embrace the yak shave
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.