Can't find DSYM file for archive App.
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
I have skip project with various dependencies, but when I upload it to AppStoreConnect or PlayStore I always receive the warning of missing DSYM. Recently I've added the Crashlytics dependencies through skip-firebase package but it seems that without dsym (also crashlytics complains about missing dsym) it mostly useless.
I've tried to look for generated dsym inside the derived data folder of Xcode, but I could only find one named skipstone.DSYM under Build\Products\PluginExecutables
I've checked on my target build settings and under Build options->Debug Information Format->Release I have DWARF with dSYM File.
Here's my Package file content:
// This is a Skip (https://skip.dev) package.
import PackageDescription
let package = Package(
name: "presenze-junohr",
defaultLocalization: "en",
platforms: [.iOS("17.4")],
products: [
.library(name: "JunoHR", type: .dynamic, targets: ["JunoHR"]),
],
dependencies: [
.package(url: "https://source.skip.tools/skip.git", from: "1.8.0"),
.package(url: "https://source.skip.tools/skip-ui.git", from: "1.0.0"),
.package(path: "../presenze-core"),
.package(url: "https://source.skip.tools/skip-firebase.git", "0.0.0"..<"2.0.0")
],
targets: [
.target(name: "JunoHR", dependencies: [
.product(name: "SkipUI", package: "skip-ui"),
.product(name: "PresenzeCoreApp", package: "presenze-core"),
.product(name: "SkipFirebaseMessaging", package: "skip-firebase"),
.product(name: "SkipFirebaseCrashlytics", package: "skip-firebase")
], resources: [.process("Resources")], plugins: [.plugin(name: "skipstone", package: "skip")])
]
)
Any help is really appreciated, even also on how to possibly generate and upload dSYM file for Android build too.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the provided Swift Package target configuration, its Release Debug Information Format setting, and the derived-data PluginExecutables output. Determine how the archived iOS and Android builds produce their symbol files, and document the verified generation and upload path for both platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, ios, swift
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100