I got up this morning and started working on the project and now it has the Icon Composer icon. I'm guessing that the Finder had the old one cached and that re-starting the Mac re-built the Finder's data base???

The developer documentation for Icon Composer: Add your Icon Composer file to an Xcode project If you create your Icon Composer file outside of Xcode, you can add it to your Xcode project anytime to view your icon in Simulator and on real devices. Just drag the Icon Composer file from Finder to the Project navigator, and Xcode provides feedback on where to drop it in a target folder. No, it doesn’t - it asks how to add it and it adds it at the top level of the navigator but it won’t change how OS 26 displays your app icon in the finder. Alternatively, choose Add Files from the Add button at the bottom of the Project navigator and select your Icon Composer file in the dialog that appears. It asks how to add it and it adds it at the top level of the project but it won’t change how OS 26 displays your app icon in the finder. In the project editor, select the target and the General tab. Under App Icons and Launch Screen, ensure that the name in the App Icon text field matches the name of the Icon Composer file without the extension. You can have multiple Icon Composer files in your project but only one that matches the name in the App Icon text field. It still doesn’t show the Icon Composer icon in the Finder. You can check Include all app icon assets but it still won’t display the Icon Composer Icon in the Finder.

Same here. The developer documentation says that you can leave the old .icns file in your project and add the .icon file. The old icon should appear on older versions of the OS but the new icon should be displayed by the finder in OS 26. It isn't. I have both types listed in the Info-plist. I deleted the old app version and re-booted the Finder. It doesn't help. I am running MacOS 26 Tahoe. ???

I use an accessory view to create a file type popup menu in the save dialog to add file types by creating a .xib with the accessory view. I can't see how to do this with a TitleBar because there is no TitleBar in the catalog of UI items in Interface builder. Any suggestions?

New Add bookmark #7 I looked into this some more. This is cast in stone in Tahoe. In order to use special characters or justification in your window title you have to create a Title bar. This seems like a lot of hassle to do something that should be simple.

Still broken - SIX YEARS later.

I get the same error. I'm not using any third party frameworks or static libraries. I have my project set to include DWARF with dSYM in the build and debugger. This is a MacOS C/Objective C XCode project. With some Swift. Most of the discussion about this for iOS projects. When I verify or upload my App I just ignore this. Is this OK? Is this an Apple bug?

Also: AppLogger.error("Couldn't get the app store transaction") won't build: "Cannot find 'AppLogger' in scope" It looks like AppLogger is a third-party API. Is this correct?

Xcode wants me to use guard appTransaction != nil for the guard statement. This does seem to be closer to what a guard wants. XCode won't build: return await inspectAppTransaction(appTransaction, verifiedByApple: false) error: Cannot find 'inspectAppTransaction' in scope Naturally I can't find anything about this method by searching the Developer Documentation

Apple released 15.4.1 Today. Maybe this fixed it? You would expect this to be a high-priority bug.

You don't want your users to have to refresh() the app because it will ask for YOUR Sandbox test user credentials.

If you sell your app from your site it could be a problem with your receipts and verification. If this is happening to users that buy it from the App Store then it's likely that there's a BIG problem with 15.5. I understand your frustration with Mac development - crappy documentation in Swift only, very weak developer support, etc.

It's hard to know exactly what happened to me. There was a valid receipt in my project that I was using for testing. This was loaded using the old API exit(173). After I upgraded to 15.4 It was either gone or invalid. In my post I added code toload a receipt if there isn't one. This posts a dialog asking me to enter my Sandbox user name and password and then gets a receipt. If you comment out the refresh() and run it again it will verify the receipt so I'm guessing that it is still in the build folder. I'm hoping that none of my users will report that they are getting this dialog. What you have going on sounds much worse. If your users are getting their app from the store, the store either didn't attach a valid receipt or their older receipt is invalid on 15.4. I'm leaning to the second option. Would they have to get a valid receipt from the store? Download the app again from the store? How could they do this? This sounds really bad.

I decided to use a different approach: @objc class MyAppTransaction: NSObject{ @objc class func checkReceipt() async -> String { var appTransaction: VerificationResult<AppTransaction>? do { appTransaction = try await AppTransaction.shared } catch { appTransaction = try? await AppTransaction.refresh() } do { switch appTransaction { case .verified(_): return "VERIFIED" case .unverified(_, _): return "NO RECEIPT" default: return "ERROR" } } } } When my program executes the refresh() method it prompts me for my Sandbox user name and password, using two-factor authentication on my phone. Then in subsequent executions of the application it doesn't. I assume that this means that the receipt stays in the application bundle. Also I assume that refresh() won't be executed when my end users launch the application because the App Store will already have attached a valid receipt. Is this correct? Couldn't I comment out the refresh() in the final build I send to the App Store?

And naturally Searching the Developer Documentation for AppTransaction.BackingValue yields no results.