Hello,
I recently updated 2 different apps that both use SciChart with XCode14 and uploaded the archives to the App Store via Organizer. They both generated the warning/error:
“The app references non-public selectors in …/Frameworks/SciChart.framework/SciChart: moveToX:y:”
This did not occur with Xcode 13.
Any advice on how best to handle this?
Thank you.
- C Bolton asked 3 years ago
- last edited 3 years ago
- Thanks for reporting this, we’re looking into it
- I can’t find any update on this issue which is now 7 months old.
- You must login to post comments
Hi all
According to developer.apple.com/forums/thread/714736 this seems to be a bug in the validation on Apple side and is affecting a number of third party libraries.
It’s a bug in the validation that runs on the backend. It’s a warning, not an error, so binary distribution is possible. I’ve already filed a bug on the Feedback Assistant (FB11488329) for this issue. developer.apple.com/forums/thread/713574 — mario25 2 months ago
One user has reported
This problem occurs even with CoreData generated source code. For example the following extension (generated from Xcode) causes similar warnings:
extension FolderItem { @objc(addItemsObject:) @NSManaged public func addToItems(_ value: FavoriteItem) @objc(removeItemsObject:) @NSManaged public func removeFromItems(_ value: FavoriteItem) @objc(addItems:) @NSManaged public func addToItems(_ values: NSSet) @objc(removeItems:) @NSManaged public func removeFromItems(_ values: NSSet) }
The warnings are related to the following lines: @objc(addItemsObject:) @objc(removeItemsObject:) @objc(removeItems:)
This is all generated code from Xcode.
Multiple users are reporting this error with other third party libraries (not scichart) and say the warning can be ignored and app continue to be published.
If you continue to have problems I suggest to comment on the forum threads above on developer.apple.com. If there is specific guidance from Apple on how to adjust our library we would be happy to do it.
Best regards,
Andrew
- Andrew Burnett-Thompson answered 2 years ago
- You must login to post comments
Thanks for the response. Cleaning derived data didn’t resolve the problem. I’ll look into more in a couple of days, and report back whatever I find.
Quick Update: I tried adding the sciChart framework to one of my projects that does not use it (no Scichart API calls). With Xcode 14 (Version 14.0 (14A309)) I got the same error. With Xcode 13, it processed fine. When I removed the framework, it uploaded fine again with xCode14.
All I did to reproduce the error was add the framework (see image attached)
- C Bolton answered 2 years ago
- last edited 2 years ago
- Thanks again, if you can make available to us anything that can reproduce the problem we’d be glad to help. Best regards, Andrew
- You must login to post comments
Enre, thanks for posting that – I’m glad I’m not alone. I am still getting the error. Fortunately, updates and releases seem to still be going through the App Store as usual even with the error.
- C Bolton answered 2 years ago
- Hi there – did you see my comment about the reports on Apple developer forum? Seems to be a bug in their side (or at least, a change where they haven’t yet provided clarification) https://developer.apple.com/forums/thread/714736
- Thank you Andrew, I did see your comment. When I reported this issue SciChart was unable to reproduce it, and had no other reports of it. I now feel a bit of relief knowing I’m not a completely isolated case. This is a weird issue, but Scichart developer support was great as always.
- You must login to post comments
Apple appears to have resolved this issue. My AppStore Connect uploads as of today are no longer generating this warning/error. I did not change XCode or SCiChart versions or anything else.
- C Bolton answered 2 years ago
- You must login to post comments
I’m getting same error too after updating Xcode 14.
- Emre Gökberk answered 2 years ago
- last edited 2 years ago
- You must login to post comments
Please login first to submit.