“offloading”

Hi eskimo, we would like our watch app to work without the phone nearby, so offloading the work to the iOS app is not an option for us. Using console app, I can see three errors: The CredStore - copyIdentPrefs - Error copying Identity cred. Error=-25300 error described above. An exception Exception: decodeObjectForKey: Object of class NSURLCredential returned nil from -initWithCoder: while being decoded for key An error TLS Client Certificates encountered error 1:89

… is mTLS just not supported on watchOS? That’s my understanding based on the bug I referenced above (r. 24523955). One workaround is to use Watch Connectivity to offload this work to your iOS app, where mTLS is available. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple 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.

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.

Huge benefits I think depending on what the price is though. Being able to offload your builds is great and even if you are a solo developer you have users I am assuming that will test your app.

Discussed this more with cross-functional teams and not using keys a no-go. This will not work if you want to share localization efforts across platforms beyond Apple which is more of a real-world scenario especially in enterprise settings. For example, Android requires localization keys to not have dots and other kinds of characters, also we found many 3rd party localization services had a character limit on key length. And when looking at very long localization entries, using the value as the key just doesn't make sense. I think sticking with my first intuition in using localization keys is the right way despite all the Apple sessions and samples showing otherwise. Also, just to share I was able to achieve isolating localization configurations by extending Text views to initialize from other Text views. This way, I can offload the localization configurations off the view by creating a bunch of static Text views and let the rest of the app pick them off the shelf. First I create the simple but awkwa

Offloading the alert logic to your servers and implementing push notifications (whether using a 3rd party push provider service, or maintaining your own push server), then sending these notifications at the intervals you wish, and developing notification scheduling as complicated as you can is definitely an option. Currently there is no way to accomplish what you want using local notifications.

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!! :)