Hello, My Apple Developer Program enrollment is still under review, and the enrollment page continues to display: “Contact us to continue your enrollment.” I have already contacted Apple Developer Support under Case 102990211108 and submitted my driver’s license for identity verification, as requested. Since then, I have not received any follow-up confirming whether the document was accepted or whether further action is required. I have not yet reached the membership payment stage, and this delay is preventing me from moving forward with publishing my game. Could someone from Apple please check the status of my case, confirm whether my documents were received, and let me know what is needed to complete my enrollment? If this requires a different support channel, I would appreciate guidance on how to follow up or escalate my existing case. Thank you

Hello, My Apple Developer Program enrollment is still under review, and the enrollment page continues to display: "Contact us to continue your enrollment." I have already contacted Apple Developer Support under Case 102990211108 and submitted my driver’s license for identity verification, as requested. Since then, I have not received any follow-up confirming whether the document was accepted or whether further action is required. I have not yet reached the membership payment stage, and this delay is preventing me from moving forward with publishing my game. Could someone from Apple please check the status of my case, confirm whether my documents were received, and let me know what is needed to complete my enrollment? If this requires a different support channel, I would appreciate guidance on how to follow up or escalate my existing case. Thank you

It seems that Safari (desktop and iOS) is not respecting the Cache-Control header for video files like video/mp4 and video/webm. The response headers for the video includes Cache-Control: public, max-age=3600 And the response comes from the network any time the page is refreshed. I've checked that the Disable Cache is not enabled in dev tools. The same video request is cached as expected on Chrome and Firefox.