AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Couldn't resolve Bluesky handle, newest first.

Current version | Edited by Rex
Changes
```Removed: ### Logs or screenshots (optional)Removed: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Couldn't resolve Bluesky handle

Summary

POST https://web.fluxer.app/api/v1/users/@me/connections/bluesky/authorize 400 Bad Request Request 
{
    "handle": "dxvil.com"
}
Response 
{
    "code": "BLUESKY_OAUTH_AUTHORIZATION_FAILED",
    "message": "We couldn't resolve that Bluesky handle. Please check it and try again."
}
Tested with and without @ and tested also geeneral bsky.social handlers. None of them work.

Steps to reproduce

  1. User Settings --> Connections --> Tap on Bluesky Icon
  2. Fill your bsky handler
  3. Click on "Connect with Bluesky"

Environment (optional)

Environment

  • stable (5b0afb2)
  • Desktop stable 0.0.8
  • Deployed 23h
  • Electron 39.2.7
  • Windows 11 10.0.26200 (x64)
--- version.json says 
{
    "sha": "5b0afb2ee",
    "buildNumber": 0,
    "timestamp": 1771684844,
    "env": "production"
}
Original by Rex
Show

Couldn't resolve Bluesky handle

Summary

POST https://web.fluxer.app/api/v1/users/@me/connections/bluesky/authorize 400 Bad Request Request 
{
    "handle": "dxvil.com"
}
Response 
{
    "code": "BLUESKY_OAUTH_AUTHORIZATION_FAILED",
    "message": "We couldn't resolve that Bluesky handle. Please check it and try again."
}
Tested with and without @ and tested also geeneral bsky.social handlers. None of them work.

Steps to reproduce

  1. User Settings --> Connections --> Tap on Bluesky Icon
  2. Fill your bsky handler
  3. Click on "Connect with Bluesky"

Environment (optional)

Environment

  • stable (5b0afb2)
  • Desktop stable 0.0.8
  • Deployed 23h
  • Electron 39.2.7
  • Windows 11 10.0.26200 (x64)
--- version.json says 
{
    "sha": "5b0afb2ee",
    "buildNumber": 0,
    "timestamp": 1771684844,
    "env": "production"
}

Logs or screenshots (optional)

No response

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.