A daily/daily/daily FAQ, the solution is to be patient and sit on your hands while the backend catches up with itself. Sit on your hands means don't hammer the backend with repeated uploads. I don't know if this is relevant or not. We don't either. devForums are Apple IDE-centric. 3rd party tools/SDKs/APIs normally come with their own support, elsewhere, which is where questions about those products are best raised. Good luck.

I think a 'business purchase' using Apple's VPP/B2B programs - https://www.apple.com/business/docs/site/VPP_Business_Guide.pdf may be your best bet. Otherwise, perhaps IAP gifting... In the end tho, Apple doesn't provide a simple scheme that fits your exact needs, so expect hurdles, gatcha's and looming compromises in this case. Good luck.

If you mean use Xcode to build an app that uses a form, the data goes where your code says it should go...only you know your code. Could be stored in your app's 'Documents' directory, - https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html emailed to another person, uploaded to iCloud, saved on a remote server, etc. link to google sheets. Yes. Sheets has an API you can use: h ttps://developers.google.com/sheets/api/

Is 9/15 apple event? As Claude notes, Apple doesn't say ahead of time. Anything is possible and info from that event may have bearing, but as we say, 'those who know, don't talk, and those that talk, don't know' ;) Just keep checking: https://developer.apple.com/download/release/ https://developer.apple.com/news/ https://apps.apple.com/us/app/xcode/id497799835?mt=12

Define 'only on TestFlight'....do you mean never for sale in the store? If so, use the TestFlight app, and if you require app review for external testors, don't change status to release it to the store/put it on sale.

doesn't seem to be caused by firebase Not sure why you felt it important to mention fb at all, then - if something's not a factor, it doesn't belong in the comment. I'd still bounce your issue of that 3rd party's product support. Usually it's a case of those 3rd parties not keeping their product in sync quickly enough to avoid issues. Onus is on the dev, in all such examples, to first thing verify with the 3rd parties that the tool/SDK/API in use is the latest most current version. You seem to have assumed that out of your conversation, and jumped right to using Apple's support channels first. A bad habit, if that's the case, and one that can often result in pushback.

What kind of developer-centric advice are you asking for? Do you have code that isn't working, or...?

we need to fill out  Yes. what exactly is this?  Short answer is "W-8BEN-E is an important tax document which allows businesses operating outside of the U.S. to claim tax exemption on U.S.-sourced income." See: https://ww w.freshbooks.com/hub/accounting/w8ben-e ...and... https://developer.apple.com/forums/thread/52583

You can try to make it a bother by requiring they keep a touch on the screen, but in the end, all a user has to do is point a camera at the screen and they're good to go. See https://developer.apple.com/forums/thread/61124 As always, if there is something you don't want captured, don't put it on the screen. Good luck.

Apple is under no obligation to shape their process and requirements to fit your business model. Review your Developer Program Agreement. No app in the store is any promise that any other app will be accepted/reviewed. The guidelines are a living document which means Apple defines them, at will, on the fly, and they can change at any time...perhaps a new crackdown was timed that your app was the first to fall under new scrutiny. They control the process. Don't expect a running dialog that opens them to a back/forth debate. If you want into the store, make changes, or not. There are no pre-reviews, and no simple recipe for what those changes may amount to, and, if they would make a difference during review. My opinion is that in your example, once an app like yours has been flagged, and unless Apple does a 180 on their policies, you're done. Find another business model and do your feasibility planning up front, prior to coding, etc. - planning that actively and generously follows, rather than risks running afoul of, the ASRGs. If the risks are not something you can afford to take, perhaps the App Store isn't for you. ...it's called 'development' for a reason. Good luck.

Suggest you take Claude's advice in this previous thread: https://developer.apple.com/forums/thread/126616 But if you really want direct contact w/an Apple Engr. you might consider using a support ticket w/DTS via the Member Center. Good luck in any case.

I believe that would be the max item/product limit... Which was 20, before it was 10k. How many products are you adding? Seen this previous thread? Maybe it's about images... https://developer.apple.com/forums/thread/100591

I *had* opened the project up in Xcode (non-beta), because I was going to build it for The App Store, maybe that did something?  Could well be. Using Xcode 11.7, create a new sample project w/appropriate template, targeting iOS 13.x, then walk thru the process to make-it-a-mac app and see how far you get.

AFAIK, there is no API to speed test. As well, given the variables, it can be more work than it's worth. Best to stick with the traditional speed test method and ping A to B. As for those widgets, they're just pinging and making best guess - nothing magic about them, they just simplify the job for users who don't even know what a ping is ;)

MDM is a (technically broad) 'scheme', designed by Apple, and as such I don't recall Apple specifically providing an MDM 'program', as in 'solution'. MDM solutions/packages have always been 3rd party. Latest layer, however, is ABM - Apple Business Manager: see https://support.apple.com/en-us/HT207516 If you're talking about 'device enrollment' see: https://support.apple.com/guide/mdm/automated-device-enrollment-settings-mdm557792f1e/web When you say 'credentials', that term usually means logins (2fa?) - see: https://developer.apple.com/documentation/security/password_autofill As for 'standing up' aka DIY your own MDM solution, many try, usually in an effort to skirt budget scares, but many fail and realize it is far easier to buy off-the-shelf. If you're talking about using an Enterprise Program to falsely enroll masses of otherwise non-authorized devices via mis-used certificates, you're in the wrong place. Good luck in any case.