[Bug]: `bal pull` fails with 'Given bala path does not exist' when proxy central repository is enabled

[Thevakumar-Luheerathan]

Description

When the proxy central repository is enabled, running bal pull ballerina/http followed by bal pull ballerina/io causes the second command to fail with the following error:

Package already exists.

ballerina: error occurred while resolving dependencies, reason: Given bala path does not exist: /Users/luheerathan/.ballerina/repositories/central.ballerina.io/bala/ballerina/io/1.8.0/java11

The tool reports that the package already exists but then immediately fails because the expected bala path (java11 platform directory) is not found. This is inconsistent — the tool should not report "Package already exists" and then fail to resolve it.

Steps to Reproduce

1. Enable the proxy central repository in Ballerina settings.
2. Run bal pull ballerina/http — succeeds.
3. Run bal pull ballerina/io

Expected behavior: Package is pulled successfully or a clear "already up-to-date" message is shown.

Actual output:

Package already exists.

ballerina: error occurred while resolving dependencies, reason: Given bala path does not exist: /Users/luheerathan/.ballerina/repositories/central.ballerina.io/bala/ballerina/io/1.8.0/java11

Affected Version(s)

2201.13.3 (Swan Lake Update 13)

OS, DB, other environment details and versions

• OS: macOS (Darwin 25.3.0, Apple Silicon / aarch64)
• Ballerina: 2201.13.3 (Swan Lake Update 13)
• Language specification: 2024R1
• Update Tool: 1.5.1

Related area

-> Central

Suggested label(s) (optional)

Area/Central, Type/Bug

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.