show when run

Hello,I got a very strange problem: UIUserNotifcationActions for my app do not show up on devices but show/work on Simulator.Setup: UIMutableUserNotificationAction* replyToChat = [UIMutableUserNotificationAction new]; replyToChat.activationMode = UIUserNotificationActivationModeForeground; replyToChat.title = @Reply; replyToChat.identifier = @replyToChat; replyToChat.destructive = NO; replyToChat.authenticationRequired = YES; UIMutableUserNotificationAction* ignoreChat = [UIMutableUserNotificationAction new]; replyToChat.activationMode = UIUserNotificationActivationModeBackground; ignoreChat.title = @Ignore; ignoreChat.identifier = @ignoreChat; ignoreChat.destructive = YES; ignoreChat.authenticationRequired = NO; UIMutableUserNotificationCategory* catChat = [[UIMutableUserNotificationCategory alloc] init]; catChat.identifier = @myChat; [catChat setActions:@[replyToChat, ignoreChat] forContext:UIUserNotificationActionContextDefault]; NSMutableSet *categories = [NSMutableSet setWithObject:catC

After upgrading to macOS 10.13 Beta (17A315i) my registered devices (iPhone 7 Plus, and iPod Touch) do not show in iTues when they are connected.

Xcode has started to show numerous errors within my project. Everytime I build my app the number of errors changes. It's always between 50 and 70 errors that cause the build to fail. The errors are always 1 of these 2. Cannot convert return expression of type '()' to return type 'UICollectionReusableView' or Cannot convert return expression of type '()' to return type 'UICollectionViewCell?' Whenever I click an error it opens up that file, shows no error in code and then the error in the issue navigation for that file disappears. In addition, the errors are always related to collection views, yet Xcode is showing errors for simple extension files or enum files, which have nothing to do with collections. I have cleaned the project build folder, removed the derived data, restarted Xcode, restarted the laptop, even reinstalled Xcode yet I still get the errors

I have downloaded PIVToken example from here https://developer.apple.com/library/content/samplecode/PIVToken/Introduction/Intro.html and trying to run it. I have put several breakpoints in the source code, but when I run it from XCode, none of them gets hit. It doesn't look like smartcard extension is properly registered or maybe there's some other problem.I have YubiKey NEO PIV smart card.I disabled built-in PIV token as mentioned in the README.md and restarted my machine.sudo defaults write /Library/Preferences/com.apple.security.smartcard DisabledTokens -array com.apple.CryptoTokenKit.pivtokenBut when I insert YubiKey NEO, I still get SmartCard Pairing popup:Do you want to connect the inserted SmartCard with the current user?Card Identity: Certificate for digital signature (Test)| Do not show again | | Cancel | | Pair |The README also mentions that the new extension will be automatically installed when the hosting application is installed. Does it mean I need to install the appli

How do I get the microseconds of an object of type Date? I'm open to any suggestions. I'm not able to set the dateFormat property of DateFormatter to be able to show microseconds.

One of my team members created an app on App store connect. but it not showing to me. I have searched more but have not found any solution. Please anyone let me the solution.

Tried to run the following code in Playgrounds as shown in this session: - https://developer.apple.com/videos/play/wwdc2020/10643/ import SwiftUI import PlaygroundSupport struct ProgressView: View { var body: some View { Text(Hello World) } } PlaygroundPage.current.setLiveView(ProgressView()) Instead of Showing a Preview the following error message is displayed: There was a problem running this playground. Check the code and try again

Xcode show build uploaded successfully, But in iTunes Connect it not showing. It show some time on iTunes connect on all build section then it disappear and not showing any build. In last 15 days we have been trying to uploaded the build on iTunes Connect and still facing that issue.