[Bug] Washington D.C. Region fails to load stops ("Unable to get stop")

[harshsomankar123-tech]

Summary:
The Washington D.C. region fails to load stops or arrivals. When attempting to view stops or arrivals in this region, the app consistently displays the error message "Unable to get stop".

Steps to Reproduce:

1. Launch OneBusAway.
2. Go to Settings → Your Region and select Washington D.C.
3. Return to the main screen.
4. Attempt to load the map or select any stop.
5. Observe the error message.

Observed Behavior:
The app fails to load stop details and displays the error message “Unable to get stop”.
The issue occurs every time and does not resolve after restarting the app.

Notes:

• The issue appears to be specific to the Washington D.C. region.
• Other regions work properly.
• Tested on both Wi-Fi and mobile data.

Expected Behavior:
The app should successfully load stops and arrival information for the Washington D.C. region without showing the “Unable to get stop” error, the same way it works for other regions.

Device Information:

• Pixel 9 Pro (Android 15)
• Pixel 2 Emulator (Android 16, API 36)
• Redmi Note 11 Pro+ 5G (Android 13)
• App Version: 2.14.9 (153)

Screenshots/Video:

Screen.Recording.2026-01-17.at.02.53.34.mov

Note: This looks like it could be a backend or server-side issue, but I’m reporting it here because it directly affects the Android app experience.