Just encountered the login issue again where it wouldn't recognize my password, which occurred on Safari but not Chrome on my MacBook, this time at https://developer.apple.com/account which redirects to https://idmsa.apple.com/IDMSWebAuth/signin?appIdKey=... I also notice I can't update my contact details at Apple Developer dashboard > Update your information. It goes to an error at https://developer.apple.com/unauthorized/: "Your account can’t access this page."

Lastly, it seems the false "expired" issue is not limited to just the dashboard message. When I go to App Store Connect > Xcode Cloud, it says "Apple Developer Program membership has expired; To continue using Xcode Cloud, renew the program membership." I'm guessing there may even be further limitations caused by this false positive "expired" detection.

Seems I spoke a day too soon. Received a renewal confirmation email this morning and the previous issues have resolved. Didn't realize processing would take that long. Resolved.

1.5 weeks later my banking update is still "processing" and I still don't have an answer to why my W-9 submission isn't going through. I called Apple Developer customer support who confirmed there's no phone number for the finance department and that a response from them can take 10 business days. There should be a faster, more direct way to resolve these issues.

Solved (or more like worked around whatever weird issue this was). I realized on this occasion I'd only tried building to VM, not YYC, although I usually tested both in the past if there were any issues. On YYC I was able to build without the codesigning error, after which I needed to open the xcodeproj manually which was located at (macuser)/gamemakerstudio2/GM_MAC/(gamename)/(gamename).

The finance team replied today and approved the bank account processing issue, about 6 business days after I contacted finance. The W-9 issue I resolved myself by selecting "Limited Liability Company - Disregarded Entity", as I understand this alternative is fine.

@DTS Engineer Thanks for the link. Developer ID Application, Apple Distribution, and Apple Development yielded a different error: "An installer signing identity (not an application signing identity) is required for signing flat-style products". 3rd Party Mac Developer Installer yielded the same error ("this identity cannot be used for signing code"). But the workaround I used works for now. Thanks again.

My ticket was escalated to engineering about a month ago. Still waiting.

I received the weekly analytics email this week so hopefully it's resolved.

Same issue. I'll contact support.

Can confirm, based on what customer support said and my actions, it seems all I had to do was add a new version in App Store Connect to get the app in an editable state to edit the age ratings. After submitting the age ratings, the warning message at the top (about updating the age ratings) did not immediately disappear, but when I checked back maybe 20 minutes later, it had gone, so it seems it worked. Did not have to upload a new build, etc, although my current builds appear expired.