“eskimo”

Are you really supplying an empty Apple Account string? Or did you just redact that for the sake of this post? Regardless, I have a couple of generic bits of advice here: To get started, use the store-credentials subcommand. It runs you through the authentication process interactively, which can help head off the most obvious errors. Make sure you’re using an app-specific password, rather than the password for your Apple Account. An app-specific password should have the format aaaa-aaaa-aaaa-aaaa, where each a is a lowercase letter. If you get stuck, switch to authenticating with an API key. IME it’s often easier to get that working. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='880678022, HuangKun, /thread/819403?answerId=880678022#880678022, /profile/HuangKun'] Could this App Review rejection have triggered a backend review of our account affecting notarization? [/quote] I can’t comment on that. See this post for a little more background about this “No comment.” Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have time to go through the doc properly today, but we just published a new technote about RDMA over Thunderbolt: TN3205 Low-latency communication with RDMA over Thunderbolt Please read it through and reply here with your thoughts. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for providing that extra context. There are two ways that Apple can grant you access to managed entitlements, via an old process or a new process. I explain those processes in detail in Using the Multicast Networking Additional Capability (this is for a different entitlement, but you should recognise the processes). It seems that your teams are configured with a mix of the old and the new. For example, WEJZZZZZZZ is using the old process whereas NWKYYYYYYY is using the new process. I don’t have any insight into the old process setup, but I can see the setup for new process stuff and I’ve confirmed that NWKYYYYYYY is set up correctly. However, to use it you have to use the new process, rather than the old process. To learn more about this, read Account > Reference > Provisioning with capabilities. At the bottom of that page is a Migrating additional entitlements to capabilities section. This explains how you can request that we migrate you from the old process to the new process. I recommend that

Please try again after a restart. I went through this process myself and hit very similar symptoms. I found that fskitd had a bunch of threads stuck like this: 816 _dispatch_call_block_and_release + 32 (libdispatch.dylib + 7004) [0x19b4ceb5c] 816 ??? (fskitd + 132900) [0x100988724] 816 ??? (fskitd + 86796) [0x10097d30c] 816 ??? (fskitd + 87588) [0x10097d624] 816 ??? (fskitd + 50740) [0x100974634] 816 objc_sync_enter + 20 (libobjc.A.dylib + 70452) [0x19b245334] 816 816 __ulock_wait2 + 8 (libsystem_kernel.dylib + 60532) [0x19b656c74] *816 ??? (kernel.release.t6031 + 6477368) [0xfffffe0008ea1638] (blocked by turnstile waiting for fskitd [634] thread 0x30444d) Worse yet, the number of threads kept growing, every time I retried the mount command! I was able to clear this by restarting, after which the mount command worked as expected. I did some spelunking based on internal resources and it seems that these threads are deadlocked due to some previous error starting the extension. Hence my idea to restart, in an a

Thanks for the confirmation. I’ve retagged your thread with ReplayKit because that’s the only option for this sort of thing on iOS [1]. Coming back to your original questions: [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] Permission Clarity [/quote] I don’t think you’ll be able to make progress on this. Broadcast extensions were designed for… well… broadcasting, and the user experience reflects that. [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] Can a Broadcast Extension reliably stay active in the background … ? [/quote] Honestly, I’m not sure. I think this is something worth prototyping before you invest heavily in this project. [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] App Store Guidelines [/quote] I don’t work for App Review and can’t offer any advice on that front. You could ask them here on the forums, over in the App Store Distribution & Marketing > App Review subtopic. However, I think it’d be best for you to c

[quote='880623022, timboudreau, /thread/818192?answerId=880623022#880623022, /profile/timboudreau'] that would … probably run afoul of one or another App Store policy [/quote] I don’t work for App Review, and thus can’t give definitive answers about their policies. My only advice is that you peruse the App Review Guidelines. At a technical level, on macOS it is possible for an app extension to communicate with an app or launchd agent or daemon that you control, even in the presence of sandboxing. If you want the server side of this to be an app, the best option is for that app to listen on a Unix domain socket that’s located in an app group container. If you want it to be a launchd job, prefix the named XPC endpoint with an app group ID. Both of these are documented in App Groups Entitlement. For more on the XPC side of this, see the various links in XPC Resources. Specifically, XPC and App-to-App Communication has a bunch of backstory you’ll need. And please don’t use Mach messaging directly! [quote='8806240

[quote='880481022, b0xch, /thread/819180?answerId=880481022#880481022, /profile/b0xch'] Is ppq.apple.com really up & running? [/quote] In general, yes. Consider the thread I mentioned earlier. It grew to 10 pages overnight. And the issue even made the front page of AppleInsider [1]. We’re seeing nothing like that right now. Which isn’t to deny your experience. However, whatever’s happening on your device is very likely related to your specific environment, and hence the advice in my previous response on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] https://appleinsider.com/articles/26/03/10/a-now-resolved-apple-server-outage-stopped-developers-from-verifying-apps

Speaking for myself only, I need a proper crash report before I can offer any insight into this. If you can post one here, using the instructions I linked to above, I’d be happy to take a look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880466022, jzilske, /thread/817599?answerId=880466022#880466022, /profile/jzilske'] it's not a WebView where I suspect the traffic comes from [/quote] Ah, OK, thanks for setting my straight. [quote='880467022, jzilske, /thread/817599?answerId=880467022#880467022, /profile/jzilske'] How would I go about setting that up? [/quote] Which bit? To get the source information from mitmproxy, view the request, switch to the Detail tab, and look at the Client Connection section. Getting process information from the packet trace is a small extension of the RVI process described in Recording a Packet Trace: Set up RVI per the Set Up iOS Packet Tracing section. When you get to the tcpdump command, add the -k option to cause it to dump each packet’s metadata. And tcpdump naturally logs the port numbers in each packet, so you can look for outgoing packets whose source port matches the port number you get from the proxy. Having said that, this won’t help given your clarification that the connection is not coming from

[quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] I am trying to verify a helper binary/dylib inside my product that can be updated separately from the main binary. [/quote] Is this an executable or a dynamic library? Or do you need this test to support both? And by “inside my product” do you mean that it’s located within an app’s bundle? Or that it’s logically part of your product, but is stored in some other location on disk? And while I’ll have a lot more to say about your overall issue once I better understand it, I want to nip this one in the bud: [quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] Does extracting a team-id … automatically verifies that the anchor is apple? [/quote] No. You can’t trust the information you get back from SecCodeCopySigningInformation unless you’ve validated the code signature. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

It’s hard to offer insight into this without more info. Do you have an Apple crash report for this? If so, please post it here. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880351022, KayleeSC, /thread/791352?answerId=880351022#880351022, /profile/KayleeSC'] Omg it was the / at the end. [/quote] Well, blat! [quote='880351022, KayleeSC, /thread/791352?answerId=880351022#880351022, /profile/KayleeSC'] I’m gonna send this to the testers and see if that’s it. [/quote] Cool. If that does turn out to be the problem, I’d appreciate you filing a bug about it. The system should either tolerate this or vend a more helpful error. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the backstory. [quote='880252022, shara7, /thread/818906?answerId=880252022#880252022, /profile/shara7'] which made me wonder whether this is a bug or intended behavior. [/quote] Well, it’s an an either or situation. Note this comment from the release notes: During the beta period, the cadence of notifications will be accelerated, enabling Apple and developers to address any issues that might occur. Honestly, I’m not sure whether this is what’s happening in your case or not. You might be able to learn more as to what’s actually going on by monitoring the system log entries from the ecosystemagent process. Many of these are at the debug level, so you’ll need to opt in to that. See Your Friend the System Log for hints and tips on using the system log effectively. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com