Way back when I dabbled around with ObjC (that was in 2002!) I created a small app that shows images from disk. About a year ago I upgraded this app to 64bit and ARC. This went well after a bit of

I played with this a bit more. It turns out that the bug is “transient”, in the sense that if you quit Xcode and relaunch, it picks up the correct deployment target.

I'm glad I could help. It's just one of those things I've run into myself a million times - I _think_ I've checked all my assumptions when I'm debugging something, and end up off in the weeds (for

Hi Jon, Turns out you’re right - the images were NOT square - they vary. It just so happened that the first image in my selection was square, and that’s what I observed in the debugger. Since it

I’m just relating what I’m observing in the video. Each icon is getting stretched vertically not by a uniform factor, but so that the drawn elements exactly fit the given bounds. Honestly, it

Hi Jon, The images are square - the rect returned by -imageRectForItemAtIndex is used to render them in the view as well as supplying the frame to the NSDraggingItem. That’s why it seems odd to me

Oh, my bad. I mean the drawing code within libItem.previewImage. - Jon

Judging from the video, your images are not square. It looks like they're only as large as they need to be to contain the drawn item, and are getting stretched to fit your square NSDraggingItem

I’m modernising some old code that does drag and drop the old, simple and perfectly functional (but deprecated) way. The new way seems twice as complicated to me, but hey-ho. Anyway, I’m creating

Hmmm, oh well, I guess I’ll just live with it. Bigger fish to fry and all that. Thanks! —Graham

I see similar results. It looks like a bug. If I set “Builds for” to “Deployment Target”, it shows the wrong deployment target (10.13 instead of 10.11), or if I choose a popup setting later

That has happened to me when I've forgotten to change the OS targets for (1) all the xibs and (2) the project itself. But it sounds like you've got all that covered... -Carl

Can anyone explain this? I’m getting the following warning in my build: But when I look at the file info for that .xib file: And the deployment target in the target as a whole: Am I missing

I have an iOS app (iOS 12.4+) which did work on iOS 12.4 … iOS 13.2 when build with Xcode 11.1. Now I have upgraded to Xcode 11.2 and the app no longer works on iOS 13.2 devices. When I

On Mon, Nov 4, 2019 at 03:52 AM, Sak Wathanasin wrote: That and the dozen or so pop-ups asking for permission that appear as soon as our app launches - all it does is condition the user to press

Yup; in our manually-signed app, we just set it to "none" from the pop-up Completely agree - we use a python script, but whatever works for you I've spent days, if not weeks to get our CI build to

I have an app that can launch apps and scripts. A script might target any app, so I can't use com.apple.security.temporary-exception.apple-events and add an app identifier for every possible app in

I don't have an answer to your particular situation, sadly, but man do I understand your pain! I can only mention two things: -As far as I understand, provisional profiles are not required for Mac

This isn’t, by any chance, one of those “ancient” apps that use an app ID whose prefix ISN’T your developer team ID? If so, that might have something to do with why it doesn’t work.

I checked that, and it’s turned on in the build settings. There’s another oddity, which is probably the real cause. In “signing and capabilities”, I have it set for Xcode to manage