offloading

And yet, after clearing out all of those settings, offloaded apps and provisioned certs the error message persists. 99$ “protection money” to, ya know, actually use your ~1000EU devices.

Hello guys.. I finally got the solution to this problem; Unable to install MyAppDomain: com.apple.dt.MobileDeviceErrorDomainCode: -402620383--The maximum number of apps for free development profiles has been reached.Domain: com.apple.dt.MobileDeviceErrorDomain Go to the Console app can be found in the Window >> Devices and Simulators >> click the 'Open Console' button in your phone's tab. In the Console app, type MIFreeProfileValidatedAppTracker in the upper right corner's search box will help you find the detail of this message after failed running your app. I have also found that most of the bundle IDs shown in the error message are auto offload apps. Turns out the Xcode misclassified all the auto offloaded apps (apps you have not used for a while) as your free developer account's test apps. If you encounter the same problem, the solution is to re-download all the offload apps. Then, turn off the auto offload in the iPhone Settings - iTunes & App Store - Offload

Found the answer in this thread. https://discussions.apple.com/thread/251383929 Turns out, you can't have any offloaded apps from ANY vendor, including Apple, installed on the device.

Having the exact same problem.@logicat Did you ever find a root cause or fix besides deleting & reinstalling your app?Can't create any new files.The error message is The file couldn't be saved. and there is no underlying error in the NSError instance.errno == 17 after the write failure.The file does not actually exist, nor are there any *.tmp.****** files present in the same parent directory.Affects a very small segment of my user base, but that number is growing.In my case, I only have reports for iOS 13+.Offloading the app *does not* fix the problemDeleting & reinstalling the app fixes the problem, but is obviously undesirable.

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

Problem is that launchscreen (splash screen) is stored in cache and not cleared when you upload without deinstalling first.There may be some trick, like renamin the image iused and removing the old one from xcassetshttps://stackoverflow.com/questions/33002829/ios-keeping-old-launch-screen-and-app-icon-after-updateAnother way is to propose users to offload (not remove) the app. So they will not loose their user data.h ttps://www.howtogeek.com/344944/how-to-delete-or-offload-an-app-on-iphone-or-ipad/

The next steps seem to me fine for keeping user data and clearing launch screen cache.1. Launch Settings and select General -> iPad/iPhone Storage -> your application -> Offload App2. After cloud icon shown, select Reinstall App

Thanks again @meaton for all the helpful replies!As I said I would do, I tried to reproduce it a lot of times, including uploading big files (3GB, 5GB) and it didn't reproduce on my Mac.However, at the customer, it reproduced easily, even with small files - she tries to upload 3 files of ~10mb each, and it happens.I checked again her Console logs, and no sign for utun_output or ctl_enqueuembuf, but those line seems related:default 17:27:22.110479 -0400 symptomsd NWPath: kNetworkPrimary NWPathStatusSatisfied interface en1 index 6 default 17:27:22.110535 -0400 symptomsd primary interface change to en1, type 1 default 17:27:22.110692 -0400 symptomsd Primary change default 17:27:22.110754 -0400 symptomsd noi: NOI: v:0 type:Wifi, isAny:yes, isBuiltin:no, loi:-1, flags:0, event: kNotificationNewPrimaryInterface, oldLoadedLqm: 100, rawLoadedLqm: 100, newLoadedLqm: 100, not posting default 17:27:22.118243 -0400 apsd Looking up connection on peer: d573aec0 found default 17:27:22.118320 -0400 apsd Looking up connection

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

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

>Do offloaded apps count as app deletionsAppears so, yes. I see no evidence there is a time factor, tho.From ASC Help / Metrics:Deletions: The number of times your app was deleted on devices running iOS 12.3 or tvOS 9 or later by users who agree to share their data with you. This data includes deletions of the app from the Home Screen and deletions of the app through Manage Storage. Data from resetting or erasing a device's content and settings is not included.

He's correct, like many have said, I went and Offloaded and removed some apps and it completed.I remembered that I had a update in iOS 11 days that did this,From my history of computers since the 90's, I think it had enough to downloa, even though I deleted and tried again - It didn't have quite enough spacevto fully extract and put all of the stuff where it needed to.This timem the screen went black for a few and it rebooted.Success!