User Profile

Posts

Posts

Post not yet marked as solved
3 Replies
Replied In Apple Pay enforced for order tracking
In iOS 17, order tracking is supposed to be available for purchases not made with Apple Pay. I found two support articles demonstrating this feature from the user’s point of view, and some developer documentation for JavaScript. But I see no instructions for adding this button to iOS apps. Am I missing something? Track orders and purchases in Apple Wallet Track your orders in Wallet on iPhone Adding a Track with Apple Wallet button (Apple Pay on the Web)
Post marked as solved
9 Replies
Replied In async/await back deployment crash in system extension
No, it’s just a regular Cocoa app, no extensions—but similar symptoms.
Post marked as solved
9 Replies
Replied In async/await back deployment crash in system extension
Hey everyone, @jaredh159’s answer helped me fix the can't resolve symbol _swift_defaultActor_initialize in /Applications/<REDACTED>/Contents/MacOS/<REDACTED> because dependent dylib @rpath/libswift_Concurrency.dylib could not be loaded crash that had occurred on macOS Big Sur (possibly Catalina too—yet to be confirmed). Thanks! I’ll add a few details specific to my case because it seems to me that Xcode may have issues with detecting whether back-deployment is needed. Native Cocoa app Deployment target: macOS 10.15 libswift_Concurrency.dylib is supposed to be back-deployed The library was in fact injected into the .app package (Contents/Frameworks/libswift_Concurrency.dylib), but the executable didn’t attempt to call it (I checked with otool -l) Both Xcode 14.3.1 and 15 beta 6 had the following default value for LD_RUNPATH_SEARCH_PATHS (at target level): $(LD_RUNPATH_SEARCH_PATHS_$(IS_MACCATALYST)) (I don’t remember seeing this value ever before) The crash stopped occurring after I changed LD_RUNPATH_SEARCH_PATHS’s value to $(inherited) @executable_path/../Frameworks @executable_path/../../../../Frameworks (from jaredh159’s answer) Changing the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES value (it had the default $(EMBEDDED_CONTENT_CONTAINS_SWIFT) value) didn’t seem to result in any change I’m concerned with Xcode failing to apply the correct build settings automatically, even though it did copy the library. Could this be a bug? CC @eskimo