submitting bugs to Apple

Hello,
on February 25 2017 I submitted a bug report to Apple:
https://bugreport.apple.com/web/?problemID=30710991
I filed it under “Other” tag.

The report-page shows that the report is still Open, yet I do not see any evaluation or any sign that it has come to notice of the concerned people/department.

Hence the question: is https://bugreport.apple.com the right place to notify bugs?
Thank you for any suggestion.

yes. It may take months to be reviewed.
If ever.

In Apple’s Bugreporter I have 421 total and from that 354 are closed and 67 open.

And the oldest open one is from 2002.

A couple of them got fixed, but a lot of are duplicates.

see
https://www.mbsplugins.de/archive/2016-10-03/Xojo_Feedback_Success_rate

@Christian Schmitz [quote]And the oldest open one is from 2002[/quote]

Thank you. Your answer is very reassuring.

We have one that was reported and closed as a duplicate of another from the mid 1990’s
I think this bug is now 20 years old
And still open

Vey good, although I don’t know if I’ll be still alive in 20 years.

All you can do is report the bugs, hopefully find a workaround and move on. It’s up to them what’s more important, emoji or bug fixes. :wink:

Never, ever, for one moment, wait for Apple to fix a bug. Even if it means a large chunk of your app needs to be rewritten.

[quote=360099:@Norman Palardy]We have one that was reported and closed as a duplicate of another from the mid 1990’s
I think this bug is now 20 years old
And still open[/quote]
then it is a mac os 8 or 9 bug … it surely won’t be fixed :wink:

That’s true of any computing environment. Apple. Microsoft. Xojo. I once found a bug on a PDP-11 where the FORTRAN optimizing compiler screwed up a for loop (back in the 80’s). This took a marathon 36-hour debug session. I submitted a bug report and threw in some bogus code to satisfy the optimizer. I don’t think the bug was ever fixed.

Actually the bug I notified them about, is related to Apple’s implementation of unicode for Bangla, where a certain character sequence turns out wrong. Imagine, in a roman script, that the horizontal stroke over a “t” printed too much on the left: would not such a minimum bug forfait the scope of writing in languages using roman fonts?
With a clumsy workaround the problem could be redressed indeed (for Mac users), but, again, would not the scope of unicode become vain, when that text is opened by Windows users?

Well, in Feedback I also have Reviewed bugs from 2008.

NeXTStep actually
And it should be fixed as that component is still in use in macOS :stuck_out_tongue: