Skip to content

Connect to OhMy.xin

Got keystore.json and the Client Secret? Then this part takes about two minutes. Haven’t got them yet — start with Create a bot on Mixin.

The walkthrough below starts at the OhMy.xin half. Click any earlier step to see where each item came from.

Mixin DevelopersOhMy.xin
ohmy.xin/mx_apps/new
Mixin DevelopersScan with Mixin Messenger
What you take to OhMy.xin
Step 5 of 7

Click the glowing spot — in the browser or in the tray — or use Next.

The Connect step of the new-circle wizard

The real wizard, step 2.

  1. You are on step 2 of 3.
  2. Drop or paste keystore.json here, or use Choose file.
  3. Paste the Client Secret — it is not in the keystore.

If the bot has been connected to another circle before, that circle has to disconnect it first before you can connect it to a new one. Disconnecting doesn’t touch the bot on the Mixin side — reconnecting brings everything back.

“Invalid JSON — please paste the complete keystore.json content”

Only part of the file got pasted, or something else (often the Client Secret) went into the keystore box. Easiest fix: click Choose file and pick keystore.json instead of pasting. If you paste, copy everything from the first { to the last }.

“Missing fields: app_id, session_private_key, …”

The file is from an older-style session that uses different field names. On developers.mixin.one, open Secret → App Session → Generate a new key and use the new file.

Launch Bot fails with a credentials error

The keystore and the secret don’t belong together, or one of them was regenerated afterwards. Check they’re from the same bot, and use the newest secret and the newest keystore file.

“Auto-configuration needs a retry”

Your bot is saved — only the Mixin profile update didn’t finish, usually because Mixin was briefly unreachable. Click Retry auto-configuration. There’s nothing to change on developers.mixin.one, and retrying is safe.