Post not yet marked as solved
Prepared archive for validation
Validation failed
error: Asset validation failed
Missing Bundle Identifier. The application bundle contains a tool or framework [aaa.bbb.ccc.ddd.pkg/Payload/my.app/Contents/Frameworks/Abc.framework] that is missing the bundle identifier in its Info.plist file. (ID: 8d117580-6d15-4b9e-8a0c-3bd069c66c77)
error: Asset validation failed
Bad Bundle Executable. You must include a valid CFBundleExecutable key in the nested bundle [aaa.bbb.ccc.ddd.pkg/Payload/shudou.app/Contents/Frameworks/Abc.framework] property list file. (ID: 62894f06-c782-4d67-85df-91912d1b6609)
Abc.framwork is a pre-built lib used in swift. I put following keys in Abc.xcframework's Info.plist, but no effect.
<key>CFBundleIdentifier</key>
<string>aaa.bbb.ccc.ddd.Libname</string>
<key>CFBundleExecutable</key>
<string>Libname</string>
Post not yet marked as solved
I am creating a project with Flutter, but in the Runner/Frameworks folder, all files such as Pods_Runner.framework etc. are red and the file is not located in the specified folder. The same situation exists in my old projects. I don't know where I'm doing wrong, it was normal until a few days ago, but now even if I create a new project, I get the same error.
Flutter Version: 3.13.9
Cocoapods Version: 1.15.2
XCode: 15.1
Post not yet marked as solved
Why not give devs pvt file bundle, with only image and video, it's not live photo!!! I can't use the quick look framework to preview it, and I also can't share to another app as live photo example: save it back to photos or share it by iMessage 🙄 . I can't understand this design, why not any detail? Another thing is so bad, the music data type has no store ID for musickit play item, so the Apple Journal app can play the music, but other apps can't do it! The live photo is the same. What are you doing Apple?
Post not yet marked as solved
We use CocoaPods to manage third-party SDKs, so how should we sign and use these third-party SDKs
Post not yet marked as solved
With Xcode 15.3, iOS SDK 17.4, in a iOS App, I have this error :
TestClass.swift:11:27: error: cannot find 'CLBeaconIdentityCondition' in scope
let beaconCondition = CLBeaconIdentityCondition(uuid: UUID(uuidString: "12345678-1234-1234-1234-123456789012"), major: 1, minor: 2)
I can reproduce with this swift code :
import CoreLocation
class TestClass: NSObject{
let beaconCondition = CLBeaconIdentityCondition(uuid: UUID(uuidString: "12345678-1234-1234-1234-123456789012"), major: 1, minor: 2)
}
And this compilation command :
xcrun swiftc -target arm64-apple-ios17.4 -sdk $(xcrun --sdk iphoneos --show-sdk-path) -emit-executable TestClass.swift -o TestClassExecutable -F /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks -framework CoreLocation
Post not yet marked as solved
0
In other frameworks, I've seen codeSignature included in dynamic cases. because dynamic frameworks have "embed and sign" option. but this time Apple said, "Signatures are so required in these cases where the listed SDKs are used as binary dependencies." Does that mean that even if the ".framework" file of the SDK you are deploying is static, you have to include codeSignature?
and if a framework is not included in Privacy-Impacting SDKs list, is it okay not to sign?
Post not yet marked as solved
The current structure of my SDK xcframework is XXXX-Release.xcframework. Inside that, I have an XXXX.xcframework and a LICENSE.md file. Currently, this structure works fine in Swift Package Manager, dropping the XXXX-Release.xcframework file into Xcode and CocoaPods.
When I sign my xcframework as per Apple's requirements, I need to sign XXXX.xcframework, which is on the second level. Signing this works fine.
Will this meet Apple's requirements for signing an xcframework? I just want to make sure the current structure of my SDK does not need to change.
Thanks
Post not yet marked as solved
this post is related to the https://developer.apple.com/videos/play/wwdc2023/10061/
Hi, we are wondering if the framework should be signed.
the video indicates that all xcframework must be signed, on the other hand framework is not mentioned even website.
does anyone have ideas?
Post marked as Apple Recommended
I have apps using CMAltimeter to get sensor data, but recently they stop working with iOS 17.4, it is not release but some user running beta version, the is no access to the sensor data anymore (altitude and barometer). Some user report they can fix it by manual the "Motion & Fitness" permission but it only appear on some device. Report has been sent to Apple but I post here to find the solution to fix it.
Post not yet marked as solved
libdispatch.dylib:_dispatch_client_callout +40
Post not yet marked as solved
Hi Team,
We have a static framework and we have included the PrivacyInfo.xcprivacy for each architecture inside the xcframework and when we try to generate the privacy report it throws error like xcprivacy not found.
Can you please tell us how to include the PrivacyInfo.xcprivacy file for static frameworks.
Post not yet marked as solved
Hi! I'm moving my UINavigationBar and UINavigationItem to the iOS 16 style and having trouble with disabling buttons.
Before:
I'm defining rightBarButtonItems with a few barButtonItems plus a (custom) menuButtonItem (which has a menu with some more actions).
After:
I'm defining trailingItemGroups and let the system create an overflow menu dynamically, depending on space. I'm also defining some additionalOverflowItems.
Here's the problem:
How can I access the button/barButtonItem that is showing the overflow menu and call isEnabled = false? My UI, so far, has disabled all buttons during edit mode. I don't want to hide them, but have them grayed out, including the overflow menu button.
class MyVC : UIViewController {
// ...
override func setEditing(_ editing: Bool, animated: Bool) {
super.setEditing(editing, animated: animated)
// ...
// This doesn't disable the overflow menu button
navigationItem
.trailingItemGroups
.forEach {
$0.barButtonItems
.forEach {
$0.isEnabled = !isEditing
}
}
}
}
Post not yet marked as solved
I have a project generated by Tuist and recently started to migrate to XCode 15.
I keep getting too many errors related to swiftmodule, swiftdoc, abi.json, swiftsourceinfo that, apparently, XCode is looking for in the DerivedData folder deep inside Objects-normal subdirectory but gets an error: No such file or directory
I also got a No type or protocol named 'nw_proxy_config_t' error too, related to Webkit that isn't even a dependency in that module.
I've tried to update cocoapods, tuist, ruby, add postInstall configs I found at StackOverflow, but nothing worked.
Could a gentle soul point me to the right direction here ?
Post not yet marked as solved
Hello,
We noticed one or more issues with a recent delivery for the following app:
xyz
Version 3.0.0
Build 18396
Please correct the following issues and upload a new binary to App Store Connect.
ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/xyz.framework/xyz: _dyld_shared_cache_file_path. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Post not yet marked as solved
I have created a visionOS framework from Xcode to bridge between Unity and visionOS which is used to call APIs from Unity to VisionOS.
visionOS framework we attached in Unity assets is not getting builded along with Unity visionOS build.
This method is working fine for iOS build. i.e, created a iOS framework from Xcode to bridge between Unity and iOS which is used to call APIs from Unity to iOS.
iOS framework we attached in Unity assets is getting builded along with Unity iOS build.
Whether the VisionOS framework will work in Unity same as that of iOS? Is there any additional settings to setup framework for visionOS?
Reference link for the setup method used: https://betterprogramming.pub/setting-up-ios-framework-for-unity-9ef4e577db89
Post not yet marked as solved
We're bringing in an updated framework in our app, and the update requires ticking "Copy only when installing" in the Embed Frameworks build phase.
When ticking that box, we get numerous other errors, suggesting frameworks xyz cannot be found.
I've tried to find some documentation on this checkbox but there doesn't appear to be much on it, other then builds magically failing/suceeding when its toggled on/off. Is anyone able to shed some light on what is happening under the hood when that checkbox is ticked?
Post marked as Apple Recommended
I'm currently experimenting with the latest Xcode beta 15.3 (15E5194e) and attempting to integrate FinanceKit](https://developer.apple.com/documentation/financekit) into my project. However, I've encountered a persistent issue where the app crashes upon attempting to read or request authorization, accompanied by the following error message:
FinanceKit/FinanceStore+FinancialDataAuthorization.swift:52: Fatal error: Process is not entitled
Upon investigation, I've found no evident entitlements for FinanceKit, despite exploring options like Apple Wallet. Furthermore, I thoroughly examined the info.plist for relevant privacy values but found nothing pertinent.
Here's the code snippet that triggers the fatal error, whether it's the request or read function:
I don't see anything in entitlements for FinanceKit (I tried Apple Wallet and that didn't make a difference). Additionally, I checked for relevant privacy values for the info.plist but again didn't see anything relevant.
Here is the code to reproduce the error (note calling either function will result in the same fatal error):
import FinanceKit
import UIKit
class ViewController: UIViewController {
override func viewDidLoad() {
super.viewDidLoad()
requestFinancePermission()
// readFinancePermission()
}
private func requestFinancePermission() {
Task {
do {
let status = try await FinanceStore.shared.requestAuthorization()
} catch {
print("Error: \(error)")
}
}
}
private func readFinancePermission() {
Task {
do {
let status = try await FinanceStore.shared.authorizationStatus()
} catch {
print("Error: \(error)")
}
}
}
}
I'm seeking clarification on whether FinanceKit is currently usable or if there are additional steps needed for proper integration. Any insights or suggestions would be greatly appreciated. Thank you!
Post not yet marked as solved
In other frameworks, I've seen codeSignature included in dynamic cases, but this time Apple said, "Signatures are so required in these cases where the listed SDKs are used as binary dependencies."
Does that mean that even if the .framework file of the SDK you are deploying is static, you have to include codeSignature?
Post not yet marked as solved
Hi there, I'm setting up a new "framework target" in my project (xcode 15.2). I dragged and drop another framework to reused (called: SDImage). But at the step of importing SDImage to my framework, my xcode 15.2 always show that
"SDImage/SDImage.h" file not found
I was trying to set target membership of SDImage, config header/framework search path already but nothing gonna help.
Please give me a solution. Thank you and have a nice day
Post not yet marked as solved
Hello, we have a universal app that runs on iOS and iPadOS today but we're having an issue where it crashes on launch on visionOS.
When I try to run our app, I see messages like these in the console logs:
AMFI: constraint violation /private/var/containers/Bundle/Application/***/***.app/Frameworks/***.framework/*** has entitlements but is not a main binary
I see these for what seems to be all of our internal frameworks, we use cocoapods for all of these.
The following output is from running: codesign -d --entitlements :- ***.framework
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict></dict></plist>
Why would this cause a crash on launch for visionOS, but not iOS or iPadOS?
Why does AMFI think there are entitlements for the framework when they are empty?
