missing package product

42,953 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode iPhone simulator not working
Hi, Sorry to hear you are having problems getting previews working. This error can often indicate a crash in your application when it launches, or a problem with the simulator. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for your app? If not, the best next step will be to file a feedback with diagnostics so we can take a look. 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
2w
iPhone Screentime feature makes little sense
What is the point of having the screen time feature if you can just disable it? Say for example I want to enable an app blocker on my phone in order to be more productive. It requires the passcode to enable it. But I can simply disable any blocker just by using the same passcode. Can Apple make it so that my app blockers work? So that if I just get bored I can’t simply disable it then go on YouTube and waste 2 hours of my life?
1
0
109
2w
Reply to Sequoia Group Container for Mac Catalyst Apps
There is a bunch of stuff to unpack here. First up, I’m gonna assume that you’re familiar with the backstory in App Groups: macOS vs iOS: Fight!. If not, read it now. In that I wrote: In Mac Catalyst things behave as they do on iOS. and I wasn’t kidding. A Mac Catalyst app should use iOS-style app group names (group.*), where those app group entitlement claims are authorised by its provisioning profile. Here’s an example of that: % vtool -show-build Test758358.app/Contents/MacOS/Test758358 … platform MACCATALYST … % codesign -d --entitlements - Test758358.app … [Key] application-identifier [Value] [String] SKMME9E2Y8.com.example.apple-samplecode.Test758358 [Key] com.apple.application-identifier [Value] [String] SKMME9E2Y8.com.example.apple-samplecode.Test758358 … [Key] com.apple.security.application-groups [Value] [Array] [String] group.eskimo1.test … % security cms -D -i Test758358.app/Contents/embedded.provisionprofile | plutil -p - { … Entitlements => { application-identifier => SKMME9E2Y8.com.exampl
2w
Reply to Sign with self-signed leaf certificate?
It seems you are on the right track but are encountering a specific issue with Xcode's handling of self-signed certificates. Here are some steps to troubleshoot and potentially resolve the problem: Ensure Certificate Trust Settings: Verify that both the root CA Dev Authority and the leaf certificate Testing 123 are trusted for code signing in Keychain Access. Open Keychain Access. Find Dev Authority, right-click, and select Get Info. Go to the Trust section and set Code Signing to Always Trust. Do the same for the Testing 123 certificate. Verify Key Usage Extensions: Ensure that the leaf certificate has the appropriate key usage extensions for code signing. Open Keychain Access. Find Testing 123, right-click, and select Get Info. Check under the Details tab to see if it includes Digital Signature under Key Usage and Code Signing under Extended Key Usage. Check Certificate Validity Period: Ensure that the certificate is valid for the current date and has not expired. This can be checked in the Details tab of t
2w
Unable to resolve CodeSign failure
Been using Xcode for a while with C++ set to sign locally (and objC before that). All worked ok. Looking to learn swift. Created a new, blank MacOS project, which starts compiling the template project (no code added yet by me) and fails with error Command CodeSign failed with a nonzero exit code. It's set to automatically manage signing. I have valid development certificates. I've read lots of forum articles etc but unable to resolve. Error description resource fork, Finder information, or similar detritus not allowed but it's exclusively apple code at this stage so would not expect any non-compliant files to be involved. Any suggestions as currently I've fallen at the first hurdle on my Swift journey? Full codesign command line below: Signing Identity: Apple Development: Steve Proctor (XXXXXXX) /usr/bin/codesign --force --sign xxxxxx -o runtime --entitlements /Users/steve/Documents/dev/t1/Build/Intermediates.noindex/Previews/macos/t1/Intermediates.noindex/t1.build/Debug/t1.build/t1.app.xcent --timestamp=none
4
0
283
3w
Reply to Can't figure out why Toolbar is not conforming to view
Welcome to the forum. I tested your code (after completing missing parts and removing reference to unknown structure) and it works OK, both with Xcode 16.0ß2 and Xcode 15.0.1. Are you sure you have declared var as State vars ? Have you declared dismiss ? Aren't you missing a closing curly bracket somewhere ? Where exactly do you get the error ? Please show the exact and complete code, as well as your configuration (Xcode version, system version…) Here is the complete code I tested: struct ContentView: View { @State var companyName: String = @State var role: String = @State var location: String = @State var yearlySalary: Double = 0 @Environment(.dismiss) var dismiss var body: some View { NavigationStack { Form { TextField(Company Name, text: $companyName) TextField(Role, text: $role) TextField(Location, text: $location) TextField(Yearly Salary, value: $yearlySalary, format: .currency(code: USD)) .keyboardType(.decimalPad) } .navigationTitle(Add Application) .navigationBarTitleDisplayMode(.
2w
Are Deep Links on Custom Product Pages working?
I created a new Custom Product Page with a Deep Link, according to the WWDC '24 session What's new in App Store Connect, and everything has been approved, but the Deep Link does not appear to be working. Is this feature fully operational yet? When the app is installed via this product page, the user should be directed to a specific page in the app, however this does not happen. It does work properly when installing directly via the Deep Link This is the link to the product page: https://apps.apple.com/app/bills-to-budget/id1636872963?ppid=ff079a93-be32-43fe-a88e-ad97a68ff725
6
0
890
Jun ’24
iOS 17: Cannot find type 'PhotogrammetrySession' in scope (Object Capture)
Dear all, I'm building a SwiftUI-based frontend for the RealityKit Object Capture feature. It is using the iOS+macOS (native, not Catalyst) template on Xcode 15.1. When compiling for macOS 14.2, everything works as expected. When compiling for iPadOS 17.2, I receive the compiler error message Cannot find type 'PhotogrammetrySession' in scope. As minimum deployment target, I selected iOS 17 and macOS 14 (see attachment). An example of the lines of code causing errors is import RealityKit typealias FeatureSensitivity = PhotogrammetrySession.Configuration.FeatureSensitivity // error: Cannot find type PhotogrammetrySession in scope typealias LevelOfDetail = PhotogrammetrySession.Request.Detail // error: Cannot find type PhotogrammetrySession in scope I made sure to wrap code that uses features unavailable on iOS (e.g. the .raw LOD setting) in #available checks. Is this an issue with Xcode or am I missing some compatibility check? The SDK clearly says /// Manages the creation of a 3D model from a set of i
2
0
689
Jan ’24
Reply to Unable to resolve CodeSign failure
[quote='794608022, swp336, /thread/759022?answerId=794608022#794608022, /profile/swp336'] I'm assuming there's something about the setup on my machine that's causing the newly minted template files created by Xcode to trigger the one of the error conditions. [/quote] Right. I’m hoping that, once you track down the identity of this ‘detritus’, it’ll be clear where it’s coming from. For example, I vaguely recall seeing a problem like this where the developer had their build products on iCloud Drive, and iCloud Drive’s extended attributes were causing this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Navigation Controller PushViewController no longer calls ViewDidAppear/will
Hello,Switching from iOS 12 to 13 caused that our views no longer function correctly. This is due that when NavigationController.PushViewController is called, it no longer calls ViewWill/DidAppear and their opposite Will/DidDisappear. I have read the iOS 13 release notes and saw the video and everyhing that has been mentioned regarding these events is directed at presentation of card-like modal views, which has nothing to do with the PushViewController function. In iOS 12 the PushViewController would navigate to a new ViewController and therefrom I could click on the default back button to navigate back to the previous one and it called the relevant lifecycle events. That is no longer possible with iOS 13.The way our Views are constructed are quite old fashioned. We use XIB files to construct our Views and furthermore, this is done programmatically and the language used is Objective-C.Most of our views are based on UIViewControllers, UITables and UITableViewController.Now one thing I do know is that UITableVi
11
0
7.8k
Oct ’19
App Store Notification
Hello, I am developing App Store Server to Server Notifications. (The app has already been deployed and is in operation.) Test notifications in both the Sandbox and Production environments have been working correctly. Additionally, I tested in-app purchases using a Sandbox account and confirmed that the server notifications are received. However, when an actual purchase is made in the live app, the server notifications are not received. Please provide the possible causes and solutions for this issue.
1
0
241
2w
AVSpeechSynthesizer is broken on iOS 17 in Xcode 15
When you initialize AVSpeechSynthesizer as View prorety in SwiftUI project in Xcode 15 with iOS 17 simulator, you get some comments in console: Failed to get sandbox extensions Query for com.apple.MobileAsset.VoiceServicesVocalizerVoice failed: 2 #FactoryInstall Unable to query results, error: 5 Unable to list voice folder Query for com.apple.MobileAsset.VoiceServices.GryphonVoice failed: 2 Unable to list voice folder Unable to list voice folder Query for com.apple.MobileAsset.VoiceServices.GryphonVoice failed: 2 Unable to list voice folder When you try to run utterance inside a Button as synthesizer.speak(AVSpeechUtterance(string: iOS 17 broke TextToSpeech)), you get endless stream of warnings that repeaths on and on in console like this: AddInstanceForFactory: No factory registered for id F8BB1C28-BAE8-11D6-9C31-00039315CD46 Cannot find executable for CFBundle 0x600003b2cd20 (not loaded) Failed to load first party audio unit from TextToSpeechMauiSupport.framework Could not instantiate audio unit. Error=Er
32
0
1.0.0k
Sep ’23
Xcode fails to start Loading a plug-in failed.
Using the Apple Store, I installed Xcode 12.0. However instead of starting, the application displays a small window with a yellow triangle ! stating that the plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled. I trashed Xcode and emptied the trash can and reinstalled, same issue. Any assistance greatly appreciated. Carl
20
0
18k
Sep ’20
Info.plist entry for watch-only app on non-exempt encryption?
I am developing a watch only app, and want to get rid of confirming compliance to non-exempt encryption every time I upload a new build App Store Connect for testing. With a regular iOS app, I can set the App Uses Non-Exempt Encryption key of the Info.plist file of the iOS target to 'No', and that handles this for me. I am trying to do the same with my watch-only app, but it has no effect. I have tried adding it to both the WatchKit extension's and the watch app's 'Info.plist' respectively. It is rejected by App Store Connect when uploading, if the key is added to the App target. It is, however, accepted when the key is added to the WatchKit extension. I still need to explicitly confirm compliance in App Store Connect to make the app available for testing though, so it seem to have no effect. I feel like I am missing something obvious. Any advice or thoughts?
2
0
1.1k
Jul ’20