Quick help documentation in Swift shows different availability than Objective-C
Originator: | michele.titolo | ||
Number: | rdar://23630349 | Date Originated: | 11/20/2015 |
Status: | Open | Resolved: | Closed |
Product: | Developer Tools | Product Version: | Xcode 7.1 |
Classification: | Reproducible: | Always |
Summary: I was looking up the quick help documentation for NSDecimalNumber notANumber in Swift and noticed it's availability was iOS 8.1. However going into an Objective-C file the availability appears as iOS 2. This is not just that method. NSDateFormatter stringFromDate also says iOS 8.1 when it's also iOS 2. Basically all the quick help documentation in Swift files shows the incorrect availability version number. Steps to Reproduce: 1. Create a Swift and Objc file. 2. Use same method. 3. Option + click to open the quick documentation. 4. See that availability versions are different Expected Results: I expect the availability version to be the same for the same method in Objc and Swift files. Actual Results: They are not the same, and Swift lies (which caused me a slight panic since we still support iOS 7). Version: Xcode 7.1 (7B91b) & OS X 10.10.5 (14F1021) Notes: Configuration: All the time Attachments: 'Screen Shot 2015-11-20 at 9.40.31 AM.png', 'Screen Shot 2015-11-20 at 9.40.49 AM.png' and 'Screen Shot 2015-11-20 at 9.43.26 AM.png' were successfully uploaded.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
That's definitely a bug, duped it: rdar://23749319
Response:
Engineering has the following feedback for you:
This is expected - Swift was not available until WWDC 2014 and the introduction of iOS 8, therefore the availability of these methods and contstants in Swift is correctly documented as iOS 8+.
Thank you for your feedback. Engineering has determined that this issue behaves as intended.
We are now closing this bug report.
If you just have questions about the resolution, then please update your bug report with that information so we can respond.
They lie!