“show when run”

Hi Ziqiao, thanks for looking into this. I'll answer your question about our share flow, then share some significant findings from today's debugging. We use a custom token-based invite flow rather than the standard system share URL tap → userDidAcceptCloudKitShareWith path. Here's the full flow: How we deliver the share URL Owner creates an invite token — stored as an InviteToken record in the public CloudKit database. The token record contains the CKShare.url string, the household ID, and a 7-day expiration. Owner sends a deep link — the invite UI generates a mesa://invite?token= URL and presents a share sheet (Messages, AirDrop, etc.). This is a custom URL scheme, not the CKShare.url directly. Participant opens the deep link — the mesa:// URL opens our app. The app extracts the token, queries the public database for the InviteToken record, and reads the shareURL field to get the CKShare.url. How we accept the share (programmatic path) Once we have the CKShare.url from the token lookup: // 1. Fetch share met

Hi Michael, Thank you for the tips. Today I tried your last recommendation but it didn't work. Let me list my process. I have got both walk and run animations as one animation in .fbx file. Then imported it to Blender. First I exported T-Pose of the entity and then exported animation in .usdz format. Started using T-Pose rabbit entity in RCP Then import that usdz animation in RCP's AnimationLibraryComponent . On the code side (as you suggested) I did clipping the timeline into two small animations as walkClip and runClip. And pass those clips in order to construct a BlendTreeeAnimation. if let rabbit = await RabbitBuilder.loadRabbit() { rabbit.components.set(RabbitWalkerComponent(elapsed: 0, speed: rabbitSpeed)) RabbitWalker.entity = rabbit content.add(rabbit) let anims = rabbit.availableAnimations // ── Slice a single combined clip into walk and run ───────────── // Walk = keyframes 0–18, Run = keyframes 19–29. // trimStart / trimEnd are in seconds, so we need the frame rate. // Re

Your layout computes the content offset adjustment during invalidation using stale bounds, which causes the offset problem during rotation. Two issues contribute to this. 1. Stale bounds in invalidateLayout(with:) Your invalidateLayout(with:) override computes the content offset adjustment using collectionView.bounds.width: let delta = (CGFloat(currentPage) * collectionView.bounds.width) - collectionView.contentOffset.x customContext.contentOffsetAdjustment.x += delta The problem is that when this runs during a bounds change (rotation), collectionView.bounds.width may still reflect the pre-rotation width. The delta calculation snaps the offset back to where it already was, rather than adjusting for the new width. Override invalidationContext(forBoundsChange:) instead — it receives the new bounds as a parameter: override func invalidationContext(forBoundsChange newBounds: CGRect) -> UICollectionViewLayoutInvalidationContext { let context = super.invalidationContext(forBoundsChange: newBounds) if le

[quote='822878021, jimmy520, /thread/822878, /profile/jimmy520'] Does this guidance also apply to UITabBar? [/quote] Yes, TN3106 applies broadly to navigation elements including UITabBar. Custom backgrounds, colors and appearances can interfere with how the system manages Liquid Glass. People use Apple products in all sorts of ways, to avoid any unexpected results, it's best to stick to recommended best practices. Consider how the system handles accessibility automatically. There's a chance going against a recommendation can make some content harder to see for some of your users. [quote='822878021, jimmy520, /thread/822878, /profile/jimmy520'] could setting a custom background color via UITabBarAppearance interfere with internal layout constraints required for the Liquid Glass effect to adapt correctly during orientation changes? [/quote] That sounds odd to me. If it's behaving differently depending on orientation. I'd be interested in taking a look and sharing that report with the relevant engineering team.

Hello, this issue should be resolved in Xcode 26.5 Beta 2. It was noted as a Known Issue in the release notes here: Testing Known Issues Tests fail to run on iOS 15 simulators (173337319) (FB22333623) However, despite being marked as a known issue, it should in fact be resolved in Beta 2, and we will update the release notes to reflect that. Please try the latest Xcode 26.5 release and file a Feedback if you continue to experience problems with testing on older simulators.

Hi There, I am also facing this problem, but I am stuck because my device is not shown in the Bluetooth panel. It is unclear how to get it to show up in this panel, but I have an iOS app that uses CoreBluetooth that can see it advertising and can pair with it. nRFConnect from Nordic can also see it and connect/pair. But I have deleted the bond table on my device and now I am completely hosed because I cannot reconnect because I always get this error. I tried deleting the Network Settings and power cycling the phone but it doesn't help - it is permanently locked out now. So I have two questions: How can I recover in this situation? How can I get my device to show up in the Bluetooth settings (both showing scan results and as a previously paired/device) so in the future I can Forget it? Thanks, Mark