API Key page not found

Bug report

Hello.
I’m currently developing a theme for Inkdrop. After finishing development, I tried to run the publish command, but I couldn’t find my API key. When I tried to check it, the API key page appeared to be missing (as shown in the attached screenshot).

> ipm publish minor
Welcome to Inkdrop!

Before you can publish packages, you'll need an API token.

Visit your account page on Inkdrop https://my.inkdrop.app/,
copy the token and paste it below when prompted.

Press [Enter] to open your account page on Inkdrop.
Access Key ID>


Could you help me resolve this?
If I’m doing something wrong on my end, please let me know.

Environment

  • Platform: Windows11
  • Platform version: 24H2 26100.7462
  • App Version: 5.11.7
  • Other …
> ipm --version
ipm  2.6.5
npm  6.14.16
node 18.15.0 x64
inkdrop 5.11.7
python 3.14.0
git 2.45.2.windows.1
visual studio 

How to reproduce

  1. Execute the ipm publish command.
  2. The API Key page opens in your browser (you’re already logged in).
  3. Not found.

Hi @Yu_Ogawa,

Thanks for the question.
The ipm bundled in v5 has been deprecated.
Can you try the new ipm command?

Note that it requires v6-canary.
Let me know if you have any issue!

Hi @craftzdog.

Thanks for your reply.
I tried inkdrop v6-canary and the new ipm command.

I followed the instructions at the URL below when running the ipm command, but I encountered an error when trying to run ipm publish.
How to use IPM - Inkdrop Desktop v6.0.0-canary.5

> ipm publish
Publishing package...
Failed to publish package: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:195:11)
    at defaultLoadSync (node:internal/modules/esm/load:142:3)
    at #loadAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:795:12)
    at #loadSync (node:internal/modules/esm/loader:815:49)
    at ModuleLoader.load (node:internal/modules/esm/loader:780:26)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:526:31)
    at #getOrCreateModuleJobAfterResolve (node:internal/modules/esm/loader:571:36)
    at afterResolve (node:internal/modules/esm/loader:624:52)
    at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:630:12)
    at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:649:32) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

It looks like the Windows OS is causing the problem, do you know a solution?

The Node.js version is v24.12.0.

Yeah, it looks like a bug on Windows.
Can you share your repository?

Yes, here it is

The Publish command completed using WSL.

> ipm publish
Publishing package...
✓ Package published successfully!

However, looking at the plugin page, it doesn’t appear to have been published properly.
(I’ve digressed a bit, so if the conversation continues I’ll create a proper thread…)

1 Like

Oops, it looks like the dryrun flag was always enabled unexpectedly on the server.
I’ve fixed the server api. Can you please try it again?
BTW, note that the package version is “0.0.0”, which should be incremented before publishing.

I hope it works!

Once published, it was properly reflected on the plugin page!
Thank you!

1 Like

Great!

However, I found that screenshots are broken on the plugin page:

The image URL gets a 404 error:

Hi @craftzdog,
Sorry for the late reply.

Thanks for your support!
After publishing the version tag to GitHub, images are now displayed correctly on the plugin page!

1 Like

Great!

1 Like