3 posts were split to a new topic: Error Loading Local Files since 5.1.3 on macOS
iPadOS Version 17.4.1
iPad Pro (11-inch) (3rd generation)
Using djay 5.1.5
Controller BEATPAD2
Have a library of MP3s sync’d locally to my iPad through Apple Music. Stating today I’m getting the following error ‘The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -1002.)’. Have looked through every proposed solution so far but they’re either inapplicable to my hardware (Windows or Mac) with the only iPad thread not having a solve. Want to remain calm and not do anything severe yet, can anyone propose a fix?
Ironically looks like it’s Version 5.1.6 that did this, a version whose only patch note is “Fixed error loading certain files from Local Music source”.
Big gig in a week, will be monitoring this thread closely. Any/all help is welcome.
Ha! Unbelievable I just got a software update that fixed it. Are you guys really that quick??
Edit: I think what happened was even though the DJAY app was showing me version 5.1.6 it hadn’t actually INSTALLED it. Did that through the app store and we seem to be in business.
@Holiday_Kirk please use search before creating new topics. I’ve merged yours with this one. Yes, we discovered and fixed the bug last night.
Anyone one else have this message comes up ( operation could not be completed (kcferror domain-cfnetwork error-1002.) using ipad pro, local library, and it’s only on Dj pro, the latest update on the latest app, no problem on the old djay pro apps and djay 2 and no problem playing music on itunes local, no problem on tidal. and it’s 80% of the music in my local library,
on a side note, do i need to connect my ipad to my controller for ableton link to work?
Hi @Mahesh_Laikhram1, please use search before creating new topics. This bug has been addressed in iOS with djay 5.1.6. Thanks.
i’ve only just updated my, my last update was weeks ago, everything was working one 1 week ago, after my update a few hours ago then i started having this issue
all fixed now, restarted my ipad and found another update was ready, all sorted