Skip to content

Commit a9eef29

Browse files
committed
added async to switch statement
1 parent 186c25e commit a9eef29

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

docs/mini-apps/core-concepts/notifications.mdx

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ You will receive webhook events when users enable or disable notifications for y
1919
<Info>
2020
Notification tokens are unique to each client app. This means a user can have separate notification preferences for your Mini App across different clients (e.g., Farcaster, the Base app). Removing your Mini App in one client does not affect its status in other clients.
2121
</Info>
22+
2223
</Panel>
2324
## Implementation
2425
<Steps>
@@ -141,7 +142,17 @@ Notification tokens are unique to each client app. This means a user can have se
141142
Use the `addMiniApp()` hook to prompt users to add your Mini App
142143

143144
<Warning>
144-
Webhooks must respond within 10 seconds to avoid timeouts from the Base app. If you encounter a "Failed to add mini app" error, your webhook may be taking too long to respond.
145+
**Important: Webhook Response Timing**
146+
147+
Webhooks must respond within 10 seconds to avoid timeouts from the Base app. If you encounter a "Failed to add mini app" error, your webhook may be taking too long to respond.
148+
149+
Different client apps handle webhook responses differently:
150+
151+
**Farcaster app**: Does not wait for webhook responses and does not require a success response to activate notification tokens
152+
153+
**Base app**: Waits for the webhook to return a success response before activating the notification token.
154+
155+
This means if your webhook processes token saving and sends notifications synchronously before returning a response, tokens may work on Farcaster but fail to activate on Base app.
145156
</Warning>
146157

147158
```tsx page.tsx highlight={11, 25-27}

0 commit comments

Comments
 (0)