Have you tried deleting Xcode, rebooting, then reinstalling Xcode?
What about trying another version of Xcode?
benst
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Melbourne/Australia
Post
Replies
Boosts
Views
Activity
Can you just remove the package from the Package Dependencies tab, then add it as a local package?
I have also submitted feedback for this: FB13816065.
To fix the timezone issue in Slack, you can run Slack from the command line (every time you want to use it), as follows:
codesign -dr - /Applications/Slack.app && TZ=Australia/Sydney open -b com.tinyspeck.slackmacgap
Replace Australia/Sydney with your timezone though. 😀
Same here, in Xcode 15 beta 1.
We too have just hit this limit, and have only run 7 builds today.
I am experiencing the same problem 2 years after this was originally raised by the OP.
I've tried both my iPhone 14 Pro and iPad Air 4, running iOS/iPadOS 16.2, connected to MacBook Pro M1 Pro running Ventura 13.2.1 and Xcode Version 14.2.
I can build and run on those devices successfully, but Xcode Preview on device does not work.
That didn't happen to me. I can see my GitHub repo as the primary repository. What happens if you delete and recreate the workflow?
Is the "production build" also from the dev branch?
It would be a huge timesaver if this could be automated.
I need to know
I think this will be possible with the Environment section of the Xcode Cloud Workflow. There's a checkbox for "Secret" next to each environment variable that you define.
@jeancachu, that has not been my experience. I have a TestFlight build that has been expired, yet it can still be run.
Use the UITextFieldDelegate and implement textFieldShouldReturn. It is called when the user presses the return key on the keyboard.
The problem went away when I switched to using the Metal renderer for Google Maps:
GMSServices.setMetalRendererEnabled(true)