Posts

Post marked as solved
5 Replies
Figured out my problem. For anyone who is using manual signing, when you create your Provisioning Profile you need to select "Mac Catalyst" for the Profile Type instead of "Mac". I guess that's pretty obvious but be aware that when you view the profile in the portal, the App Groups capability still won't show up on the Enabled Capabilities section.
Post marked as solved
5 Replies
I'm having the same issue but because of CarPlay support, I had to turn off "automatically manage signing" in Xcode. When I go to the developer portal, look at my identifier, and click on the information button for App Groups it says the Platform Support is "tvOS, iOS, watchOS". I'm using the same identifier for macOS and iOS. Anyone know how to manually add the App Group capability to the macOS provisioning profile?
Post not yet marked as solved
7 Replies
I'm experiencing the same issue but for the entitlement "com.apple.developer.networking.wifi-info"Luckily I don't need it on mac so I was able to remove it from the Mac Catalyst build using your script. Thanks.
Post marked as solved
29 Replies
Did you ever resolve the issue:error: unable to find any specific architecture information in the binary at 'foo/bar/x86_64/libavcodec.a'I'm running into the same error trying to build an xcframework for FFmpeg.EDIT:Nevermind, I see that you figured out the cause: https://github.com/kewlbear/FFmpeg-iOS-build-script/pull/147#issue-325840617 "x86_64 binaries are built without ASM support, since ASM for x86_64 is actually x86 and that confuses xcodebuild -create-xcframework"For anyone else running into this issue with FFmpeg, you need to add "--disable-asm" to the configure flags.