We are unable to process your request

Just following up as I am still in need of a resolution. Quinn was handling this from the code/operation side, so wasn't really tracking this thread. However, there are two common issues here from the framework usage side. The first one is that by calling scheduleAppRefresh at app launch, you're unintentionally preventing your own task from reliably firing. Basically, here is what happens: Your app stopped running at some earlier point in the day for normal reasons (free up device memory, etc.). It came time to run your task, so the system launched your app. Your app started up, you configured the background task framework, then ran scheduleAppRefresh. scheduleAppRefresh scheduled your task to run 10 mins from now. Duet (the daemon that supports the background task framework) assessed your task state, determined that you had not tasks ready to run (since the next one isn't runnable for 10 min...) and suspended your app. Secondly, I think you probably want to use BGProcessingTask, NOT BGAppRefreshTask. These t

@neil95 This is great!! Thank you so much for this. I see you included a link to the code. I would recommend to zip it and upload it into the bug itself. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. I'll keep an eye out for issue and fix. Albert Pascual
  Worldwide Developer Relations.

Hi @arthurfromberlin Thanks for the response and detail. Can you attach a sysdiagnose to the feedback request? You can find instructions on how to capture a sysdiagnose here. The issue is tricky to debug since it only happens via TestFlight so the logs will help.

They are known to use an iPad to test the iOS app you submit regardless of the intended platform. I would ask them to send me a screen-capture video. But I don't know if they comply. I don't remember if they have ever sent me a screen-capture video. It's true that they sometimes go terribly wrong. Back in July, they claimed that nothing had happened in making an in-app purchase. It has turned out he or she failed to scroll down further and tapped an image, not a button. The same reviewer also claimed that a user would not be able to request customer support at our web site when in fact it was just the matter of scrolling down further, again, to find a comment box. I would send them a screenshot after circling the button they are supposed to tap to make sure he or she is not off the track. It's true that I sometimes make a mistake and deserve to get my software submissions rejected. But reviewers collectively make more mistakes than I do. I say they are wrong 2/3 of the times.

I have updated the system to iOS 26.1 beta 3, and I am still unable to connect to Bluetooth. Everything is the same as before. I have submitted feedback using the same Apple ID on the phone experiencing the issue, and I included the system logs and Bluetooth logs. Please investigate as soon as possible.@Engineer

@hxsmart was able to provide me with an example project attached to a code-level support request, so I can see that you are building a closed source framework, where you're distributing a binary to your clients, rather than distributing source code. In your project, you have a precompiled .framework file, with Objective-C source code. I don't readily have a version of Xcode 13.2.1 to use to see the compilation error in that project myself, so are you able to provide the text of that error message here? — Ed Ford,  DTS Engineer

Thank you for your answer. So, having talked to App Review about this, the basic answer I have currently is that we don't currently support 3rd-party App Extensions on the iOS App Store. The framework itself is built to work across all of our platforms and is public (which is why new functionality is added that's available on iOS), however, the App Store policy has not changed. If you haven't already, I'd appreciate you filing a bug on this and then posting the bug number back here. It sounds like you're trying to create extensions that are specifically for your apps’ usage, and that's a distinct use case that we need to more actively consider. Clarifying a few details, I think the difference here is basically a quirk caused by slightly different handling paths: The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other times it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: For many years, the ap