“testflight the requested app is not avaliable”

@Manuel_Apps I am in the same situation... the current version of my app on the App Store is defunct for iOS 12 people. I am now working on a build with target iOS 15. As soon as it’s submitted and released I am planning on making the broken release unavailable. This way iOS 12 users have to uninstall the broken version so they can reinstall the (still working) version before that. I totally agree with you. I wish Xcode 16 (the first Xcode that did not support iOS 12 anymore) would have prevented me from building the app with the unsupported target. Instead it was waved through without warning. Yes, the Xcode support page said it didn’t support iOS 12, yet there was no hard stop. I was not aware I was sitting on a time bomb for at least 1 year. I thought only debugging was not supported but building was -- because it worked. The broken app happened a few days ago when my customer was holding an event in front of an audience, some of which

Thanks @Manuel_Apps and @BioDranik for your metoo’s. In the meantime I have received a response from dev support. They gave me the same answer that is found in the thread pointed to by @DTS Engineer . This is the tech part of the answer: When you submit to the App Store, Apple modifies your binary. They strip your signature, encrypt the binary and re-sign it. This encryption alters the Mach-O file's page alignments and load commands. Nothing I can do about that. I’m fine with progress but I wish Xcode would have somehow prevented me from using the unsupported deployment target. Ever since Xcode 16 (which also does not support iOS 12) I thought my target was ok. So I will bump the target to iOS 15 (for now, in the future possibly higher). Since my app in the App Store is defunct for iOS 12 users I will upload a build with target iOS 15 and then mark the broken build as unavailable (App Connect > Pricing and Availability). This way the legacy users will get the la

That's the way the world works today. ChatGPT was successful, so now they have de-facto control over the acronym GPT. App Review thinks that end users would be confused and think your app is associated with ChatGPT. Apple knows how people think. Just change the name. And make sure to do a trademark search first.

Thanks to all the reports and from different countries in the EU! I would encourage you to file a FB number so its a bug for that team using https://developer.apple.com/forums/thread/712889 And as @App Store Connect Engineer asked, please include screen recordings and HAR logs. Thanks again, Albert Pascual
  Worldwide Developer Relations.

@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