Search results for

“show when run”

115,098 results found

Post

Replies

Boosts

Views

Activity

Reply to ParticleEmitterComponent Position Offset Issue After iOS 26.1 Update – Seeking Solutions & Workarounds

On iPhone 17 Pro with iOS 26.3.1, ParticleEmitterComponent impact VFX appear visually rooted near the device / the world pose from when tracking stabilized, not at the intended world-space hit, even though the host entity hierarchy is correct: we parent clones under ground_anchor with convert(position:from: nil) from world hits, and runtime logs show holderOriginWorld matches requestedWorldPos with worldPosErrM = 0, so this is not an app-side anchor math bug. particlesInheritTransform = true (Apple’s suggested workaround) does not fix the visible misplacement. This matches the ParticleEmitterComponent / transform regression discussed around iOS 26.1+ (e.g. forum thread / FB21346746). We’re looking for confirmation, workarounds, or a fix timeline from Apple Engineering.

Graphics & Games RealityKit

segmented picker style causes runtime warning

On OSX, using a segmented picker style causes the following warning to be emitted (when a different selection is made) : Publishing changes from within view updates is not allowed, this will cause undefined behavior. The warning is not emitted using the 'Preview Canvas' only when running the app. Changing the picker style to automatic also fixes it, but the segmented style is used extensively. Tested using XCode 26.4.1 on MacOS 26.3.1 --- view --- import SwiftUI internal import Combine enum Mode : String { case one, two, three } class MyObject : ObservableObject { @Published var mode : Mode = .one } struct ContentView: View { @StateObject var obj = MyObject() var body: some View { VStack { Picker(Mode,selection: $obj.mode) { Text(One).tag(Mode.one) Text(Two).tag(Mode.two) Text(Three).tag(Mode.three) } .pickerStyle(.segmented) } .padding() } } #Preview { ContentView() } --- app --- import SwiftUI @main struct SwiftUIBugApp: App { var body: some Scene { WindowGroup { ContentView() } } }

UI Frameworks SwiftUI Combine

Reply to segmented picker style causes runtime warning

I can't really run the beta, because I need to build for production. Did you verify that it occurs under the latest XCode production release?

UI Frameworks SwiftUI

App Store Connect invitation showing "Invalid" immediately after being sent

Hi everyone, I’m facing a persistent issue where App Store Connect invitations are marked as Invalid or Expired the moment the recipient clicks the link, even if it was sent just minutes prior. I have already tried the following troubleshooting steps without success: Removed and re-added the user multiple times. Sent invitations to different email addresses (different domains). Changed the assigned Roles (tried Developer and Support). Tried opening the invitation link in Incognito/Private mode and different browsers. Despite these attempts, the link remains invalid. Is there an ongoing server issue or a specific workaround for this? Thanks in advance for any help!

App Store Distribution & Marketing App Store Connect App Store Connect TestFlight

135

Reply to SMAppService.daemon and AirWatch installation

The installation script has to update an endpoint security extension, so it first copies a signed app with the extension embedded in it and then executes that app and suspends security checks until the main app is installed. Then it runs the main app as a command line tool. The first app that updates the security extension is then removed. The two steps are needed because the endpoint security extension prevents modifying the main app. When the main app acts in install mode, it configures a daemon and an agent. It configures a security agent plugin and updates authorization db to use it. The main app and security agent plugin communicate with the daemon using XPC. A managed policy is installed that gives the app and the endpoint security extension full disk access.

App & System Services Core OS

Reply to SMAppService.daemon and AirWatch installation

Yes. The app is run as a command line tool with an argument telling it to perform an install. That causes the calls with SMAppService.

App & System Services Core OS

Reply to Invitation problem

Experiencing the exact same problem - tried deleting user add user again. Also tried with other email address - same issue - link shows its expired as soon as opened - tried in incognito safari / chrome. Not sure what more to do

App Store Distribution & Marketing General

Apple developer PAID but NOT ACTIVE yet

Hi, I purchased the Apple Developer subscription yesterday and the payment has already been successfully processed. However, my account is still not showing as active. Given that the payment has been completed, I would expect the activation to be reflected by now. This delay is impacting my ability to proceed with development and deployment, so I need clarification on what is causing the issue. Please review my account status as soon as possible and let me know: • If there is any pending verification or required action on my end • The reason for the delay in activation • The expected timeframe for the subscription to become active I would appreciate a prompt resolution to this matter. Thank you.

Developer Tools & Services Apple Developer Program Developer Program

118

SKStoreReviewController requestReviewInScene: does not display review prompt in debug builds on iOS 26.5 beta (23F5043k)

[SKStoreReviewController requestReviewInScene:] no longer displays the review prompt in debug/development builds on iOS 26.5 beta (23F5043k and 23F5043g). According to Apple's documentation, the review prompt should always appear in debug builds to facilitate testing. This was working in previous iOS versions (iOS 26.4 and older). Steps to reproduce: Run app from Xcode in debug configuration on a device running iOS 26.5 beta (23F5043k or 23F5043g) Call [SKStoreReviewController requestReviewInScene:windowScene] with a valid, foreground-active UIWindowScene Observe that the method executes without error (scene is valid per NSLog) but no review prompt appears Expected: Review prompt should display in debug builds Actual: No prompt appears, despite the scene being valid and foreground-active This worked correctly on previous iOS versions (26.4) so looks like this bug was introduced in 26.5 Beta versions. I have already filed a bug report in Feedback Assistant with number: FB22445620

App & System Services StoreKit iOS Beta StoreKit

226

Reply to iOS 26 regression: `DeviceActivityEvent`: `eventDidReachThreshold` called immediately (instead of waiting till threshold is reached)

[quote='885208022, DTS Engineer, /thread/808470?answerId=885208022#885208022'] Provide a focused project showing what you trying to accomplish and that the API is doing currently. [/quote] Thanks @DTS Engineer Albert for your response. I believe it’s currently not required to add an additional sample project, as the Screen Time team has informed me that the issue is most likely resolved in iOS 26.5 beta. So far I wasn't able to reproduce the issue anymore. I was just confused by your comment above that mentioned updating all devices signed into a family account, since we also reproduced the issue on devices where the user’s own screen time was managed compared to an underage family member. The bug might apply to families managing their kids’ screen time as well, but we don’t have that use-case in our app. Anyway, I hope this all doesn't matter anyway since the bug is hopefully addressed!

Accessibility & Inclusion General

Reply to libtool: warning: 'Foo.o' has no symbols on Xcode 26.4

Thanks for confirming. And it turns out that this is easy to reproduce: Using Xcode 26.4, create a new project from the macOS > Library template, and choose to create a Cocoa static library. In the resulting .h file, remove the whole @interface block. And in the .m file, convert the @implementation block to a category. For example: @implementation NSUUID (Foo) - (void)test { } @end Choose Product > Build. This issues the following warning: libtool: warning: 'Foo.o' has no symbols This actually makes some degree of sense: Xcode has run libtool to convert the various object (.o) files in the target into a static library (.a). There’s only one object file. It only contains a category. Objective-C categories don’t publish any symbols. Consider this: % nm …/Foo.o 0000000000000000 t -[NSUUID(Foo) test] U _OBJC_CLASS_$_NSUUID 0000000000000028 s __OBJC_$_CATEGORY_INSTANCE_METHODS_NSUUID_$_Foo 0000000000000048 s __OBJC_$_CATEGORY_NSUUID_$_Foo 0000000000000014 s l_OBJC_CLASS_NAME_ 0000000000000088 s l_OB

Developer Tools & Services Xcode

Reply to Time to register a developer account

Same issue i'm experiencing. I paid on the 14th of April, i received the receipt immediately and can see the subsription active but on web it's still showing pending. I've logged 2 tickets but no response since last week Would really love to get this sorted out asap

Developer Tools & Services Apple Developer Program

Reply to AI framework usage without user session

[quote='885202022, boilerla220, /thread/820379?answerId=885202022#885202022, /profile/boilerla220'] I guess worth clarifying also is what is meant by user session. [/quote] Right. I generally try to follow the terminology from TN2083 Daemons and Agents. A system extension [1] is effectively a launchd daemon and thus runs in the global context. It can’t reliably access the window server. And any XPC service it calls upon will be similarly restricted. However, the GPU lifecycle isn’t tied directly to the window server lifecycle, so there is some wiggle room there, and that’s the point I’m still working to clarify internally. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Non-DEXT system extensions. DEXTs are weird (-:

Machine Learning & AI General

Reply to FIPS140-3 Compliance Intel

I’m not going to be able to answer questions about FIPS compliance, which is more of a legal issue than a technical issue. You might have more luck asking this over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Privacy & Security General

Integrating BugSplat Crash Reporter

Hello, For the past few days I have been working on integrating a Crash Reporter called BugSplat to our macOS desktop app and it got me thinking, how do crash reporters work on macOS ? After days of trial and error (and claude's help) I managed to integrate it but with a different behavior than windows. On Windows: When the app crashes, the BugSplat crash report window opens and allows you to write your details and message to be sent with the crash report (along with a log file) On macOS: It displays the normal macOS' App exit unexpectedly, to which I click dismiss. But then when I re-open the app the BugSplat crash report window appears. I asked claude if I can avoid the normal macOS dialog entirely, to which it replied: This is by design — BugSplat macOS is a next-launch crash reporter, not an in-process one. Here's why that's intentional and unavoidable: When a process crashes (SIGSEGV, SIGBUS, etc.), macOS's ReportCrash daemon independently monitors all processes and shows the quit unexpectedly d

App & System Services Core OS Exception Handling Debugging