APPSINITYGuides and support
Common errors
These strings come from the shipped code, not from a guess list. Find yours in the table, apply the fix, and if nothing matches, the message text is exactly what support needs.
Open Appsinity StudioOn this pageSign-in and sessionUploadsSigning and releasesListing and storeDesktop client and downloadsFrequently asked questions
Sign-in and session
| You see | It means | Fix |
|---|---|---|
| Email or password is incorrect | Either half is wrong; deliberately indistinguishable | Check the address first, then reset |
| Sign in again first | No bearer header reached the API | Sign in; confirm the request sends Authorization |
| Invalid session | Token present but failed verification | Log out and back in; the token is thirty days old at most |
| Code expired. Please request a new one. | The OTP is past ten minutes | Resend and paste it promptly |
| Invalid verification code | Digits wrong, or an older mail's code | Use the newest email only |
| Password must be at least 6 characters | Registration input | Six or more |
| An account with this email already exists | Address taken | Sign in or reset |
| Signing in loops after a refresh | Token cleared or expired mid-session | Complete the OTP step; a hard refresh first |
| Stale dashboard behaviour after an update | Cached bundle | Hard refresh; store HTML can be edge-cached a day |
Watch out: There is no server-side revocation. If you suspect a token leaked, change the password and sign out on every machine you used; the outstanding token still lives out its thirty days.
Uploads
| You see | It means | Fix |
|---|---|---|
| Sign in again before uploading. | No token in local storage when the sheet opened | Re-authenticate, then retry the file |
| File too large (X GB). Max 5.00 GB. | The browser client's ceiling check | Split assets or rebuild lighter |
| Blocked file type: .exe | The extension is denied outright | Package it in a ZIP |
| Presign API failed (401). | Worker rejected the session | Sign in again |
| Presign API failed (400). | Payload missing gameId or appId | Upload from the correct listing |
| File is too large for this upload category. | Worker-side ceiling, authoritative | app-media is 250 MiB, not 5 GiB |
| App media must be an image or MP4 video. | Wrong media extension | png, jpg, jpeg, webp or mp4 |
| Game web uploads cannot be APK or AAB files. | Android binary in the web sheet | Use the build category |
| Progress bar starts and never moves | The presigned PUT is blocked in flight | Large PUTs are commonly killed by a corporate proxy |
| Upload succeeds, URL 404s | The stored URL is missing /public/ | Rebuild the URL as storage.appsinity.com/public/<key> |
| Direct MinIO PUT failed (503). | Object storage unavailable | Back off and retry; the presign is still valid |
Note: The signed PUT lasts three hours. A file that fails near the end is usually an expired URL, and a fresh presign is cheap; do not retry the old one.
Signing and releases
| You see | It means | Fix |
|---|---|---|
| Failed to fetch when you press Sign | The synchronous call crossed the gateway's sixty-second timeout | The job usually finished; poll the listing for signingStatus |
| A 504 on the sign request | Same event with a real status code | Do not resubmit; wait and re-read |
| Signing never starts | Only .aab and .apk are eligible | A ZIP or web build has nothing to sign |
| App id required | The build route got no identifier | Send it from the listing's own sheet |
| App not found | Wrong identifier or a deleted listing | Check the slug |
| A version shows unsigned after a while | The signer polls every thirty seconds and may have failed on that object | Re-trigger once, then report with the object key |
| Installed build cannot upgrade in place | Version code did not increase | Bump it in the build, not in Studio |
Watch out: A timed-out request and a failed request look identical in the browser. The listing record is the truth, so always confirm state before re-signing.
Listing and store
| You see | It means | Fix |
|---|---|---|
| Checklist row reads Not started | Required fields for that section are missing | Privacy needs a policy URL and both attestations |
| Listing saved but nothing appears in search | Status is not published | Or it is still a pre-registration row |
| Download button greyed out | Downloads are disabled or the target does not match the visitor | Check the platform targets |
| Will not install on your device | An Android-only listing opened from desktop | Add a web or desktop target, or accept the label |
| Age badge shows 3+ you never chose | No content declaration exists | Complete the rating form |
| This domain is already connected to another page. | A custom domain collision | Disconnect it from the other page first |
| Only the workspace owner can manage members | You are not the owner | Ask the owner to invite |
| You cannot invite yourself | Invite address equals your address | Invite a different email |
| Analytics show nothing after launch | Events need traffic | Confirm your own view was recorded as a visit |
Not available: A listing that is correct but invisible is almost always a status problem, not a caching problem. Read the status field first, see Store visibility and status.
Desktop client and downloads
| You see | It means | Fix |
|---|---|---|
| A game will not launch from the library | The installed directory is corrupt or incomplete | Delete %LOCALAPPDATA%\Appsinity\library\<slug> and reinstall |
| Installer runs, game absent | The release was an installer-only archive | Ship the game directory inside the ZIP |
| The client is still in the tray after Close | Close hides to tray by design | Quit from the tray icon |
| A Windows download link 404s | The published file name carries a version | Point at the real object key, not a generic name |
| No 32-bit installer exists | Only the current Electron target is built | Ship the 64-bit release |
Note: The client browses the store; it never publishes. Someone saying they cannot upload "from the Studio app" means the browser dashboard, see Desktop client.
Frequently asked questions
My error is not in these tables.
Copy the exact sentence, the endpoint or screen, and the listing identifier, then send it to support. These strings are unique enough to trace.
Should I retry a failed upload?
Re-presign first and retry once. Retrying the same signed URL after an expiry or a 503 is what turns one failure into ten.
Why does the same message appear for wrong email and wrong password?
Deliberately. Distinguishing them turns the login form into an address verifier.
Is there a status page?
No. There is no incident feed and no uptime page; a platform-wide problem is discovered through support volume.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]