MS Graph API file replace SharePoint ReactJS 404 item not found or stream issue

I am trying to use the MS Graph API and ReactJS to download a file from SharePoint and then replace the file. I have managed the download part after using the @microsoft.graph.downloadUrl value. Here is the code that gets me the XML document from SharePoint.

export async function getDriveFileList(accessToken,siteId,driveId,fileName) {
  const client = getAuthenticatedClient(accessToken);
  //https://graph.microsoft.com/v1.0/sites/{site-id}/drives/{drive-id}/root:/{item-path}
  const files = await client
    .api('/sites/' + siteId + '/drives/' + driveId + '/root:/' + fileName)
    .select('id,name,webUrl,content.downloadUrl')
    .orderby('name')
    .get();
  //console.log(files['@microsoft.graph.downloadUrl']);
  return files;
}

When attempting to upload the same file back up I get a 404 itemNotFounderror return. Because this user was able to get it to work I think I have the MS Graph API correct, although I am not sure I'm translating correctly to ReactJS syntax. Even though the error message says item not found I think MS Graph might actually be upset with how I'm sending the XML file back. The Microsoft documentation for updating an existing file state the contents of the file in a stream should be returned. Since I've loaded the XML file into the state I'm not entirely sure how to send it back. The closest match I found involved converting a PDF to a blob so I tried that.

export async function putDriveFile(accessToken,siteId,itemId,xmldoc) {
  const client = getAuthenticatedClient(accessToken);
  // /sites/{site-id}/drive/items/{item-id}/content
  let url = '/sites/' + siteId + '/drive/items/' + itemId + '/content';
  var convertedFile = null;
  try{
    convertedFile = new Blob(
        [xmldoc],
        {type: 'text/xml'});
  }
  catch(err) {
    console.log(err);
  }
  const file = await client
    .api(url)
    .put(convertedFile);
  console.log(file);
  return file;
}

I'm pretty sure it's the way I'm sending the file back but the Graph API has some bugs so I can't entirely be sure. I was convinced I was getting the correct ID of the drive item but I've seen where the site ID syntax can be different with the Graph API so maybe it is the item ID.