ITMS-90863: Macs with Apple silicon support issue (iCloud library)

For what its worth, I don't have that library at that location on my personal or work apple silicon mac.

For what its worth, I don't have that library at that location on my personal or work apple silicon mac.

Right. That’s because the library has been rolled into the dynamic linker shared cache. See this post for an explanation.

You confirm this using the dyld_info tool, which is aware of the shared cache. On my system the file isn’t present:

% ls -l /usr/lib/swift/libswiftCloudKit.dylib
ls: /usr/lib/swift/libswiftCloudKit.dylib: No such file or directory

but dyld_info is able to ‘see’ in in the shared cache:

% dyld_info -platform /usr/lib/swift/libswiftCloudKit.dylib
/usr/lib/swift/libswiftCloudKit.dylib [arm64e]:
    -platform:
        platform     minOS      sdk
           macOS     14.4      14.4   
     MacCatalyst     17.4      17.4  

As to why App Store Connect is complaining about it, I’ve no insight into that )-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I ran into this, too. All betas that I posted by GitHub/XClode Cloud to TestFlight were marked as incompatible with Macs.

Now, I fooled a little around and suddenly there was a version that was accepted as compatible, however, the issue was still reported by email (see above).

What I did:

• Cleared the build folder
• Called

dyld_info -platform /usr/lib/swift/libswiftCloudKit.dylib

• Added libswiftCloudKit.tdb to the framework list
• Removed the LSMinimumVersion key from the Info.plist

I have no idea why this finally ended up in a working build, but it did. I assume that calling the dyld_info is the key.

I've been having this issue for the past few days, despite making no code changes to my app (I even went back and re-built my codebase at a point that was previously OK, and got the issue still. Cannot figure out what's going on!

Recently, I’ve started receiving the following error when submitting a new app version:

ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS:

/usr/lib/swift/libswiftCloudKit.dylib

This has led to my app (previously available on the Mac App Store as “Designed for iPad”) no longer being downloadable on macOS.

Recent Changes:

• No updates were made in the code related to CloudKit or other libraries.
• Upgraded to macOS 15.0, then 15.1, and Xcode 16.0, then 16.1.

Problem:

I’ve tried clearing the build folder, adding libswiftCloudKit.tbd, and adjusting the LSMinimumSystemVersion value, but the issue persists.

The message lacks specific guidance on the issue or resolution. I’ve reviewed project settings but found nothing relevant. Any help or similar experiences would be appreciated!

Thanks!

Another thread relating to the same issue. https://forums.developer.apple.com/forums/thread/766061

Upgraded to macOS 15.1, and Xcode 16.1 and start seeing this issue.

Currently it blocks availability of my app on Mac via TestFlight (and probably would block it on AppStore after release). However, when I ran app on Mac it runs just fine (see attached image), it connects to iCloud and does what it needs to do.

I did try all above suggestions with setting LSMinimumVersion different versions, clearing cache, rebooting Mac, reinstalling SDK -- so far NOTHING works for me.

Is there any update on the issue? We still have this error. Our users complaint about unable to download our app on Mac

ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib

I recently experienced some issues with App Store Connect, but after it started working again, I uploaded a new version of the app. Interestingly, without any special actions on my end, the newly uploaded version is now marked as macOS-compatible. Since it’s still under review, I’m not entirely sure if the issue is fully resolved yet, but I haven’t received any related issue emails so far. I’m hopeful that once the review is complete, the app will appear again on the macOS App Store.

It seems that this might have been an issue on the App Store Connect side.