Use FiatEx
When something does not work
Check the failure before retrying a transaction or uploading the same file again.
Launch or swap is disabled
In the current release, contracts are not deployed, so those actions are deliberately unavailable. Connecting a wallet does not remove that gate. Once deployment is active, the app also checks the network, matching API configuration, quote, inputs, and wallet state.
If a deployment mismatch appears, do not bypass it by calling an address copied from a message. Confirm the release configuration first.
The price is missing or the swap reverted
A current quote needs a working RPC, supported asset, sufficient route liquidity, and valid amounts. A buy simulation also needs the matching native value. Refresh the quote, check your gas balance, and try a smaller amount if price impact is high.
An expired deadline or minimum-output failure means the transaction did not meet the signed limits. Check the receipt before resubmitting. Increasing slippage changes the protection you accept; it is not a general error fix.
The token or milestone has not appeared
A successful receipt can arrive before indexing finishes. Retry the asset address after a short delay. If the receipt failed, no launch should appear. Names and tickers can repeat, so search by the correct address.
A displayed reserve valuation above target does not always mean the milestone has been recorded. After an external route settles, an eligible checkpoint or the next token buy records it.
The image will not upload
Check that the file is a non-animated PNG, JPEG, or WebP within the size and dimension limits. Enter the token name and ticker, then accept public-upload consent. If you change the identity after uploading, publish the metadata again.
A configuration message means uploads are disabled server-side. A rate-limit message means wait before retrying. A partial pinning failure can leave the image public even though the metadata did not finish.
Fees are queued but nothing has burned
A queue is only the first step. Execution needs sufficient price history, the cooldown to expire, acceptable pricing, a positive reserve-based budget, and a caller paying gas. The keeper can also be stopped, unfunded, or waiting on an unresolved transaction.
Look for a BuybackExecuted receipt and the burn history rather than assuming the queue should disappear on a fixed schedule.