Premium Extension Composer Error

whisperwow

I have an active subscription and am using the Flarum Extension Manager along with this WordPress extension. However, the extension no longer updates via the Extension Manager. I have updated the token again but still can't figure out what is wrong.

Following is the error message I get in the logs. Any thoughts?

[2026-02-24 22:43:20] composer.ERROR: update --prefer-dist --no-dev -a --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires kilowhat/flarum-ext-wordpress *, found kilowhat/flarum-ext-wordpress[2.0.2] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

<warning>Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.</warning>

endlessedits

Same here, I think, with kilowhat/flarum-ext-rich-embeds.

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires kilowhat/flarum-ext-rich-embeds ¹.3, found kilowhat/flarum-ext-rich-embeds[1.4.0] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

@clarkwinkelmann

KBExit

whisperwow endlessedits
I don't think it's this specific extension itself. Multiple client sites I run are having difficulties updating premium extensions at this moment too. I've been ripping my hair out trying to diagnose it on my end. Really glad I'm not the only one dealing with this issue lol. It is unfortunate, but I'm sure the responsible party will get this remedied.
@GreXXL any ideas who to report this to?
This is affecting this extension and realtime on my end.

To add, I've cleared composer cache, Flarum cache, ran composer install, all combinations of composer update, reset auth tokens, created new tokens, etc.etc.etc. Still hit with that hard fail and composer stops.

IanM

KBExit this is an issue for @luceos to look into, he manages the premium extension codebase 🙂

KBExit

IanM thank you for tagging him as well! 🙂

clarkwinkelmann

So far, every time I've seen this error with a customer it was because of an expired token, and/or the new token not being properly configured (wrong Composer config file, basic instead of bearer, etc.).

But we can't exclude infrastructure issues with the marketplace.

Unfortunately I don't have a lot of hands-on experience, since I don't actually use any premium extension from the marketplace myself 😅 My own forums use the development version of my extensions straight from GitHub.

KBExit

clarkwinkelmann yeah I've made new tokens and applied them in to no success. I firmly believe this is an issue with the infrastructure.

endlessedits

For what it's worth in debugging, yesterday I updated everything and no problem, today I got that error.

KBExit

endlessedits I agree and can attest the same.
I'm sure a remedy will be out soon. 🙂

endlessedits

KBExit

Yes, to be clear, the extension kilowhat/flarum-ext-rich-embeds 1.4 still works great for me, it's just that the overall update command did not complete other available updates due to something with the remote repositories. (I'm no expert.)

luceos

There is an issue with the premium extension availability. It was reported to me last night by @maicol07 . So far I was able to see the problem occur, but not yet identify a cause.

My investigation will continue today, I will update everyone here as soon as I can.

luceos

Found the issue, all premium extensions are syncing now and should be available again within the next 15 minutes.

My apologies for the inconvenience.

Pupswoof117

For what it's worth, I'm still having issues.

KBExit

Pupswoof117 what are you being faced with? I haven't had the chance to try it yet.

Pupswoof117

KBExit it says this

`
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires maicol07/flarum-oidc-client, it could not be found in any version, there may be a typo in the package name.
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
It's a private package and you forgot to add a custom repository to find it
Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
allisonw@pi4:/var/www/forums.webpoweredlab.com
`

Pupswoof117

KBExit they approved it, disregard this reply.

KBExit

Pupswoof117 I see your reply.
Did you try creating a new token first and adding it to your Flarum instance first?

Pupswoof117

KBExit repeatedly

Pupswoof117

Maintainer said it worked, I haven't seen that on my end.