Search results for

“DTiPhoneSimulatorErrorDomain Code 2”

162,374 results found

Post

Replies

Boosts

Views

Activity

Family Controls entitlement: no response for over 2 weeks
Hi, I submitted my Family Controls entitlement requests on April 21 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. Has anyone had a similar delay recently? Is the recommended next step to file a code-level support request with my Team ID, or should I continue waiting? Thanks.
6
0
407
2w
No Response from Appeal or Support
I'm hoping someone can help me get clarity on my app submission for LinkUp, an iMessage-native group scheduling app. Here's the timeline: • Initial rejection (~1 month ago): Rejected under 4.3(a) for duplicating functionality of other apps • I updated screenshots, app description, and submitted again • For the past 2 weeks the app has been stuck with no meaningful response from App Review • I have called Apple support, submitted messages through the Resolution Center, and filed an App Review Board appeal — but I have received no confirmation email for the appeal and it does not appear on my developer support request page What LinkUp actually does: it lets friend groups coordinate availability entirely inside iMessage. Users send a schedule card as a message bubble, and participants vote on availability directly in the conversation thread — no redirects, no external app required. The heatmap updates in the bubble as people respond. To my knowledge, nothing on the App Store does this.
1
0
123
2w
App invisible in BOTH App Store search AND Apple Search Ads — Apple Support refuses to disclose violation flag (38 days)
Posting to document a case that matches a pattern of unresolved reports on this forum (e.g. thread #815203 Brutal Time), with the addition of new evidence: my app is missing from both the App Store search index and the Apple Search Ads campaign-creation index. Setup App: ZenTerm (App ID 6760935103, Bundle ID com.zenterm.mobile) Developer: Individual (Japan) Released: 2026-03-31 (live for 45 days) Status: Ready for Sale, 1.3.2 live (released 2026-05-06) App name: pure ASCII, coined word, no other apps share the name Symptoms Channel Result App Store app, search zenterm (exact name) Zero results, 38 days running iTunes Search API (https://itunes.apple.com/search?term=zenterm&country=jp) Returns my app correctly Direct App Store URL Opens product page normally Apple Search Ads — search by app name Zero candidates Apple Search Ads — paste canonical App Store URL Zero candidates The absence from both the App Store search index and the Apple Search Ads selection index is the key new finding. Since these run on
2
0
120
2w
Defining custom file types
On iOS:When one receives a file of type .pages by email, Mail displays a large Pages icon and tapping on it opens Pages. (A long-press brings up the more complicated Actions screen).When one receives a file of type .vcf by email, Mail displays a large Contacts icon and tapping on it opens Contacts. (A long-press brings up the more complicated Actions screen).I have my own custom file type, .ripf, and I want to have the same behaviour because that is what my users will expect. Accordingly, in my app's Info.plist I have a CFBundleDocumentTypes dictionary providing a one-element LSItemContentTypes array referring to the name 'com.universalis.ripcard', and a UTExportedTypeDeclarations dictionary associating the UTTypeIdentifier 'com.universalis.ripcard' with a public.filename-extension 'ripf' and a public.mime-type 'text/vnd.universalis.ripcard'. All the other entries in those two dictionaries are present and correct as far as I can tell. Both CFBundleDocumentTypes[0].CFBundleTypeIconFiles and UTExported
13
0
6.8k
2w
App not appearing in App Store search for over 6 weeks — including branded searches for its own name
I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app Brutal Time - Typographic Clock does not appear in App Store search results at all — not even when searching for its exact name Brutal Time. This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates a
1
0
255
2w
Reply to App not appearing in App Store search for over 6 weeks — including branded searches for its own name
Adding another data point — same symptoms, same lack of resolution. Sharing here in case the pattern helps Apple eventually acknowledge this as a systemic issue. App: ZenTerm (App ID 6760935103, Bundle ID com.zenterm.mobile) Released: 2026-03-31 (45 days ago) Status: Ready for Sale (1.3.2 live) Developer: Individual Symptoms (matches Brutal Time exactly) App Store search for the exact name zenterm → zero results, 45+ days running iTunes Search API (https://itunes.apple.com/search?term=zenterm&country=jp) returns my app correctly Direct App Store URL https://apps.apple.com/jp/app/zenterm/id6760935103 works fine Apple Search Ads campaign creation flow cannot find my app either — neither by name search nor by pasting the canonical App Store URL v1.3.2 (released 2026-05-06, with all third-party trademarks proactively removed from keywords) has now been live for 9 days — no change in search visibility Apple Support response so far Date Action Result 2026-04-11 First written inquiry Templated reply: we don't gu
2w
Reply to Radiometric interpretation of Apple ProRAW and Bayer RAW access via AVFoundation
Thanks for the precise framing — answering each in turn. Q1 — Bayer RAW capture through AVFoundation: Yes, third-party apps can capture Bayer RAW through AVFoundation. Both Bayer RAW and Apple ProRAW formats appear in AVCapturePhotoOutput.availableRawPhotoPixelFormatTypes. The recommended way to discriminate them is through the static query methods: AVCapturePhotoOutput.isBayerRAWPixelFormat(_:) AVCapturePhotoOutput.isAppleProRAWPixelFormat(_:) Apple ProRAW is opt-in: confirm photoOutput.isAppleProRAWSupported, then set photoOutput.isAppleProRAWEnabled = true. With ProRAW disabled, availableRawPhotoPixelFormatTypes exposes only Bayer formats; enabling ProRAW adds the ProRAW format to the same array. Device and format restrictions: Apple ProRAW: iPhone 12 Pro / Pro Max and later Pro models (iOS 14.3+). Bayer RAW: broadly available on devices that support RAW capture. Some virtual / fusion capture devices (for example, multi-cam) may not expose Bayer RAW because there is no single sensor providing the Bayer mos
2w
PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled
Feedback: PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled Summary PHBackgroundResourceUploadExtension's init() and process() methods are never called by the system when iCloud Photos is enabled on the device, even though setUploadJobExtensionEnabled(true) succeeds and uploadJobExtensionEnabled returns true. Environment iOS 26.4 (both devices) Xcode 26.x Tested on iPhone 17 Pro (primary device, 10,000+ photos) and an older iPhone (development device, 200+ photos) Same build deployed to both devices Full photo library access (.authorized) on both devices Steps to Reproduce Create an app with a PHBackgroundResourceUploadExtension (ExtensionKit, extension point com.apple.photos.background-upload) Enable iCloud Photos on the device (Settings > Photos > iCloud Photos) In the host app, request .readWrite photo library authorization and receive .authorized Call PHPhotoLibrary.shared().setUploadJobExtensionEnabled(true) — succeeds without error Verify PHPhotoLibrary.shared().
1
0
357
2w
Reply to PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled
Thanks for the thorough investigation — using Console.app to pinpoint the gating decision at assetsd (Checked all submitted library bundles. Result: NO with iCloud Photos on, versus YES with it off) is exactly the diagnostic level engineering needs. Based on the public API documentation, the observed behavior doesn't match the framework's documented design. The Uploading asset resources in the background article and the documentation for setUploadJobExtensionEnabled(_:) enumerate two preconditions for the extension to run: full photo library authorization, and registration of the extension point com.apple.photos.background-upload. Neither mentions iCloud Photos. The stronger signal comes from the documented description of PHAssetResourceUploadJob.Type.upload: An upload job type (will download the resource from iCloud if required, then upload). That description is only meaningful if iCloud Photos can be enabled — the framework is explicitly designed to handle the case where photo assets are stored in
2w
Reply to Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
Quick update with results from a diagnostic build I ran on iOS/watchOS 26.5. To validate the distinction you described between the NSE-returned content path and the locally posted notification path, I shipped an internal TestFlight build where the NSE additionally posts a local UNNotificationRequest via UNUserNotificationCenter.add() in parallel with the standard contentHandler() call. The local notification uses the same title and body as the NSE-returned notification, except for a [L] prefix in the body and a local-z- identifier prefix. The same [L] marker is visible on iPhone and Apple Watch, so the local-route notification can be reliably matched across both devices. Test protocol: Send a message with a known timestamp in the body, for example Timestamp 00:19 Wait for delivery on Apple Watch Turn the Watch screen off Wait approximately 2–3 minutes Wake the Watch and open Notification Center Result on Apple Watch, using iOS 26.5 + watchOS 26.5: Local-route notification, [L] Timestamp 00:19: correc
2w
Reply to 2+ months blocked on error 7000. Apple's "correct escalation path" is broken.
Adding my experience here as well. I started getting the same 7000 error code randomly two days ago during notarization. It seems to be triggered with larger builds. I tested out notarizing a small 8kb file, and that took 25 minutes, which is much slower than expected but eventually succeeded. My actual applications are around 500mb, and those either hang forever, or result in the 7000 Team is not yet configured for notarization error. I'm blocked on publishing any new app updates.
Topic: Code Signing SubTopic: Notarization Tags:
2w
Reply to RealityView AR - anchored to the screen not the floor
FYI: // // ContentView.swift // XRSandbox // // Created by Andy Wyatt on 3/15/26. // import SwiftUI import RealityKit struct ContentView: View { private let rootEntity = Entity() var body: some View { RealityView { content in content.add(rootEntity) } update: { content in updateARState(&content) } .ignoresSafeArea() .onAppear() { configureVirtualCamera() rootEntity.addChild(makeThing()) } .onTapGesture { spinThing() } .overlay { overlayView } } //MARK: - overlay with toggles at bottom @State private var arToggleState: Bool = false @State private var showARView: Bool = false @State private var perspectiveCameraInAR: Bool = false private var overlayView: some View { VStack { Spacer() VStack { Toggle(Enable AR, isOn: $arToggleState) .onChange(of: arToggleState) { handleARToggle() } // If PerspectiveCamera is in the RealityView entity heirarchy // the content is anchored to the screen rather than the floor Toggle(Keep PerspectiveCamera in AR, isOn: $perspectiveCameraInAR) .disabled(arToggleState) // can only
Topic: Graphics & Games SubTopic: RealityKit Tags:
2w
RealityView AR - anchored to the screen not the floor
This started out as a plea for help, but in preparing this post I discovered the root cause. I'm posting it as a lesson learned in hopes it will help someone. I've spent a good chunk of March trying to get AR-mode working again in my unreleased game. I had it working with SceneKit and ARView 5 years ago, but since 2024 I've been converting the game to use RealityKit and RealityView on iOS, macOS, visionOS, and tvOS. I've been having no joy getting AR mode to work on iOS. I get the pass-through device video but the game content isn't anchored to the floor but rather anchored to the screen. I made a simple project with just a simple shape in the middle of a RealityView and an overlay with a SwiftUI toggle to go in and out of AR-mode. At first, my simple project worked, and I couldn't figure out what was different in the logic. Both projects used the same logic: func transitionToXR(_ content: inout RealityViewCameraContent) { content.remove(gameBoard.rootEntity) content.add(xrAnchor) content.camera = .spatialTra
5
0
383
2w
Reply to Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. I'm not aware of any issue like this, and the general behavior you’re describing sounds like a bug. Have you filed a bug on this and, if so, what's the bug number? Also, what system versions are you seeing this on and have you seen it on watchOS 26.5? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? In theory, what you're doing should just work. More specifically, by design, your extension doesn't control the time data of the notification you're returning, so what actually happens is that the UNNotificationContent your extension returned is immediately embedded into a newly created UNNotification object, which is then processed normally. How that would end up creating the situation you're describing is something I can't explain. However, this i
2w
Family Controls entitlement: no response for over 2 weeks
Hi, I submitted my Family Controls entitlement requests on April 21 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. Has anyone had a similar delay recently? Is the recommended next step to file a code-level support request with my Team ID, or should I continue waiting? Thanks.
Replies
6
Boosts
0
Views
407
Activity
2w
No Response from Appeal or Support
I'm hoping someone can help me get clarity on my app submission for LinkUp, an iMessage-native group scheduling app. Here's the timeline: • Initial rejection (~1 month ago): Rejected under 4.3(a) for duplicating functionality of other apps • I updated screenshots, app description, and submitted again • For the past 2 weeks the app has been stuck with no meaningful response from App Review • I have called Apple support, submitted messages through the Resolution Center, and filed an App Review Board appeal — but I have received no confirmation email for the appeal and it does not appear on my developer support request page What LinkUp actually does: it lets friend groups coordinate availability entirely inside iMessage. Users send a schedule card as a message bubble, and participants vote on availability directly in the conversation thread — no redirects, no external app required. The heatmap updates in the bubble as people respond. To my knowledge, nothing on the App Store does this.
Replies
1
Boosts
0
Views
123
Activity
2w
App invisible in BOTH App Store search AND Apple Search Ads — Apple Support refuses to disclose violation flag (38 days)
Posting to document a case that matches a pattern of unresolved reports on this forum (e.g. thread #815203 Brutal Time), with the addition of new evidence: my app is missing from both the App Store search index and the Apple Search Ads campaign-creation index. Setup App: ZenTerm (App ID 6760935103, Bundle ID com.zenterm.mobile) Developer: Individual (Japan) Released: 2026-03-31 (live for 45 days) Status: Ready for Sale, 1.3.2 live (released 2026-05-06) App name: pure ASCII, coined word, no other apps share the name Symptoms Channel Result App Store app, search zenterm (exact name) Zero results, 38 days running iTunes Search API (https://itunes.apple.com/search?term=zenterm&country=jp) Returns my app correctly Direct App Store URL Opens product page normally Apple Search Ads — search by app name Zero candidates Apple Search Ads — paste canonical App Store URL Zero candidates The absence from both the App Store search index and the Apple Search Ads selection index is the key new finding. Since these run on
Replies
2
Boosts
0
Views
120
Activity
2w
Defining custom file types
On iOS:When one receives a file of type .pages by email, Mail displays a large Pages icon and tapping on it opens Pages. (A long-press brings up the more complicated Actions screen).When one receives a file of type .vcf by email, Mail displays a large Contacts icon and tapping on it opens Contacts. (A long-press brings up the more complicated Actions screen).I have my own custom file type, .ripf, and I want to have the same behaviour because that is what my users will expect. Accordingly, in my app's Info.plist I have a CFBundleDocumentTypes dictionary providing a one-element LSItemContentTypes array referring to the name 'com.universalis.ripcard', and a UTExportedTypeDeclarations dictionary associating the UTTypeIdentifier 'com.universalis.ripcard' with a public.filename-extension 'ripf' and a public.mime-type 'text/vnd.universalis.ripcard'. All the other entries in those two dictionaries are present and correct as far as I can tell. Both CFBundleDocumentTypes[0].CFBundleTypeIconFiles and UTExported
Replies
13
Boosts
0
Views
6.8k
Activity
2w
App not appearing in App Store search for over 6 weeks — including branded searches for its own name
I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app Brutal Time - Typographic Clock does not appear in App Store search results at all — not even when searching for its exact name Brutal Time. This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates a
Replies
1
Boosts
0
Views
255
Activity
2w
Reply to App not appearing in App Store search for over 6 weeks — including branded searches for its own name
Adding another data point — same symptoms, same lack of resolution. Sharing here in case the pattern helps Apple eventually acknowledge this as a systemic issue. App: ZenTerm (App ID 6760935103, Bundle ID com.zenterm.mobile) Released: 2026-03-31 (45 days ago) Status: Ready for Sale (1.3.2 live) Developer: Individual Symptoms (matches Brutal Time exactly) App Store search for the exact name zenterm → zero results, 45+ days running iTunes Search API (https://itunes.apple.com/search?term=zenterm&country=jp) returns my app correctly Direct App Store URL https://apps.apple.com/jp/app/zenterm/id6760935103 works fine Apple Search Ads campaign creation flow cannot find my app either — neither by name search nor by pasting the canonical App Store URL v1.3.2 (released 2026-05-06, with all third-party trademarks proactively removed from keywords) has now been live for 9 days — no change in search visibility Apple Support response so far Date Action Result 2026-04-11 First written inquiry Templated reply: we don't gu
Replies
Boosts
Views
Activity
2w
Reply to Radiometric interpretation of Apple ProRAW and Bayer RAW access via AVFoundation
Thanks for the precise framing — answering each in turn. Q1 — Bayer RAW capture through AVFoundation: Yes, third-party apps can capture Bayer RAW through AVFoundation. Both Bayer RAW and Apple ProRAW formats appear in AVCapturePhotoOutput.availableRawPhotoPixelFormatTypes. The recommended way to discriminate them is through the static query methods: AVCapturePhotoOutput.isBayerRAWPixelFormat(_:) AVCapturePhotoOutput.isAppleProRAWPixelFormat(_:) Apple ProRAW is opt-in: confirm photoOutput.isAppleProRAWSupported, then set photoOutput.isAppleProRAWEnabled = true. With ProRAW disabled, availableRawPhotoPixelFormatTypes exposes only Bayer formats; enabling ProRAW adds the ProRAW format to the same array. Device and format restrictions: Apple ProRAW: iPhone 12 Pro / Pro Max and later Pro models (iOS 14.3+). Bayer RAW: broadly available on devices that support RAW capture. Some virtual / fusion capture devices (for example, multi-cam) may not expose Bayer RAW because there is no single sensor providing the Bayer mos
Replies
Boosts
Views
Activity
2w
PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled
Feedback: PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled Summary PHBackgroundResourceUploadExtension's init() and process() methods are never called by the system when iCloud Photos is enabled on the device, even though setUploadJobExtensionEnabled(true) succeeds and uploadJobExtensionEnabled returns true. Environment iOS 26.4 (both devices) Xcode 26.x Tested on iPhone 17 Pro (primary device, 10,000+ photos) and an older iPhone (development device, 200+ photos) Same build deployed to both devices Full photo library access (.authorized) on both devices Steps to Reproduce Create an app with a PHBackgroundResourceUploadExtension (ExtensionKit, extension point com.apple.photos.background-upload) Enable iCloud Photos on the device (Settings > Photos > iCloud Photos) In the host app, request .readWrite photo library authorization and receive .authorized Call PHPhotoLibrary.shared().setUploadJobExtensionEnabled(true) — succeeds without error Verify PHPhotoLibrary.shared().
Replies
1
Boosts
0
Views
357
Activity
2w
Reply to PHBackgroundResourceUploadExtension is never scheduled when iCloud Photos is enabled
Thanks for the thorough investigation — using Console.app to pinpoint the gating decision at assetsd (Checked all submitted library bundles. Result: NO with iCloud Photos on, versus YES with it off) is exactly the diagnostic level engineering needs. Based on the public API documentation, the observed behavior doesn't match the framework's documented design. The Uploading asset resources in the background article and the documentation for setUploadJobExtensionEnabled(_:) enumerate two preconditions for the extension to run: full photo library authorization, and registration of the extension point com.apple.photos.background-upload. Neither mentions iCloud Photos. The stronger signal comes from the documented description of PHAssetResourceUploadJob.Type.upload: An upload job type (will download the resource from iCloud if required, then upload). That description is only meaningful if iCloud Photos can be enabled — the framework is explicitly designed to handle the case where photo assets are stored in
Replies
Boosts
Views
Activity
2w
Reply to Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
Quick update with results from a diagnostic build I ran on iOS/watchOS 26.5. To validate the distinction you described between the NSE-returned content path and the locally posted notification path, I shipped an internal TestFlight build where the NSE additionally posts a local UNNotificationRequest via UNUserNotificationCenter.add() in parallel with the standard contentHandler() call. The local notification uses the same title and body as the NSE-returned notification, except for a [L] prefix in the body and a local-z- identifier prefix. The same [L] marker is visible on iPhone and Apple Watch, so the local-route notification can be reliably matched across both devices. Test protocol: Send a message with a known timestamp in the body, for example Timestamp 00:19 Wait for delivery on Apple Watch Turn the Watch screen off Wait approximately 2–3 minutes Wake the Watch and open Notification Center Result on Apple Watch, using iOS 26.5 + watchOS 26.5: Local-route notification, [L] Timestamp 00:19: correc
Replies
Boosts
Views
Activity
2w
Reply to 2+ months blocked on error 7000. Apple's "correct escalation path" is broken.
Adding my experience here as well. I started getting the same 7000 error code randomly two days ago during notarization. It seems to be triggered with larger builds. I tested out notarizing a small 8kb file, and that took 25 minutes, which is much slower than expected but eventually succeeded. My actual applications are around 500mb, and those either hang forever, or result in the 7000 Team is not yet configured for notarization error. I'm blocked on publishing any new app updates.
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
2w
Reply to RealityView AR - anchored to the screen not the floor
FYI: // // ContentView.swift // XRSandbox // // Created by Andy Wyatt on 3/15/26. // import SwiftUI import RealityKit struct ContentView: View { private let rootEntity = Entity() var body: some View { RealityView { content in content.add(rootEntity) } update: { content in updateARState(&content) } .ignoresSafeArea() .onAppear() { configureVirtualCamera() rootEntity.addChild(makeThing()) } .onTapGesture { spinThing() } .overlay { overlayView } } //MARK: - overlay with toggles at bottom @State private var arToggleState: Bool = false @State private var showARView: Bool = false @State private var perspectiveCameraInAR: Bool = false private var overlayView: some View { VStack { Spacer() VStack { Toggle(Enable AR, isOn: $arToggleState) .onChange(of: arToggleState) { handleARToggle() } // If PerspectiveCamera is in the RealityView entity heirarchy // the content is anchored to the screen rather than the floor Toggle(Keep PerspectiveCamera in AR, isOn: $perspectiveCameraInAR) .disabled(arToggleState) // can only
Topic: Graphics & Games SubTopic: RealityKit Tags:
Replies
Boosts
Views
Activity
2w
RealityView AR - anchored to the screen not the floor
This started out as a plea for help, but in preparing this post I discovered the root cause. I'm posting it as a lesson learned in hopes it will help someone. I've spent a good chunk of March trying to get AR-mode working again in my unreleased game. I had it working with SceneKit and ARView 5 years ago, but since 2024 I've been converting the game to use RealityKit and RealityView on iOS, macOS, visionOS, and tvOS. I've been having no joy getting AR mode to work on iOS. I get the pass-through device video but the game content isn't anchored to the floor but rather anchored to the screen. I made a simple project with just a simple shape in the middle of a RealityView and an overlay with a SwiftUI toggle to go in and out of AR-mode. At first, my simple project worked, and I couldn't figure out what was different in the logic. Both projects used the same logic: func transitionToXR(_ content: inout RealityViewCameraContent) { content.remove(gameBoard.rootEntity) content.add(xrAnchor) content.camera = .spatialTra
Replies
5
Boosts
0
Views
383
Activity
2w
Reply to RealityView AR - anchored to the screen not the floor
Sorry for my slow response. I just created FB22780449 with the source code of my simple test project. Please see my comments in that post about the content sometimes not appearing where expected when returning from AR, and sometimes not finding an anchor when going in&out&in&out&in&out&in&out of AR like a squeezebox. (c;
Topic: Graphics & Games SubTopic: RealityKit Tags:
Replies
Boosts
Views
Activity
2w
Reply to Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. I'm not aware of any issue like this, and the general behavior you’re describing sounds like a bug. Have you filed a bug on this and, if so, what's the bug number? Also, what system versions are you seeing this on and have you seen it on watchOS 26.5? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? In theory, what you're doing should just work. More specifically, by design, your extension doesn't control the time data of the notification you're returning, so what actually happens is that the UNNotificationContent your extension returned is immediately embedded into a newly created UNNotification object, which is then processed normally. How that would end up creating the situation you're describing is something I can't explain. However, this i
Replies
Boosts
Views
Activity
2w