You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've run into an issue where the redirection from /pay/index.tsx to /pay/success.tsx is causing duplicate Payment Intents.
For some reason lost in time, I decided that I would use a client-side payment submission instead of the action-based one in the repo, but it's possible that the repo will also exhibit the same behaviour.
Because both /routes/pay/index.tsx and /routes/pay/success.tsx live underneath the loader in /routes/pay.tsx, each time one of them is visited, the pay.tsx loader creates a new intent.
I solved this by moving /routes/pay/success.tsx to /routes/pay.success.tsx, and I thought it might be worth an update to the tutorial
The text was updated successfully, but these errors were encountered:
Hi @charliematters, thanks for the solution, I'm not experienced using Remix, can I ask you what is the difference between as it is now and the change that you suggested? Why they are working different
I've run into an issue where the redirection from
/pay/index.tsx
to/pay/success.tsx
is causing duplicate Payment Intents.For some reason lost in time, I decided that I would use a client-side payment submission instead of the action-based one in the repo, but it's possible that the repo will also exhibit the same behaviour.
Because both
/routes/pay/index.tsx
and/routes/pay/success.tsx
live underneath the loader in/routes/pay.tsx
, each time one of them is visited, thepay.tsx
loader creates a new intent.I solved this by moving
/routes/pay/success.tsx
to/routes/pay.success.tsx
, and I thought it might be worth an update to the tutorialThe text was updated successfully, but these errors were encountered: