breautek commented on issue #652: URL: https://github.com/apache/cordova-plugin-file/issues/652#issuecomment-3927154679
> but when we're forced to use Xcode 26.0 / iOS 26 to build with by April, this will give issues because the ALAssetsLibrary isn't included anymore, no? No, not necessarily. The deployment-target allows Apple to make certain optimizations. So if it's set lower, as to indicate that you support lower iOS devices -- then the SDK will enable backwards compatibility to those devices in most cases. If something was removed in an iOS version and the deployment target was set higher -- then Apple can optimize by removing that backwards compatibility. That's why setting it high can lead to breakage. cordova-ios@8 if I recall right supports iOS 13+ and so any plugin may be using ios 13+ APIs even if they are deprecated, as the replacement APIs may not be available in those older iOS devices. I feel this issue isn't really a bug but plugins **could** do preprocessor compiler conditions to swap the implementation where necessary but sometimes the newer API works very differently than the deprecated API and it requires a breaking change to get it to really work -- so if we wanted to support a higher deployment target on this plugin, someone would have to first evaluate if using the replacement API will require breaking changes or not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
