After trying to build with macOS 15 and XCode 16 (beta and beta2), XcodeCloud started to crash at the Resolve package dependencies step. Everything works perfect on my local system running same OS same XC. Details: [] Function: unregisterDependencyFileReferences(_:) Thread: <_NSMainThread: 0x600002094200>{number = 1, name = main} Hints: Backtrace: 0 -[DVTAssertionHandler handleFailureInFunction:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in DVTFoundation) 1 _DVTAssertionHandler (in DVTFoundation) 2 _DVTAssertFromSwift (in DVTFoundation) 3 _DVTAssert(_:file:line:function:varargs:) (in DVTFoundation) 4 DVTAssert(_:_:file:line:function:) (in DVTFoundation) 5 closure #1 in closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore) 6 closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore) 7 closure #1 in OS_dispatch_queue.dvt_sync(execute:) (in DVTFoundation) 8 thunk for @callee_guaranteed
missing package product
42,979 results found
Post
Replies
Boosts
Views
Activity
I created package.swift for my framework. And was work correctly in iOS. Now we need to support tvOS. I don't understood how can we do it. Because source code is different but networking layer is same. When I create dynamic targets: extension Target{ static func allTargets() -> [Target]{ return ([ Target.SDKTarget(), ] as [[Target]]).flatMap{$0} } static func SDKTarget() -> [Target] { #if os(tvOS) return [ .target(name: frameworkName, dependencies: [ .product(name: GRPC, package: grpc-swift), ], path: Sources/tvOS, ) ] #else and when I select tvOS build this code in preprocessor block still gray and won't compile. How to make single package.swift for my framework for support tvOS and iOS with different code base and shared networking source code?
Hello, Our product registers a daemon in the system through SMAppService (API available from Ventura) and also checks its status in case it has to tell the user to allow the daemon process as a background process. To check the status we call a script written in applescript that returns the status of the service. Script excerpt: NSString* scriptText = @use framework AppKitn @use framework ServiceManagementn @use scripting additionsn @on startCommand()n @tryn @local this, service, SMAppServiceInstance, retn @set this to a reference to current applicationn @set SMAppServiceInstance to a reference to SMAppService of thisn @set service to SMAppServiceInstance's daemonServiceWithPlistName: %@n @set str to service's status as stringn @set success to str as numbern @return successn @on error errorMessage number errorNumbern @log (errorMessage: & errorMessage & , errorNumber: & errorNumber)n @end tryn @return -1n @end startCommandn; The problem we see is sometimes when we try to check the status
我创建了一个developer id instanller 证书，并且安装在自己电脑上，我使用productbuild --component xx.app /Applications --sign Developer ID Installer: --product xx.app/Contents/Info.plist ST.pkg签名并生成pkg，使用 spctl -a -v --type install ST.pkg 去验证签名的时候，出现rejected source=Unnotarized Developer ID，我不知道哪里有问题，将pkg安装到其他电脑也会出现pkg无法打开，apple无法检查是否包含恶意软件 提示信息，希望可以得到大家的帮助谢谢，
I have a project with 2-5k daily online users, but have only 5 users that have this crashes. They all have iOS 16 installed Attached logs from FireBase First Log: Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x1c20 objc_msgSend + 32 1 UIKitCore 0x9bd754 -[UIView _backing_traitCollectionDidChange:] + 64 2 UIKitCore 0x169754 -[UIView _traitCollectionDidChangeInternal:] + 628 3 UIKitCore 0x1692b4 -[UIView _wrappedProcessTraitCollectionDidChange:forceNotification:] + 156 4 UIKitCore 0x169424 -[UIView _wrappedProcessTraitCollectionDidChange:forceNotification:] + 524 5 UIKitCore 0x927e8 -[UIView(AdditionalLayoutSupport) _withUnsatisfiableConstraintsLoggingSuspendedIfEngineDelegateExists:] + 96 6 UIKitCore 0x90cac -[UIView _processDidChangeRecursivelyFromOldTraits:toCurrentTraits:forceNotification:] + 212 7 UIKitCore 0x43d0 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1732 8 QuartzCore 0x97fc CA::Layer::layout_if_needed(CA::Transaction*) + 500 9 QuartzCore 0x1ceb0 CA::Layer::layout_and_display_if_needed(
Hello, Thank you for your response. However, you have not provided any documentation to demonstrate that you are currently authorized by the rights holder to represent the products or services included in your app. It would be appropriate to either submit documentation demonstrating this authorization or to remove any third-party Dead Walker imagery or likeness from your app icon and marketing screenshots. Once you've made the appropriate revisions to your app and its metadata, you can upload your new binary to App Store Connect. We look forward to reviewing your revised and resubmitted app. Best regards, App Review This is what I got from them.
Apple Rejected my Game which is published on my Google Play Account. It Requires me to Send the documentation to demonstrate that you are currently authorized by the rights holder to represent the products. I have sent them My Google Play Console Screenshot for the proof But they are requiring to submit documentation for that. Can you please guide me how can I prove them that I own that game in third party store? It has same package name and website/Privacy Policy links etc.
The situation: 1A) On last week our development team applied on-line for three idVendors with the format as the following: USB-VendorID: 547h(1351), 3488h(13448),4B4h(1204) Describe your apps: it shall be functional equivalence of existing Android-SDK for X-ray sensor-models:...with 15..25 text lines of the description below 1B) We received auto-reply, that we granted all the the entitlements. We've expected to have entitlements like approx like the these: <key>com.apple.developer.driverkit.transport.usb</key> <array> <dict> <key>idVendor</key> <integer>1351</integer> </dict> <dict> <key>idVendor</key> <integer>131448</integer> </dict> <dict> <key>idVendor</key> <integer>1204</integer> </dict> </array> 1C) Unexpectingly (for us) ASCII-strings-fragment from our iOS-target-binary com.rayence.dexta.driver (built with automatic signing; seemingly this shall be our actual granted prvi
Hey @caleach, Great question here! I am a very large user of the Download Sales and Trends Reports API as documented below and I make many requests every day. https://developer.apple.com/documentation/appstoreconnectapi/download_sales_and_trends_reports While I have not experienced what you have experienced (I am also not looking at the data for the same reasons), I have experienced times where the data coming from Apple has disappeared and the API has stopped making the data available even though it was previously available and the API returns different flavors of a 403 response with no data. When this has happened, I have taken all of my requests and logs, opened up a Feedback with Apple, and then eventually the team was able to resolve the reporting issue and data flowed freely for the dates that had disappeared. Sales Reports and Finance Reports can be tricky as well with all of the variables that go into what makes a unique purchase while also respecting the privacy of users. If you have questions about
I'm an iOS developer, and I've been testing our app in iOS 18.0 Beta. I noticed that there's a problem with the font rendering, and after troubleshooting, I've found out that it's caused by the removal of the PingFang.ttc font in 18.0. I would like to ask the reason for removing this font file and which font should be used to display Chinese in the future? My test device is an iPhone 11 Pro and the system version is iOS 18.0 (22A5297). I have also tested Beta 1 and it has the same issue. In previous versions of the system, the PingFang font is located in this directory /System/Library/Fonts/LanguageSupport/PingFang.ttc. But in iOS 18.0, the font file in this directory has become Kohinoor.ttc, and I've tested that this font can't display Chinese either. I traversed the following system font directories and could not find the PingFang.ttc font file. /System/Library/Fonts/AppFonts /System/Library/Fonts/Core /System/Library/Fonts/CoreAddition /System/Library/Fonts/CoreUI /System/Library/Fonts/LanguageSupport /Sys
The documentation states canMakePaymentsWithActiveCard is deprecated but will continue to work on Safari browsers. The suggested method to use applePayCapabilities is in Beta. This is confusing for a developer! which method should be used. I do not want to use a 'Beta' version in a Production environment. On the other hand, I also don't want to use a method which is deprecated. Any help or guidance would be welcome. Thank you
Odd bug. My unfortunate workaround is to use CIDetectorAccuracyLow, in the case that we're on an iOS simulator: #if targetEnvironment(simulator) let detectorAccuracy = CIDetectorAccuracyLow #else let detectorAccuracy = CIDetectorAccuracyHigh #endif let options = [CIDetectorAccuracy: detectorAccuracy] let faceDetector = CIDetector(ofType: CIDetectorTypeFace, context: nil, options: options) I don't love the solution, as it seems like the type of hack that will remain, forgotten, in the codebase, quietly confusing future developers, for the rest of eternity. But, low accuracy works on Simulator and I suppose it doesn't matter too much so long as production users still get the high accuracy detection.
I've updated my mac to Sequoia (MacOS 15) beta, my iPhone to iOS 18 beta, and Xcode to Xcode 16 beta. Only then, I realized I couldn't publish app updates with Xcode beta (error in AppStore Connect). I tried using the non-beta Xcode version but got Invalid Binary during app review: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. I really need to publish updates and I can't wait for September. I can't downgrade my devices because that would require me to erase both my Mac and my iPhone (for testing), which is not something I can do. Is there any option I didn't think about? How can I publish app updates in the current situation? It really should be more explicit before updating that you can't release updates with the beta versions...
There is a workaround, but you won't be able to use the debugger but hopefully your project will run. Go to: Product -> Schema -> Edit Schema -> Click Run Menu -> Select Info Tab -> Uncheck Debug executable
Xcode will build and analyze fine using the Debug build configuration but trying to use Analyze or Archive with Release configuration generates 3 errors: Undefined symbol: protocol conformance descriptor, Undefined symbol: type metadata accessor, and Undefined symbol: nominal type descriptor causing the linker to command to fail. The library is included and already linked and a previous version did not have the error so I think it's a code issue but not quite sure what it is or how to fix! The project/package can be found here: https://github.com/kudit/Device/tree/v2.1.17 (to reproduce, checkout this version and rename appending .swiftpm to the folder, then right-click to show package contents, open the Development folder and open the Xcode project there. It's done this way so the package can be imported and edited on iPad Swift Playgrounds)