You type a Bluesky handle you know is correct, press search, and see the error ‘Could Not Find User.’ This usually happens even when the handle belongs to an active account that you have interacted with before. The root cause is often a mismatch between the local cache on your device and the current state of Bluesky’s directory servers. This article explains why this error appears and provides the specific steps to fix it.
Key Takeaways: Fixing the ‘Could Not Find User’ Error on Bluesky
- Clear app cache on mobile: Removing the Bluesky app’s local data forces a fresh directory lookup and resolves most stale handle errors.
- Log out and log back in: This refreshes your authentication token and clears any broken session data tied to the directory server.
- Use the web version as a test: If the handle works on the Bluesky web app but not on your phone, the issue is local to the mobile app cache.
Why Bluesky Shows ‘Could Not Find User’ on a Valid Handle
Bluesky uses a distributed directory system called the Personal Data Server. When you search for a handle, your app sends a query to the directory server that belongs to that user’s hosting provider. If your local cache has an outdated routing entry, the query goes to the wrong server or times out. The result is the ‘Could Not Find User’ error even though the handle is valid.
Another common cause is a corrupted session token. When your authentication token becomes stale without a proper refresh, the app can lose the ability to resolve certain handles. This is not a problem with the user’s account. It is a problem with how your app connects to the Bluesky network.
A third cause is a recent handle migration. If the user moved their account from one hosting provider to another, the DNS records for their handle may take up to 24 hours to propagate. During that window, some clients will see the old routing data and fail to find the user.
Steps to Fix ‘Could Not Find User’ on Bluesky
- Refresh the search manually
Pull down on the search results screen in the Bluesky app. This forces a new network request instead of using the cached result. If the handle appears, the fix was a temporary network glitch. - Clear the Bluesky app cache on iOS or Android
On iOS: Go to Settings > General > iPhone Storage > Bluesky > Offload App. Then reinstall Bluesky from the App Store. On Android: Go to Settings > Apps > Bluesky > Storage > Clear Cache. Do not tap Clear Data unless you want to log in again. Clearing cache alone often fixes the error. - Log out and log back into your account
Tap the menu icon in the top-left corner of the Bluesky app. Tap Settings at the bottom of the menu. Scroll down and tap Sign Out. Close the app completely. Open the app again and sign in with your handle and app password. This refreshes your session token and forces the app to re-fetch the directory routing table. - Search using the full handle with the domain
Instead of typing just the username, type the full handle including the domain. For example, type@user.bsky.socialinstead ofuser. The full handle bypasses some local auto-complete logic that may be corrupted. - Test the handle on the Bluesky web app
Open a browser on your computer or phone. Go to bsky.app. Search for the same handle. If the handle works on the web app but not on your mobile app, the problem is isolated to your mobile app cache or session. Follow steps 2 and 3 above. - Wait if the user recently changed their hosting provider
If the user tells you they moved their account to a different server, wait 24 hours. DNS propagation for the handle’s domain must complete before all clients can resolve it. After 24 hours, retry the search.
If Bluesky Still Shows ‘Could Not Find User’ After the Main Fix
The handle contains a typo or special character you missed
Bluesky handles are case-sensitive. Double-check the exact spelling. Pay attention to underscores, hyphens, and dots. A common mistake is confusing a lowercase L with the number 1.
The user deleted their account or changed their handle
If the user deletes their account, the handle becomes unresolvable. If they change their handle, the old handle stops working immediately. Ask the user to confirm their current handle by sending you a direct message from their account.
The Bluesky directory server is temporarily down
Bluesky’s infrastructure can experience regional outages. Check the Bluesky status page at status.bsky.app. If there is a reported outage, wait until the service is restored before retrying the search.
Your app version is outdated
An old version of the Bluesky app may have a bug in the directory query logic. Update the app to the latest version from the App Store or Google Play Store. After updating, repeat steps 2 and 3.
| Item | Clear Cache Method | Log Out / Log In Method |
|---|---|---|
| What it fixes | Stale directory routing data in local storage | Corrupted session token and authentication issues |
| Time required | 2 to 3 minutes | 3 to 5 minutes |
| Risk of data loss | None if you clear only cache | None if you remember your app password |
| Best for | Handles that worked before but now fail | Error appears immediately after login |
Now you can resolve the ‘Could Not Find User’ error on Bluesky by clearing the app cache or refreshing your session. Start with the manual refresh and full handle search. If those fail, proceed to clearing the cache and logging out. As an advanced tip, you can prevent this error by using an app password instead of your main password when logging into third-party Bluesky clients. App passwords reduce the chance of session corruption.