Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[bug]: upload symbols fails with Flutter 3.44 because the SourcePackages have moved

Aperta
  • Qualcosa non va?
#443 18 commenti 12 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
dart, firebase
Ambito
cli

Direzione di ricerca

Riproduci il problema con un progetto Flutter 3.44 pulito, quindi individua il punto di ingresso che invoca SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run di Firebase Crashlytics e risolve DERIVED_DATA_PATH. Verifica la gestione del percorso rispetto alla posizione di BUILD_ROOT e conferma che una build iOS carichi correttamente i simboli.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug Needs Attention triage
Is there an existing issue for this?
  • I have searched the existing issues.
CLI Version

1.3.2

Firebase Tools version

15.18.0

Flutter Doctor Output

[✓] Flutter (Channel stable, 3.44.0, on macOS 26.5 25F71 darwin-arm64, locale de-DE) [301ms]
• Flutter version 3.44.0 on channel stable at /Users/xxx/sdk/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 559ffa3f75 (6 days ago), 2026-05-15 14:13:13 -0700
• Engine revision 4c525dac5e
• Dart version 3.12.0
• DevTools version 2.57.0
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets,
enable-swift-package-manager, omit-legacy-version-file, enable-lldb-debugging, enable-uiscene-migration

[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0) [1.360ms]
• Android SDK at /Users/xxx/sdk/android
• Emulator version 36.5.11.0 (build_id 15261927) (CL:N/A)
• Platform android-36.1, build-tools 36.1.0
• ANDROID_HOME = /Users/xxx/sdk/android
• ANDROID_SDK_ROOT = /Users/xxx/sdk/android
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: flutter config --jdk-dir="path/to/jdk".
• Java version OpenJDK Runtime Environment (build 21.0.10+-117844308-b1163.108)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 26.4.1) [1.508ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 17E202
• CocoaPods version 1.16.2

[✓] Chrome - develop for the web [4ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Network resources [185ms]
• All expected network resources are available.

• No issues found!

Description

The build fails because with flutter 3.44, the SourcePackages are no longer at DERIVED_DATA_PATH, but at BUILD_ROOT.

Trying to build a clean project produces the following error:

Unhandled exception:
    ProcessException: No such file or directory
      Command:
      /Users/XXX/Library/Developer/Xcode/DerivedData/Runner-asnmalsvsfbtamfmomnltzgnmkzh/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run --validate --flutter-project .../app_id_file.json

Checking the derived data directory reveals there is no SourcePackages directory:

Image

However, checking the build/ios dir reveales it has moved there:

Image
Steps to reproduce
  1. Create a new flutter project with firebase_crashlytics or run flutter clean on an existing one (as otherwise the SourcePackages might still exist from previous builds)
  2. Build the project.
Expected behavior

It uploads the symbols correctly.

Screenshots

See Description

Additional context and comments

No response

Lingua principale
Dart
Stelle
194
Fork
76
Merge medio
2g 9h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di invertase/flutterfire_cli

Tutte le issue di invertase/flutterfire_cli

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.