missing package product

Hello, I'm using MulitpeerNetworking in an App for Long- and Tripplejump (JumpControl). A camera is located close to the take-off-board and is controlled by another device connected via Multipeer-Networking-API. Usually this works fine even for several meters distance. In real events, when there are more other devices around the connectivity becomes more and more unstable. Connection is lost or cannot be established again. Is there a way to make this connection more stable or at least get more information about the circumstances that makes it unstable? Is there a possibility to connect two iOS-Devices via cable-connection to improve stability?

[quote='869055022, Yvan.d, /thread/809534?answerId=869055022#869055022, /profile/Yvan.d'] could this type of Keychain item design … lead to the kind of attribute inconsistency [/quote] It’s certainly possible. My experience is that there’s a lot of really bad keychain code out there )-: That’s partly because the SecItem API is way more subtle than people think, and partly because Apple’s initial documentation and sample code for it was… well… less than ideal. Moreover, the keychain is a persistent database where it’s important to not lose user state. So if your app has been around for a while, debugging a keychain problem means that you have to understand your current code and all the previous iterations of that code. There’s a few ways to tackle a problem like this: You could use source control to resurrect old versions of your keychain code, put all that code in a test app, and then try it out. You could use telemetry to understand the state of your users’ keychain items in practice. You could do w

My response on that other thread still applies here. Can you reproduce this on a clean machine? Or are you only seeing this on specific Macs? Specifically, I recommend that you run this test: Install your target OS in a VM. Take a snapshot of the clean VM for the benefit of future tests. Install your product as a user would. Update your product as a user would. Does that reproduce the problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Actually it's even worse. I submitted the app together with the in-app purchases. You reject the app and I answer before resubmitting. On the next review the app is rejected again because in-app purchases are missing. I thought I made a mistake in the beginning but you did. I cannot reassign the in-app purchases. they are waiting for review and will be rejected eventually because the app is missing, the app is rejected because the in-app purchases are missing. They are stuck in limbus.

Hi Ed, Thank you very much for your previous guidance. Our current app requirement is to allow users to run a Shortcut, share an image to our app, and then immediately receive some chat-based suggestions after we process the image. When using App Intent, I noticed that we cannot process the image directly within the invoked UI. It appears that this is restricted by Apple’s privacy protections—any attempt to handle the data immediately results in the background privacy indicator showing a blocked status. Therefore, App Intent does not seem to meet our need to process user-provided images directly. Following your advice, I added an Action Extension to the project. This successfully adds our app to Shortcuts as an available action. However, when I try to use the “Share with App” feature from the share sheet, our app still does not appear in the list. The only options shown are: Notes, Health, Reminders, and Freeform. Could you help us understand why our app does not show up in the “Share with App” menu, even tho

I am having the same exact issue. I don't want to miss the deadline!

Please file an enhancement request using the Feedback Assistant so that your request can be seen by the appropriate decision makers. If you file the request, please post the Feedback number here so we can make sure it gets routed to the right team. Please note that filing an enhancement request does not guarantee Apple will add any requested functionality to Apple products in the future. However, with that said, filing an enhancement request is a good way to get your ideas in front of the folks who make decisions about that sort of thing. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

I built Dext with a development ID and successfully re-signed and notarized it. This time, I only notarized the Driverkit, and plan to do the installer app later. Here are the steps I tried: Signed the build using Apple Development in Xcode Re-signed the build product Zipped the build product Notarized using xcrun notarytool submit, which returned Accept. Below is a sample re-signing command. codesign --sign $CODE_SIGN_IDENTITY --entitlements --options runtime --verbose --force build/Release/.app I'll probably need to eventually create an installer app and notarize it, but I think I've temporarily resolved the recent issue of not being able to sign with a Developer ID in Xcode. If you have any issues from an engineering perspective, please let me know.