Sure thing, I did it at the same time I made this post: Jun 15, 2024 at 6:34 PM – FB13918574 Developer Account: Horsie in the Hedge Limited App Name: Werble: Photo & Video Animator. App Id: 966009633 Thanks for your help.

Same here.

Dear Jason, I just have to chime in to voice our displeasure at the insanely short notice of this change. One month's notice for a change of this magnitude is very short considering that you're asking us to implement an entirely separate and secure hosting setup, test it and ensure it is ready for full scale production in four weeks, despite an already packed development schedule (for many of us I'm sure). ODR is too limited an alternative for many people to plug into and as others have pointed out does not have the security of SKDownload. I submit that 6 months is a more reasonable timeframe for such a grand change and ask you to pass it up the chain. Thank you.

@tpian928 did you get this functioning in the end? I see no real difference between your code and mine (although obviously more code is needed to generate a live photo), but it's still not functioning on iOS 15.1. On attempting to add the paired video and photo to the library we get a non-nil assetPlaceholder but the completion handler is not called by [[PHPhotoLibrary sharedPhotoLibrary] performChanges:completionHandler:] and we see errors like this in the log: 2021-11-09 13:54:48.122501+0000 REDACTED[480:23929] [error] error: XPC: synchronousRemoteObjectProxyWithErrorHandler encountered error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service created from an endpoint was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003." UserInfo={NSDebugDescription=The connection to service created from an endpoint was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003.} 2021-11-09 13:54:48.122518+0000 REDACTED[480:23913] CoreData: XPC: XPC connection was invalidated CoreData: error: XPC: synchronousRemoteObjectProxyWithErrorHandler encountered error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service created from an endpoint was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003." UserInfo={NSDebugDescription=The connection to service created from an endpoint was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003.} 2021-11-09 13:54:50.796119+0000 REDACTED[480:23913] [tcp] tcp_input [C1.1:3] flags=[R] seq=1735303655, ack=0, win=0 state=LAST_ACK rcv_nxt=1735303655, snd_una=3874278604

Our feedback report FB9692102 changed to indicate: Recent Similar Reports:Less than 10 Resolution:Potential fix identified - For a future OS update

Our feedback report FB9692102 changed to indicate: Recent Similar Reports:Less than 10 Resolution:Potential fix identified - For a future OS update

We're still having these issues. Has anyone found a solution, or are we waiting on a fix from Apple? We've certainly done our part with bug reports and sysdiagnoses, but haven't had any response to our report.

We're in the exact same boat as you guys. Immensely frustrating. We only saw the issue rear its head after the public release of iOS 15 because the statistics were such that we just didn't see it until the whole world started upgrading. Bug report filed with sysdiagnose since 10th October but no response as yet. My advice is to file bug reports as soon as you can, with sysdiagnose. The more people flag this, the more seriously Apple will take it. FWIW we started referring affected users to our beta version. For some reason, even with a code-identical build, people seem to have better luck in the beta version, presumably because of different servers/infrastructure.

Did you ever get to the bottom of this? We see the same error on iOS 14.8 iPhone XS Max.

We solved the problem by following advice from https://developer.apple.com/forums/thread/662947 There appears to be a bug in Xcode 12 where enabling code coverage support causes bitcode recompilation failure. We don't need the code coverage support anyway. 1) In Build Settings 'Apple Clang - Code Generation' set 'Enable Code Coverage Support' to NO in the project. 2) In Build Settings ensure that '-fprofile-instr-generate' is not set in 'Other Linker Flags'. With those steps complete, archiving and exporting with bitcode recompilation worked under Xcode 12.

We observe this same error when exporting ad hoc or development builds in Xcode 12 with bitcode recompilation enabled. We suspected an issue with a third party framework, so we created a version of our project without any external dependencies (the only frameworks we import are Apple's own e.g., StoreKit, CoreImage...). The problem persisted. There are no problems using Xcode 11 - we can export the archive with bitcode recompilation and App Store processing works fine. Of course, we can't use any iOS 14 APIs with Xcode 11. Our only option appears to be to disable bitcode in our project if we want to use Xcode 12. Given that we see failure when using only Apple frameworks, we believe that this as a bug that Apple needs to fix.

I'm also a bit baffled as to why there aren't more reports about this. My app utilizes IAP content lightly, but there must be developers whose business model heavily depends upon it - surely they must be suffering? /nods head Do your failed downloads eventually succeed if you retry multiple times? I'm thinking about this from a customer support perspective. If a failed download will eventually succeed then at least I can suggest that a customer should keep retrying. The problems do seem intermittent - retrying (potentially multiple times) can result in success. We do recommend people reinstall (to force the caches/ directory to be purged) - thinking about adding a function to purge the caches directory if no downloads are in progress! A question: do you see tremendous lag in the finishing and removal of transactions from the payment queue? Pre iOS 14 we would batch finish transactions and see the paymentQueue:removedTransactions: method called very rapidly. Now it is painfully slow and can take up to a minute to finish say 30 transactions (we have a lot of in-app purchases).

These issues persist in 14.2 beta.

And now it seems like there are additional StoreKit / App Store server issues making further testing difficult: SKPaymentQueue: 0x2826811c0>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "Unhandled exception" UserInfo={NSUnderlyingError=0x282b94180 {Error Domain=AMSErrorDomain Code=301 "Invalid Status Code" UserInfo={NSLocalizedDescription=Invalid Status Code, NSLocalizedFailureReason=The response has an invalid status code}}, NSLocalizedFailureReason=An unknown error occurred, NSLocalizedDescription=Unhandled exception

Unfortunately I'm still seeing issues in iOS 14.0 GM seed. I'm using a fresh install to avoid issues from prior beta installations. Can anyone else confirm this? I'm still seeing paymentQueue:updatedDownloads: called with finished downloads with nil/zero-length download.contentURL or with no content at the URL. Sometimes this method gets called twice, the first time there is no content and the second time there is content. I have heard nothing direct from Apple, but I note that the status of my feedback report has changed. 'Recent similar reports' is marked as 'less than 10', and resolution has changed to 'potential fix identified - in iOS 14'. I am confused as to how there can be so few similar reports given that everyone has to use the same API in the same way.