Bug Report: GitHub Android app fails to load issues that use ProjectNextItem #204543
Unanswered
dailylights
asked this question in
Mobile
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Android
Body
GitHub Android App (
com.github.android)- Platform: Android- Screenshot time: 2026-08-08 08:47 (UTC+8)- Repro: Opening an issue page that references a Projects (beta) itemProblem Description
When opening certain issues in the Android client, the page fails to load properly, showing:> No such type ProjectNextItem, so it can't be a fragment condition, and it fails to load properly.
Root Cause Analysis
The client is still using the deprecated GraphQL type
ProjectNextItem(old Projects beta). GitHub migrated to Projects (new), where the type isProjectV2Item(viaProjectV2/ProjectV2Itemconnection).ProjectNextItemwas removed from the schema, so the client can't resolve the fragment at runtime and the whole issue page fails to load.Suggested Fixes
ProjectNextItemfragment toProjectV2Itemto match the current schema.ProjectNextItemso existing clients don't crash before they update.Expected Behavior
Any issue (even Projects-linked) should load normally in the Android client without GraphQL schema errors.Screenshot:
All reactions