Troubleshooting

Can't sign in after registrationCopy Anchor Link

New accounts must verify their email before signing in. Open the verification link, then sign in with your email and password. The dashboard does not offer Google sign-in.

Verification links expire after one hour. Check spam, then open the resend page, enter the address you registered and select Send a new link. Wait for the cooldown before requesting another link.

Forgot your passwordCopy Anchor Link

Select Forgot password? on the sign-in page, enter your email and select Send reset link. The email contains a link to set a new password. After saving it, sign in with the new password.

Unable to load your accountCopy Anchor Link

Select Try again on the error screen. If the problem continues, select Sign out, then sign in again. An account-loading failure does not prove that your account was deleted.

A list is empty or out of dateCopy Anchor Link

If the page shows an Unable to load error, select Try again before treating the list as empty.

Showing the last loaded data. It may be out of date. means the visible rows are from an earlier successful load. Wait for a successful refresh before deciding whether a recent change saved.

Project or request is missingCopy Anchor Link

1. Check the account under Settings and open the intended app under Apps.
2. In the app's Requests tab, clear the search box and expand Done and Declined, which start collapsed. Pending requests appear in this list too, marked with a pending icon.
3. In Requests, check the selected app and the search box, and expand Done and Declined. Requests shows approved requests only. Use Inbox to review pending ones.
4. For a request missing from the mobile app, check approval and visibility. Pending requests are normally visible only to their submitter, and Declined requests stay hidden from the normal list.

An app's Requests tab shows up to the 200 most recent requests. When the app has more, it says Showing the 200 most recent of 250 requests., with your app's numbers. Inbox checks the 50 most recent requests across your apps and lists the pending ones among them. To find an older pending request, open its app. These views do not have a next-page control. A request missing from the displayed rows has not necessarily been deleted.

An action failed or timed outCopy Anchor Link

Before repeating a create, reply, or other update, refresh and inspect the relevant app, request, or comments. The change may have saved even if its confirmation did not reach you.

When you move several requests at once, each one is a separate update. A message such as 2 of 5 requests could not be moved means some succeeded. Check each selected request's resulting status and retry only the requests that still need the change.

For a payment with an unknown result, do not pay again. Follow Payment is not confirmed.

New app or branding controls are unavailableCopy Anchor Link

The hosted service requires lifetime access before app creation and before hiding the branding. Without it, Apps shows Get lifetime access instead of New app, and the Featurama branding switch stays locked. First check for a billing loading error and use Try again if offered.

If the account already has lifetime access, do not buy again because a control is temporarily unavailable. See Unlock hosted lifetime access.

Mobile API key is rejectedCopy Anchor Link

Ask your developer to check that the mobile app uses the full project API key from the same Featurama instance as its configured API address. A key prefix alone cannot connect the app. An agent token doesn't work as an API key.

If the key was regenerated, the old key stopped working immediately. Update the affected integrations with the new key. Existing full keys cannot be recovered from the dashboard. See API key settings and SDK setup.

Votes, comments, and emailCopy Anchor Link

A new request already has its creator's vote, but further voting requires approval. Review the request in Inbox first.

If a mobile submission requires an email address, provide a valid address in its form or review the app's Ask for email setting. Required is enforced when the request is submitted.

A developer reply is a comment that users see in the app. If the request has an email address, Featurama also emails the reply and status changes to that address, unless the user unsubscribed. Approval without a status change does not email the submitter. Notifications to the app owner about new SDK submissions are best-effort. Check Inbox even if no email arrives.

User did not get a reply emailCopy Anchor Link

1. Open the request and check the Email row. Not provided means Featurama had no address to send to. Unsubscribed next to the address means the user used the unsubscribe link in an earlier email, so they get no reply or status emails from that app. In both cases the reply is still visible in the app.
2. Check that your reply appears under Comments with a Developer badge. Comments from other users do not send reply notifications. Status changes send a separate notification.
3. Ask the user to check their spam folder for the request title. The subject also contains the current status in the app's selected email language.

Featurama sends each reply email once, in the background, after saving the reply. It does not retry a failed email, and the reply stays saved either way. Reply posted. The user gets an email. confirms the saved reply and the stored address, not delivery. Sending also requires email to be set up on the Featurama instance.

To reach the user another way, select the address in the Email row to write from your own email app. See Reply emails.

npx featurama runs the wrong programCopy Anchor Link

Use the scoped package and commands in CLI agent setup. The unscoped npm package named featurama belongs to an unrelated project.

CLI cannot find an instanceCopy Anchor Link

Follow Multiple instances to check the active context and API origin. A dashboard URL or a URL ending in /mcp is not the API origin expected by the CLI.

CLI login or MCP verification failsCopy Anchor Link

Use an agent token from the same instance, not an app's API key. Follow CLI agent setup or MCP access to check authentication without creating an app.

Do not paste a token or the CLI configuration file into a support message. The configuration can contain plaintext tokens.