Search results for

“DTiPhoneSimulatorErrorDomain Code 2”

162,375 results found

Post

Replies

Boosts

Views

Activity

Question regarding app ownership and payment processing by separate legal entities
I have a question regarding your policies on app ownership and payment processing. We have two separate legal entities: • Company A: owns the app and the Apple Developer account • Company B: operates the business and processes all payments (via a third-party payment provider, Klarna) Klarna’s merchant agreement is signed with Company B, and all payments go to Company B’s bank account. Company A has no involvement in the payment flow. Is this setup permitted under Apple’s App Store guidelines? Specifically, is it acceptable for the developer account and app ownership to be held by Company A, while all in-app payments are processed and received by Company B?
0
0
80
2w
Reply to Overlay window above all windows, even when moving spaces
Your collectionBehavior is close — canJoinAllApplications is the right option for spanning other apps' Spaces — but two other pieces are missing for floating above full-screen apps: 1. Accessory activation policy. macOS doesn't layer regular foreground apps above other apps' full-screen Spaces. Overlay utilities like DropOver use NSApplicationActivationPolicyAccessory, which removes the Dock icon and app menu bar (most overlay utilities add a menu bar status item in their place) and lets the app's windows appear above full-screen content from other apps. In your app delegate's applicationDidFinishLaunching: NSApp.setActivationPolicy(.accessory) 2. NSPanel with .nonactivatingPanel. An NSWindow activates its app when ordered front, which can cause a full-screen app to exit its Space. An NSPanel with the .nonactivatingPanel style mask doesn't. Full panel setup: let panel = NSPanel( contentRect: NSRect(x: 200, y: 200, width: 260, height: 140), styleMask: [.nonactivatingPanel, .titled, .closable]
Topic: UI Frameworks SubTopic: General Tags:
2w
How much practical benefit is there to XPC-based privilege separation?
Privilege separation is one of the two main reasons to use XPC services given by https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingXPCServices.html — With traditional applications, if an application becomes compromised through a buffer overflow or other security vulnerability, the attacker gains the ability to do anything that the user can do. To mitigate this risk, Mac OS X provides sandboxing—limiting what types of operations a process can perform. […] Each XPC service has its own sandbox, so XPC services can make it easier to implement proper privilege separation. The idea (iiuc) being that if the main process is compromised, the spicier operations have been separated out to a separate process space, and this improves the security of the system. But if the main process is compromised, and that main process is trusted by the more-privileged XPC service, is not the system still compromised in practice? That is rather than the exploit being:
3
0
198
2w
Reply to Issues with TCP Socket Management and Ghost Data on ESP32 (Swift)
Hello, thank you for the insights and the links; I am already reviewing the documentation to implement the necessary fixes. To provide more context on my scenario: the app communicates with a scale via TCP protocol. The scale creates its own dedicated Wi-Fi network exclusively for local network data transmission. The workflow is as follows: as soon as the app connects, the scale starts continuously sending data strings in the format: C, 050.1,c,N,000.0,. The app is only supposed to receive and process these values. Regarding the disconnection issue: the scale is dropping the TCP connection. The hardware developer (scale side) analyzed their logs and identified that the scale is receiving strange character sequences, such as ggggggggggfdhj. According to them, these strings are originating from the app. The critical point is that, in my iOS logs, I cannot find any record of the app sending this data, whether voluntarily or involuntarily. Since my code does not use unsafe pointers, as you observed, I am
2w
Markup Tool: Support for persistent tool presets (color, stroke, fill settings)
Markup Tool: Support for persistent tool presets (color, stroke, fill settings) I use Markup heavily for work — up to 20 images per day, always with the same settings: red arrow or rectangle, no fill, specific stroke width. The problem has two parts: Part 1 – Markup resets everything: Every time Markup is opened, all settings reset: tool, color, fill, stroke width. This means 3–4 manual steps per image, adding up to 80 unnecessary interactions per day. Part 2 – The default red is unusable: The red in Apple’s color palette is muted and too pale for clear, high-contrast annotations. I have to open the color wheel every single time to manually select a proper, vivid red. The copy/duplicate workaround only helps within one image — as soon as a new photo or screenshot is opened, everything starts over from scratch. Markup has no memory between different images. Switching to a third-party annotation app is not a solution — the entire advantage of Markup is its native integration directly within th
2
0
321
2w
Workarounds for Xcode previews errors: Cannot preview in this file - Failed to Launch
I have started to have issues with SwiftUI previews of iOS apps with projects under the Documents folder. I have experimented that in Xcode 26.4 and I am still seeing it in 26.5. The error is: Cannot preview in this file. Failed to launch xyz.abc.TestApp Looking at the diagnostics, Xcode gets a permission denied error when trying to open /Users/me/Documents/path/to/TestApp/DerivedData/TestApp/Build/Intermediates.noindex/TestApp.build/Debug-iphonesimulator/TestApp.build/Objects-normal/arm64/ContentView.1.preview-thunk-launch.o Error details below. Note that I have set DerivedData folders relative to the projects' roots. Additional information: I get errors on freshly created iOS projects, just trying to preview the default ContentView. Xcode has full disk access set in System Preferences > Privacy & Security. I have cleaned build folders, deleted the simulators, Xcode itself, cleared various caches, restarted and reinstalled Xcode to no avail. Checking Editor > Canvas > Use Legacy Previews Executi
4
0
210
2w
Please Help, Pending Termination Notice After App Stuck in Review
HI, Following up on this thread, the situation has escalated significantly. After my app was stuck in review for nearly 2 months, I received a Pending Termination Notice on my entire developer account citing section 3.2(f), concept or feature switch schemes. All of my apps have been removed from the App Store, including apps that were already live and had not been submitted or modified in any way. The notice states that automation may have been used as part of the review process, and I received the exact same notice for every single app on my account, which suggests this was a blanket automated action rather than a specific finding per app. I have already submitted individual app appeals and a full account reinstatement request through the official channels. I am an independent developer based in France under the Small Business Program and this account represents years of work. I would kindly ask if this can be looked into and escalated to the appropriate team. I am happy to provide any information n
1
0
95
2w
Reply to System Panic with IOUserSCSIParallelInterfaceController during Dispatch Queue Configuration
Hi Kevin, Thank you for your guidance on the UserProcessBundledParallelTasks architecture and IPC optimization. After several adjustments, our DEXT driver is now running stably. We have completed a comprehensive performance comparison between Bundled Mode and Legacy Mode. Below is a summary of our findings. Following your suggestion, we analyzed the console logs during 4K Random I/O stress tests (iodepth=32). By analyzing approximately 6,363 calls, we confirmed that the kernel actively performs command batching: Results: Slots per Call (Count) Frequency Observation 1 Slot 5,654 Standard/Low load; kernel dispatches immediately. 2 Slots 628 Active Batching initiated under increased pressure. 3 - 4 Slots 75 Sustained high-concurrency batching. 5+ Slots 6 High-load peaks (Max observed: 11 slots per call). This data confirms that the batching mechanism effectively reduces the number of RPC/IPC calls to the DEXT when the system is under pressure. We conducted benchmarks using fio on RAID 5 array (4 HDDs) c
Topic: App & System Services SubTopic: Drivers Tags:
2w
Apple Developer Program Enrolment
My Apple Developer Program enrolment been pending since April 2026. I have received no response from Apple since around 2 weeks. I have also contacted support last week but received no response from them as well. I had initially submitted by identity/company verification documents 2 weeks back. However, I still kept getting weekly reminders to upload documents. I have now uploaded the documents for the second time as after the first time I did not receive any confirmation for the submission. I am unable to request for call/phone support. My enrollment ID: QDH59Y57T7 My Case ID: 102887512171 Is there anything else I need to provide? Has anyone else encountered this problem? And what should I do? Thank you.
1
0
130
2w
LAContext and its usage in context of Local Authentication
While working with Local Authentication framework, specifically LAContext class I found myself with few contradictions to documentation, and although I believe that those differences are rather positive than negative, either documentation is lacking behind or those APIs are not working as intended - which I believe is combination of both. 1. Local Authentication 1.1 Biometry type, and associated with it hash With introduction of LADomainState one can extract underlying biometry type along it's (current) state hash this way: @available(iOS 18, macOS 15, *) func postIOS18() { let context = LAContext() let biometryType = context.domainState.biometry.biometryType // (1) let biometryStateHash = context.domainState.biometry.stateHash // (2) } prior to receiving above APIs, we would retrieve such information something along those lines: func preIOS18() { let context = LAContext() let policy: LAPolicy // ... var error: NSError? _ = context.canEvaluatePolicy(policy, error: error) // (3) // ... (Handle error -
1
0
284
2w
LAContext and its usage in context of Local Authentication
While working with Local Authentication framework, specifically LAContext class I found myself with few contradictions to documentation, and although I believe that those differences are rather positive than negative, either documentation is lacking behind or those APIs are not working as intended - which I believe is combination of both. 1. Local Authentication 1.1 Biometry type, and associated with it hash With introduction of LADomainState one can extract underlying biometry type along it's (current) state hash this way: @available(iOS 18, macOS 15, *) func postIOS18() { let context = LAContext() let biometryType = context.domainState.biometry.biometryType // (1) let biometryStateHash = context.domainState.biometry.stateHash // (2) } prior to receiving above APIs, we would retrieve such information something along those lines: func preIOS18() { let context = LAContext() let policy: LAPolicy // ... var error: NSError? _ = context.canEvaluatePolicy(policy, error: error) // (3) // ... (Handle error -
2
0
337
2w
Need help urgent for FlightTest add external testers issue.
Hello, I'm experiencing a persistent issue with TestFlight and app reviews on App Store Connect, and I hope someone else has encountered this before. About a week ago, when trying to add external testers to test the initial TestFlight builds, I received the following error: There was an error processing your request. Please try again later. Since there were no other details, it was impossible to know the source of the problem. After doing some research, I found the root cause of the problem in the browser console; errors : [ { id : c7300330-93d7-4aee-af8e-1aeffeff81ae, status : 422, code : ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, title : Beta contract is missing for the app., detail : Beta Contract is missing. } ] Since then: I've researched everything needed for TestFlight, including contracts, bank details, and so on, but I can't create external TestFlight tests. Internal TestFlight builds appear, but they can't be downloaded (Requested application not available or present). My applications just
0
0
122
2w
Reply to Keychain Group
[quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] it cannot be debugged. [/quote] Why is that? [quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] The same IPA file is installed on both this problematic device and the normally functioning devices. [/quote] How do you create that .ipa? The usual process for doing that is to export an Ad Hoc signed version of your app. If that’s the case then you can export a Development signed version from the some Xcode archive. At that point you have an exact some copy of the code that you can run and debug with Xcode. Just to be sure, you should check the keychain entitlements for each build. The .ipa is a zip archive under the covers, so you can change the extension to .zip and unpack it. Once you do that, dump the entitlements like so: % codesign -d --entitlements - /path/to/my.app Then use the same command to dump the entitlements of the Development signed version. Finally, compare the
Topic: Privacy & Security SubTopic: General Tags:
2w
Reply to Issues with TCP Socket Management and Ghost Data on ESP32 (Swift)
You’re using the term socket as a synonym for network connection. That’s not correct, and it muddies the waters when it comes to how to approach this problem. For example, one of your issues relates to connection viability, and the best way to handle that problem varies depending on whether you’re using the BSD Sockets API or the Network framework API. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Is it possible to keep this TCP connection active in the background indefinitely on iOS while the user interacts with other apps? [/quote] No. See iOS Background Execution Limits. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Invalid Outbound Data … My logs show strange character sequences (like gggggggggfdhj or vfgdddddddddddtty) being sent involuntarily. [/quote] It’s very unlikely that’s being generated by Network framework. The majority of times when I see problems like this it’s because the app itself is sending that junk, usually because
2w
Question regarding app ownership and payment processing by separate legal entities
I have a question regarding your policies on app ownership and payment processing. We have two separate legal entities: • Company A: owns the app and the Apple Developer account • Company B: operates the business and processes all payments (via a third-party payment provider, Klarna) Klarna’s merchant agreement is signed with Company B, and all payments go to Company B’s bank account. Company A has no involvement in the payment flow. Is this setup permitted under Apple’s App Store guidelines? Specifically, is it acceptable for the developer account and app ownership to be held by Company A, while all in-app payments are processed and received by Company B?
Replies
0
Boosts
0
Views
80
Activity
2w
Reply to Overlay window above all windows, even when moving spaces
Your collectionBehavior is close — canJoinAllApplications is the right option for spanning other apps' Spaces — but two other pieces are missing for floating above full-screen apps: 1. Accessory activation policy. macOS doesn't layer regular foreground apps above other apps' full-screen Spaces. Overlay utilities like DropOver use NSApplicationActivationPolicyAccessory, which removes the Dock icon and app menu bar (most overlay utilities add a menu bar status item in their place) and lets the app's windows appear above full-screen content from other apps. In your app delegate's applicationDidFinishLaunching: NSApp.setActivationPolicy(.accessory) 2. NSPanel with .nonactivatingPanel. An NSWindow activates its app when ordered front, which can cause a full-screen app to exit its Space. An NSPanel with the .nonactivatingPanel style mask doesn't. Full panel setup: let panel = NSPanel( contentRect: NSRect(x: 200, y: 200, width: 260, height: 140), styleMask: [.nonactivatingPanel, .titled, .closable]
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
How much practical benefit is there to XPC-based privilege separation?
Privilege separation is one of the two main reasons to use XPC services given by https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingXPCServices.html — With traditional applications, if an application becomes compromised through a buffer overflow or other security vulnerability, the attacker gains the ability to do anything that the user can do. To mitigate this risk, Mac OS X provides sandboxing—limiting what types of operations a process can perform. […] Each XPC service has its own sandbox, so XPC services can make it easier to implement proper privilege separation. The idea (iiuc) being that if the main process is compromised, the spicier operations have been separated out to a separate process space, and this improves the security of the system. But if the main process is compromised, and that main process is trusted by the more-privileged XPC service, is not the system still compromised in practice? That is rather than the exploit being:
Replies
3
Boosts
0
Views
198
Activity
2w
Reply to Issues with TCP Socket Management and Ghost Data on ESP32 (Swift)
Hello, thank you for the insights and the links; I am already reviewing the documentation to implement the necessary fixes. To provide more context on my scenario: the app communicates with a scale via TCP protocol. The scale creates its own dedicated Wi-Fi network exclusively for local network data transmission. The workflow is as follows: as soon as the app connects, the scale starts continuously sending data strings in the format: C, 050.1,c,N,000.0,. The app is only supposed to receive and process these values. Regarding the disconnection issue: the scale is dropping the TCP connection. The hardware developer (scale side) analyzed their logs and identified that the scale is receiving strange character sequences, such as ggggggggggfdhj. According to them, these strings are originating from the app. The critical point is that, in my iOS logs, I cannot find any record of the app sending this data, whether voluntarily or involuntarily. Since my code does not use unsafe pointers, as you observed, I am
Replies
Boosts
Views
Activity
2w
tahoe 26.4.1 chdir(2) problem
as of this posting, chdir(2) is now following symbolic links. As per the man page, this IS NOT what it is supposed to do. This is a recent change as of 5/13/26
Replies
2
Boosts
0
Views
176
Activity
2w
Markup Tool: Support for persistent tool presets (color, stroke, fill settings)
Markup Tool: Support for persistent tool presets (color, stroke, fill settings) I use Markup heavily for work — up to 20 images per day, always with the same settings: red arrow or rectangle, no fill, specific stroke width. The problem has two parts: Part 1 – Markup resets everything: Every time Markup is opened, all settings reset: tool, color, fill, stroke width. This means 3–4 manual steps per image, adding up to 80 unnecessary interactions per day. Part 2 – The default red is unusable: The red in Apple’s color palette is muted and too pale for clear, high-contrast annotations. I have to open the color wheel every single time to manually select a proper, vivid red. The copy/duplicate workaround only helps within one image — as soon as a new photo or screenshot is opened, everything starts over from scratch. Markup has no memory between different images. Switching to a third-party annotation app is not a solution — the entire advantage of Markup is its native integration directly within th
Replies
2
Boosts
0
Views
321
Activity
2w
Workarounds for Xcode previews errors: Cannot preview in this file - Failed to Launch
I have started to have issues with SwiftUI previews of iOS apps with projects under the Documents folder. I have experimented that in Xcode 26.4 and I am still seeing it in 26.5. The error is: Cannot preview in this file. Failed to launch xyz.abc.TestApp Looking at the diagnostics, Xcode gets a permission denied error when trying to open /Users/me/Documents/path/to/TestApp/DerivedData/TestApp/Build/Intermediates.noindex/TestApp.build/Debug-iphonesimulator/TestApp.build/Objects-normal/arm64/ContentView.1.preview-thunk-launch.o Error details below. Note that I have set DerivedData folders relative to the projects' roots. Additional information: I get errors on freshly created iOS projects, just trying to preview the default ContentView. Xcode has full disk access set in System Preferences > Privacy & Security. I have cleaned build folders, deleted the simulators, Xcode itself, cleared various caches, restarted and reinstalled Xcode to no avail. Checking Editor > Canvas > Use Legacy Previews Executi
Replies
4
Boosts
0
Views
210
Activity
2w
Please Help, Pending Termination Notice After App Stuck in Review
HI, Following up on this thread, the situation has escalated significantly. After my app was stuck in review for nearly 2 months, I received a Pending Termination Notice on my entire developer account citing section 3.2(f), concept or feature switch schemes. All of my apps have been removed from the App Store, including apps that were already live and had not been submitted or modified in any way. The notice states that automation may have been used as part of the review process, and I received the exact same notice for every single app on my account, which suggests this was a blanket automated action rather than a specific finding per app. I have already submitted individual app appeals and a full account reinstatement request through the official channels. I am an independent developer based in France under the Small Business Program and this account represents years of work. I would kindly ask if this can be looked into and escalated to the appropriate team. I am happy to provide any information n
Replies
1
Boosts
0
Views
95
Activity
2w
Reply to System Panic with IOUserSCSIParallelInterfaceController during Dispatch Queue Configuration
Hi Kevin, Thank you for your guidance on the UserProcessBundledParallelTasks architecture and IPC optimization. After several adjustments, our DEXT driver is now running stably. We have completed a comprehensive performance comparison between Bundled Mode and Legacy Mode. Below is a summary of our findings. Following your suggestion, we analyzed the console logs during 4K Random I/O stress tests (iodepth=32). By analyzing approximately 6,363 calls, we confirmed that the kernel actively performs command batching: Results: Slots per Call (Count) Frequency Observation 1 Slot 5,654 Standard/Low load; kernel dispatches immediately. 2 Slots 628 Active Batching initiated under increased pressure. 3 - 4 Slots 75 Sustained high-concurrency batching. 5+ Slots 6 High-load peaks (Max observed: 11 slots per call). This data confirms that the batching mechanism effectively reduces the number of RPC/IPC calls to the DEXT when the system is under pressure. We conducted benchmarks using fio on RAID 5 array (4 HDDs) c
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
2w
Apple Developer Program Enrolment
My Apple Developer Program enrolment been pending since April 2026. I have received no response from Apple since around 2 weeks. I have also contacted support last week but received no response from them as well. I had initially submitted by identity/company verification documents 2 weeks back. However, I still kept getting weekly reminders to upload documents. I have now uploaded the documents for the second time as after the first time I did not receive any confirmation for the submission. I am unable to request for call/phone support. My enrollment ID: QDH59Y57T7 My Case ID: 102887512171 Is there anything else I need to provide? Has anyone else encountered this problem? And what should I do? Thank you.
Replies
1
Boosts
0
Views
130
Activity
2w
LAContext and its usage in context of Local Authentication
While working with Local Authentication framework, specifically LAContext class I found myself with few contradictions to documentation, and although I believe that those differences are rather positive than negative, either documentation is lacking behind or those APIs are not working as intended - which I believe is combination of both. 1. Local Authentication 1.1 Biometry type, and associated with it hash With introduction of LADomainState one can extract underlying biometry type along it's (current) state hash this way: @available(iOS 18, macOS 15, *) func postIOS18() { let context = LAContext() let biometryType = context.domainState.biometry.biometryType // (1) let biometryStateHash = context.domainState.biometry.stateHash // (2) } prior to receiving above APIs, we would retrieve such information something along those lines: func preIOS18() { let context = LAContext() let policy: LAPolicy // ... var error: NSError? _ = context.canEvaluatePolicy(policy, error: error) // (3) // ... (Handle error -
Replies
1
Boosts
0
Views
284
Activity
2w
LAContext and its usage in context of Local Authentication
While working with Local Authentication framework, specifically LAContext class I found myself with few contradictions to documentation, and although I believe that those differences are rather positive than negative, either documentation is lacking behind or those APIs are not working as intended - which I believe is combination of both. 1. Local Authentication 1.1 Biometry type, and associated with it hash With introduction of LADomainState one can extract underlying biometry type along it's (current) state hash this way: @available(iOS 18, macOS 15, *) func postIOS18() { let context = LAContext() let biometryType = context.domainState.biometry.biometryType // (1) let biometryStateHash = context.domainState.biometry.stateHash // (2) } prior to receiving above APIs, we would retrieve such information something along those lines: func preIOS18() { let context = LAContext() let policy: LAPolicy // ... var error: NSError? _ = context.canEvaluatePolicy(policy, error: error) // (3) // ... (Handle error -
Replies
2
Boosts
0
Views
337
Activity
2w
Need help urgent for FlightTest add external testers issue.
Hello, I'm experiencing a persistent issue with TestFlight and app reviews on App Store Connect, and I hope someone else has encountered this before. About a week ago, when trying to add external testers to test the initial TestFlight builds, I received the following error: There was an error processing your request. Please try again later. Since there were no other details, it was impossible to know the source of the problem. After doing some research, I found the root cause of the problem in the browser console; errors : [ { id : c7300330-93d7-4aee-af8e-1aeffeff81ae, status : 422, code : ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, title : Beta contract is missing for the app., detail : Beta Contract is missing. } ] Since then: I've researched everything needed for TestFlight, including contracts, bank details, and so on, but I can't create external TestFlight tests. Internal TestFlight builds appear, but they can't be downloaded (Requested application not available or present). My applications just
Replies
0
Boosts
0
Views
122
Activity
2w
Reply to Keychain Group
[quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] it cannot be debugged. [/quote] Why is that? [quote='887425022, iceboy, /thread/825789?answerId=887425022#887425022, /profile/iceboy'] The same IPA file is installed on both this problematic device and the normally functioning devices. [/quote] How do you create that .ipa? The usual process for doing that is to export an Ad Hoc signed version of your app. If that’s the case then you can export a Development signed version from the some Xcode archive. At that point you have an exact some copy of the code that you can run and debug with Xcode. Just to be sure, you should check the keychain entitlements for each build. The .ipa is a zip archive under the covers, so you can change the extension to .zip and unpack it. Once you do that, dump the entitlements like so: % codesign -d --entitlements - /path/to/my.app Then use the same command to dump the entitlements of the Development signed version. Finally, compare the
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Issues with TCP Socket Management and Ghost Data on ESP32 (Swift)
You’re using the term socket as a synonym for network connection. That’s not correct, and it muddies the waters when it comes to how to approach this problem. For example, one of your issues relates to connection viability, and the best way to handle that problem varies depending on whether you’re using the BSD Sockets API or the Network framework API. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Is it possible to keep this TCP connection active in the background indefinitely on iOS while the user interacts with other apps? [/quote] No. See iOS Background Execution Limits. [quote='826000021, Gabriel_Heidemann, /thread/826000, /profile/Gabriel_Heidemann'] Invalid Outbound Data … My logs show strange character sequences (like gggggggggfdhj or vfgdddddddddddtty) being sent involuntarily. [/quote] It’s very unlikely that’s being generated by Network framework. The majority of times when I see problems like this it’s because the app itself is sending that junk, usually because
Replies
Boosts
Views
Activity
2w