Hello, I would like to ask if I can use ThreadNetwork.framework. My project has been configured with com.apple.developer. networking. manage thread network credentials according to the documentation, but the relevant API still cannot be used. Currently, there is an error message: Client: - [THClient getConnectionEntitlementValidity] block invoice - Error: (null) Client: [THClient retrieveAllCredits:] _block_invoke - Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 555 named com. apple. ThreadNetwork. xpc was validated from this process." UserInfo={NSDebugDescription=The connection to service with pid 555 named com. apple. ThreadNetwork. xpc was validated from this process.} May I ask if I can use the relevant API

Is there a good source of documentation on what IP ports and protocols are used by HomeKit accessories?

Safari Browser killing Long Running API requests after 60 seconds. Do we have any way to increase a timeout limit?

尊敬的开发者社区成员， 我最近在开发iOS平台上的VPN应用程序时遇到了一个问题，希望能在这里寻求一些帮助和建议。在我的应用程序中，我注意到在iOS 17及以上版本中，连接到VPN后，特定流量似乎不再通过本地网络发送，而是直接通过VPN连接发送。 为了解决这个问题，我已经尝试了以下几种方法： 确保VPN配置正确，并与VPN服务提供商确认配置是否符合预期。 在iOS设备上检查系统设置，确保VPN配置被正确应用。 使用网络抓包工具分析网络流量，观察流量的源和目的地址，以确定是否通过VPN连接发送数据。 然而，尽管我已经采取了这些步骤，问题仍然存在。我怀疑这可能是iOS 17及以上版本中网络堆栈实现的变化所导致的。因此，我正在寻找更多的调查和解决方案，以确定问题的根本原因，并找到一个可行的解决方案。 如果您在iOS 17及以上版本中遇到了类似的问题，或者您对iOS网络连接行为有深入的了解，请不要犹豫，与我分享您的经验和建议。我非常感谢您的帮助和支持。 谢谢！

Hi there I tried to use a Thread Network in my App. Actually I added ThreadNetwork in frameworks folder and I tried to initialize THClient pointer. THClient* Thread = [[THClient alloc] init]; but error is occur as bellowing "[thclient] Client: -[THClient connectToXPCService]_block_invoke - CTCS XPC Client is invalidated." May I get an advice?? Thanks

Hi, I am trying to use ThreadNetwork APIs in my app. When I try to invoke any thread API I am getting the following error: "[thclient] Client: -[THClient connectToXPCService]_block_invoke - CTCS XPC Client is invalidated." Also the process to add thread entitlement to the app is not clear. I have added the ThreadNetwork Mobile Profile on my device but I still get the above error. Could I get some help with this? Thanks.

I have run thru the Matter documentation and going to create my own non-standard cluster in my matter device for my own use case. Question is Can I control a non-standard matter cluster by HomeKit SDK? I run thru the HomeKit SDK document but cannot find any hints.

Our App is starting to crash (SIGABRT) with the following semaphore failure: _dispatch_semaphore_wait_slow + 132 that´s the stack trace of the affected threads: CrashReporter Key: 682241501eca714a73bcfc32a9fc72f3697580c2 Hardware Model: iPad8,3 Process: TapestryPRO [590] Path: /private/var/containers/Bundle/Application/19755567-CB9E-49C2-9506-C3087BB86227/TapestryPRO.app/TapestryPRO Identifier: com.t-mobile.Tapestry-PRO Version: 1.900.8 (1.900.8) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.t-mobile.Tapestry-PRO [529] Date/Time: 2023-09-12 14:18:50.2918 -0400 Launch Time: 2023-09-12 14:17:34.2497 -0400 OS Version: iPhone OS 16.6.1 (20G81) Release Type: User Baseband Version: 5.03.01 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application<com.t-mobile.Tapestry-PRO>:590 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Foreground WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 40.950 (user 40.950, system 0.000), 47% CPU", "Elapsed application CPU time (seconds): 0.300, 0% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive> Triggered by Thread: 0 Kernel Triage: VM - (arg = 0x0) pmap_enter retried due to resource shortage Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1ebc52c20 semaphore_wait_trap + 8 1 libdispatch.dylib 0x1b4a64448 _dispatch_sema4_wait + 28 2 libdispatch.dylib 0x1b4a64afc _dispatch_semaphore_wait_slow + 132 3 TapestryPRO 0x104fc70a8 -[TapestryServices serviceCallUsingRequest:] + 632 4 TapestryPRO 0x104fc6e18 -[TapestryServices serviceCallUsingMutableRequest:] + 232 5 TapestryPRO 0x104fc6c6c -[TapestryServices serviceCallUsingMutableRequestReturnData:] + 180 6 TapestryPRO 0x104fdf370 -[TapestrySSOAccess getStoreId:error:] + 948 7 TapestryPRO 0x104f2efcc -[TapestrySSO getStoreId:] + 416 8 TapestryPRO 0x104f34794 -[LoginViewController getStoreId] + 132 9 TapestryPRO 0x104f33fa4 __39-[LoginViewController handleSSOHandoff]_block_invoke_3 + 116 10 libdispatch.dylib 0x1b4a62320 _dispatch_call_block_and_release + 32 11 libdispatch.dylib 0x1b4a63eac _dispatch_client_callout + 20 12 libdispatch.dylib 0x1b4a726a4 _dispatch_main_queue_drain + 928 13 libdispatch.dylib 0x1b4a722f4 _dispatch_main_queue_callback_4CF + 44 14 CoreFoundation 0x1ad62fc28 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 15 CoreFoundation 0x1ad611560 __CFRunLoopRun + 1992 16 CoreFoundation 0x1ad6163ec CFRunLoopRunSpecific + 612 17 GraphicsServices 0x1e822435c GSEventRunModal + 164 18 UIKitCore 0x1af9a2f58 -[UIApplication _run] + 888 19 UIKitCore 0x1af9a2bbc UIApplicationMain + 340 20 TapestryPRO 0x104fc8b3c main + 112 21 dyld 0x1ccb38dec start + 2220 Thread 1 name: Dispatch queue: com.apple.UIKit.KeyboardManagement Thread 1: 0 libsystem_kernel.dylib 0x1ebc537dc __ulock_wait + 8 1 libdispatch.dylib 0x1b4a6489c _dlock_wait + 56 2 libdispatch.dylib 0x1b4a64650 _dispatch_thread_event_wait_slow + 56 3 libdispatch.dylib 0x1b4a73714 __DISPATCH_WAIT_FOR_QUEUE__ + 368 4 libdispatch.dylib 0x1b4a732c0 _dispatch_sync_f_slow + 148 5 UIKitCore 0x1af9a322c __37-[_UIRemoteKeyboards startConnection]_block_invoke_3 + 156 6 CoreFoundation 0x1ad609c04 __invoking___ + 148 7 CoreFoundation 0x1ad5b7cb4 -[NSInvocation invoke] + 428 8 Foundation 0x1a79626f8 __NSXPCCONNECTION_IS_CALLING_OUT_TO_REPLY_BLOCK__ + 16 9 Foundation 0x1a7933a5c -[NSXPCConnection _decodeAndInvokeReplyBlockWithEvent:sequence:replyInfo:] + 520 10 Foundation 0x1a7ea4a00 __88-[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:]_block_invoke_5 + 188 11 libxpc.dylib 0x20c9baee4 _xpc_connection_reply_callout + 124 12 libxpc.dylib 0x20c9adee8 _xpc_connection_call_reply_async + 88 13 libdispatch.dylib 0x1b4a63f2c _dispatch_client_callout3 + 20 14 libdispatch.dylib 0x1b4a81e38 _dispatch_mach_msg_async_reply_invoke + 344 15 libdispatch.dylib 0x1b4a6b40c _dispatch_lane_serial_drain + 372 16 libdispatch.dylib 0x1b4a6c0d8 _dispatch_lane_invoke + 436 17 libdispatch.dylib 0x1b4a76cdc _dispatch_workloop_worker_thread + 648 18 libsystem_pthread.dylib 0x20c95addc _pthread_wqthread + 288 19 libsystem_pthread.dylib 0x20c95ab7c start_wqthread + 8

Hello fellow developers, I am in the process of developing an iOS application that support the Matter Framework. My goal is to enable user to commission their Matter-enabled device to a fabric and control them through the fabric. However, I stumbled upon a few questions and areas that I would greatly appreciate guidance on: Commission Process What is the recommended steps to successfully commission a Matter-enabled device? Using the Matter API I have reviewed the provided sample app in the CHIP repo. However, I find it a bit complex to understand fully (background context: I am a junior developer and have never work on iOS development before). I replicated the app using Swift since the sample is written in ObjC but often times got stuck on [connection] nw_read_request_report [C1] Receive failed with error "Operation timed out" log. How to effectively use the Matter API to handle commissioning, device control and other interactions with Matter-enabled devices? Keypair generation I have noticed that the framework doesn't provide an API with the keypair generation (correct me if I am wrong). What is the best practice or resources for handling the keypair generation within the Matter context? Matter Support vs Matter framework I need clarification on the roles of these two framework. From my understanding, MatterSupport adds Matter devices into my ecosystem(?) while Matter framework handles the commission and control in the Matter fabric. And we can use the Matter framework within the MatterSupport using the request handler to commission Matter-enabled device.

Hello, I trying to commission and joint thread matter device through I-phone ( ios 16.3.1) and apple home pod mini (16.3.2). After scanning QR code and following setup process it fails to add accessory and iPhone shows" Pairing with device failed" (attaching screen shot). I confirmed with device manufacturer, and it seems to be problem from apple side. Any help will be appreciated, Thank you.