I am using the developer beta, and I made some simple code changes to my app. The changes do not include any new beta features. I am blocked from posting my update on the app store because of the following error. Error: Unable to Add for Review The items below are required to start the review process: New apps and app updates must be built with the latest public (GM) versions of Xcode, and the iOS, macOS, watchOS, and tvOS SDKs. Apps built with beta versions aren't allowed. Learn More This build is using a beta version of Xcode and can’t be submitted. Make sure you’re using the latest version of Xcode or the latest seed release found on the releases tab in News and Updates This has been discussed extensively in the past: https://forums.developer.apple.com/forums/thread/740853 And I already comtacted Apple Developer Support and received a generic response that did not address my issue at all. Response from support: Thank you for contacting App Review Support. We greatly appreciate the efforts of developers who
missing package product
42,936 results found
Post
Replies
Boosts
Views
Activity
These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. These forums have nothing to do with product support. I'd suggest you ask it over at the Apple Support Forums. or contact the manufacturer of the screen protector. We can't help you here. Thanks.
Several users are seeing a crash in a new app version that introduces the use of a UITabBarController. We haven't been able to isolate the crash to a specific user flow, device, or OS version. Fatal Exception: NSInternalInconsistencyException Inconsistency in UITabBar items and view controllers detected. No view controller matches the UITabBarItem ' title='Today' image= selected'. 0 CoreFoundation 0x83f20 __exceptionPreprocess 1 libobjc.A.dylib 0x16018 objc_exception_throw 2 Foundation 0x6de868 _userInfoForFileAndLine 3 UIKitCore 0x85c9d8 -[UITabBarController _viewControllerForTabBarItem:] 4 UIKitCore 0x85ca80 -[UITabBarController _tabBarItemClicked:] 5 UIKitCore 0x3fb31c -[UIApplication sendAction:to:from:forEvent:] 6 UIKitCore 0x785d18 -[UITabBar _sendAction:withEvent:] 7 UIKitCore 0x3fb31c -[UIApplication sendAction:to:from:forEvent:] 8 UIKitCore 0x3fb1f4 -[UIControl sendAction:to:forEvent:] 9 UIKitCore 0x3fb044 -[UIControl _sendActionsForEvents:withEvent:] 10 UIKitCore 0x787054 -[UITabBar _buttonUp:] 11 U
Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “ZigBank.app” bundle should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources. Apple Developer Relations I tried defining the string explaining why the app needs the data but the error persist. kindly see
@macmyday yes, in my case using the &ll=coords&q=description does not work since it plots the pin properly but when you tap the directions button, it moves the pin to the end of the driving route which couple be multiple miles away from the plotted coordinates. This might work for some who deal in locations that are nearby roads and the pin only moves a very small amount. I'm at a loss on how to get a response from Apple on this, I'm frustrated and based on some of the emails I am getting, so are my customers.
The Keras Embedding layer cannot be calculated on Metal because of the missing Op:StatelessRandomGetKeyCounter, as shown in this error message: tensorflow.python.framework.errors_impl.InvalidArgumentError: Could not satisfy device specification '/job:localhost/replica:0/task:0/device:GPU:0'. enable_soft_placement=0. Supported device types [CPU]. All available devices [/job:localhost/replica:0/task:0/device:GPU:0, /job:localhost/replica:0/task:0/device:CPU:0]. [Op:StatelessRandomGetKeyCounter] A workaround is to enable soft placement, but this obviously is slower: tf.config.set_soft_device_placement(True) Reporting it here as recommended by the TensorFlow Plugin Metal team.
Yes, you are correct about the non-admin user. In our case, I think it's either rare or the non-admin user shouldn't be able to update the app in the first place, so I think that's a fair restriction. We have looked into Sparkle, yes. It was one of the first things we suggested, but we had a few showstoppers: we have a cross-platform core in the app, and it takes care of the downloading, so we only need to apply the downloaded package and not manage the whole flow. That said, I DID study the heck out of it when you mentioned the executable, and that's where I saw the separate Installer app and it all began to make sense. I will indeed file an enhancement request - and thank you so much for the guidance.
Hey, Being on MacOS Beta, I would like to use Xcloud Cloud for submitting my App. It's an VisionOS App, but when I trying to build with Xcode Cloud, I get this error : Missing package product 'RealityKitContent' How can I resolve it ? Thanks, PAB.
Hi Quinn, I have tried the installation of my package on a fresh macOS 14.5 VM. Downloaded the package, disconnected the network. I could install and launch the application without any issue. I did not observe the firewall popup as well. I have tried following command on the app and bundle as well. These commands executed successfully. spctl -a -t exec -vvv codesign -vvvv -R=notarized --check-notarization On other machines, I could see the firewall popup for the same . Regards Prema
The most common cause of this is a missing intermediate. See Fixing an untrusted code signing certificate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
[quote='794989022, jalkut, /thread/759366?answerId=794989022#794989022, /profile/jalkut'] I'll try it in a VM first... [/quote] That’s the approach I recommend. See Testing a Notarised Product for an example of the process I use. I’ve seen a lot of folks suggest a lot of hacky solutions to problems like this. Frankly, I’m not a fan of those because they make it hard to tell whether the behaviour you’re seeing is what your users will see or just an artefact of your hackery. Ripley I say we take off and nuke the entire site from orbit. [dramatic pause] Ripley It’s the only way to be sure. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
[quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] Is there a way to do pinning without it going through SSL_CTX_set_custom_verify? [/quote] What pinning? In the example from my previous post, there’s no pinning at all. Rather, the program is just calling standard Apple APIs. [quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] Does NSPinnedDomains goes through SSL_CTX_set_custom_verify eventually? [/quote] As I demonstrate above, all TLS trust evaluation on our system goes through that call. [quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] It is a requirement … to not be intercepted by hackers and scripts to bypass this SSL pinning checks. [/quote] I see a lot of this and IMO this issue here isn’t your code but your security requirements. If someone attacking your app is able to intercept the code path between your app cal
Hi, I believe this question belongs here instead of Stack Overflow as SwiftUI + SwiftData is too new. I am using Model Context from a static Helper class: Class Helper { static let shared = Helper() var modelContext: ModelContext? } call to insert data on the 1st screen: Helper.shared.modelContext?.insert(item) Query Model declaration on the 1st screen: @Query private var products: [ProductModel] also autoSave turned to false: .onAppear{ Helper.shared.modelContext?.autosaveEnabled = false } periodically update data via a standard Timer object: for item in products { item.price = 500 } SwiftData works just fine in this 1st screen, but when we try to delete the Model and move on to next screen, we found out memory of the previous screen Model (ProductModel) in this case is still persisted and keep increasing! Eventually causing hang in the 2nd screen. Model deletion code in onDisappear of the 1st screen: .onDisappear{ try? Helper.shared.modelContext?.delete(model: ProductModel.self) try? Helpe
With connection of SSH via Jenkins 2.332.1 to the remote Macs, swift-package module crashes and leaves crash report on Console. Absolutely swift command itself fails. Filed https://feedbackassistant.apple.com/feedback/14285692 with the crash report created. Really hard to explain what happens exactly but seems like it is related to Xcode 16 beta (xcrun version 70) because the same problem never occurs on Xcode 15.4 (xcrun version 68).
Thank you @ssmith_c. I had followed the same steps before the forum post to diagnose the problem, and we both observed the same results. Unfortunately, I am having a hard time explaining this to the App review team. It has been two weeks. I requested code-level support, appeal, and rejection clearance, but these are not working as they should. At this rate, it may take a month for them to admit they are wrong, and a simple sorry shouldn't be an answer to the financial losses caused by the delay of the software to market.