“iPhone 16 pro”

Hello, we are experiencing a similiar issues on different Apple devices (iPhones and iPads). Was there any solution to this problem?

Encountering a network issue in WKWebView on iPhone 15 models with iOS 16.2, particularly under conditions of frequent large WebSocket data packets, is indeed unusual and concerning. This issue seems to affect the entire network stack for the app, which points to a deeper problem possibly related to resource exhaustion or a bug in handling network resources. Here are some steps and considerations to help diagnose and potentially resolve this issue: Diagnostic Steps Monitor Resource Usage: Use Instruments on macOS to monitor the app’s resource usage, especially focusing on CPU, memory, and network activity when the issue occurs. Look for spikes or anomalies that could indicate resource exhaustion. Check for Leaks: Ensure there are no memory leaks in your WebView handling code. Leaks can gradually consume resources, leading to instability. Instruments can also help identify memory leaks. Network Activity Logging: Log network activity to understand what happens when connections time out. Use URLSession’

Running large models like Qwen3 1.7B on devices with limited resources, such as the iPhone SE 3 with 4 GB of RAM, is indeed challenging. Let's address your questions and explore potential approaches to mitigate the issues you're facing: Observations and Possible Causes Memory Spike During Load: Dynamic Shape Usage: While dynamic shapes can help manage memory allocation during inference by not preallocating for the full context length, the initial loading process often requires more fixed memory to parse the model, set up internal structures, and potentially convert certain operations to formats supported by the hardware. Intermediate Conversion: Core ML might internally convert some operations from INT4 to INT8 or FP16 if the underlying hardware (BNNS/ANE) doesn't natively support INT4 operations. This can cause temporary spikes in memory usage during loading. Memory Limitations: The iPhone SE 3's 4 GB RAM is quite limited for large models, especially if additional overhead from the operatin

Ok, I have found a workaround. See the attached text, which contains a routine that shows how to create a CGImage from the NSImage that vImageBuffer_InitWithCGImage can handle successfully for the problematic image files. Apparently vImageBuffer_InitWithCGImage is brittle and it needs for the CGImage to be rather vanilla which this rendering logic accomplishes. The files that cause failures are jpegs that came from an Android phone which feature color profiles that confuse vImageBuffer_InitWithCGImage. This new method seems to fix all the problems, fingers crossed. CGImageFromNSImage.txt

Use this command: mount -t my_ngpc ngpc://login ~/my_ngpc Interesting. The part that makes this strange is that having the volume appear in the sidebar is actually the default behavior, which you normally DISABLE by passing the nobrowse option into mount. A few things: Please file a bug on this and post the bug number back here. Even if the behavior is expected, at a minimum it would probably be worth better documenting. I'd also appreciate you filing a separate bug asking for a high-level (it would probably end up in DiskArb) mount API that supports FSKit. The underlying issue here is that the lack of a high-level API means that you're not properly integrated into the system full volume architecture, which means the system isn't necessarily designed to pick up your mount. This is something we're obviously already aware of, but developer bugs help us prioritize work. What does the mount entry for your volume show when run mount to list all current mounts? This will between the kernel mark the volume nobrowse

Reporting this as still an issue as well. The red RDAR bar is still present and the app being tested on the Simulator zooms in incredibly far. No system apps are affected. The workaround until this is fixed is to change the display zoom in Settings > Developer to Large Text and then revert back to normal. You will need to do this every time you reboot the simulator for iPhone 12+13 Mini on any iOS version.

Use the following command 你说 mount | grep my_ngpc ngpc://login on /Users/li/my_mnt (my_ngpc, noowners, noatime, fskit, mounted by li) li@lideMacBook-Pro ~ % diskutil list | grep NGPC li@lideMacBook-Pro ~ % diskutil list | grep ngpc li@lideMacBook-Pro ~ % diskutil list | grep my_ngpc

Apple Developer Payment Issue (India – UPI + Developer App Case) Sharing this in case it helps another founder avoid confusion. I was trying to purchase the Apple Developer Program under my company Apple ID using the Apple Developer App on my iPhone. Inside the Developer App, I was correctly logged in using my company Apple ID. When I initiated the ₹8,700 payment using UPI: The UPI auto-renew mandate failed. The app then prompted me to complete the payment using Apple Account balance (Apple Wallet). I proceeded with the payment. The transaction was successful. However, the ₹8,700 was credited to my personal Apple ID’s Apple Account balance, not the company Apple ID. Why This Happened Even though I was logged into the Developer App with my company Apple ID, in my iPhone Settings, my personal Apple ID was signed in. When the payment was processed to Apple Wallet, it was credited to the Apple ID logged in at the device level (Settings) — not the Apple ID inside the Developer App. To verify this

Apple Developer Payment Issue (India – UPI + Developer App Case) Sharing this in case it helps another founder avoid confusion. I was trying to purchase the Apple Developer Program under my company Apple ID using the Apple Developer App on my iPhone. Inside the Developer App, I was correctly logged in using my company Apple ID. When I initiated the ₹8,700 payment using UPI: The UPI auto-renew mandate failed. The app then prompted me to complete the payment using Apple Account balance (Apple Wallet). I proceeded with the payment. The transaction was successful. However, the ₹8,700 was credited to my personal Apple ID’s Apple Account balance, not the company Apple ID. Why This Happened Even though I was logged into the Developer App with my company Apple ID, in my iPhone Settings, my personal Apple ID was signed in. When the payment was processed to Apple Wallet, it was credited to the Apple ID logged in at the device level (Settings) — not the Apple ID inside the Developer App. To verify this