I'm trying to commit ~9k files but I'm getting this error. I'm on Xcode 12.5.1.
There are some pods that I updated so lots of files were added and removed. Not sure if that is related to this issue.
This did not work
Post
Replies
Boosts
Views
Activity
I have this issue with concurrency where it is crashing on a real device but not in the simulator. Are there any general steps I could take to troubleshoot these kinds of issues? Where something works on the simulator but not on the device?
My specific issue was Tasks not working on the real device.
I've been running a test for 7 days now and the analytics keep saying that the conversion rate of the variant is identical to the baseline. I am just finding it very hard to believe that two variants can have an identical conversion rate every single day. I would expect there to be at least some variance.
Is this normal behavior? Has anyone else experienced this? Perhaps I need to wait longer?
I get this error when I try to apply any treatment in Product Page Optimization. I already have screenshots for the primary language. Still haven't received any solutions from the support team.
Unable to Apply Treatment
You must upload at least one screenshot for the primary language of your app before this treatment can be applied to the following:
7.14 Ready for Sale
@Parameter(title: "Date", default: Date.now)
var date: Date
I get this error on the parameter line: No exact matches in call to initializer. I've tried writing it in different ways but I can't get it to work.
It works fine if I don't have a default value, however that would prompt for the date every time.
Issue: unresolvable because: Could not complete create template: empty template: Failed # variables.0.definitions.0.synomyms.0
I have no idea what this means.
Issue: unresolved variable(s) found: +applicationName
I don't know how to fix this warning. Also need help figuring out what the other warning is. All showed up after upgrading to Xcode 16.
When a workout session is being recovered, if it is paused, the elapsed time will be incorrect. It will seem like that workout never was paused.
The recovery works fine if the workout was never paused.
Steps to reproduce:
Implement recoverActiveWorkoutSession
Start workout
Pause session and print the elapsed time
Stop simulator / cause crash
When recoverActiveWorkoutSession is called the elapsed time will not equal the elapsed time when the session was paused.
Here is my implementation. I haven't seen any examples online.
guard let recovered = try? await healthStore.recoverActiveWorkoutSession() else {return}
self.session = recovered
self.builder = recovered.associatedWorkoutBuilder()
self.session?.delegate = self
self.builder?.delegate = self
self.builder?.dataSource = HKLiveWorkoutDataSource(healthStore: healthStore, workoutConfiguration: recovered.workoutConfiguration)
self.sessionState = recovered.state