Troubleshoot common issues

Troubleshooting confusing scenarios while developing and shipping Pear applications.

Looking for peer-to-peer building-block issues instead? See P2P's troubleshooting guide. Looking for Bare runtime issues? See Bare's troubleshooting guide.

✖ Unexpected argument '<value>'

Pear does not recognize the command or subcommand you typed, so it reports the word as a stray argument. Check the spelling, then run pear help to list the commands your version has. Commands have been removed or renamed across the v3 releases. For example, pear init is gone, and pear blind-peer identity is now pear identity blind-peer-client. The CLI reference lists what was removed and what replaced it.

On Pear 3.5.0 and earlier the same failure reads ✖ Unrecognized Argument at index <n> with value <value>.

A valid pear link must be specified. on a quoted link

On Pear 3.5.0 and earlier, a link wrapped in quotes is rejected with this message, because the quote characters are read as part of the link. It happens when a shell or CI system passes the quotes through literally, and when you paste a link along with its quotes. Remove the quotes, or upgrade to Pear 3.6.0 or later, which strips one matching pair of quotes before it parses a link. The CLI reference describes this in its Quoting links section.

If you see the message on 3.6.0 or later, the link itself is malformed. It should look like pear://<key>, and any quotes around it have to match.

The terminal misbehaves after Ctrl+C at a confirmation prompt

On Pear 3.5.0 and earlier, pressing Ctrl+C at a typed confirmation prompt, such as STAGE in pear stage or CLEAR in pear gc cores, could leave the terminal unresponsive or stuck in raw mode, where what you type no longer echoes. Run reset on macOS or Linux, or open a new terminal, to get it back. Pear 3.6.0 and later restore the terminal when you interrupt a prompt.