SwiftUI List performance

Thanks for the post, very interesting and got a few questions reading your post mainly instead of answers, I’ll invite other developers for their opinion as I’m mainly in SwiftUI, but your post is interesting and intriguing to me. What the motivation of creating a macOS AppKit app without using Storyboards or SwiftUI. How are you planning to do with the UI/UX? Yes, even though the shift is more towards SwiftUI and other modern frameworks. However, the @main attribute can be tricky when used in conjunction with AppKit, especially when you want to manually set up your application lifecycle? Are you talking about his? import Cocoa @main class AppDelegate: NSObject, NSApplicationDelegate { var window: NSWindow? } Trying to understand what you are trying to accomplish and your goals on the project. Looking forward to your answer! Albert Pascual
  Worldwide Developer Relations.

@AET720 I then began by using the iMessage App template in xCode. And BAM right off the bat, I could not get the In-App Purchases capability to show up when I select my iMessage extension target. When you add the In-App Purchase capability to a target in Xcode, it adds the com.apple.developer.storekit entitlement string. This entitlement isn't a supported entitlement as explained in Determining if an entitlement is real. For a list of entitlements Apple supports, see Capabilities overview > Supported capabilities. if you added the In-App Purchase capability to your app target in Xcode, remove it. It is unnecessary. This capability is already enabled when you use an explicit App ID. If your iMessage extension uses an App ID, In-App Purchase is already enabled.

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. It works on macOS Cool. is it also possible on iOS? Core WLAN is not available on iOS. For a list of Wi-Fi APIs that are available in iOS, see TN3111 iOS Wi-Fi API overview. I don’t think that any of these return the information you’re looking for. The nearest that I can think of is fetchCurrent(completionHandler:), which returns some details, like the security type, but no channel info. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to start by addressing this: [quote='814024021, Jashaun-12, /thread/814024, /profile/Jashaun-12'] i am creating a app on appmysite [/quote] The Apple Developer Forums are primarily focused on Apple APIs, tools, and services. If you need help with your third-party tooling, I encourage you to seek that help via the support channel for those tools. Having said that, I want to point you at some Apple docs that should give you a better model for how this stuff works: TN3125 Inside Code Signing: Provisioning Profiles explains what provisioning profiles do and how they’re structured. TN3161 Inside Code Signing: Certificates has a whole bunch of backstory about code-signing identities and their associated certificates. [quote='814024021, Jashaun-12, /thread/814024, /profile/Jashaun-12'] because the uploaded certificate had to be uploaded as .p12 [but the] certificate in the provisioning profile [/quote] This comment suggests you’ve misunderstood a key element of this process, namely the difference between a ce

Actually I have no code so far to style the navigation bar. I am looking for code to put into viewDidLoad() to style the back button so that it has the same blue color as the other buttons. In my original post I have listed some unsuccessful attempts.

I have a SwiftUI app that opens a user-selected audio file (wave). For each audio file, an additional file exists containing events that were extracted from the audio file. This additional file has the same filename and uses the extension bcCalls. I load the audio file using FileImporter view modifier and then access the audio file with a security-scoped bookmark. That works well. To clarify here, do you mean that you’re able to access both the directly selected file and its related sidecar? Or just that you're able to access the direct file? After loading the audio, I create a CallsSidecar NSFilePresenter with the URL of the audio file. I make the presenter known to the NSFileCoordinator and then add it to the FileCoordinator. This fails with NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension for; Error Domain=NSPOSIXErrorDomain Code=3 No such process Is the failure here about opening an existing file or about writing a new file? Also, what directory are you working out of? __ Ke

Your last message might explain the issues you are having, that your list of tokens might not be correct. For starters, the tokens for the development/sandbox environment and production environment are not interchangeable. What works for one, will be invalid for the other. So, that's the answer to that problem. The sandbox and development endpoint names are identical, and they should both resolve to the same collection of APNs endpoints. Getting different results like you described for the same token could be indicative of an issue. So, if you are getting these different results for the same token at the different named endpoints, we would like to hear more details about that. If you can share the token, exact time/tz of the accepted and failed requests, and if you can, a log of the communications with APNs.