0.7.4 - 2026-08-11
Release Notes
Added
debug-files upload --type il2cpp-linemap— upload Unity IL2CPP
LineNumberMappings.json(+ siblingMethodMap.tsv/il2cppFileRoot.txt)
keyed bylibil2cpp/UnityFrameworkmodule UUID(s). See
docs/unity-il2cpp-linenumber-mappings.md.debug-files upload --type rust— one command for a Cargo project,
whatever target it built for. A Rust project's symbols are a.dSYM(Apple),
a.pdb(*-pc-windows-msvc), or the ELF binary itself keyed by its GNU
build-id (Linux/Android); this discovers whichever is present and routes each
to the same upload path its--type-specific command would use.- Discovery is content-based (container magic, not host OS), so a
cross-compiledtarget/<triple>/releaseuploads correctly from any host. - Cargo intermediates —
deps/,build/,incremental/,.fingerprint/—
are skipped; walking them would register a symbol document per dependency
and build script. - Loose ELF binaries are uploaded per-file, keyed by build-id with the
Breakpad transform (the existing--type elfpath takes AGP's pre-built
native-debug-symbols.zipand is unchanged). --uuidis rejected: every Rust debug format carries its own identity, and
that identity is what the SDK reports for the module at crash time.
- Discovery is content-based (container magic, not host OS), so a
- Build-configuration preflight for Rust. Each format has a setting that,
when missing, yields an upload that is accepted and then resolves nothing —
no DWARF (debug = 0), no.dSYM(split-debuginfonot"packed"), no
build-id (missing-Wl,--build-id). Near-misses found during the walk are
warned about with the exact stanza that fixes them, and a walk that finds
nothing uploadable fails with the full recipe instead of a bare "not found".
Verified against realcargo build --releaseoutput in both directions.
Fixed
- Cargo publishes the profile-root
.dSYMas a symlink intodeps/, which
walkdirdoes not follow — combined with skippingdeps/, a correctly
configured macOS build would have been reported as missing its debug info and
advised to setsplit-debuginfo, which it already had.
Install bugsee-cli 0.7.4
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/bugsee/bugsee-cli/releases/download/v0.7.4/bugsee-cli-installer.sh | sh
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/bugsee/bugsee-cli/releases/download/v0.7.4/bugsee-cli-installer.ps1 | iex"
Install prebuilt binaries via Homebrew
brew install bugsee/tap/bugsee-cli
Install prebuilt binaries into your npm project
npm install @bugsee/bugsee-cli@0.7.4
Download bugsee-cli 0.7.4
| File | Platform | Checksum |
|---|---|---|
| bugsee-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| bugsee-cli-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| bugsee-cli-x86_64-pc-windows-msvc.zip | x64 Windows | checksum |
| bugsee-cli-aarch64-unknown-linux-gnu.tar.xz | ARM64 Linux | checksum |
| bugsee-cli-x86_64-unknown-linux-gnu.tar.xz | x64 Linux | checksum |