’m experiencing two problems with the new Asset Library / Header and Search Results features in App Store Connect. These are search-results creative videos, rather than traditional App Preview videos. Videos fail processing or remain stuck Several uploaded videos initially appeared to be processing, then showed a red error: Your file couldn’t be saved. Try again. If the problem persists, contact us. The App Store Connect API reports FAILED with POST_PROCESSING_FAILED for affected assets. Some also have a failed poster frame. This has occurred across multiple localizations, including the default product page and a custom product page. Waiting another 10 minutes did not resolve the failed assets. One example uses: MP4 container with H.264/AVC video 3840 × 2560 resolution 30 fps 16-second duration No audio The videos play and decode successfully locally. The original exports were approximately 2 MB. To test whether aggressive compression was involved, I also uploaded a higher-quality 19.2 MB export using H.264 High profile, Level 6.0, 8-bit YUV 4:2:0 and BT.709 colour settings. That latest upload remains at UPLOAD_COMPLETE after 10 minutes, without a processed video or poster frame. It has not yet reported a failure. Are there additional codec, profile, level, bitrate or colour-space requirements specifically for these new search-results videos? Is there a known processing issue, or a way to obtain a more detailed failure reason? Failed assets cannot be deleted after review withdrawal The app version was submitted and then withdrawn. It is now Developer Rejected and editable. After removing the video placements from both the default and custom product pages, some unused assets still cannot be deleted from Asset Library. The API returns HTTP 409: STATE_ERROR.ASSET_PREVIOUSLY_SUBMITTED_FOR_REVIEW The asset was previously submitted for App Review and can no longer be deleted. Other assets deleted successfully, but these remain locked even though the submission was withdrawn and their placements were removed. Is this deletion restriction expected after withdrawal? How can failed, unused assets be removed or reset? Does this require Apple Developer Support to clear them? Has anyone successfully uploaded videos through the new Search Results creative feature, or encountered either of these issues? I tried to manually delete the video from appstore connect but got this warning:

I have seen a lot of tutorials on pytorchvision models being able to be converted to coreml models but I have not been able to google or find any tutorials for torchaudio models. Is converting to a torchaudio to coreml model even possible? Does anybody have links that show how to do it?

Given that I have a function that does not need to share and store state; should I use a static class/struct/enum to hold the function? I have read in many places that it is a bad design to use static functions to hold code, as static function do not adhere to the SOLID principles and are considered procedural code. Testability seems to be there as I can isolate the parent class with the injected static Enums by injecting mock static enums. E.g. I can encapsulate and have polymorphism by using protocols for static functions: Static Protocol Approach enum StaticEnum: TestProtocol { static func staticMethod() { print("hello") } } enum StaticEnum2: TestProtocol { static func staticMethod() { print("hello2") } } protocol TestProtocol { static func staticMethod() } class TestClass { let staticTypes: [TestProtocol.Type] init (staticTypes: [TestProtocol.Type]) { self.staticTypes = staticTypes } } class TestFactory { func makeTestClass() -> TestClass { return TestClass(staticTypes: [StaticEnum.self, StaticEnum2.self]) } } vs Object Oriented Approach class InstanceClass: TestProtocol { func staticMethod() { print("hello") } } class InstanceClass2: TestProtocol { func staticMethod() { print("hello2") } } protocol TestProtocol { func staticMethod() } class TestClass { let instances: [TestProtocol] init (instances: [TestProtocol]) { self.instances = instances } } class TestFactory { func makeTestClass() -> TestClass { return TestClass(instances: [InstanceClass(), InstanceClass2()]) } } The static version still allows for protocol polymorphism as you can have multiple enums adhere to the static protocols. Furthermore no initialisation is needed after the first dispatch call to create the static function. Is there any drawback in using the Static Protocol approach?