Apple has clamped down on such apps recently. Sounds like you're an example of their changed response. Outside of keeping in touch with them directly, there isn't much to suggest. Good luck.

It's not about that app, it's about your conduct. Clear your head and recognize you're the issue. Once they flag devs/accounts like this, moving forward is not an easy task. They know to keep an eye on your account now. Good luck.

You can't use the store to run a raffle/fundraiser, which is what you describe. Not sure why you'd want to, given that Apple will take a 30% bite. Not everything needs an app - consider making an HTML5 website where you'll have platform-agnostic desktop and mobile device support out of the box, with no need to run an approval gauntlet, or share revenue.

I wouldn't spend money on any mac that only had 8GB ram. At least buy one you can upgrade. And by upgrade, I mean both ram and SSD, but why make things harder on yourself - spend that money up front and be done. If you think you've found a good deal, think again. The constant demand for compatible hardware exists for a reason. The market knows what's worth buying and what isn't.

Not much we can do here. The Team doesn't spend much time on the forums these days, I think. If your goal is direct contact, use the 'contact us' link below, but for your complaint, I'd not expect more than an apology and suggestion to come here for sympathy from the dev community. I'd suggest that while there are routine hiccups involving the backend, it seems worse than ever lately, including internet outages, keeping in mind that the West Coast is having a harder time than usual with fires and high winds. Then there's the move for more work-from-home, etc. My suggestion is to change tactics/browsers/networks - if you're using Safari on macOS, try the App Store Connect app on your phone instead. Visit a cafe and use their internet instead of yours. But again, that message points to factors out of your control, so... Good luck.

Suppose I release the approved version with the territories/countries limited to 0 of 175 countries The backend won't let you do exactly that. If you are facing a deadline to release to the store, then go ahead and release the approved version, with at least one compatible country selected, then, after only a very short delay before anyone can grab it, take it off sale in all countries, and then get your improved version going as soon as it is ready. Good luck.

Confirm your process here: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/establishing_a_certificate-based_connection_to_apns Come back with any specific issues, being sure to show any errors, etc., don't paraphrase.

Enterprise apps don't go thru review and the store, so if you can keep an app working with outdated code on modern devices/OS, then go for it, just don't complain/ask for support when things go south ;)

This is a frequent daily FAQ - Be patient while the backend catches up with itself. Sit on your hands and check again a bit later. It's normal, but confusing, yes. Just be sure to not pound on the backend and shotgun multiple uploads, etc.

Owning and using a developer program account, vs. an enterprise account, should allow you to add apps.  Can I not use same apple id Must, not can. Is the Apple ID you're using also used with other accounts, free provisioning, etc., or is it entirely unique to this dev account? If not, there may be conflicts on the backend and you may need to contact support to clear them up. Are you using Safari on macOS? If all you see when you login is 'Users', then your role is not account holder and you need to sort that out. If you believe your role is correct, sign out from all other backend services with that login and try App Store Connect again.

HELP ME UNDERSTAND WHAT THEY ARE TRYING TO SAY Can't do that unless we know what they said, exactly. Talking about a rejection, and a crash log, but only sharing the crash log leaves questions. Show the rejection. But sure, it could be a mistake. Again, show the rejection and we'll know what they told you to do, that's what we need to know and you need to follow up on. How many rejections, did you appeal, what did you say, etc. etc. If all they did was to say fix the meta data and not to upload another binary, then do that and ignore the crash log for now.

received it via email from the developer site.  eh? Apple doesn't issue DUNS numbers. Perhaps you meant you checked to see if your company already has one. Confirm your process here: https://developer.apple.com/support/D-U-N-S/ If you think you have a valid 9 character number... Are you using Safari on macOS Are you using the same Apple ID associated with the account signup? Using 2FA?

It's the odds part that Apple is focused on - it's not about the path, it's about the risk. An exchange that hinges on a gamble. If there is no risk/gamble, then the admonition about odds doesn't apply.

Is there some reason you're not relying on the store's native pricing? Apple tends to frown on DIY pricing inside an app... As well, have you considered that prices are subject to changes/conversion, and even if you succeeded, what you hardwire/show in your app may not reflect reality in the store...which is one of the main reasons Apple frowns on the practice. User don't take kindly to seeing the price change by the time they get the receipt.

asking before submitting the app for review and risking rejection.  There are no pre-reviews, app review isn't here and no one here can promise what review will/won't accept reject. All you can hope for here are the opinions of volunteer referrees - mine is that nothing has changed over the years... Apple frowns on anyone but them using their stuff - see the ASRGs 5.2 - https://developer.apple.com/app-store/review/guidelines/#intellectual-property