From f7a420300395b19c1f249859ada3533e8089a4df Mon Sep 17 00:00:00 2001
From: dangered wolf <d@ngeredwolf.me>
Date: Fri, 15 Jul 2022 16:36:24 -0400
Subject: [PATCH] Handle invalid API responses better

---
 src/fetch.ts | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/src/fetch.ts b/src/fetch.ts
index da4afd6..db2f1af 100644
--- a/src/fetch.ts
+++ b/src/fetch.ts
@@ -55,15 +55,24 @@ export const fetchUsingGuest = async (status: string): Promise<TimelineBlobParti
 
     /* We pretend to be the Twitter Web App as closely as possible,
       so we use twitter.com/i/api/2 instead of api.twitter.com/2 */
-    const conversation = (await (
-      await fetch(
+    let conversation: TimelineBlobPartial;
+    let apiRequest;
+    
+    try {
+      apiRequest = await fetch(
         `${Constants.TWITTER_ROOT}/i/api/2/timeline/conversation/${status}.json?${Constants.GUEST_FETCH_PARAMETERS}`,
         {
           method: 'GET',
           headers: headers
         }
       )
-    ).json()) as TimelineBlobPartial;
+      conversation = (await apiRequest.json());
+    } catch(e: any) {
+      /* We'll usually only hit this if we get an invalid response from Twitter.
+         It's rare, but it happens */
+      console.error('Unknown error while fetching conversation from API');
+      continue;
+    }
 
     if (
       typeof conversation.globalObjects === 'undefined' &&