Unable to “Share Feedback” here using GitHub app for iOS

[dotext]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

iOS

Body

As seen here: #209875

If I tap on “Share Feedback” on the GitHub iOS app Settings, then create a new post in the community after selecting the “Mobile” category in the app, it automatically gets closed and told that we didn’t use the template… which we never were provided. The “ℹ️ Additional Debug Info” gets automatically populated, but that’s it. As a result, it’s preventing us from actually submitting any feedback.

As it is, no one can submit any feedback via the Share Feedback button on the GitHub iOS app.

I’ve resorted to using the desktop web to submit this one, otherwise anything I post will get rejected.

The auto response says to reach out to the maintainers, which we can’t do, so this is the only avenue I could find to bring attention to this.

I made a ticket to GitHub Support, but it was immediately closed and got told to use the GitHub Community Discussions… which once again, we can’t use on the GitHub app on iOS. (Edit: Thank you to Steve who passed the ticked over to the GitHub mobile team once I reopened the ticket and explained the situation again.)

Could this please be resolved?

Thank you.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[iamyakay]

#209875 shows the feedback being closed specifically for not using the discussion template, even though the app populated its debug information. That supports a mismatch between the app's submission flow and the Community's template requirement. It doesn't establish that every iOS user is affected, but your example gives the mobile team a concrete case to investigate.

The fix needs to connect those two parts: either Share Feedback should open the required form, or the Community submission checks should accept the format the app produces. Sending users back to the same flow just repeats the failure.

Since Steve has already passed the ticket to the mobile team, I'd keep the discussion and that ticket linked. The desktop form worked for this report, but it remains a workaround. The useful confirmation from the team would be whether they can reproduce the rejection on version 1.280.0 (206799080) and which part of the submission flow needs changing.

[f94149904-commits]

halo

[jessica12ryan]

The issue persists completely across GitHub for any repo using a .yml (YAML) issue template. They are a better option than Markdown templates but they lose the ability to create issues from within the mobile app.

#209974