“offloading”

Hi all, I'm facing a strange issue on my iPhone 15 Pro Max with iOS 17.0.3 official release. A few days ago I was using WeChat and was making a voice call with my Airpods, and accidentally dropeed one of the Airdpod, after I picked it up, all of a sudden the person on the other end cannot hear me via the voice call anymore. Then I tried to send a voice message on WeChat and noticed it's also failing. Here's a list of things I've tried to investigate/narrow down this issue: I checked in Privacy settings and confirmed the toggle for Microphone is turned on for WeChat, also tried switching it to off then back on. I also checked WeChat's own permission settings and made sure all the toggles for Microphone are turned on, also tried switching them to off then back on. Tested other apps that uses the microphone (e.g. phone, facetime, voice memo, instagram, QQ (also from Tencent) etc.), and they are all working fine. Tried normal restart and hard restart of the phone, issue persists Log out from Wechat and log back i

Hi, I have an app that is used by several Shortcuts. In many cases, users download the Shortcut, install the app, and only use the App through the Shortcut, and only through the in-extension Intent. They might never open the app. I've received complaints from users that the app keeps disappearing: apparently, because the app itself is never opened (only the in-extension Intent is), it doesn't count as an actual usage for offloading, and so the app gets offloaded. What can I do?

It appears that some attachments get stuck and aren't offloaded like they are on iOS. I have 200-300 attachments, all dated 5/3/2021 (perhaps that's when I last formatted this Mac and downloaded from iCloud), and then it keeps 1-10 attachments from every month after that. I don't want to delete the attachments because I want them to stay in iCloud. Is there a terminal command to offload or set the maximum space Messages may use or something? Signing out and signing back in does nothing. They stay on the hard drive. Messages on my phone with the same synced conversations stay around 21GB.

Hi all, I've been struggling a bit with SwiftData, I have a really simple data model but I need to do a fairly complex query over a one-to-many relationship that results in aggregate values. And I want to be able to sort and filter those aggregates. The model looks like this: @Model class Category { var name: String var items = [Item]() } @Model class Item { var added: Date var checked: Date? } In a typical use case I'd expect their to be at most around 50 categories and perhaps 20 items per category. In my UI I would like to be able to sort categories in a couple of ways: by name, by date added and by date checked with a fallback on date added. Also, in my list view I want to be able to list categories and show the checked date of the most recently checked item. I can think of a couple of solutions here, to start of with I can do all the sorting and filtering client-side. In the list view I could retrieve all the categories and then find the most recently checked item per category and go from there. Another

I have multiple mobile applications, one developed in React Native and the other in Objective-C and Swift hybrid technology. I use my own system to send push notifications, and these notifications are left encrypted in the Apple queues. However, in any of my applications, I am unable to catch these messages in the code block where I decrypt them. As a result, users see the messages encrypted. While I can deterministically detect this issue on devices experiencing the offload feature from Apple, I've also noticed sporadic occurrences of this issue on devices not utilizing offload. Due to my security policies, I have no chance of sending messages unencrypted. I'm trying to understand why this is happening and need suggestions for a solution. Is there anyone who can help? Additional Information: I use my own system for push notifications. Messages are left encrypted in the Apple queues. I am unable to catch the messages in the code block where I decrypt them in one of the applications. I can de

We are developing an app which connects to a BLE peripheral in the background whenever it gets close to it. What we have used so far is that we monitor a circular region. When the phone enters the region the app will start scanning for peripherals and when it discovers the peripheral it connects to it. This worked pretty well for the last few iOS versions, perhaps iOS 14-16. It wasn't perfect but for the most part it would feel like it connected rather quickly when you would approach the BLE peripheral. If you listen to music via BLE or talk to someone using your BLE headset then it could sometimes work noticeably worse. But, as said, for the most part it would work satisfactory. Starting with iOS 17 and analyzing the functionality over the past 6 months or so we've noticed a clear worsening of it. It does generally connect to the peripheral but the user might often have to wait for quite some time. Rather frequently the user must even light up the screen of the phone before anything even happens. It appears

Hi, When using Swift Concurrency blocking tasks like file I/O, GPU work and networking can prevent forward moving progress and have the potential to exhaust the cooperative thread pool and under utilize the CPU. It's been recommended to offload these tasks from the cooperative thread pool. Is my understanding correct that the preferred way to do this is by creating async tasks via Dispatch or OperationQueue? And combining these with Continuations if a return value from the task is required? Or should I always be using Continuations in combination with Dispatch/OperationQueue? There are also Executors but the documentation seems a bit limited on how to use these. The new TaskExecutor is also only available on the latest beta's. My question is basically what is the recommend way to offload a task? Thanks!