We eventually had our game accepted which was failing in review due to ODR. The whole thing took about 5 weeks from the first time we submitted to get accepted, in that time 3 weeks I believe was the App Reviewer waiting for a fix which ended up not working. After we got contact with a developer via a TSI they knew of a problem with how apps were loaded onto devices for review which was preventing ODR from working, they said they had fixed this issue with the internal tools and to re-submit the app. We resubmitted and it failed again getting stuck on a loading screen waiting for ODR with the 4994 error. Went back to the TSI who then later responded saying the issue was fixed again with another change and to resubmit the app. The same thing happened again and our app could not fetch ODR, the TSI person and app review person were in communication and we had phone calls with the reviewer as well who asked us to send a video of the game. We resubmitted the app and it was accepted, I am not sure if they fixed the issue or just passed us based on the video we sent them. But if you do encounter the same problem I would advise raising a TSI, and reference it every time when submitting the app. It's a known issue to the developers but the app review took a while to understand where the problem was. We didn't have to do a lot for the dev to take responsibility and remove the burden from us to update or fix the app, then referencing the TSI and speaking with the reviewer to explain the situation got the ball rolling.... Good luck!

We have submitted report via Feedback Assistant: FB8888989 The reviewer also responded after I cited this forum post and said the app review will now take longer because of the new information provided and they will either pass the app or respond with further issues, so it sounds like it is possibly something they know about. Awaiting further response now. Will update if we hear anything more.

We are seeing the same behaviour. We hide the status bar so it's interesting to see people mentioning VPN and remote working being a possible problem. We have been developing for over a year using ODR and have had no problems via TestFlight we went to remote external QA and distributed builds to lots of people with no issues. Now we get error 4994 on the first ODR tag which should be also included in the initial install. Would love to see some positive responses and fixes for this, so far just had dead pan, robotic response from reviewer, wouldn't send logs or engage in discussion.

I have managed to find a solution and fix the issue, The problem was that MTLTextureDescriptor.swizzle was not initialised. I was not calling init on the MTLTextureDescriptor after allocating so some values mustn't have been set to their defaults.Luckily I caught this issue when doing some other work which asserted that swizzles were not supported on render targets which led me to double check this.