Conversation
✅ Deploy Preview for superhero-trendminer-har2sa45a90zw62 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for celadon-youtiao-c85d92 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for superhero-c9df18 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
CedrikNikita
force-pushed
the
hotfix/fix-sdk-migration-leftovers
branch
from
b97459b to
45f210e
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| setSuccessMessage(undefined); | ||
|
|
||
| try { | ||
| const account = new MemoryAccount(invitationCode); |
There was a problem hiding this comment.
Missing user-friendly error handler for secret key normalization
Low Severity
The getInvitationRewardAmount function now calls normalizeSecretKey (line 72) but its catch block lacks the "Secret key" error handler that was added to the claimOrRevokeReward catch block (line 159). When normalizeSecretKey throws in getInvitationRewardAmount, users see a raw technical message like "Secret key has invalid hex format" instead of the friendlier "This invite link uses an unsupported or corrupted secret key format."
Additional Locations (1)
1 participant
Note
Medium Risk
Touches contract initialization and signing paths used for invitation claiming/revoking and sponsored profile transactions; mistakes could break on-chain interactions across networks.
Overview
Completes the aepp-sdk v14 migration by adding
ensureSdkInitializeContractand routing contract creation through a compatibilityinitializeContractshim, then applying it across community factory/affiliation initialization andcreateCommunity.Introduces
normalizeSecretKeyto accept legacy/hex secret formats and consistently producesk_secrets, updating invitation link generation, invitation claim/revoke flows, andpayForProfileTxpayer key handling; invitation claiming now uses the typed contract method (redeem_invitation_code) with explicitonAccountand adds a clearer error for invalid/corrupted invite keys.Written by Cursor Bugbot for commit 45f210e. This will update automatically on new commits. Configure here.