4 Replies
      Latest reply: Jul 9, 2015 8:02 AM by Lord Andrei RSS
      gtzpower Level 1 Level 1 (0 points)

        Hi everyone,

         

        So I reported a bug to Apple in WatchOS, and thought, this is great, I will be able to see when it is resolved.  I quickly lost that warm and fuzzy feeling when it was closed as a duplicate of another case number.  I cannot find a way to track that other case number.  Does anyone know if there is any way to continue to track bug repoorts when they are closed as duplicate (other than watching the release notes for each following version)?

         

        Apple, if you are listening, I would love to be able to see the existing bug reports.  This would make my life as a developer much easier to know that there is an open bug report for something I am trying to implement (as well as being a solution to my problem above).  If the reason for not allowing this viewability is that you want a guage of how many people the bug affects by the number of reports, allow a "voting" option on each report so users can vote that the bug is affecting them.

        • Re: Bug reporting: tracking issues closed as "duplicate"
          donarb Level 3 Level 3 (150 points)

          The reason is privacy, some bug reporters include project and source files in their reports. If everyone could see the reports, they could see the source files attached to those reports. In addition, hackers could troll the reporting system looking for security vulnerabilities.

           

          There is no harm in filing duplicate bugs, Apple uses this to gauge how serious a bug is.

           

          If you want to find bug reports that might be similar to yours, go to openradar.me. People will copy their Apple bug reports on that site.

            • Re: Bug reporting: tracking issues closed as "duplicate"
              gtzpower Level 1 Level 1 (0 points)

              Thanks for the link to openradar.me.  Sounds like the next best thing. 

               

              There are solutions to most of the things you mentioned, like allowing developers to mark bugs as private, and keeping attached files private regardless.  As far as hackers trolling, that is certainly the biggest threat IMO, but one that exists anyway with the advent of openradar.me.

               

              The only harm in filing duplicate reports, besides that I cannot track the status when it is closed as duplicate, is the effort required by me to determine that there is indeed an OS bug, and to fill out the report.  The last one took me around 6 hours to be confident that it was an OS issue and to file the report. That is a lot of harm to my productivity.


              Also, openradar.me will probably discourage developers from filing a bug report if they see its already open, why go through the effort just to have it marked as closed for being duplicate (thats a lot more work than a "vote" would be).  It also allows hackers a place to troll.  If visibility going to happen anyway via openradar.me, why not try to do it in house and make a better experience for developers and give Apple the ability to better gauge severity with a voting system.  Not to mention that Apple could "hide" issues from the public if they are known to be a severe threat.

               

              I appreciate your reply.   I am just challenging the current solution hoping to encourage a better one.

              • Re: Bug reporting: tracking issues closed as "duplicate"
                Lord Andrei Level 1 Level 1 (0 points)

                I've alwats wondered. Is openradar.me a violation of Developer privacy agreements?

              • Re: Bug reporting: tracking issues closed as "duplicate"
                gtzpower Level 1 Level 1 (0 points)

                I just noticed that the bug report I submitted shows the status of the duplicate issue at the top.  I can see that the other issue is still open, and this is what I was originally looking for.