List.GetCheckedOutFiles API Returns Duplicate Site Path

[gitpk-0]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

No response

Describe the bug / error

The GetCheckedOutFiles() API method returns incorrect ServerRelativePath values with duplicated site paths for checked-out files.

The API returns a malformed path with the site segment duplicated:

<d:DecodedUrl>/sites/site-name/sites/site-name/Shared Documents/example-file.png</d:DecodedUrl>

The site path /sites/site-name appears twice consecutively, making the path invalid and unusable without manual correction.

Steps to reproduce

1. Upload a new file to any document library on a SharePoint Online site

2. Do NOT check in the file (leave it in checked-out state with no version)

3. Call the REST API endpoint:
   https://tenant.sharepoint.com/sites/site-name/_api/web/lists/getbytitle('Shared Documents')/GetCheckedOutFiles

4. Observe the ServerRelativePath.DecodedUrl values contain duplicate site paths

Expected behavior

For files with no checked-in version, the API should return the correct server-relative path:

<d:DecodedUrl>/sites/site-name/Shared Documents/example-file.png</d:DecodedUrl>

This path should be directly usable for:

• Constructing file URLs
• Making subsequent API calls
• Path-based file operations

[Ashlesha-MSFT]

Hello @gitpk-0,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@gitpk-0,
We tried reproducing issue by uploading a file and leaving it checked out (no check-in or version),

However, the GetCheckedOutFiles() API continues to return an empty feed.
Are there any specific conditions or steps we might be missing to trigger this behavior?
Also, have you tried reproducing it on another tenant or with a different document library?

Appreciate your guidance on this.

[gitpk-0]

@Ashlesha-MSFT Thank you for investigating. You will also need to enable "Require Check Out" in the library settings.

1. Document Library > Settings > Versioning settings > Require Check Out
2. Upload a new file to the library (the new file will automatically be checked out due to the setting above)

As for testing scope -- Yes, extensively tested:

• Multiple document libraries in same site (Shared Documents, custom libraries)
• Two separate developer tenants (E5 trial tenants)
• One GCC High tenant (government cloud)
• Reproducible in all environments

[Ashlesha-MSFT]

@gitpk-0,
Thank you for your help in checking the settings and for your input throughout the investigation.

We were able to reproduce the issue with the duplicated site path in the GetCheckedOutFiles() API response. We will log this as a bug, and our engineering team will be looking into it further.