Does an app need to be rebuilt against a new iOS version release to get the bug fixes of that version as mentioned under release

admin管理员组

文章数量:1287774

Under every release note it mentions the resolved issues for various frameworks, eg SwiftUI, AVFoundation etc..

For example,

Does the app need to be rebuilt to get these fixes or does it come as part of the os update on the device? So if my app were built against the iOS 17.5 and the user device were on 18.1 it would get the fixes of 18.1.

Apple doesn’t explain this in the notes so I’m wondering what we’re supposed to figure out ourselves or if apple just fot to describe something quite important, IMO.

Under every release note it mentions the resolved issues for various frameworks, eg SwiftUI, AVFoundation etc..

For example, https://developer.apple/documentation/ios-ipados-release-notes/ios-ipados-18_1-release-notes

Does the app need to be rebuilt to get these fixes or does it come as part of the os update on the device? So if my app were built against the iOS 17.5 and the user device were on 18.1 it would get the fixes of 18.1.

Apple doesn’t explain this in the notes so I’m wondering what we’re supposed to figure out ourselves or if apple just fot to describe something quite important, IMO.

• ios

Share Improve this question Follow asked Feb 22 at 20:30 Minh HuynhMinh Huynh 1111 silver badge11 bronze badge 1

• 1 Imagine every developer had to post an updated app every time iOS was updated. The sheer number of app reviews would destroy Apple. – HangarRash Commented Feb 22 at 20:49

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

System framework fixes and improvements—like those noted for SwiftUI, AVFoundation, and others—are delivered as part of the OS update itself. This means that if your app was built against an older SDK (for example, iOS 17.5) and a user updates their device to iOS 18.1, the updated system libraries (which now include those fixes) are used at runtime. In other words, your app will automatically benefit from the improvements without needing to be rebuilt.

This effect is achieved by using dynamic libraries: most of Apple’s frameworks are provided as dynamic libraries. They’re not embedded into your app; instead, they’re loaded from the OS at runtime. So when the OS is updated, the new versions of these libraries are used.

You can find more detailed info here: https://developer.apple/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Frameworks.html, especially in Frameworks and building article:

Clients of dynamic shared libraries do not need to be aware of any dependencies required by the library. When a dynamic shared library is built, the static linker stores information about any dependent libraries inside the dynamic shared library executable. At runtime, the dynamic link editor reads this information and uses it to load the dependent libraries as needed.

本文标签：