Two errors in debug: com.apple.modelcatalog.catalog sync and nw_protocol_instance_set_output_handler

Question

Created 9h

Replies 1

Boosts 0

Participants 2

We get two error message in Xcode debug. apple.model.catalog we get 1 time at startup, and the nw_protocol_instance_set_output_handler Not calling remove_input_handler on 0x152ac3c00:udp we get on sartup and some time during running of the app. I have tested cutoff repos WS eg. But nothing helpss, thats for the nw_protocol. We have a fondationmodel in a repo but we check if it is available if not we do not touch it.

Please help me?

nw_protocol_instance_set_output_handler Not calling remove_input_handler on 0x152ac3c00:udp

com.apple.modelcatalog.catalog sync: connection error during call: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.modelcatalog.catalog was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.modelcatalog.catalog was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} reached max num connection attempts: 1

The function we have in the repo is this:

public actor FoundationRepo: JobDescriptionChecker, SubskillSuggester {
    private var session: LanguageModelSession?
    private let isEnabled: Bool
    private let shouldUseLocalFoundation: Bool

    private let baseURLString = "https://xx.xx.xxx/xx"
    private let http: HTTPPac

    public init(http: HTTPPac, isEnabled: Bool = true) {
        self.http = http
        self.isEnabled = isEnabled
        self.session = nil

        guard isEnabled else {
            self.shouldUseLocalFoundation = false
            return
        }

        let model = SystemLanguageModel.default

        guard model.supportsLocale() else {
            self.shouldUseLocalFoundation = false
            return
        }

        switch model.availability {
        case .available:
            self.shouldUseLocalFoundation = true

        case .unavailable(.deviceNotEligible),
             .unavailable(.appleIntelligenceNotEnabled),
             .unavailable(.modelNotReady):
            self.shouldUseLocalFoundation = false

        @unknown default:
            self.shouldUseLocalFoundation = false
        }
    }

So here we decide if we are going to use iPhone ML or my backend-remote?

Boost

Answer 1

IAiSeed OP

4h

Based on the error messages you're encountering in Xcode, it seems like there are two main issues to address:

nwprotocolinstancesetoutputhandler Not calling removeinput_handler: This error typically indicates a problem with how network connections are being managed using Apple's Network framework. Specifically, it suggests that an output handler was set on a network protocol instance without a corresponding removal of the input handler, which could lead to resource leaks or crashes. Steps to Resolve:

Ensure that every call to nw_protocol_instance_set_output_handler is matched with a call to nw_protocol_instance_remove_input_handler when you're done with the connection or when the connection is closed. Review the lifecycle of your network connections to ensure handlers are properly managed, especially in asynchronous or error-prone paths. Check if there are any closures or network operations that might inadvertently leave handlers dangling.

com.apple.modelcatalog.catalog sync: connection error: This error points to an issue with accessing a service named com.apple.modelcatalog.catalog, likely due to sandbox restrictions, as indicated by the error message.

Steps to Resolve: Entitlements: Verify that your app's entitlements file includes the necessary permissions to access this service. You might need specific entitlements related to model catalogs or network services. App Sandbox: Since the error mentions sandbox restrictions, ensure that your app's sandbox configuration allows for the required network connections. You may need to adjust the sandbox profile to permit connections to the specific service or domain.

Error Handling: Implement robust error handling to manage cases where the connection fails due to permissions or other issues. This can include retry logic or user notifications.

Debugging: Temporarily disable the feature that interacts with com.apple.modelcatalog.catalog to confirm that it's the source of the problem. If the error persists without it, investigate other parts of your network code.

Additional Considerations for Your FoundationRepo:

Conditional Logic: Your FoundationRepo seems to handle whether to use local or remote models based on system capabilities. Ensure that these checks are accurate and that the logic for switching between them is sound. Network Requests: Within FoundationRepo, ensure that network requests are properly configured, especially with respect to URLs and headers. The base URL you're using looks placeholder-like, so confirm it's correct before making requests.

Concurrency: Given that FoundationRepo is an actor, ensure that all accesses to its properties and methods are properly synchronized to avoid concurrency issues.

By addressing these areas, you should be able to resolve the errors you're encountering. If the issues persist, consider reviewing recent changes to your codebase or consulting Apple's documentation and developer forums for more specific guidance related to the frameworks you're using.

1