“testflight the requested app is not avaliable”

@hiauhong The groups that contain reminder lists To fetch all calendar list, create an instance of EKEventStore, then use its calendars(for:) instance method of with a reminder entity type: let eventStore = EKEventStore() let list = eventStore.calendars(for: .reminder) The sections inside each reminder list (available since iOS 17) After you get a list of calendar lists available on your device, iterate through the list: for item in list { .... } then use the list identifier of each list to fetch their reminders: let identifier = item.calendarIdentifier if let calendar = eventStore.calendar(withIdentifier: identifier) { let predicate = eventStore.predicateForReminders(in: [calendar]) // Do the fetch. } I forgot this one: 3. The subtasks of the reminder. EventKit doesn't have an API that allows you to retrieve the subtask of an EKReminder object. If you would like for Apple to consider adding support for such features, please submit your suggestion request via Feedback Assistant (https://feedbackassis

I would like to kindly ask for your assistance regarding our TestFlight external testing review. We submitted 1.0.1(1) build for external testing on March 17, and it has now been over two weeks, but the review has still not started. This delay is affecting our testing schedule. Could you please help check the status of this submission and assist in moving the review forward if possible? We would greatly appreciate your support.

My app has the phrase GPT in it as it is an app that runs private open source offline AI models (for free) on the iPhone. The app is called LiberaGPT. What does 'to have the phrase GPT' mean? Explain to the reviewer as if you talk to your grandparent. If you use the phrases you have invented for yourself, you are partially the source of confusion. Do you have the word 'ChatGPT' in your app description box? Or do you use it as one of the keywords? And you don't mention 'ChatGPT' over your meta screenshots? If you do, it's you causing the problem. If you don't, then you have to convince the reviewer somehow. If you take it to the Appeal Board, that will probably put an end to your app. I had a desktop application back in 2011. Its name starts with 'Rip.' And the reviewer rejected it by saying Illegal file sharing. He or she gave me another rejection reason, which said that it didn't read a DVD disc or a VOD file. The problem was that I never said anything an

@seokurdu I would recommend to go over the app review design part to make sure your app provides enough functionality: https://developer.apple.com/app-store/review/guidelines/#design I'm sure other experts will jump into this thread to provide better guidance and better resources. Albert Pascual
  Worldwide Developer Relations.

Hi Travis, Thanks for your reply. I have tried using the zoom navigation transition, but I could not get a proper hero-style animation between the mini player artwork and the full player artwork. As you mentioned, using a sheet does not fully solve the problem either, since it does not behave like a true full screen experience. Right now, I am mainly struggling with: Swipe to dismiss on a full-screen player or a full-screen sheet that has swipe-to-dismiss behavior A smooth hero transition from the mini player artwork to the full player artwork Do you have any suggestions on how to approach this, or how to get closer to the Apple Music behavior? Here's my example code: struct ContentView: View { @Namespace private var namespace @State private var isFullPlayerPresented = false var body: some View { TabView { Tab(Home, systemImage: house) { Text(Home) .frame(maxWidth: .infinity, maxHeight: .infinity) .background(.green) } Tab(Library, systemImage: rectangle.stack.fill) { Text(Library)

I cannot find anywhere in the documentation how to invalidate an FSItem. What are you actually trying to do here? It seems to be cached indefinitely or am I missing something? In terms of caching, reclaimItem is the point where you'd typically drop all of your references to the FSItem, since that's the point where the larger system no longer has any reference to the object. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Hi @DTS Engineer, hi @App Store Connect Engineer, Thanks both of you for following up! I have a ticket open since this morning with the ID 102858856688. I can confirm the error persists to this very moment. Two apps worked (one update, one new submission), one consistently does not, giving the DAC7 compliance error. Again, it does not make sense that compliance triggers app-specific errors. I am happy I am not fully blocked in at least releasing updates to my apps, but still, this is quite bad, and I would be happy for some help. Btw., posting here works only 50% of the time. I often get Your post couldn’t be saved. Please try again in a few minutes. and then my post is just lost. It comes from your backend. Some weird glitches right now. Hope this gets more stable again soon. Best regards, Robert

Lately we are seeing reports from the market that on M5 Macbooks and A18 Neos the system will kernel panic using our solution, even though it never happens on M1-M4 and no significant code changes were made in the mean time. All crashes seem to be related to an internal double free in the kernel: Have you filed a bug on this and, if so, what's the bug number? Can you tell us please if this is a known problem and if there's a workaround or what can we do to narrow it down? I'm need full panic logs to be sure (that's why I asked about the bug) but, yes, I suspect this is a known issue (r.172793638). __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Are there any known issues within the 'EADemo' app that we should know about/and/ or need to fix? Not that I'm aware of, but the sample is quite old and, to be honest, I don't think it's been looked at closely very recently. Does Apple have any other EA example application? No, I'm afraid not. One comment here: Attempting to send either a string or hex packet results in nothing being sent. The app does not appear to attempt to send a packet when these are pressed. Two things I would try here: Hard coding some direct sends. If those are reaching your accessory, then the issue is probably that the interface code itself is broken. Try sending more data. NSStream is also quite old and it's possible that we're (incorrectly) buffering the data instead of sending it immediately. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

but my auto-renewable subscription does not appear in the selector The subscription appears in the “In-App Purchases and Subscriptions” section when its status is Ready to Submit. If the status of your subscription is Missing Metadata, complete any missing information such as price or localization for the subscription group display name. For more information, see submitting In-App Purchases, see In-App Purchase statuses and Submit an In-App Purchase..

Thanks for the detailed issue report. I am experiencing the exact same issue with the same scenario (I invited myself as a tester and redeemed on a device using a personal Apple ID, now I can't re-invite myself to the same app using my work Apple ID even if I delete myself from all testers.) Waiting 90 days to resolve this seems unreasonable especially as it's unclear this would actually resolve the issue. I can't figure out any other action I can take inside TestFlight that would allow me to generate a new invite not locked to the old tester Apple ID. As the old feedback here has appeared to have been ignored for over a year, I have opened a new feedback at FB22398790 to attempt to re-escalate this issue.