Post

Replies

Boosts

Views

Activity

Reply to App Store Connect Operation Error
I'm getting: "App Store Connect Operation Error The app references non-public selectors in Payload: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, navigationDelegate, navigationType, setNavigationDelegate:, setProcessPool:, targetFrame, userContentController" I have code where I'm updating WKWebViewConfiguration.applicationNameForUserAgent="...". I replaced that with this (to update the user agent): WKWebView.customUserAgent="..." and resubmitted my app as another build and it was accepted without error. I also use "initWithFrame:configuration:" and "setNavigationDelegate:" with WKWebView but I didn't change any of that code but my second build was still accepted - so who knows.
Jun ’22
Reply to altool --upload-package bitcode-build-tool internal error (iOS app)
After updating to Xcode 14 I'm no longer getting this error message and the upload time is back down to ~120 seconds for me (when the error occurred upload time was ~400 seconds). One thing I did notice too in Xcode 14 is that it appears that "xcrun altool --upload-package" is in debug b/c it is printing out a lot of debug-like text. I'm going to mark this as answered b/c this is no longer an issue for me after upgrading to Xcode 14.
Sep ’22
Reply to Xcode SPM when switching between branches
Has anyone figured out how to resolve this? I already have Package.resolved being ignored by git but every time I switch branches resolving dependencies starts all over again. A few things do get updated when I switch branches (like bundle id, app name etc) but I don't think that should trigger SPM dependency resolution again b/c the packages are exactly the same. Thanks in advance.
Sep ’22
Reply to Xcode SPM when switching between branches
I posted here about this issue about six months ago.. Just the other day though I added "-clonedSourcePackagesDirPath SourcePackages" to my xcodebuild command and so far I haven't experienced the problem – I won't know for sure if this is true true fix or not for a while because the issue was intermittent for me, but so far so good. The idea is to cache the SPM dependencies in the project dir instead of the default behavior which places them in derived data. I read about it – after trying, again, to find a solution – here: https://www.uptech.team/blog/swift-package-manager. Anyway I hope this works, otherwise I have to seriously consider going back to CocoaPods.
Apr ’23