You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem was two-fold: the library was sending name instead of the nickname field that Openfire's roster entity actually expects, and it was passing false values for unset optional parameters, which Openfire rejects with a 500.
Activity
[-]`$api->addToRoster()` is not working[/-][+]$api->addToRoster() is not working[/+]Fix roster/user endpoints, upgrade Guzzle, unpin composer version
gidkom commentedon Apr 11, 2026
Fixed in v1.2.0 (commit ae71237).
The problem was two-fold: the library was sending
nameinstead of thenicknamefield that Openfire's roster entity actually expects, and it was passingfalsevalues for unset optional parameters, which Openfire rejects with a 500.Both are fixed — please upgrade: