From 90544316bf2d752bf324bc43662cd31b3b2c78db Mon Sep 17 00:00:00 2001 From: Vladyslav Dalechyn Date: Thu, 25 Jul 2024 23:27:49 +0300 Subject: [PATCH] fix: check for `prop` in `intent` (#444) This is quite a mysterious bug since it cannot be reproduced locally, and is only reproduced on Vercel/Next.js Platforms. I assume that some sort of build caching is being made and previous fixes didn't come through, thus trying now with this one. --- src/utils/getButtonValues.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/utils/getButtonValues.ts b/src/utils/getButtonValues.ts index 4d20c9bb..b584a279 100644 --- a/src/utils/getButtonValues.ts +++ b/src/utils/getButtonValues.ts @@ -8,7 +8,7 @@ export function getButtonValues( const buttonValues: FrameButtonValue[] = [] for (const intent of intents) { - if (!intent) continue + if (!intent || !('props' in intent)) continue const { property } = intent.props if (!(property as string).match(/^fc:frame:button:(1|2|3|4)$/)) continue buttonValues.push(intent.props['data-value'])