missing package product

18th-20th of July are still missing for us.

Hi Harry, I have a quite similar use case and I am really interested, how you have solved the problem. What was your solution? How did you use in-app purchases for your products? Did you configure one in-app purchase product for each item? Best regards, Ömer

Hi! Thanks for the excellent insight on what SMAppService does! All it cares about is whether or not the target exists. The fact that most daemon's haven't been insides app bundles is ENTIRELY a matter historical accident/choice, NOT because of any requirement, benefit, or even formal choice. This is true. I've put my Daemon in an app bundle out of choice. I technically do not need to do that, but I found that it will make a few things easier. I just wanted to be extra clear about that, since it looks like this isn't that common or recommended. The sandbox side of this is even more confusing, since launchd.plist's can be other tools on the system or even shell script. You can have a daemon that's sandbox'd, but nothing in launchd requires (or even cares) about that, as the sandbox is well outside of launchd's area of responsibility. The reason why I have my Daemon sandboxed is this: If I try to register a daemon that is not sandboxed (irrelevant if it is in an app bundle or not) from a sandboxed application I

Thanks, I just tried that. Then I realized that I can barely see any of my app's symbol names in the disassembly (which I created with otool -vt /path/to/executable). For instance I cannot find any of the method names mentioned in the crash reports. The disassembly looks like this: ~/Library/Developer/Xcode/Archives/2024-07-12/MyApp macOS 12.07.2024, 20.43.xcarchive/Products/Applications/MyApp.app/Contents/MacOS/MyApp (architecture arm64): (__TEXT,__text) section 0000000100004a00 stp x20, x19, [sp, #-0x20]! 0000000100004a04 stp x29, x30, [sp, #0x10] 0000000100004a08 add x29, sp, #0x10 0000000100004a0c adrp x8, 567 ; 0x10023b000 0000000100004a10 ldr x0, [x8, #0xc30] ; Objc class ref: bad class ref 0000000100004a14 bl 0x1001d664c ; symbol stub for: _objc_opt_self 0000000100004a18 adrp x8, 567 ; 0x10023b000 0000000100004a1c ldr x1, [x8, #0x588] ; Objc selector ref: sharedApplication 0000000100004a20 bl 0x1001d6634 ; Objc message: -[x0 sharedApplication] 0000000100004a24 mov x29, x29 0000000100004a28 bl

[quote='796464022, ingconti, /thread/691407?answerId=796464022#796464022, /profile/ingconti'] is better to use a TSI?? [/quote] DTS tech support incidents (TSIs) have been replaced by code-level support request and, as part of that process, DTS has switched to doing the bulk of our work on DevForums. There are three common file extensions for crash reports: .txt .ips .crash I’ll cover each in turn. Additionally, there is a lot of useful info in the various docs linked to by Diagnosing issues using crash reports and device logs. The first (.txt) isn’t ideal. You see it in places where the system requires a text file, like here on DevForums (see Posting a Crash Report) and in reports from App Review. If you get a .txt file, open it with a text editor to see what the real format is, and then change the extension to either .crash or .ips. The second format (.ips) is used for JSON crash reports. This is easy to identify because it looks like JSON. For example: {app_name:Xcode,…} { uptime : 1400000, … } IMPORTANT I

Problem solved. When compared to another project I’m working on, I noticed something missing from the “Signing & Capabilities” under macOS App Sandbox… Once I checked Outgoing Connections (Client), Xcode created a new entitlements file (oddly named AppNameDebug.entitlements) and added the setting Outgoing Network Connections = YES. Following my next build and run, sync to CloudKit databases worked perfectly. Can’t figure why this wasn’t required before. I didn't uncheck this and the previous entitlements file did not contain this line item before. All I can suggest is that I added an #if DEBUG macro to my project around the same time, so maybe this triggered the requirement? #if DEBUG do { // Use the container to initialize the development schema. try container.initializeCloudKitSchema(options: []) } catch { // Handle any errors. } #endif But main problem solved. If anyone has an explanation that would be appreciated.

I 've managed to start my app now i can see the following crash report information: Termination Reason: Namespace DYLD, Code 1 Library missing Library not loaded: @loader_path/libsteam_api.dylib Referenced from: <......B-3DDF-3AD6-B3C8-C39C3771A824> /Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/WattAttack-Mac-Shipping Reason: tried: '/Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/libsteam_api.dylib' (code signature invalid in <.......-0547-37ED-844E-89C9CABACBCA> '/Applications/WattAttack-Mac-Shipping.app/Contents/MacOS/libsteam_api.dylib' (errno=1) sliceOffset=0x00004000, codeBlobOffset=0x00027B70, codeBlobSize=0x000055F0) (terminated at launch; ignore backtrace) I've read different articles related to this code signing error but cant figure out how to fix the problem :(

OK. Did you look at the logs that Xcode generates when you export? I suspect you’ll see that it’s not passing the right values for --preserve-metadata. Regardless, you should file a bug against Xcode here. Please post your bug number, just for the record. As to the workaround, you’ll have to manually export your code from your Xcode archive. See Creating distribution-signed code for macOS, starting at the Export a non-app product built with Xcode section. Note that this isn’t as tricky than it might seem because you can follow the trail blazed by Xcode: Export using Xcode. Look in the logs to see what Xcode did. Apply the minor tweak to the --preserve-metadata option. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com