Transaction failure when triggering claim page allowlists via mobile scripts?

Hey everyone, I’m running into a bit of a wall with a custom claim page I set up on my Manifold creator contract. I’m trying to test the user experience for a mobile-first drop I have coming up, but I’m experiencing consistent “Transaction Failed” errors when the mint request is triggered through a specific mobile environment.

I’ve been using https://deltaexector.com/ as a testing ground to see how my contract handles high-frequency calls and automated allowlist verification on iOS. It seems like the signature request isn’t popping up correctly in the wallet when the call is initiated through the executor’s internal browser, or perhaps there’s a timeout issue with the Manifold API because the script is executing too quickly for the mempool to catch up.

Has anyone else here experimented with using mobile-based executors or automation scripts to verify their claim pages? I’m trying to determine if I need to adjust the gas limit in my contract settings or if the Manifold “Claim App” has a built-in rate limit that blocks rapid-fire requests from the same IP. I’m worried that if my collectors use any kind of automation to snag their spots, they’ll just end up with failed transactions and high gas fees. I’d love to hear if any other devs have dealt with script-based interference or if there’s a way to make the allowlist handshake more resilient for these kinds of mobile setups!

Hey! Thanks for reporting this. To help us dig into what’s going on, could you share a bit more context?

  • Which Manifold mint page is this? Drop us the link if you can.
  • How did you set up the claim page / allowlists? Please walk us through the steps you took, did you use the Manifold Studio UI?
  • What’s the project? A quick overview of what you’re working on and how you are incorporating the Manifold drop would help.
  • What exactly happens on mobile? Are you seeing a specific error message, or does the transaction just silently fail? Which wallet/browser are you using on mobile?

The more detail you can give us, the faster we can narrow down whether this is a config issue or a bug on our end.