Bug reports are just ignored on bugzilla

YuraBabiyYuraBabiy UAMember ✭✭✭

I have reported two bugs, and after days there is nothing. Not at all.


  • DaveHuntDaveHunt USMember ✭✭✭✭✭


    Your bugs probably won't be addressed except maybe to mark them as "NEEDINFO".

    Bug reports should not be simple links to StackOverflow questions or very brief descriptions that don't provide a lot of detail. You need to very clearly describe the problem, the steps to reproduce it and, if at all possible, a small, stripped down project that demonstrates the problem.

    There's not enough information in your bug reports for anyone to take action. In addition, it's not clear whether your problems are actually with Xamarin.Forms or an incompatibility between a 3rd party library and the current version of Xamarin.Forms.

  • YuraBabiyYuraBabiy UAMember ✭✭✭

    I described them as I could. What is the meaning of rewriting all info that you can see on StackOverflow? Also, future comments from another people will be also visible. If one will read comments on StackOverflow, he sees that there is the comment which tells, that bug isn't in a library.
    I can understand, that Xamarin team and you trying to do your best, but there is no comment. Nothing.

  • DaveHuntDaveHunt USMember ✭✭✭✭✭

    As you stated in the first bug report you linked, there's no guarantee that your stackoverflow question will be there for reference. In fact, I just checked your "twinkle" stackoverflow post and it has been deleted. The purpose of the bug report is to keep all the information related to the problem in one place and not lose valuable information.

    As far as describing the problem, "it has twinkle on Android" is not particularly helpful.

    You mentioned in the FlowListView post that you tried with a ListView and still had the problem, so it may be a bug in Forms. Without details, clear steps to reproduce the problem, and/or a sample project that demonstrates it, that would be very difficult to prove.

    The "twinkle" bug sounds like an incompatibility with that custom control was introduced with an update to Forms. It may be a Forms bug, but it also may be that the custom control needs to be tweaked to work with the new version of Forms.

  • YuraBabiyYuraBabiy UAMember ✭✭✭

    After your words, it really has blank spaces. I will try to add more details and work around it.
    But see, it is what I needed below my bug in Bugzilla because it is hard to understand what is happening on their side.
    And I saw many questions, where they were saying about what someone should add or check. So I waited for something.
    Thanks for your work.

  • JonDouglasJonDouglas USXamarin Team, University, Developer Group Leader Xamurai

    Hi @YuraBabiy

    You can check out our support options article on the best practices you can follow when filing an issue with Xamarin tooling:


    When writing a bug in Bugzilla, please try to provide as much information as possible based on our guidelines:


    If you aren't sure if a bug should be filed or not, please follow our guide on this topic here:


  • RobClotherRobClother GBUniversity ✭✭

    So I reported two bugs, and they've just dissolved into the ether.

    They are pretty fundamental bugs as well.


    The first one of these is hardly difficult to reproduce: just open Visual Studio, do File -> New Project, and build the solution. I don't see how it could be more simple than that.

    For the second one, I have uploaded a full repro to GitHub.

    If an entire template is broken, I would have thought it would be a matter of urgency to get it fixed.

  • DaveHuntDaveHunt USMember ✭✭✭✭✭

    Your bug reports are barely two days old! They have a weekly (I believe) triage where bug reports are reviewed and prioritized. Give it a little time.

Sign In or Register to comment.