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 first BlueSky profile added to Postiz correctly retrieves the BlueSky profile name.
The second BlueSky channel did not grab anything for the channel name. Note that my second channel name contains a "-" character in the name and @ handle.
👟 Reproduction steps
Add a BlueSky profile with username/password from the https://bsky.social service with a username and password combination
See that the first profile name and picture is retrieved from the BlueSky profile
Add another BlueSky profile, note that the name is not retrieved and is left blank in the Postiz console
👍 Expected behavior
I would expect that BlueSky profile names are retrieved and displayed in the interface
👎 Actual Behavior with Screenshots
I've marked the BlueSky profile that won't load the name to illustrate what is going on.
💻 Operating system
Linux
🤖 Node Version
Running latest docker
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
I checked and didn't find similar issue
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered:
📜 Description
The first BlueSky profile added to Postiz correctly retrieves the BlueSky profile name.
The second BlueSky channel did not grab anything for the channel name. Note that my second channel name contains a "-" character in the name and @ handle.
👟 Reproduction steps
👍 Expected behavior
I would expect that BlueSky profile names are retrieved and displayed in the interface
👎 Actual Behavior with Screenshots
I've marked the BlueSky profile that won't load the name to illustrate what is going on.
💻 Operating system
Linux
🤖 Node Version
Running latest docker
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: