Skip to content

Run/Test Mode fails - git clone error on FlutterFlow's own dropdown_button2 dependency (exit code 69) #7460

Description

@maxdemarini-AnimalAlert

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Run Mode and Test Mode both fail consistently (multiple retries, fresh sessions) with: 'flutter pub get failed with exit code 69'. Build output shows: Git error. Command: git clone --mirror https://github.com/FlutterFlow/dropdown_button2.git / fatal: could not read Username for 'https://github.com': No such device or address / exit code: 128. The dropdown_button2 dependency (source: git) appears under Settings > Pubspec > FlutterFlow Pub Dependencies (not something I added manually) and is read-only from my side. Note: this looks similar to #7068, but different root cause — my Custom Pub Dependencies tab is empty (no custom deps with bad format), and the error is a git authentication failure ('could not read Username'), not a pubspec YAML syntax error.

Expected Behavior

Run/Test Mode should successfully fetch packages and load the app preview.

Steps to Reproduce

  1. Open the AnimalAlert project in FlutterFlow / 2. Click 'Run' (or 'Test Mode') to preview the app / 3. Package fetching starts, then fails with 'Error Getting Packages' / 'flutter pub get failed with exit code 69' / 4. Clicking 'Retry' reproduces the same error consistently, both from Run mode and from a completely fresh Test Mode session

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ol8nf5Yt1ofpE7arAdcBsnSQWOVM3ars3iMpOGDwbfaKvPIlzacjRTxFoOcOkTWxpKEWJmmc0peiMvfHuGPVcG0+aRrU5+qtyEgqWTk+/aoubCZa0P3N5L8BhGEiw0cG7oCZ+FM5oSCU9wHGmCtytST3fH4f7Zwh9f6PHaOI=

Visual documentation

Image Image

Environment

- FlutterFlow version: (Flutter SDK shown as 3.38.6 in error message)
- Platform: Web (also reproduced via FlutterFlow Desktop app)
- Browser name and version: Chrome (latest)
- Operating system and version affected: macOS Sequoia 15.7.9 (MacBook Pro 15-inch 2018, Intel)

Additional Information

This is blocking all testing before launch (target: January). The project itself has 0 errors in the Issues panel — confirmed via Activity Monitor that CPU usage stays idle during the failed build, ruling out a local hardware issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bugstatus: confirmedIssue has been reproduced and confirmed as a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions