Fix body reading in logging middleware for non-JSON responses

The logging middleware was calling response.json() and falling back to
response.text() on the same cloned response. This fails when json()
fails to parse (e.g., HTML error pages from Cloudflare) because json()
consumes the body stream even when parsing fails.

Fix: Read as text() first, then try JSON.parse() on the string. This
only consumes the body once and handles non-JSON responses correctly.

Author: clavery

packages/b2c-tooling-sdk/src/clients/middleware.ts

@@ -165,10 +165,14 @@ export function createLoggingMiddleware(config?: string | LoggingMiddlewareConfi
 
       const clonedResponse = response.clone();
       let responseBody: unknown;
+      // Read as text first, then try to parse as JSON.
+      // This avoids a bug where json() consumes the body stream even when parsing fails,
+      // making subsequent text() calls fail with "Body has already been read".
+      const text = await clonedResponse.text();
       try {
-        responseBody = await clonedResponse.json();
+        responseBody = JSON.parse(text);
       } catch {
-        responseBody = await clonedResponse.text();
+        responseBody = text;
       }
 
       // Mask sensitive/large body keys before logging