I am getting an error on Xcode Build
The bundle version must be higher than the previously uploaded version.
I am at a loss. My bundle version is set at 20. The latest version uploaded has bundle version 18. The project is clearly higher than the most recently uploaded version.
What am I doing wrong?
I tried setting the Bundle version in both the General tab for the target, in the Build Settings and in the Info.plist. Which takes precedence?
Fastlane reports the current build version as 18 on TestFlight.
Confusingly, throughout Xcode, Bundle Version is variously referred to as both 'Bundle Version' and 'Current Project Version', and is 'Build' on App Store Connect.
App Store Version is variously referred to as 'Version', 'Bundle version string (Short)', and 'Marketing Version'.
Dive into the vast array of tools, services, and support available to developers.
Post
Replies
Boosts
Views
Activity
The documentation states that Xcode Cloud comes with support for git lfs (https://developer.apple.com/documentation/xcode/source-code-management-setup) but when I run my unit tests in Xcode Cloud, which have many images which are stored in git lfs, the tests all fail because they don't have the images.
How do I get Xcode Cloud to fetch git lfs images?
Thanks
Hi,
Overview
I am using Xcode Cloud for my multi platform app.
The macOS test case fails, however the iOS test case runs and succeeds.
I don't have any UI test cases written, the test case are simple and have nothing platform (macOS) specific.
Questions
What can I do to fix this?
Is there any user privileges needed to launch the macOS app for testing? I ask because when I ran the UI tests locally it launched the app and asked for my macOS user password. Just wondering if that is the reason it didn't launch in Xcode Cloud.
Error:
<Appname> encountered an error (Failed to install or launch the test runner. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult.(Underlying Error: Could not launch "AppnameTests. The LaunchServices launcher has returned an error. Please check the system logs for
the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed) )))
× Could not launch "<Appname>"
× Could not launch "AppnameTests"
× AppnameUITests.testExample()
Failed to get launch progress for <XCUIApplicationImpl: 0x600000564630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.app>: Could not launch "app name". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:28
* AppnameUITests.testLaunchPerformance)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:37 g
* AppnameUITestsLaunchTests.testLaunch)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/Testroducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed.
My app has a debugging mode in which it invokes 'leaks' on itself. I am now seeing this message on stderr:
Target process is an ancestor and permitting live process for ancestors so not generating a corpse to save resources by default.
This sort of makes sense, but I would like a more detailed explanation. Is there some option I should be sending to 'leaks' to operate in a better mode? Should I be invoking it differently?
I get this error from time to time in UI tests when they are run on CI. Any ideas what might be causing this error?
DemoCode:
import SwiftUI
import UIKit
import PencilKit
class PencilKitViewController: UIViewController, PKCanvasViewDelegate, PKToolPickerObserver {
lazy var canvasView: PKCanvasView = {
let canvasView = PKCanvasView()
canvasView.drawingPolicy = .anyInput
canvasView.translatesAutoresizingMaskIntoConstraints = false
return canvasView
}()
lazy var toolPicker: PKToolPicker = {
let toolPicker = PKToolPicker()
toolPicker.showsDrawingPolicyControls = true
toolPicker.addObserver(self)
return toolPicker
}()
let drawing = PKDrawing()
override func viewDidLoad() {
super.viewDidLoad()
canvasView.drawing = drawing
canvasView.delegate = self
view.addSubview(canvasView)
}
override func viewDidLayoutSubviews() {
super.viewDidLayoutSubviews()
canvasView.frame = view.bounds
}
override func viewDidAppear(_ animated: Bool) {
super.viewDidAppear(animated)
toolPicker.setVisible(true, forFirstResponder: canvasView)
toolPicker.addObserver(canvasView)
canvasView.becomeFirstResponder()
}
// canvas
func canvasViewDrawingDidChange(_ canvasView: PKCanvasView) {
print("drawing")
}
func canvasViewDidFinishRendering(_ canvasView: PKCanvasView) {
}
func canvasViewDidEndUsingTool(_ canvasView: PKCanvasView) {
}
func canvasViewDidBeginUsingTool(_ canvasView: PKCanvasView) {
}
}
// UIRepresentable for SwiftUI
struct PencilKitView: UIViewControllerRepresentable {
class Coordinator {
var parentObserver: NSKeyValueObservation?
}
var onSubmit: ((UIImage?, Error?) -> Void)? = .none
func makeUIViewController(context: Context) -> PencilKitViewController {
let pencilKitViewController = PencilKitViewController()
context.coordinator.parentObserver = pencilKitViewController.observe(\.parent, changeHandler: { vc, _ in
})
return pencilKitViewController
}
func updateUIViewController(_ uiViewController: PencilKitViewController, context: Context) {
}
func makeCoordinator() -> Self.Coordinator { Coordinator() }
}
struct ContentView: View {
var onSubmit: ((UIImage?, Error?) -> Void)? = .none
var body: some View {
PencilKitView()
}
}
struct ContentView_Previews: PreviewProvider {
static var previews: some View {
ContentView()
}
}
iOS:
macCatalyst:
Hi all,
I got the email saying my certificate(s) will be expiring in 30 days.
I can view my certificates (distribution, distribution managed, and 2x developments) on my account page.
The distribution expires in 30 days (4/20/2023)
The distribution managed expires in 6 months
Development #1 (under my name) expires in 30 days (4/20/2023)
Development #2 (also under my name) expires in 2 months (5/26/2023)
However, I don't see any way to renew them.
I have read other posts that talk about 'edit' or 'generate' buttons, but I don't see that and I presume those posts are just out of date.
When I look in my xcode project, I see that I am using 'automatically manage singing'.
Xcode also shows that a provisioning profile is expiring in 2 months. I presume that is something different? It has the same expiration date as my development #2 certificate (5/26/2023).
It's also unclear what is going to happen when these certificates expire.
I read that devices running builds with the expired distribution cert will stop working.
Is that just for internal builds downloaded from something like Test Flight?
Will live builds, downloaded by actual players from the AppStore, stop working if I don't push a release with a new cert in the next month?
I am the one that set this all up and 'maintains' it, but I don't engage with it often enough to remember the bits and bobs.
My apologies for all the newbie questions.
Thank you for your assistance
I'm trying to debug my metal shaders in Xcode 14.2. However clicking "Capture metal GPU" while debugging recently started showing the following error:
Capturing MTLPipelineLibrary is not supported.
Unsupported method: -[MTLDevice newPipelineLibraryWithFilePath:error:]
To enable capturing, disable calls to unsupported APIs and relaunch your application.
I can't find any info about MTLPipelineLibrary or how to disable it. I've also confirmed that Metal GPU Frame Capture is enabled in my build
What's causing this issue and how can I work around it so I can debug my shaders again?
Specifically,
In (https://developer.apple.com/account/resources/identifiers/):
I can't find the Weatherkit option under Capabilities or App Services in the configuration of the identifier.
In Xcode:
Add WeatherKit capability fail. output log:
The capability associated with "WEATHERKIT" could not be determined. Please file a bug report at https://feedbackassistant.apple.com and include the Update Signing report from the Report navigator.
Is it related to my region and account?
My account is Apple Developer Enterprise Program , the region is Mainland China.
I'm testing a video stream (HLS) with AVPlayer. On XCode 14.3 and simulators running iOS 16.4, there is no video image, only black screen. The audio is playing normally, also progress/duration of the video is showing as expected. The problem does not occur on same XCode version with earlier versions of the simulator. Is this a simulator bug? I've also tested it on real device with iOS 16.4 - no problem there.
I have os_log statements in my app. With my phone connected to the Mac, when I run the app through XCode, open Console app, those logs are shown. However, when I'm launching the app on its own, those logs don't appear in Console (phone still connected).
Am I missing something very basic? Please help.
Have downloaded playgrounds 4.3 to my iPad Air running ipados 16.5.
Trying to use playground “Get started with Apps” but receiving message “Unsupported file format Get Started with Apps.swiftpm cannot be opened in Swift Playgrounds”.
I do not have Mac or windows PC so am stuck! Help ??
Xcode cloud builds were failing with the following error. It wasn't the problem before yesterday morning 26.Apr.2023 before 1:00 PM.
Please let me know what the issue is or if there is anything I can do to solve this.
Additional information:
The app is a react-native app.
error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
fatal: expected flush after ref listing
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[in /Volumes/workspace/repository/ios]
[!] Invalid Podfile file: cannot load such file -- /Volumes/workspace/repository/node_modules/react-native/scripts/react_native_pods.
from /Volumes/workspace/repository/ios/Podfile:1
-------------------------------------------
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
-------------------------------------------
Error
Command exited with non-zero exit-code: 1
hello. i have 3 time started a new project now
I am making a app and i get a Error code on Info.plist file.
I have been trying to resolve an issue with the Info.plist file in an Xcode project. The error message is "Multiple commands produce" related to the Info.plist file. I have tried several approaches to fix the issue, including:
Checking the "Copy Bundle Resources" section in the "Build Phases" tab of the project settings to ensure there is only one Info.plist file listed.
Deleting the Info.plist file from the project and creating a new one, then updating the reference to the Info.plist file in the "Build Settings" tab.
Can anyone help me with this??
Hi community:
I'm coming across two error types on Xcode cloud during ui tests.
encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal kill before starting test execution. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundlexcresult))
encountered an error (Failed to prepare device 'Clone 7 of iPhone 14 Pro' for impending launch. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/ resultbundle.xcresult. (Underlying Error: Unable to boot the Simulator. launch failed to respond. (Underlying Error: Failed to start launch_ sim: could not bind to session, launchd_sim may have crashed or quit responding)))
Any ideas on how to solve them?
Thanks
Buenas a toda la comunidad, quería comentar mi caso para ver si me pueden ayudar.
Me registré y realicé lo requerido para dar de alta a la membresía en apple developer, hace mas de 96hs. todavía figura pendiente y nadie me responde.
Alguna sugerencia? ya he intentado realizarla con otro correo, etc.
Muchas gracias
Hi,
Since yesterday (May 11, 2023) I can no longer send an update on TestFlight for the Apple Developer account of a client on which I am admin. It gives me the following error:
The last time I sent a version to TestFlight was May 4, 2023 and I had no problem.
With other client applications I have no problem sending my updates to TestFlight.
I have no problem connecting to Apple Connect with my Apple ID, I can see that I am an admin on the Apple Developer account.
My config:
macOS 13.3.1 (a)
Xcode Version 14.3 (14E222b)
Regards
Tof
My tests fail with "Restarting after unexpected exit, crash, or test timeout". This is what I have so far established:
Does only happen when building with xcodebuild (14.3) but not when building with Xcode (14.3)
Tests that are failing are in a .testTarget within a local swift package and part of a test plan together with tests that are in subprojects
there are no crashlogs, so likely these tests are not crashing
with Xcode 14.2 there are no problems whatsoever (xcodebuild or Xcode)
Any ideas on how to debug this any further?
Best Roddi
The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log.
Hai gais.. i have question about xcode installation.. can i use m2/ssd storage to install n running xcode? For free up my internal space