Search results for

“Xcode”

93,785 results found

Post

Replies

Boosts

Views

Activity

Reply to iOS 26 TabBar Remove Selected Capsule
Thanks for the post. Any chance you can provide a simple focused project we can download and run it to see what you are seeing? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. What happens when you disable Liquid Glass? Do you get the results that you want? When you create a standard UIView (or SwiftUI View) that contains your custom buttons and layout and add custom view to the UITabBarController's view and anchor it to the bottom of the screen. When a user taps a button in your custom view, manually update the selected tab is when you get that result? Are you testing on iOS 26.4? What Xcode version are you using? Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
2h
Interface Builder - Xcode 26.4 - Changing Between Attributes Inspector, File Inspector, Etc. Is Now A Pop Up Button?
In Interface Builder there use to be a segmented control to switch Inspectors. It's been this way forever. I could switch from: File Inspector Attributes Inspector Size Inspector Etc... Now in Xcode 26.4, it is this clunky pop up button? What? I thought Apple didn't like Interface Builder anymore so I'm surprised they are even touching it. This part of a SwiftUI rewrite or just bad vibes?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
13
3h
Reply to In-App Purchase dialog not appearing during App Review but works on physical device
Thank you for your response. I would like to clarify that all previously suggested steps have been completed: StoreKit Testing Disabled StoreKit configuration in Xcode is not used. The app connects directly to Apple’s sandbox environment for testing. Successful Sandbox Testing The In-App Purchase product (remove_ads, Non-Consumable) has been thoroughly tested in the sandbox environment. The StoreKit purchase sheet appears correctly, and the transaction completes successfully. A screen recording is available to demonstrate this behavior. Product Properly Submitted The In-App Purchase product is fully configured in App Store Connect and has been submitted for review together with the app version. Both the app binary and the IAP product are included in the same submission. Despite this, the app continues to be rejected again under Guideline 2.1(b) stating that Premium feature was still implemented without triggering any purchase flow.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
11h
Reply to App Crash with mxSignpost function not found
Just a quick update… I’m confidant that we now have a handle on this issue (FB22384135). I can’t offer any concrete details about timelines but, as always, I encourage you to test with the latest betas as we seed them. And in this case that means Xcode betas, because this is an Xcode issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
13h
Reply to Updating Apps on the AppStore no longer working for me.
What version of Swift Playground are you using? And is this on Mac or iPad? [quote='821471021, GMacD53, /thread/821471, /profile/GMacD53'] because Playground does not use Xcode as far as I am aware? [/quote] Yes and no. It’s an independent product but, when you submit to App Store Connect, it reuses a bunch of the same infrastructure. Thus it’s not a huge surprise that you’re seeing Xcode in this error message. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
15h
Xcode Cloud workflow shows "There are no branches available" for Tuist-based repository
Description: I'm trying to set up Xcode Cloud for a tvOS project that uses Tuist for project generation. The workflow is created successfully, but when I try to manually start a build, no branches are listed — it just shows There are no branches available. Setup: tvOS app project using Tuist 4.x for project generation Hosted on GitHub (private repository, organization) The .xcodeproj and .xcworkspace files were originally in .gitignore (standard practice for Tuist projects) ci_scripts/ci_post_clone.sh is configured to install Tuist and run tuist generate --no-open after cloning What I've tried: Removed *.xcodeproj and *.xcworkspace from .gitignore and committed the generated project.pbxproj to Git — branches still not visible Changed the Project or Workspace path in the workflow settings to match the actual location of project.pbxproj (Projects/App/.xcodeproj) — no change Temporarily changed the default branch to one that contains the committed .xcodeproj with project.pbxproj — still no bran
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
0
0
32
16h
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. I also created a brand-new Xcode 26.4 project and enabled the Enhanced Security capability there. Xcode generated these two entitlements as String values (1 and 2) by default in the new project as well. So at least in my current Xcode 26.4 / OS 26.4 environment, the string-based form appears to be both the Xcode default and the only form that launches normally in testing.
Topic: Code Signing SubTopic: Entitlements Tags:
18h
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. So at least in my current Xcode 26.4 / OS 26.4 environment, the Boolean form appears to break launch, while the string-based form works normally.
Topic: Code Signing SubTopic: Entitlements Tags:
18h
Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
Hi, I’m hoping someone can help clarify the correct entitlement format for the Enhanced Security capability in a macOS App Store build. Context Our app is a sandboxed macOS app built with Xcode 26.4. We enabled the Enhanced Security capability in Signing & Capabilities, and we configured the entitlements based on the current documentation. What’s confusing me The Xcode 26.4 release notes say apps that already adopted Enhanced Security should remove: com.apple.security.hardened-process.enhanced-security-version com.apple.security.hardened-process.platform-restrictions and replace them with: com.apple.security.hardened-process.enhanced-security-version-string with value 1 com.apple.security.hardened-process.platform-restrictions-string with value 2 Reference: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes The entitlement reference pages also seem consistent with that: https://developer.apple.com/documentation/bundleresources/entitle
Topic: Code Signing SubTopic: Entitlements Tags:
3
0
29
19h
Updating Apps on the AppStore no longer working for me.
I have been using Swift Playground to build and submit my apps to the appstore for around three years now. Recently I uploaded two of my apps but now when I submit them for approval an error is issued… “Unable to Add for Review”… (see pic attached). I don’t understand it because Playground does not use Xcode as far as I am aware? Can someone advise me what I can do to resolve this? Is it something I have to wait to be fixed by an Apple update?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1
0
62
21h
Reply to iOS 26 TabBar Remove Selected Capsule
Thanks for the post. Any chance you can provide a simple focused project we can download and run it to see what you are seeing? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. What happens when you disable Liquid Glass? Do you get the results that you want? When you create a standard UIView (or SwiftUI View) that contains your custom buttons and layout and add custom view to the UITabBarController's view and anchor it to the bottom of the screen. When a user taps a button in your custom view, manually update the selected tab is when you get that result? Are you testing on iOS 26.4? What Xcode version are you using? Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
2h
Interface Builder - Xcode 26.4 - Changing Between Attributes Inspector, File Inspector, Etc. Is Now A Pop Up Button?
In Interface Builder there use to be a segmented control to switch Inspectors. It's been this way forever. I could switch from: File Inspector Attributes Inspector Size Inspector Etc... Now in Xcode 26.4, it is this clunky pop up button? What? I thought Apple didn't like Interface Builder anymore so I'm surprised they are even touching it. This part of a SwiftUI rewrite or just bad vibes?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
13
Activity
3h
Reply to Xcode Cloud builds stuck on "Queued"
same all morning, the developer system status page was updated 20min ago. Xcode Cloud has an outage now.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
Boosts
Views
Activity
8h
Reply to Xcode 26.4 rc
@DTS Engineer I started using the Xcode 26.5 Beta and this problem has not resolved.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
9h
Reply to In-App Purchase dialog not appearing during App Review but works on physical device
Thank you for your response. I would like to clarify that all previously suggested steps have been completed: StoreKit Testing Disabled StoreKit configuration in Xcode is not used. The app connects directly to Apple’s sandbox environment for testing. Successful Sandbox Testing The In-App Purchase product (remove_ads, Non-Consumable) has been thoroughly tested in the sandbox environment. The StoreKit purchase sheet appears correctly, and the transaction completes successfully. A screen recording is available to demonstrate this behavior. Product Properly Submitted The In-App Purchase product is fully configured in App Store Connect and has been submitted for review together with the app version. Both the app binary and the IAP product are included in the same submission. Despite this, the app continues to be rejected again under Guideline 2.1(b) stating that Premium feature was still implemented without triggering any purchase flow.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
11h
Xcode Cloud builds stuck on "Queued"
Xcode Cloud seems to be queueing up builds but not processing them. Currently the earliest queued build on my end is about 3 hours ago. System status pages don't show any issues. I just want to check if this is something other people are seeing or just something going weird on our account.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
7
Boosts
0
Views
149
Activity
13h
Reply to App Crash with mxSignpost function not found
Just a quick update… I’m confidant that we now have a handle on this issue (FB22384135). I can’t offer any concrete details about timelines but, as always, I encourage you to test with the latest betas as we seed them. And in this case that means Xcode betas, because this is an Xcode issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
13h
Reply to Updating Apps on the AppStore no longer working for me.
What version of Swift Playground are you using? And is this on Mac or iPad? [quote='821471021, GMacD53, /thread/821471, /profile/GMacD53'] because Playground does not use Xcode as far as I am aware? [/quote] Yes and no. It’s an independent product but, when you submit to App Store Connect, it reuses a bunch of the same infrastructure. Thus it’s not a huge surprise that you’re seeing Xcode in this error message. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
15h
Reply to Can’t paste into Simulator after updating to Xcode 26.4
I can't recall the exact Xcode version but this issue has occurred in the past, but was isolated to older simulator runtimes. This time it looks like affecting both 26.4 and previous simulators. One has to wonder how the same feature gets repeatedly fixed and then broken again.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
16h
Xcode Cloud workflow shows "There are no branches available" for Tuist-based repository
Description: I'm trying to set up Xcode Cloud for a tvOS project that uses Tuist for project generation. The workflow is created successfully, but when I try to manually start a build, no branches are listed — it just shows There are no branches available. Setup: tvOS app project using Tuist 4.x for project generation Hosted on GitHub (private repository, organization) The .xcodeproj and .xcworkspace files were originally in .gitignore (standard practice for Tuist projects) ci_scripts/ci_post_clone.sh is configured to install Tuist and run tuist generate --no-open after cloning What I've tried: Removed *.xcodeproj and *.xcworkspace from .gitignore and committed the generated project.pbxproj to Git — branches still not visible Changed the Project or Workspace path in the workflow settings to match the actual location of project.pbxproj (Projects/App/.xcodeproj) — no change Temporarily changed the default branch to one that contains the committed .xcodeproj with project.pbxproj — still no bran
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
0
Boosts
0
Views
32
Activity
16h
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. I also created a brand-new Xcode 26.4 project and enabled the Enhanced Security capability there. Xcode generated these two entitlements as String values (1 and 2) by default in the new project as well. So at least in my current Xcode 26.4 / OS 26.4 environment, the string-based form appears to be both the Xcode default and the only form that launches normally in testing.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
18h
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. So at least in my current Xcode 26.4 / OS 26.4 environment, the Boolean form appears to break launch, while the string-based form works normally.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
18h
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
For reference, I’m attaching screenshots of: the App Review message that says these entitlements must be boolean and true, and the Xcode 26.4 release note section that says to use the new -string variants with values 1 and 2. These are the two pieces of guidance I’m trying to reconcile.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
19h
Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
Hi, I’m hoping someone can help clarify the correct entitlement format for the Enhanced Security capability in a macOS App Store build. Context Our app is a sandboxed macOS app built with Xcode 26.4. We enabled the Enhanced Security capability in Signing & Capabilities, and we configured the entitlements based on the current documentation. What’s confusing me The Xcode 26.4 release notes say apps that already adopted Enhanced Security should remove: com.apple.security.hardened-process.enhanced-security-version com.apple.security.hardened-process.platform-restrictions and replace them with: com.apple.security.hardened-process.enhanced-security-version-string with value 1 com.apple.security.hardened-process.platform-restrictions-string with value 2 Reference: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes The entitlement reference pages also seem consistent with that: https://developer.apple.com/documentation/bundleresources/entitle
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
3
Boosts
0
Views
29
Activity
19h
Updating Apps on the AppStore no longer working for me.
I have been using Swift Playground to build and submit my apps to the appstore for around three years now. Recently I uploaded two of my apps but now when I submit them for approval an error is issued… “Unable to Add for Review”… (see pic attached). I don’t understand it because Playground does not use Xcode as far as I am aware? Can someone advise me what I can do to resolve this? Is it something I have to wait to be fixed by an Apple update?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
1
Boosts
0
Views
62
Activity
21h