missing package product

42,954 results found

Post

Replies

Boosts

Views

Activity

Reply to Crash __CFRunLoopServiceMachPort - 99% background
You won’t be able to debug this based on the info from your third-party crash reporter. In fact, I’m not ever sure there’s anything to debug! The crash report says that it’s crashed here: Crashed: com.apple.main-thread 0 libsystem_kernel.dylib 0x1808 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x5008 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x4f20 mach_msg_overwrite + 436 3 libsystem_kernel.dylib 0x4d60 mach_msg + 24 4 CoreFoundation 0x53f5c __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x53600 __CFRunLoopRun + 1208 6 CoreFoundation 0x52cd8 CFRunLoopRunSpecific + 608 7 GraphicsServices 0x11a8 GSEventRunModal + 164 8 UIKitCore 0x40a90c -[UIApplication _run] + 888 9 UIKitCore 0x4be9d0 UIApplicationMain + 340 10 UIKitCore 0x638384 keypath_get_selector_hoverStyle + 11024 11 MYAPP 0x6a348 main + 4365591368 (YAppDelegate.swift:4365591368) 12 ??? 0x1abc85e4c (Missing) but that makes no sense. This indicates that your main thread crashed, but the main thread is suspended in its run loop waiting f
3w
Reply to Apple's Choice: USDZ over Other 3D File Formats like GLTF
@Umbra: I completely agree with you on this. Working with USDZ for iOS AR experiences is incredibly time-consuming and frustrating for our company. We frequently find ourselves reverse-engineering problems and issues specific to the USDZ format that simply don't exist with GLB. Let me provide an example: We create high-quality 3D product models for web and AR applications. These can be compressed to 4-12 MB as GLB files. However, maintaining the same quality in USDZ format often results in file sizes of 60 MB or more. This leads to frequent crashes in iOS Safari or excessively long loading times in AR, making it impractical to offer to customers. Consequently, we're forced to adopt a dual approach: high-quality models for Android AR cases and lower quality for Apple devices. This clearly contradicts Apple's mission of providing superior user experiences. Furthermore, we're reliant on unpolished software like Reality Converter, which seems to be in perpetual development with virtually no communication
3w
Reply to LOCALIZED_STRING_MACRO_NAMES for Swift package targets?
There is not a way to set build settings like this in Swift Packages. One alternative would be to define something like this: func myPackageLocalizedString(_ key: String.LocalizationValue) -> String { return String(localized: key, bundle: Bundle.module) } Strings using this method would be extracted without needing to define any custom macro names. However when doing that you lose the ability to customize the localization comment or table name from callers of your function. (Though comments can still be added directly from the String Catalog Editor.) We would welcome enhancement requests in both of these areas.
3w
Reply to on-line entitlement format to obtain relevant "transport.usb|idVendor"
Thank you :) Right now: - I'm building for developing. Three months later: - for communicating with End-User-Apps-developers of ... of various backgrounds The situation: I see non-logical logs of USB-gadget-attachment in Console.app; though that app is obviously buggy and really misses messages, timing of certain logs' in my tests look non-logical (so I am suspecting/expecting huge bugs in the core of OS development) such bugs aren't fatal; but those shall be stable bugs~=features but to treat (potential) system-bugs (or my bugs andOS quirks) as features I would prefer to have the same (as much as possible) binaries with resources at development and at distribution
3w
LOCALIZED_STRING_MACRO_NAMES for Swift package targets?
I have a custom localisation function in my project that enforces the inclusion of the bundle parameter (specifically so that Swift packages are forced to include the Bundle.module value). While migrating to String Catalogs, I noticed that my custom localisation function wasn't being recognised by the automatic extraction that the Swift compiler is doing, but only in my Swift package targets. Is there a way to set something like LOCALIZED_STRING_MACRO_NAMES in Swift Packages?
1
0
301
3w
SwiftData custom migration crash
Starting point I have an app that is in production that has a single entity called CDShift. This is the class: @Model final class CDShift { var identifier: UUID = UUID() var date: Date = Date() ... } This is how this model is written in the current version. Where I need to go Now, I'm updating the app and I have to do some modifications, that are: add a new entity, called DayPlan add the relationship between DayPlan and CDShift What I did is this: enum SchemaV1: VersionedSchema { static var versionIdentifier = Schema.Version(1, 0, 0) static var models: [any PersistentModel.Type] { [CDShift.self] } @Model final class CDShift { var identifier: UUID = UUID() var date: Date = Date() } } To encapsulate the current CDShift in a version 1 of the schema. Then I created the version 2: enum SchemaV2: VersionedSchema { static var versionIdentifier = Schema.Version(2, 0, 0) static var models: [any PersistentModel.Type] { [CDShift.self, DayPlan.self] } @Model final class DayPlan { var identifier: UUID = UUID() va
12
0
446
3w
Reply to SwiftUI Preview + Swift Packages Break App
Sorry you're hitting this error, this sounds like something we'll need more diagnostics to figure out what's going on. Could you please file a bug report and attach your preview diagnostics? Steps to generate helpful diagnostics: Download and install the logging profile on all devices involved. Instructions and profiles are available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Reproduce the issue Click the Diagnostics button in the error banner in Previews' Canvas area (or if the banner is missing you can use the menu: Editor > Canvas > Diagnostics) In the sheet that appears, click Generate Report in the bottom left of the sheet Attach (or make from the folder) the resulting zip file to the bug report (will be named something like previews-diagnostics-0123456789.zip) Generate the sysdiagnose(s) and attach those too
3w
Apple pay web authentication failed (SSL connection)
I have setup the server settings TLS, HTTPS I have performed the following steps but not working for me: 1. I have validated my domain 2. Generate Certificate Signing Request (CSR) using keychain. It created public and private key in MAC keychain 3. Uploaded CSR (from point 2) to apple Pay Merchant Identity Certificate. It gave me merchant_id.cer 4. Generated .p12 with merchant_id.cer, public and private key using keychain Now I am using this .p12 to create the ApplePaySession (paymentSession) using server side code in C# but getting error from apple side. Exception: The SSL connection could not be established Inner Exception: Authentication failed, The credentials supplied to the package were not recognized at System.Net.SSPIWrapper.AcquireCredentialsHandle Sample Code: var request = new MerchantSessionRequest() { DisplayName = StoreName, Initiative = web, InitiativeContext = applepaypoc.xxxxxx.com, MerchantIdentifier = merchant.com.xxxxxx.applepaypoc, }; string certPath = Path.Combine(Directory.Get
2
0
245
3w
Sending Data via Bonjour and NWConnection
Using NWBrowser and NWListener I'm trying to send a small package of data from the listener/server to the device. However the device never receives the actual bytes. It either: gets stuck the preparing state the connection gets reset the data is null and is marked as isComplete = true The only way I can get the device to receive the data is by calling cancel on the NWConnection on the server/NWListener end. Here is some sample code I am working with: https://github.com/leogdion/JustBonjour/tree/nwlistener Is this expected behavior that cancel is required?
2
0
431
3w
SwiftUI Preview + Swift Packages Break App
I have a multi-platform app with the SwiftUI code a separate Swift Package. Any Views with SwiftUI Previews break the compilation of the app. Here's the error message I get in Xcode: Showing All Messages ld: warning: Could not parse or use implicit file '/Applications/Xcode-beta.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS.sdk/System/Library/Frameworks/SwiftUICore.framework/SwiftUICore.tbd': cannot link directly with 'SwiftUICore' because product being built is not an allowed client of it Undefined symbols for architecture arm64_32: (extension in SwiftUI):DeveloperToolsSupport.Preview.init(_: Swift.String?, traits: DeveloperToolsSupport.PreviewTrait<DeveloperToolsSupport.Preview.ViewTraits>..., body: @Swift.MainActor @Sendable () -> SwiftUI.View) -> DeveloperToolsSupport.Preview, referenced from: static BitnessViews.$s12BitnessViews33_ABDBADF565C741E50A2A5746CE94FCD9Ll7PreviewfMf_15PreviewRegistryfMu_.makePreview() throws -> DeveloperToolsSupport.Pr
1
0
248
3w
Xcode and Transporter inconsistent with provisioning profile
Xcode > Target > Signing & Capabilities Automaticaly manage signing Mac OS Signing Certificate: Development --> Provisioning Profile None Required General Identity App Category Productivity Transporter Asset validation failed (90242) --> Cannot be used with TestFlight because the bundle at “LargeNumberCalculator.app” is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. (90889). What is wrong: Provisioning Profile None Required vs missing a provisioning profile ?
3
0
368
3w
Pay attention to StoreKit Configuration settings
It's not a question, I just want to share my experience of resolving a bug. We where adding a new product to the app and couldn't get why it's not loading. StoreKit 2 simply did not return the product, so we switched to StoreKit 1 to get invalidProductIdentifiers from the response. The product was there of course. So many time was spend... We checked App Store configuration, everything was approved. Checked id, localization, multiple devices. Everyone start to get mad, we filled issues for RevenueCat and Apple. Then we uploaded a TF build (because product wasn't loading when running from Xcode). And, suddenly the product did appear there! I understood that it can be connected to StoreKit Configuration, since it works only in debugger mode (Debug or Release), but not in TF. But there was no any .storekit files in the project folder. I search it many times - no success. And finally the bug was resolved when I checked Run Scheme. As you can see on the screenshot, it h
0
0
187
3w
[StoreKit2] Purchase completion is displayed even if it has not been completed.
StoreKit2 is being tested in a Sandbox environment for the purchase of consumable items. The code being implemented is below. let result = try? await product.purchase() switch result { case let .success(verification): switch verification { case let .verified(transaction): let jws = verification.jwsRepresentation let success = await purchaseItem(of: itemId, with: jws) if success { await transaction.finish() return (success: true, error: nil) } else { return (success: false, error: .serverError) } case .unverified: return (success: false, error: .unverified) } Assume that the verification was successful, but a server error occurred. in let success = await purchaseItem(of: itemId, with: jws), success = false When tested in Sandbox and local environment, the first alert of purchase completion is displayed. After that, a purchase failure alert is displayed. (The purchase failure alert is displayed by the result of return (success: false, error: .serverError)) Is it proper behavior to display purchase completion on
1
0
218
3w