“missing package product”

The initialization of your MapKit request will receive an error with a status field, and there is an enum you can check to see the reason — TooManyRequests. Are these limits strict daily hard limits that should never be exceeded in production? From a code perspective, you should design your code with good error handling to gracefully handle the TooManyRequests error state, in addition to the other errors in the ConfigurationErrorStatus enumeration. If you're asking this question from more of a business planning angle, see below. Is there an official pricing model for usage above the free quota, or do we need to contact Apple to request higher limits? If you start running out of the daily quota, the next thing you'll need to do is to fill out the increased capacity form and go from there. — Ed Ford,  DTS Engineer

Thank you for the replies and for sharing your experiences. Since this is our first app submission, we just wanted to double-check that our App Store Connect metadata and review information are complete and clear for the App Review team. The app is a simple B2B ordering tool for registered wholesale clients and includes reviewer login instructions in the App Review Information section. If anyone from the App Review team happens to see this thread and notices anything missing in our submission, we would really appreciate the guidance. App ID: 6759172913 Thank you again for your time. Kindest regards Jose Rodriguez

FSEventStreamRef reports changes on a directory. I have some comments below, but FSEvents are a complicated topic in their own right. If you've got a product that's actually focused on monitoring and updating a large hierarchy (this isn't actually all that common), then it might be worth starting a new thread that's focused on those issues. Does it work on file reference URLs? No, it takes the opposite approach, which is basically force you to iterate the hierarchy until it happens to stabilize. The core underlying issue here is that the file system doesn't restrict how it's modified and the API it provides only provides a picture of a particular instant in time. That is, when you ask for a directories contents what you actually get is the contents at that instant without any guarantee that they're still the current contents. Most of the time the contents don't change fast enough for that to matter, but in a frequently changing directory the past and now can diverge VERY quickly. You'll note that FSE

Thanks for the post and good question that is good to explain the privacy policy. Apple enforces a strict security architecture called App Sandboxing, which isolates apps from each other and from the core operating system to protect user privacy. Because of this, Apple does not provide developers with the APIs (application programming interfaces) required to perform any of the tasks you mentioned. Third-party apps have absolutely zero read access to the iOS Messages app database. You cannot read, export, or save a user's SMS or iMessage history. In some cases allows apps to read text messages in only two highly restricted scenarios like an app can act as a spam filter. However, it can only see incoming messages from unknown numbers, and the system does not allow the app to save or export those messages. Just like SMS, the native Phone app's call history is completely locked down. A third-party app cannot read the incoming, outgoing, or missed call logs. Hope this helps. Albert Pascual
  Worldwide De

From your answer, I realise I was overlooking the obvious: after doing the work in the fast temp directory, I then need to create a second temp directory on the slower destination volume using URL(for: .itemReplacementDirectory…), copy the file across, and then use replaceItemAt from there. Sure, that makes sense. I think this is also one of those cases where the broader context of your app and user base is really a really important factor. Some apps (smaller documents, more consumer focused) should do their best to hide all of these details from the user, as they're not really useful/relevant and they just end up creating noise. Other apps (larger documents, more expert focused) benefit from making this visible to the user, as it lets them understand what's going on both to correct any problems (for example, space loss due to save failures) and take advantage of the data you have for them (for example, failure recovery). So any attempts to use that will continue to fail until the kernel (?) has fini

Honestly, I’m not sure what’s going on here. None of this sounds at all familiar. I’d like to get a copy of your installer package so that I can poke at it myself. Can you share a link to a download site here? [1] If not, you can file a bug and attach it to your bug report, and then post the bug number here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Posty your link in the clear; see tip 14 in Quinn’s Top Ten DevForums Tips.

Update: still waiting for review, just checking if there might be anything missing in our submission metadata. Thank you! kindest regards Jose Rodriguez