3.3 causes warning because of availability
Closed this issue · 4 comments
sbhhbs commented
Availability is meant to annotate a method is available since certain version or deprecate since certain version.
If anyone want to annotate a device's availability, they should define their own method or macro, otherwise compile the project will cause warnings.
SlaunchaMan commented
Yep, this is a side effect of a PR I made—I’ll send a new PR today that will silence these warnings when building SDVersion. In your own code, there’s a #pragma you can use to silence availability warnings if you need to use the constants for old versions.
sebyddd commented
@sbhhbs – I reverted the latest commit as a temporary solution.
@SlaunchaMan – Looking forward to that PR!
SlaunchaMan commented
@sebyddd Done!