What would a valid export options plist look like for a macOS executable? When exporting through Xcode, it's the 'custom' > 'Built Products' distribution method. This is not a notarized app.
I've tried using 'package' and 'mac-application' but I get an error, "exportOptionsPlist error for key "method": expected one of {}, but found mac-application".
Post not yet marked as solved
When displaying a popover that contains a TextField, selecting the TextField and presenting the keyboard shrinks the popover. When the popover shrinks, it pushes the TextField out of frame where it can't be seen.
I've tried various ways of sprinkling .ignoresSafeArea(.keyboard) throughout which doesn't help. Also, I've tried making focus explicit with FocusState for the TextField.
Below is an example and screenshots are attached showing how it looks.
import Foundation
import SwiftUI
struct PopoverLab: View {
@State private var showPopover: Bool = false
var body: some View {
Form {
Button("Show Popover", action: { showPopover = true })
.popover(isPresented: $showPopover) {
PopoverForm()
.frame(width: 200, height: 300)
.ignoresSafeArea(.keyboard)
}
}
}
}
private struct PopoverForm: View {
@State private var text: String = ""
@FocusState private var isTextFocused: Bool
var body: some View {
Form {
TextField("Text", text: $text)
.focused($isTextFocused)
}
.ignoresSafeArea(.keyboard)
}
}
Is there a way to make a popover more resilient to the keyboard presenting?
In an effort to get more visibility to when there are network related errors, I tried implementing URLSessionTaskDelegate's didCompleteWithError function. However, this delegate function is never called although there are tasks that fail. URLSessionDelegate functions work as expected. Also, URLSessionTaskDelegate's didCreateTask function is called as expected.
Is there more nuance that I'm missing concerning when didCompleteWithError should be called?
Some additional context:
Our URLSession delegate conforms to URLSessionDelegate, URLSessionTaskDelegate, and URLSessionDataDelegate
All 3 protocols work as expected except didCompleteWithError
The app in question integrates with BlackBerry Dynamics SDK. However, their documentation does not say that didCompleteWithError is effected by the SDK.
https://developer.blackberry.com/files/blackberry-dynamics/ios/nsurlsession_support.html
The implementation of creating a task can be seen here: https://github.com/MFB-Technologies-Inc/NetworkService/blob/main/Sources/NetworkService/NetworkServiceClient%2BStart.swift
Post not yet marked as solved
I've been struggling with writing some dependency injection types for Foundation types like NotificationCenter, UIDevice, etc. I've created a sample package to demonstrate: https://github.com/MFB-Technologies-Inc/notification-center-client-demo.
The goal is to mimic NotificationCenter's Publisher and notifications AsyncSequence.
LiveNotificationCenterClientTests.testStream will fail unless it's run in isolation. If more than one test is run, it will never complete because no values are ever received from the stream.
MockNotificationCenterClientTests.testPublisher fails because the expectations are not fulfilled before the timeout. For whatever reason, the published values are not being received in the sink. MockNotificationCenterClientTests.testStream never completes because the value is being endlessly awaited.
It seems that there are some fundamental things about concurrency that I'm getting wrong. Can anybody help me debug this? For the two stream tests, I know I could rewrite them to fail with a timeout like the publisher tests but that's not the real problem.
Post not yet marked as solved
We started receiving this error a few days ago when it appeared to be a wide spread problem on Apple's end. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022
Although it is supposedly resolved, I am still getting this error. I have incremented build and version numbers along with tweaking code. Also, the build agent is running macOS 12.4 and Xcode 13.4.1.
ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Align-Dev: isActivated. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
The only remaining use of isActivated is the BlackBerry Dynamics dynamic SDK. That property is not new in the SDK and has never been flagged before.
andrew-mfbtech.