Post

Replies

Boosts

Views

Activity

About Privacy updates for App Store submissions
The text from https://developer.apple.com/news/?id=3d8a9yyh states, "Make sure to use a version of the SDK that includes its privacy manifest and note that signatures are also required when the SDK is added as a binary dependency." Does this imply that I must update all the third-party libraries I use to versions that "include a privacy manifest"? I do not wish to upgrade the third-party library code, but I can ensure that the privacy manifest in my app will include the privacy manifest related to the APIs utilized by these older versions of the third-party libraries
1
0
407
Mar ’24
nw_protocol_error Crash on iOS 17.2 and later versions
Problem Description I've encountered a crash that only appears on iOS 17.2 and later versions (specifically iOS 17.2, iOS 17.2.1, and iOS 17.3). The crash started occurring after we switched our CDN to HTTP/3. Reverting the CDN back to a previous version eliminated the crash. The crash is of type EXC_BAD_ACCESS (SIGSEGV) with a KERN_INVALID_ADDRESS error. It was triggered in Thread 8, and the stack trace points to functions within the Network framework. I am unsure which part of my code is causing this issue when using HTTP/3. Any insights into what might be causing this crash or how to troubleshoot it would be greatly appreciated. Thank you. Steps to Reproduce It cannot be reproduced at present, but there are many crash logs in the crash report. Crash Report Triggered by Thread: 8 Kernel Triage: VM - (arg = ) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = ) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = ) mach_vm_allocate_kernel failed within call to vm_map_enter Thread 8 name: Thread 8 Crashed: 0 Network <memory_address> nw_protocol_error + 68 (protocol.cpp:577) 1 Network <memory_address> nw_channel_disconnect_flow(nw_channel*, nw_channel_input_flow*) + 172 (channel.cpp:2168) 2 Network <memory_address> invocation function for block in nw_channel_handle_defunct(nw_channel*) + 40 (channel.cpp:2928) 3 Network <memory_address> nw_hash_table_apply + 2696 (hash_table.cpp:454) 4 Network <memory_address> nw_channel_handle_defunct(nw_channel*) + 644 (channel.cpp:2926) 5 Network <memory_address> nw_channel_check_defunct(nw_channel*) + 92 (channel.cpp:2996) 6 Network <memory_address> nw_channel_remove_input_handler(nw_protocol*, nw_protocol*, bool) + 3332 (channel.cpp:661) 7 Network <memory_address> nw_protocol_ipv4_remove_input_handler(nw_protocol*, nw_protocol*, bool) + 148 (protocol_ip.cpp:639) 8 Network <memory_address> nw_protocol_udp_remove_input_handler(nw_protocol*, nw_protocol*, bool) + 156 (protocol_udp.cpp:271) 9 Network <memory_address> nw_protocol_implementation_teardown + 1028 (protocol_implementation.m:936) 10 Network <memory_address> nw_protocol_implementation_remove_input_handler + 2988 (protocol_implementation.m:0) 11 CFNetwork <memory_address> ConnectionProtocolRemoveInputHandler(nw_protocol*, nw_protocol*, bool) + 264 (ConnectionProtocol.cpp:102) 12 Network <memory_address> nw_endpoint_flow_failed_with_error(NWConcrete_nw_endpoint_handler*, bool, NSObject<OS_nw_error>*) + 536 (endpoint_flow.cpp:3449) 13 libdispatch.dylib <memory_address> _dispatch_call_block_and_release + 32 (init.c:1530) 14 libdispatch.dylib <memory_address> _dispatch_client_callout + 20 (object.m:561) 15 libdispatch.dylib <memory_address> _dispatch_workloop_invoke + 2152 (queue.c:4485) 16 libdispatch.dylib <memory_address> _dispatch_root_queue_drain_deferred_wlh + 288 (queue.c:6913) 17 libdispatch.dylib <memory_address> _dispatch_workloop_worker_thread + 404 (queue.c:6507) 18 libsystem_pthread.dylib <memory_address> _pthread_wqthread + 288 (pthread.c:2629) 19 libsystem_pthread.dylib <memory_address> start_wqthread + 8 (:-1)
3
0
843
Jan ’24
Inconsistent Date Output and 24-Hour Format Issue on iOS 15.4 and iOS 16.3.1
When using the following code: [dateFormatter setDateFormat:@"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'"]; The output on iOS 15.4 is "2023-05-02T03:40:15.748Z", while the output on iOS 16.3.1 is "2023-05-02T上午3:41:19.606Z". This inconsistency in the output is causing issues with my app's functionality. I would also like to add that it is important for the output to always maintain the 24-hour format. This consistency is crucial for my app's functionality, and any suggestions on how to ensure that the output always displays the time in 24-hour format would be greatly appreciated. Thank you.
2
0
593
Apr ’23
Built using Xcode 14, the app crashed on iOS 11 due to lack of network.framewok
dyld: Library not loaded: /System/Library/Frameworks/Network.framework/Network Referenced from: /var/containers/Bundle/Application/F656B952-BCEA-45AA-AFE8-35460D9C2872/TuyaSmartPublic.app/TuyaSmartPublic Reason: image not found I found the same code compiled using Xcode 13, execute the command “otool -L ***”: /System/Library/PrivateFrameworks/Network.framework/Network (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libnetwork.dylib (compatibility version 1.0.0, current version 1.0.0, weak) using Xcode 14 is different: /System/Library/Frameworks/Network.framework/Network (compatibility version 1.0.0, current version 1.0.0, weak) How do I solve this problem?
0
0
700
Sep ’22
iOS 16.0 Beta: UDP broadcast not working with "No route to host" error.
After updating my iphone to iOS 16.0 Beta, I am not able to broadcast UDP (using broadcasting IP 226.120.89.84) message on my local network and getting the error message: "No route to host" premise: 1、entitlements.plist in .ipa, multicast has been granted com.apple.developer.networking.multicast 2、Already grant the app access to your local network 3、iOS 15.5、iOS 15.6.1 is working Here is my code: res = sendto(socket_info-&gt;sock_fd, buffer, 1, 0, (sockaddr *)&amp;multicast_addr, addr_len); When I run on an iPhone with iOS 16.0 Beta installed, I get the following error: The"sendto" function return -1 errno = 65 - no route to host Any help is appreciated. Thanks in advance.
2
1
1.7k
Aug ’22