Philip Gichuhi

Hi @Mohanavalli-A, thanks for reaching out. Could you please share what version of the SDK you're using and sample code you're using to make the two requests? (Just the `graphClient....`...

Hi @Mohanavalli-A Unfortunately, we're only providing active support for version 6.x of this SDK and security fixes only for 5.x. I would recommend upgrading if you can. Here's an [upgrade...

My apologies for this experience @susanYYT As I try to reproduce this, you can add [`microsoft-kiota-abstractions`](https://central.sonatype.com/artifact/com.microsoft.kiota/microsoft-kiota-abstractions) as a direct dependency and let me know if this unblocks you. Thank you...

@susanYYT To get sites by URL: `Site site = graphClient.sites().bySiteId(sitePath).get();` should work with the sitePath being "{hostname}:/{server-relative-path}" Similarly for Drives: use `graphClient.drives().byDriveId("driveId").items().byDriveItemId("itemPath").get()` with itemPath as `root:/{relative path}:` (with trailing colon)

Thank you for the detailed issue @skattekristian. We will prioritize looking into this. At first glance, it seems like an issue on the API side that we may need to...

Hi @qiurunxing Thanks for raising this issue and the detailed logs. This seems to be a change on the API side causing this and not a change on the SDK....

@qiurunxing created the [issue](https://learn.microsoft.com/en-us/answers/questions/1691132/large-file-upload-to-onedrive-now-fails-for-some-a) on Q&A for you. You'd need to sign-in and `follow question` to get updates and respond to any follow-up questions from the support team.

@qiurunxing I'm not sure why it's been taken down. But yes, you can create the issue yourself so that you get notified about responses and requests for more info.

Thank you for pointing this out @DamianNowak5f. An alternative work-around is to set the requestAdapter property to `null` or initialize a `GraphServiceClient` with an `AnonymousAuthenticationProvider`. Adding this to our backlog...

@SashaUsov this will need to be prioritized against other issues. For now, it's likely that it won't make it into the next release. I'm also unable to reproduce the behaviour...