“offloading”

Hi, Could you elaborate on When overloaded, stale metal render passes need to be 'aborted', which results in metal callbacks not being called.? This approach seems like dynamic load balancing to maximize throughput. It's unclear how well this could work with current Metal API and seems unlikely to be successful with OS watchdogs. Instead we recommend reducing and optimizing workload. Guidance on that can be found in Improving your game’s graphics performance and settings (even though your app may not be a game). You may also want to consider offloading some rendering work to compute to improve efficiency. See Compute Passes.

Thanks for the post. Very interesting question about that API! What do you mean for staleness check? Once a Network Extension is installed, authorized by the user, and saved to the system preferences via its respective manager, the configuration is owned by the OS. The OS will continue to invoke the extension binaries as needed, regardless of whether the main app has been force-quit or hasn't been launched in months. I’m interested on the behavior you are seeing is almost certainly caused by a secondary factors. Has the user has offload unused apps? I believe when an app is offloaded, its extension binaries are deleted along with the main app. The VPN profile or Hotspot configuration will still appear in iOS Settings, but the OS will silently fail to invoke the NEHotspotHelper or fail to connect the NEPacketTunnelProvider because the executable no longer exists. You have mentioned 90 days? If this app is being distributed to internal testers or beta users via TestFlight, the app and its exte

We have a UNUserNotification that is scheduled for a certain date. The content of this notification might be subject to change as we get closer to its delivery. My preferred way to do this is to offload the logic for ‘rendering’ the notification to a push provider. At that point your app doesn’t need to resume in the background and update the notification; rather, the push provider just sends the right push notification at the right time.If you can’t do that, refreshing the notification on the client is going to be problematic. BGAppRefreshTask is the right option for this but most developers who try to use this tech (which is equivalent to the old ‘background fetch’ mechanism) are disappointed with how infrequently it resumes their app. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Documents or an Application Support directory in the Library. From everything I’ve read, it seems that Apple’s intent is Library/Application Support. Which is the correct location? Application Support - though it doesn’t really matter except in the case where you have a mixture of “documents” that the user needs to have access to via e.g. the Files app and “non-documents” that they shouldn’t. the app stopped displaying what was two years of data in SQLite. I haven’t yet tested for index corruption, however one of the programmers believes this resulted from an iOS update that needed space and cleared data in the cache (but that makes no sense to myself). You weren’t storing it in the Caches directory, or using the “don’t backup” xattr, were you? OS updates can “offload” apps, but I’ve not seen any reports of that causing problems. Do you vacuum your sqlite db?

Well from a design perspective I like to use @State variables in views just for dealing with state in the view. What you're doing would seem to classify as part of the business logic of your app so I would offload that logic away from your view to your model or view model. Look up MVVM if you don't know what these are. Anyway if you were to take an MVVM approach your code might look like: struct ContentView: View { @ObservedObject var viewModel: MyViewModel var body: some View { Button(action: { viewModel.readApk() }) { Text(Read Apk) } .padding() Button(action: { viewModel.signApk() }) { Text(Sign Apk) } .padding() } } With this approach processString, usingDirString, and returnDirString are all abstracted away from your view. By keeping your view code and your business logic separate it makes it easier to deal with each of them in a more isolated and clear manner.

My app lets you know if there are upcoming events in your area and it would be nice if it could check every week or so with my server to see if there were any and update the users local Notifications. So this would require it to run in the background and access the web.iOS has a mechanism for this, namely background fetch. You learn more about it in the Background Execution section of the App Programming Guide for iOS.However, if your app is not being run regularly by the user then it’s likely that your app will fall off the background fetch radar. The best way to meet your requirements is to offload this periodic work to a server. That is, have your server poll the event database and, if there’s anything relevant for this user, post a push notification. That is power efficient (no code needs to execute on the user’s device) and reliable.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I have a 128 Gig Mac Mini. I was ready to give up on Big Sur after seeing how much free space I needed to free up. Here's how I made the space available. Copy the Big Sur installer to a removable drive and remove it from your startup drive. Run the installer to see how much more space you need. Follow Apple instructions to offload Music and Photos libraries to a removable drive. If you are a developer, you probably have a huge Developer folder in your user library. Copy it to a removable drive and remove it temporarily. These steps worked for me and I was able to upgrade to Big Sur. The installer seemed to do a very good job of cleaning up OS X folders because I had 50 GB available after the install. Plenty of space to copy the Developer folder back to the startup drive.

SOLVED (at least for me)! Over several weeks after upgrading from 13.7 to 14.4.x I tried turning off MANY Settings and offloading all 3rd-party apps -- to no avail. Still sluggish, overheating, and fast battery drain anytime screen was on. An apple-support tech mgr suggested doing a full Settings&Content Reset to confirm if a hardware problem. And phone worked fine as as empty new phone... so was definately confused software. So I re-did a full reset and restored from iCloud backup and it SOLVED this problem on my iPhoneSE(1st gen). So do THIS: do a full icloud-backup (pay 99 cents for 1 month increased storage) (Settings/General/RESET ALL CONTENT AND SETTINGS (As it reboots it will reset/reinstall to 14.4.2) Follow phone setup steps and login into your apple ID and restore from the iCloud backup. After doing those my SE was back to normal!! :)

OK, this specific goal:I need to do a background pull request every 10 seconds using Swift.is not achievable on iOS. Once your app is moved to the background, it is typically suspended, and it can’t make network requests while it’s suspended. There are things you can do to hold off that suspension, and also get resumed in the background, but nothing will give you regular background executable time every 10 seconds.Even if you could, you’d quick run through the user’s battery.You need to rethink your approach. I specifically recommend that you reconsider using push notifications. There’s a reason Apple puts so much emphasis on push notifications. In a push model, you offload this work to a server that doesn’t have to worry about all day battery life.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I feel you have a bit wrong idea what Neural Engine is. It have nothing common to CPU or GPU - it's just a machine learning accelerator with very limited area of application - even not every layer type in your model can be used. Look at This FAQ for better understanding what it is and what it can. Q: Is there any low-level API to create my very own work-loads? A: Yes and No. Low level AppleNeuralEngine.framework is private to Apple and you can't use it. But: take a look at ANE Tools - compiler and decompiler for Neural Engine. Also there is coremltools - this will help to interface with TensorFlow and PyTorch Q: Can I use the Neural Engine to offload the CPU? I am especially interested in parallelism using threads. A: Basically - No. ANE can't execute CPU/GPU code and don't have threads. It operates with layer connectivity map and net weights. One more thing - vDSP and veclib DONT use ANE.

And another found is that on the home Wifi network(which has PPPoE router provided by carrier) with an iOS 14 iPhone the message will be like udp_validate_cksum_internal * udp incorrect IPv4-UDP non-offload checksum * ulen 1506 And the pppoe header length is 6. Compared with previous network with Vlan the error message showed ulen is 1502. I believe there most probably a bug exists somewhere in iOS 14 kernel or in network extension. Since I didn't found such issue under the same condition on iOS 12, this issue may only exists in iOS 14. The reproduce condition is with NEPacketTunnelProvider set the MTU of the UTUN to be a value bigger or equal than 1480(Theoretically we should be able to set this value to a very big size like 65535 and without any problem) or overhead size to be 0, and run it on an iOS 14 iPhone, on a Wifi network which has a Vlan setting or PPPoE, on inbound packets there will be such problem.

Reusing one big buffer instead of many seems like a great idea. Less moving parts the better here. Why the vertices are expensive to compute is mostly a question of scale. For instance, with indirect draw calls I can handle 4000+ chunks of terrain and 25 million+ vertices at 60 fps. With much lower terrain distances the meshing on the CPU can keep up fine, but when I push it there is a lot of frame dropping when moving over the terrain and generating meshes for dozens or hundreds of chunks. Part of this is that my meshing is single-threaded on the CPU, but my experience with Swift multi-threading is so far hit and miss for this kind of thing. As such, parallelism is the entire point of trying to offload this to a compute shader. The process of vertex generation is pretty standard for block/Minecraft-style terrain. We loop through all the blocks in a chunk, and if a block is solid, we check if any of its neighbours are air, and therefore if we should put a quad opposite it. Roughly: for y in i..

Oh, interesting. This actually came up when I filed a different bug where kernel offloaded IO wasn't working (FB17773100). At first, it was closed because I didn't include that key (since it wasn't documented or in the template), but it still didn't work after adding that key until macOS 15.6 beta 3, where it's now fixed. Adding some background context, the reason the key exists is that because kernel memory is involved, we wanted to make sure it would only occur in clients that explicitly asked for it. The metadata I/O APIs also involve kernel memory, which is why it ended up being limited by the same plist key. For anyone else who finds this thread, FB18614667 is fixed in macOS 15.6 RC (24G84). Yep. It's always tricky to talk about future stuff, but it's often the case that the bug fix is already on its way to shipping when I'm writing about them. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

There could be several reasons why quick replies are not being saved on WhatsApp for Business on iOS 16.3.1. Here are some troubleshooting steps you can try: 1.Check if you have the latest version of WhatsApp for Business installed on your device. If not, update it from the App Store. 2.Make sure that you have enabled the Quick Replies feature in the Business Settings of your WhatsApp account. To do this, go to Settings > Business Settings > Quick Replies and toggle the switch to ON. 3.Ensure that you have granted WhatsApp permission to access your device's microphone and camera. Quick Replies require access to these features to work properly. 4.Try clearing the cache of WhatsApp. Go to Settings > General > iPhone Storage, find WhatsApp in the list of apps, and tap on it. Then, tap Offload App or Delete App to remove it from your device. After that, reinstall WhatsApp and try setting up Quick Replies again. 5.If none of the above solutions work, contact WhatsApp support for further assist

Yes, we have a similar problem: We have two installer plugins, and they have worked fine for 12 years (well, every few years, Apple makes a silent change and we have to adjust). Starting in OSX 10.14 or 10.15, the Installer is not working right for us: does not totally hang, but the GUI is non-responsive. Fortunately, in our design, the installation more-or-less finishes.It definitely looks like Apple changed the Installer app to offload any plugin software into other processes: the com.Apple.InstallerRemotePluginService ... it gets its own PID. In our case, a single Installer has three processes are running: Installer and two InstallerRemotePluginService processes.Our issue is that the plugins are not able to dynamically update controls/widgets on the installer GUI. They are updating a progress bar: but the main/GUI thread in the Installer process is not responding. I guess that software in the InstallerRemotePluginService cannot update widgets drawn by the main Installer process??Have not figured o