Post

Replies

Boosts

Views

Activity

Why would i not activate 'Preserve Vector Data' for SVGs?
First off, i believe i do know what the option 'Preserve Vector Data' does. But just in case, let me recap: When using PDFs or SVGs in my Asset Catalog, Xcode by default creates assets at fixed sizes from these files at buildtime. When i tick the 'Preserve Vector Data' box, the asset is scaled at runtime using the vector data, allowing for smooth scaling and crisp images at any scale. But the question i'm asking myself now is what exactly is the drawback - most likely performance-wise - to simply activating this option for each an every SVG or PDF Asset i use in my project? I would be very happy if someone could elaborate on this or direct me to some more in-depth documentation on Vector Assets :)
2
3
4.8k
Aug ’24
Umbrella Header [...].h not found
When trying to build my framework, I suddenly receive the following error: Umbrella Header [...].h not found Honestly, I'm not even sure why there should be a header file in the first place since the framework is pure swift. There are no objective-c files in the project at all. I don't have an idea where to begin the investigation for this issue since I haven't really used objective-c ever and am therefore not too familiar with the topic. Can someone here maybe point me in the right direction?
0
0
1.2k
Nov ’22
Objective C App has wrong [UIScreen mainScreen].bounds value since iOS 16
Device: Physical iPhone X (16.0.2) A legacy app (Objective C) of my client has worked just fine on iOS 15. On iOS 16 though, the app has suddenly 'shrunken in height'. The app opens as usual but on the top and bottom of the screen, there are black bars, as the app itself seems to be constrained to a certain size. After some investigation, I found out that the device actually reports its Screen Height to be 480pt (iPhone X). Forcing the UIWindow to have a different size doesn't solve the issue, the app is still constrained to be the same wrong height. It seems the device 'actually believes' to be shorter than it is. Since this behavior kind of resembles what happens when starting an iPhone app on an iPad (at least I remember seeing something like that some time ago), I was wondering whether or not this behavior is expected as of iOS 16? If not, I would really appreciate some help here.
6
1
1.8k
Sep ’22
Why would i not activate 'Preserve Vector Data' for SVGs?
First off, i believe i do know what the option 'Preserve Vector Data' does. But just in case, let me recap: When using PDFs or SVGs in my Asset Catalog, Xcode by default creates assets at fixed sizes from these files at buildtime. When i tick the 'Preserve Vector Data' box, the asset is scaled at runtime using the vector data, allowing for smooth scaling and crisp images at any scale. But the question i'm asking myself now is what exactly is the drawback - most likely performance-wise - to simply activating this option for each an every SVG or PDF Asset i use in my project? I would be very happy if someone could elaborate on this or direct me to some more in-depth documentation on Vector Assets :)
Replies
2
Boosts
3
Views
4.8k
Activity
Aug ’24
Umbrella Header [...].h not found
When trying to build my framework, I suddenly receive the following error: Umbrella Header [...].h not found Honestly, I'm not even sure why there should be a header file in the first place since the framework is pure swift. There are no objective-c files in the project at all. I don't have an idea where to begin the investigation for this issue since I haven't really used objective-c ever and am therefore not too familiar with the topic. Can someone here maybe point me in the right direction?
Replies
0
Boosts
0
Views
1.2k
Activity
Nov ’22
Objective C App has wrong [UIScreen mainScreen].bounds value since iOS 16
Device: Physical iPhone X (16.0.2) A legacy app (Objective C) of my client has worked just fine on iOS 15. On iOS 16 though, the app has suddenly 'shrunken in height'. The app opens as usual but on the top and bottom of the screen, there are black bars, as the app itself seems to be constrained to a certain size. After some investigation, I found out that the device actually reports its Screen Height to be 480pt (iPhone X). Forcing the UIWindow to have a different size doesn't solve the issue, the app is still constrained to be the same wrong height. It seems the device 'actually believes' to be shorter than it is. Since this behavior kind of resembles what happens when starting an iPhone app on an iPad (at least I remember seeing something like that some time ago), I was wondering whether or not this behavior is expected as of iOS 16? If not, I would really appreciate some help here.
Replies
6
Boosts
1
Views
1.8k
Activity
Sep ’22