eskimo

[quote='808455021, raunits, /thread/808455, /profile/raunits'] thus using a exports file just for that seems to bug me. [/quote] What part of this do you think is a bug? In my experience, a .exp file is a great way to manage the symbols exported by your framework because it gives you explicit control. Other mechanisms tend to rely on implicit behaviour, which is a lot harder to understand. So, are you concerned about the use of a .exp file at all? Or the mechanism you use to generate that file? Or that exporting all that extraneous stuff will costly? Depending on what your actual concern is, there are a variety of less explicit options available to you. To learn more, search the ld man page for export and hidden. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='808475021, StanLey-Pliszko, /thread/808475, /profile/StanLey-Pliszko'] Why does local codesign --verify pass but Apple notarization service fails? [/quote] I’ve seen this happen for a couple of reasons: Case sensitivity Packaging To test the first: Create a case sensitive APFS disk image. Use the Finder to copy your app to it. Run your codesign --verify test against that copy. On the packaging front, it’s common for apps using third-party tooling to not follow the guidelines in Placing content in a bundle. When that happens, the app can end up with a code signature that relies on extended attributes. And when that happens you can run into problems during notarisation because of the various ways that those extended attributes are packaged. To test this: Build your app to a disk image. Use xattr to check entire app bundle for extended attributes starting with the com.apple.cs. prefix. Finally, I want to address two other things that are unlikely to be the cause of this issue but you should fix anyway. [

[quote='808594021, AckwelFoley, /thread/808594, /profile/AckwelFoley'] the end goal is to mount a user's entire home directory via my FSKit [/quote] That’s gonna be really challenging. FSKit is based on app extensions, and app extensions are fundamentally scoped to a given user. [quote='808594021, AckwelFoley, /thread/808594, /profile/AckwelFoley'] Is there a way to enable my FSKit module globally [/quote] No. Honestly, I think that’d make a reasonable enhancement request. On the networking side of things, macOS allows developers to package a Network Extension provider as a system extension, which runs globally. If you do file an ER, please post your bug number, just for the record. What’s your distribution plan here? Is this something you’re building for yourself? Or something you plan to ship to a wide range of users? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

In general, the simulator uses the host’s TCP/IP implementation. So, for example, if you use URLSession to run a request in the simulator, that’ll use the simulator’s CFNetwork which uses the simulator’s Network framework which uses BSD Sockets which ends up in the host kernel. From there, the simulator looks like any other (big) BSD Sockets client. As to why it’s causing the host’s networking stack to fail, I’ve got no good theories. However, I suspect it’s somehow tied to your NE providers, because if this were failing in general there’d be a lot more grumbling. But that doesn’t mean that your NE providers are at fault. It could just as easily be a latent system bug that happens to be triggered by your NE providers. How reproducible is this? If you can reproduce it reasonably reliably, one option would be to replace your NE providers with simple ‘pass through’ versions. If the problem persists, then that’d form a good basis of a bug report. Alternatively, if that eliminates the problem then you have somethi

I’m glad to hear you get this sorted out. And thanks for posting your solution. [quote='867546022, charles.cc, /thread/807467?answerId=867546022#867546022, /profile/charles.cc'] Do not attempt to configure the Distribution Profile directly in Xcode’s Target settings [/quote] Right. [quote='867546022, charles.cc, /thread/807467?answerId=867546022#867546022, /profile/charles.cc'] only swap in the Distribution Certificates (Manual) during the Organizer Distribution phase. [/quote] Right. When using the Xcode organiser’s distribution workflows, you want the Xcode archive to be Development signed. Anything else is pointless — because when you distribute from the organiser it’s going to overwrite the signature — and a potential source of confusion. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

AFAICT com.apple.developer.activitykit.allow-third-party-activity isn’t a real entitlement. See Determining if an entitlement is real. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867520022, LawrenceLiu, /thread/808311?answerId=867520022#867520022, /profile/LawrenceLiu'] Can anyone respond? [/quote] Sure. But please note a) tip 3 in Quinn’s Top Ten DevForums Tips, and b) the US was largely shut down last week in observance of the Thanksgiving holiday. Anyway, regarding your technical question, is there some reason you started a new thread for this? Because we’re already talking about it over on your existing thread. I’ll try to reply there once I’ve cleared the Thanksgiving backlog. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The general rule for networking in the background on iOS is that everything works as long as your process is running. Once your process gets suspended, you start running into edge cases. TN2277 Networking and Multitasking talks about this idea, although it’s somewhat out of date. Specifically, I now talk about connections being defuncted rather than using the older socket resource reclaim terminology, because Network framework supports a user-space networking stack that doesn’t involve sockets. However, it sounds like you’re using BSD Sockets directly, in which case TN2277 is still as relevant as it ever was. Specifically: [quote='808351021, RiteshV, /thread/808351, /profile/RiteshV'] we attempt to establish a DTLS handshake over our existing socket [/quote] It’s likely that this socket was defuncted when your app was suspended in the background, and thus the issue isn’t with DTLS per se, but rather with networking proper. If you open a network connection in this situation, does that work? Share and Enjoy — Q

[quote='808429021, thebenuzi, /thread/808429, /profile/thebenuzi'] I read online that there is no way to extract the call log from an iPhone. [/quote] That is correct, but only if you apply some nuance. I think it’s better to say that there’s no supported API for accessing the user’s call log. And given that, I don’t see any reasonable way to achieve your overall goal. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Ruby is part of the macOS base system. That’s immutable, and so there’s no way for you to “update or remove” it. Most folks in your situation install the latest Ruby using their mechanism of choice and then change their environment so that they use that version of Ruby by default. However, you wrote: [quote='808618021, teapeagee, /thread/808618, /profile/teapeagee'] so that my mac meets minimum cybersecurity requirements? [/quote] which suggests that you’re working in some sort of managed environment that imposes these minimum requirements. If so, I recommend that you talk to your site manager about this. They could, for example, deploy an endpoint security client on to your Mac that blocks execution of the built-in Ruby. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

See the discussion on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

maybe this should be a new thread. Yes, this should definitely be a new thread (-: If you do start a thread, use the subtopic and tags as this thread; that way I’ll be sure to see it go by. Before you do that, however, make sure to review TN3179 Understanding local network privacy. I suspect this is as simple as you not signing your app with the com.apple.developer.networking.multicast entitlement, a requirement that’s documented in that technote. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com