“testflight the requested app is not avaliable”

Hello everyone, Since roughly 12 hours i can no longer submit updated to my Apps, i always get a Unable to Add for Review with To submit new apps or avoid potential payment blocks, add compliance information for Directive on Administrative Cooperation–7th Amendment (DAC7).. I of course already a few weeks ago went to the Business sections and selected No as it does not apply to us. I tried a lot but cannot make submissions work. I also contacted the Apple support but got no Feedback yet, does anyone have the same issue? What i tried: Switching DAC7 from No to Yes and then back to No again Private Browsing (Cache reset) Checked all other Agreementes, all is fine and active I fail to see any issue and assume it is an Apple central issue as they 1st of April rolled out the new DAC7 compliance check. With many greetings Robert

We are currently experiencing an unexpected issue with the DeviceCheck query_two_bits endpoint. According to the official documentation (Accessing and Modifying Per-Device Data), the last_update_time field should represent the month and year when the bits were last modified. The Issue: For several specific device tokens, our server is receiving a last_update_time value that is set in the future. Current Date: April 2026 Returned last_update_time: 2026-12 (December 2026) Here is a response: { body: {bit0:false,bit1:true,last_update_time:2026-12}, headers: { Server: [Apple], Date: [Thu, 02 Apr 2026 06:05:23 GMT], Content-Type: [application/json; charset=UTF-8], Transfer-Encoding: [chunked], Connection: [keep-alive], X-Apple-Request-UUID: [53e16c38-d9f7-4d58-a354-ce07a4eaa35b], X-Responding-Instance: [af-bit-store-56b5b6b478-k8hnh], Strict-Transport-Security: [max-age=31536000; includeSubdomains], X-Frame-Options: [SAMEORIGIN], X-Content-Type-Options: [nosniff], X-XSS-Protection: [1; mode=block

Hi everyone, I enrolled in the Developer Program 6 days ago and I'm still unable to access my account. I'm hoping someone here can help or that this gets the attention of Apple staff. Here's my situation: I enrolled on Saturday and completed the process on the website The fee has been successfully charged to my bank account I received both a purchase acknowledgement and an invoice from Apple Despite all of this, the Apple Developer website still shows Complete your purchase as if nothing happened I already opened a support case, but have not received any response whatsoever No activation, no update, and no communication from Apple I have proof of payment (bank statement, order confirmation, and invoice), so this does not appear to be a payment issue on my end. Has anyone experienced this and managed to get it resolved? Thanks guys.

I registered for the program and received an email deducting the money. I waited two days but haven't received any response. It shows pending and still isn't finished. Please help me. I've messaged support but haven't received a reply.

Hi everyone, I'm integrating Apple's DeviceCheck API into my app and have run into a strange issue that I can't find documented anywhere. The Problem When I call Apple's DeviceCheck query endpoint (POST https://api.devicecheck.apple.com/v1/query_two_bits), the response occasionally returns a last_update_time value that is in the future — ahead of the current server time. Example response: { bit0: true, bit1: false, last_update_time: 2026-05 // future month, not yet reached } What I've Checked My server's system clock is correctly synced via NTP The JWT token I generate uses the current timestamp for the iat field This doesn't happen on every device — only on some specific devices The issue is reproducible on the same device across multiple calls Questions Is last_update_time sourced from the device's local clock at the time update_two_bits was called? Or is it stamped server-side by Apple? Could a device with an incorrectly set system clock (set to the future) cause Apple's servers to record