Aniimo mobile login help: missing PC progress, downloads & support

Account restriction, missing character or connection error?

The official September 30 notice is an enforcement announcement, not evidence that every failed login is a ban. Identify the message you actually see before changing settings.

Our suggested support checklist is not a published appeal policy: use the official contact route, describe what happened and ask for the appropriate next step. No appeal deadline, response time or guaranteed outcome is established here. Keep passwords, verification codes and recovery codes out of reports and screenshots.

For the publisher’s account-sharing and boosting warning, see account safety before linking. Do not post your identifier or restriction screenshot in this fan site’s field notes.

Start with the symptom, not a reinstall

These checks are our support workflow, not a list of four officially confirmed mobile defects. Record what you see before changing settings.

Missing PC or console progress: verify three identities

The official mobile launch notice confirms cross-progression for the same account on the same server. Your device can change; the character’s server cannot be assumed to change with it.

1. On the device that still shows the character, record the server and character identifier.
2. Confirm the game account and linked provider used there. Typing an email for a verification code is not automatically the same account as pressing a third-party sign-in button.
3. On mobile, select the matching server and legitimate login method. If the expected method is unavailable, do not create a new account as a transfer workaround.
4. If the mismatch remains, contact official support with the two platforms and their account/server details. Do not post passwords, verification codes or full account identifiers publicly.

Consult the account continuity guide for existing Steam and console exceptions. This site cannot merge game accounts, move a character between servers or inspect your save.

The September 22 mobile FAQ now explains the general Link Email prompt for first-time third-party login. Use the email belonging to the existing game account or previous registration; verify the provider and server before continuing. One email may link multiple third-party platform accounts, but each third-party account can link to only one email. This is not a promise to merge duplicate accounts or transfer a character between servers.

The older September 15 reward notice discusses new users and specific existing-character exceptions. Its warning to seek support for character-preserving relinking still matters, but it should not replace the later general mobile instructions. Read the actual prompt; when two existing accounts or a prior skipped link are involved, stop and ask official support rather than assume a safe automatic merge.

Installation trouble is separate from account identity

Use the official App Store listing or Google Play listing. Follow the client’s actual resource prompts and compare your device with the minimum and recommended specifications.

The mobile FAQ asks for at least 18 GB of free storage and stable Wi-Fi. Free space and RAM are different requirements. An update or resource download is not proof that your character has been lost.

Do not apply PC-only DX11/DX12, Steam Input or launcher-repair instructions to the native phone app. We do not recommend unofficial APKs, certificates, security bypasses or deleting app data before account access is confirmed.

Download frozen at 0% or rolling backward

The September 22 mobile FAQ gives practical checks for this symptom. Confirm free storage, try another trusted Wi-Fi or mobile connection, and restart your router when appropriate. Prefer 5 GHz Wi-Fi if available and pause competing large downloads. Cellular downloads may use your data allowance.

If you personally configured a VPN, proxy, Private DNS or content blocker, it may affect the connection. Test one setting at a time only where permitted, note the original value, and restore it afterwards. Do not remove workplace security controls or disable a firewall indiscriminately. Reinstallation is a last resort, after you have verified the account and server holding your progress.

Old beta client, incompatible Android or excessive heat

The FAQ says earlier test clients are no longer usable; use the current official store client. This is not an instruction to erase the data of a working current installation. Android requires Vulkan 1.1 support as well as the other published specifications.

A 60 FPS option is enabled except on some lower-end devices, but it is not a guaranteed measured frame rate. The FAQ notes that higher frame rates can produce more heat; lower graphics quality or rendering scale when needed. Tablets use automatic large-screen mode with higher rendering scale, which can also be reduced to ease the load. No device benchmark is claimed here.

A passed opening time is not proof that every server is healthy

Mobile opening was September 23 at 02:00 UTC. A present error should not be dismissed as “preload only,” but the launch announcement also cannot prove the health of every server at the moment you read this.

Check the official announcement list, your current client version and the exact server selected. For a support report, note when the error occurred, its code or text, and whether it happens before or after character selection. Avoid repeated account changes while diagnosing a connection problem.

For network errors, the September 22 mobile FAQ also names iCloud Private Relay on iOS as a possible connection factor. A temporary, permitted comparison with the original setting recorded is different from permanently weakening device security. Connection-switching or restarting does not merge accounts.

Cross-region play can add latency, but an existing character does not migrate when you select a different server. Preserve the character’s server while diagnosing access; ask support before treating a new region as a progress-recovery method.

Missing rewards need their own eligibility check

Cross-progression and reward entitlement are different. The mobile announcement includes a cross-platform login reward, but does not establish an amount or deadline for every individual account. Use the event rules in your client instead of assuming that any second device unlocks every bonus.

Beta Sealed Egg claiming, a Bond Egg hatching condition and the new Home-level Prismana eggs are separate topics. See test-reward guidance and the version 1.1 preparation guide. Never delete an egg or character to test a claim.

The September 22 mobile FAQ and September 23 launch notice direct prior testers to the official Test Reward Redemption page. Sign in there with the account used for the test to inspect available rewards and archived Bonded Promise eggs. Portal availability does not guarantee that every archived egg or every individual account is eligible to claim again.

Send a useful report through official support

The mobile notice directs players to Menu → Support in the game, or its Customer Service Center. If you cannot reach the menu, start at the official launch notice rather than an unsolicited support message.

Include your platform, device model, OS, app version, server, approximate occurrence time, exact error and the steps that reproduce it. A screenshot should hide private account details. Support can assess account-specific problems; our fan site cannot recover characters.

Once access is working, continue exploring with the interactive Aniimo map and private catch planner. The embedded map’s collection is separate from your game account and from the planner stored in this browser.

Missing compensation: an appended notice describes two mails

The official Steam announcement index currently contains a follow-up under the older update-preview headline. It adds 500 Glimmers for the delayed launch to the original 500, and lists one Sparkling Cube for a known issue. It describes two mails: 1,000 Glimmers and one Sparkling Cube, to be sent after mailbox restoration.

This is a notice observed on September 25, not confirmation that the mailbox is still down or that every account has received the items. The follow-up’s precise edit date and delivery completion are not verified. The original maintenance eligibility was registration before the version 1.1 update; this is not a universal new-account reward, and the follow-up does not separately establish every account’s Cube eligibility.

Check the correct character/server and current official messages before reporting a missing mail. Keep maintenance compensation separate from beta Sealed Eggs, Home milestones and code redemption. Do not unlink accounts or enter credentials into a third-party claim form.