“testflight the requested app is not avaliable”

@MetaImre Entitlement com.apple.developer.mail-client not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. What is the type (Development, Ad hoc, Distribution) of your provisioning profile? The com.apple.developer.mail-client entitlement is only supported for apps built for Development and Distribution.

Hello! We still cannot upload an update of the AppClip, since the form is KO, when trying to setting the title, the subtitle or the image of the AppClip. When tapping the button save, it turns red with an exclamation mark. And when looking at the Inspector, we can see the error Failed to load resource: the server responded with a status of 409 (), on /iris/v1/appClipDefaultExperiences. We have no news on the bug ticket. Could you please help us?

this forum is for questions related to developing software for Apple platforms. your question would be better asked at https://discussions.apple.com

Hello, Can we have an update on the progress ? It's been several months, we're now at Xcode 26.5, and still no fix in sight for this issue. We are still stuck on Xcode 16 for any kind of device debugging and we are not alone...

I suggest you get in touch with the maintainer of the project you cite. I tried building it, but it went off into the weeds when trying to parse the USB descriptor of three different UVC cameras. Have you found the code which enables/disables the zoom control? That should give you some clue. You said tt seems that the zoom control commands are not successfully sent or recognized by the camera - which is it - sent, or recognized? Does your code send the command? How? (show code). Does the camera or the USB stack return an error, and if so, which error? You're not giving us much to go on here.

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

As a workaround, the mail composer is no longer presented fullscreen, allowing it to be dismissed by tapping outside the mail window. An updated version of the app has been submitted for review following user reports.

Dear bradley_7, 10-bit UVC is not supported on iPadOS nor macOS, and might not be officially supported in the UVC specification. Thanks for asking, Richard Yeh  Developer Technical Support

I think we finally found a way to reproduce the issue in a reliable way (a stress binary which mixes random file creations, APFS transparent compression, and extended attributes adding and removal, all this mixed in a ton of different threads). A kernel deadlock (similar to the real one we have) usually happens after 15-20 minutes of this stress binary running, without needing any Endpoint Security client to be registered (and without needing root privileges): it works on a fresh clean VM. We reproduce it on macOS 15 and macOS 26, up to 26.4 (not included) — the tool ran for hours on this macOS version without any repro. So I believe the issue was actually fixed starting from 26.4. We are continuing our test to confirm that. We can add this tool in the feedback / DTS ticket if needed, but if the bug is fixed, I guess Apple kernel team figured out a way to reproduce it themselves.

Hello @sheikhbayazid This is a great start! While we are unable to share exactly how Apple achieved this in the Music app, you might still find the following helpful: [quote='820932021, sheikhbayazid, /thread/820932, /profile/sheikhbayazid'] Should this be a custom container instead of fullScreenCover? [/quote] You might be looking for a sheet. Users can swipe down to dismiss a sheet interactively by default. .fullScreenCover has no built-in-swipe-to-dismiss, you must provide an explicit mechanism, like a dismiss button. For more information on Sheets see https://developer.apple.com/design/human-interface-guidelines/sheets [quote='820932021, sheikhbayazid, /thread/820932, /profile/sheikhbayazid'] How would you support both new and older iOS versions? [/quote] Configure the Xcode project to support the intended lowest OS version, then use conditionals to handle differences between iOS versions with availability checks such as #available if #available(iOS 18.0, *) { // Content in iOS 18.0 and