WkWebView is very opaque. It is almost always a better idea to do such things in CSS or Javascript inside the view.

There is a bit about "eligible members can also connect with Apple engineers over WWDC20 content on the forums". This account I'm using now won't be worthy.I'm pretty sure Jive has been purged from ASC. I used to make some pretty heavy use of latent Jive APIs. I built my own ASC search tool! They slowly closed those off one by one and finally got rid of them all.They will have to do something to provide virtual WWDC content. The challenge will be that all developers have access, not just developers with the golden WWDC ticket. But maybe this will be a chance to reboot the forums with real developers. Maybe they will come back after WWDC is over. I sure get tired of the "why did apple reject my gambling app for kids that uses bitcoin to circumvent IAP?" questions.

The developer forums are going to be scrapped and redone on June 18. I guess the new features will be available and documented at that time.

Is there a line break mode on mac so that a word never breaks, even if the word is bigger than a single line?I sure hope not. Wouldn't that be a text layout mode that runs in an infinite layout loop?

The user is going to have to specify those files. the only way to do that, at least in the sandbox, is via open panel and security-scoped bookmark.However, that is how you initially access the files. My suggestion would be to immediately copy the files into the app's private document folder, inside a uniquely named folder for good measure. All systems run APFS now, so the copy is free. The user can then delete, move, change the original with no harm to your version.

You're totally getting busted back down to Level 1.

The game uses only UDP sockets to connect to a server on port 53487(ipv4) and 53488(ipv6). I didn't setup DNS64/NAT64 because it works without it on other platforms.Well now you're on a new platform. I'm sure Apple is inside a corporate network with all kinds of firewalls and deep packet inspection. Some of my customers on corporate networks sometimes can't connect to my server using TCP on port 80/443.The easiest solution is to have your server accept TCP over port 80 as a fallback. You don't need to have great response or low latency or anything. You just need to pass app review.

We already did.And what did they say?We also submitted a case with Apple since there seem to be exceptions:There aren't any exceptions. Did you check the date on that document? It says 2012. Technically, it is accurate when it says "you can request temporary exception entitlements that we will consider on a case-by-case basis". In other words, you can always ask....I can assure you, with absolute certainty, that Apple is not going to allow any unsandboxed excutables to be bundled inside your app.Does the Zoom SDK need those apps to function? IDKWhat kind of feedback or hint are you looking for? I don't know anything about the Zoom SDK. If Zoom support doesn't know, or can't give you any substantial feed back or hints, why do you expect us to do better? Did you try deleting those apps from the framework? Does it still work? IDKMy feedback and hint would be to avoid this entirely. Zoom isn't your software. It would be a bad idea to make your app dependent on some other company. What if they discontinue the SDK? What if they decide to start charging you? What if the SDK isn't compatible with the App Store (oh, never mind on that one). Why Zoom anyway? It is also a bad idea to jump on bandwagons like Zoom and COVID-19. It is always a much better idea to develop your own app for your own customers.

Contact zoom?

Are you calling that Apple URL from your app? That's not how it is supposed to work.Also, how are you testing the app locally? You said you were using a "both debug builds and release builds". Forget debug builds. That's for actual development in Xcode. The only way to properly test is to archive and then do an export using the "Development" option. Then test that on an entirely separate machine. New volumes and new users don't count. You can use a VM in most cases, but you should still test this on real hardware that isn't your development machine.

You need to notarize only the outermost container. In this case, that would be the package.Note that the only way to say that you have actually "notarized" it is to successfully download and install it on a pristine machine that has never before seen the app. I recommend a virtual machine.

Don't use someone else's identifier. Use your own, something like "org.tmiskiew.ah". The word "zoom" is trademarked by Zoom, I'm sure, so don't use that.

To channel my inner Apple support engineer, webarchives are not an API. You would need to properly implement whatever it is you are trying to do without relying on private, undocumented Apple file formats.

I'm not seeing any "gray area". As far as I can tell, you would be in direct violation of those two guidelines that you cited. Ultimately, no one here can answer your question. We are just other developers. Even the Apple engineers are just engineering support. They have no influence over app review. All you can do is submit and hope for the best.I have seen a number of posts that suggest developers who attempt to circumvent the guidelines can be expelled from the developer program. I suggest making sure there are no "gray areas" before you submit.

What do you want us to do about it? There is no reason to believe that the app reviewers are making it up. What are these "simulations" you keep talking about? That sounds fishy.