Lnpopupcontroller: iOS 9, 10 support has been dropped in 2.9.0+
Hi guys,
I am planning to clean up the code and drop support for 9, 10. I will create a stabilized version with iOS 13 support, and that will be the last to support legacy OSes.
After that, I plan to clean the code from legacy and maybe rewrite some of the presentation stuff as time permits.
LeoNatan
All 13 comments
Don't forget we should merge #321 first :P
coolstar
on 9 Jun 2019
I haven鈥檛 forgotten. I am thinking how to make it more generalized to any docking view.
LeoNatan
on 9 Jun 2019
Maybe it makes sense to merge the changes of the @coolstar before drop down the support of iOS 9/10 and maximally stabilize the current version?
djmixroman
on 10 Jun 2019
Actually, I鈥檓 not sure about that. Adding such a big feature would require a long stabilization period, which I have neither the capacity for not the interest. iOS 9 and 10 are very outdated in their API.
LeoNatan
on 10 Jun 2019
Seems like the dev tools are broken for iOS 10 anyway:
https://twitter.com/LeoNatan/status/1140695880015777792
and Apple is abandoning the iOS 8/9 simulator runtime after Xcode 11:
https://twitter.com/xenadu02/status/1140093901438689280
More nails in the 鈿帮笍.
LeoNatan
on 17 Jun 2019
In Music demo, it crash when selecting a music cell on iOS 10.3.1, not verified with iOS 11 & 12 yet:
iDevelopper
on 25 Aug 2019
The Music storyboard no longer compiles for iOS 10. That's the demo app, it is unrelated to the framework itself.
LeoNatan
on 25 Aug 2019
It would be nice to extend the iOS 9 and 10 support until next year. My apps still have a deployment target of iOS 9.0+.
wimbledon
on 11 Sep 2019
Unfortunately, it's just not sustainable.
iOS 9 & 10 are very outdated in their API, and there is such minuscule userbase.
LeoNatan
on 11 Sep 2019
It's happening. With the planned 2.9.x release (iOS 14 support), iOS 9-11 support is removed. Only iOS 12 and above will be supported.
LeoNatan
on 31 Jul 2020
@LeoNatan just wondering, are there any APIs we need that are only on iOS 12+?
I鈥檇 like to keep iOS 11 support, but I鈥檓 fine with dropping 10.x and lower
coolstar
on 31 Jul 2020
I want to minimize the swizzled API usage to a minimum. I'll look at the stuff I removed (and still need to remove) and I'll see if iOS 11 complicates stuff. iOS 11 has support for safe areas, which is a big plus, but it's pretty broken. No promises, but I'll look favorably if it doesn't need extra swizzles over iOS 12.
LeoNatan
on 31 Jul 2020
iOS 11 and above.
LeoNatan
on 4 Aug 2020
Related issues
nhatduong
路
7Comments
PrakashMaharjan
路
6Comments
funkenstrahlen
路
3Comments
user3587412
路
4Comments
dancarasco
路
6Comments
Most helpful comment
Actually, I鈥檓 not sure about that. Adding such a big feature would require a long stabilization period, which I have neither the capacity for not the interest. iOS 9 and 10 are very outdated in their API.