Xcode 11 GM generates many Analyzer warnings

[yoasha]

There are many reported issues by the Xcode Analyzer which are probably indicating semantic rather than functional issues. However, I think that when performing Xcode > Product > Analyze, it's a good practice to get an empty issue list just like good developers would strive to get an empty warning list when they compile their project.

Currently, there are dozens of NSNumber * conversion issues, among a single "Dead Store" issue which is attached in a screenshot. If you can find the time and put the required efforts to cleanup these Analyzer issues, it would be much appreciated by me and probably by many other developers.

[greg-db]

Thanks for the report! I'll ask the team to clean this up.

[kelohedeb]

It's been over a year now since @yoasha (very respectfully) reported these careless coding issues.
When do you plan to fix them?
The occurrence of 80 issues in supposedly production-quality code reflects poorly on you, Dropbox, and all of us who must use your slipshod library.

[greg-db]

@kelohedeb Thanks for the feedback! I can't offer a specific timeline for when the team would be working on this, but I'll bring this up with them again and share the feedback.

[yoasha]

Hi,
Originally, I reported these warnings for Xcode 11, however, we are already on Xcode 13 and I still see dozens of warnings.
Can you please handle this?

[greg-db]

This is still open with the team, but I don't have an update on it. I'll follow up here once I do.