forcedotcom / forcedotcom/dataloader

Release tags not matching source?

Open
#1,617 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
541
Forks
312
PR merge metrics
No merged PRs in 30d

Description

I am investigating an issue using Data Loader v64.0.2.

During the investigation, I uncovered inconsistencies between the release tags applied to the source code and the actual code used in the release.

This stack trace from v64.0.2 logs reveals the problem:
2025-07-15 09:58:04,923 INFO [main] action.OperationInfoUIHelper instantiateWizard (OperationInfoUIHelper.java:113) - Instantiating wizard: extract
2025-07-15 09:58:09,519 INFO [Thread-2] oauth.OAuthFlowHandler handleOAuthLogin (OAuthFlowHandler.java:71) - Starting OAuth flow
2025-07-15 09:58:09,519 INFO [Thread-2] oauth.OAuthFlowHandler handleOAuthLogin (OAuthFlowHandler.java:84) - Checking if PKCE flow is enabled in Connected App...
2025-07-15 09:58:09,805 INFO [Thread-2] oauth.OAuthFlowHandler isPkceFlowEnabled (OAuthFlowHandler.java:298) - PKCE pre-flight error response: {"error":"invalid_grant","error_description":"invalid authorization code"}
2025-07-15 09:58:09,810 INFO [Thread-2] oauth.OAuthFlowHandler isPkceFlowEnabled (OAuthFlowHandler.java:300) - PKCE pre-flight full response:
2025-07-15 09:58:09,810 WARN [Thread-2] **_oauth.OAuthFlowHandler isFlowEnabledFromError (OAuthFlowHandler.java:401) - OAuth flow pre-flight check received_** 'invalid_grant: invalid authorization code'. This may indicate missing OAuth scope (e.g., refresh_token) or other misconfiguration in the Connected App.

Viewing the Code in Github, tag 64.0.2, for the file "src/main/java/com/salesforce/dataloader/oauth/OAuthFlowHandler.java" line 401 reveals that no such logging statement is present!
It appears this line was present in Commit 214b0066f43d8c7ec04a5ef33e82850eccd298c7, but not actually in 64.0.2.

From the looks of it, I think the bug I was investigating would actually be fixed if the source code tagged by 64.0.2 was actually used to build the release, but that doesn't seem to be the case?

I think the Data Loader release/tagging process might need to be scrutinized.
Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.