Overview

How can I allow the popup I am encountering while I run my UI tests with video recording in the Github actions. Since these tests are running on VMs, it's not possible to manually click Allow. Also the remote robot cannot interact with OS-level dialogs.

I don't know if this is the right place to raise this, so apologies if not. For years now, I have exported an NFS share from a host Mac which I connect to from a Raspberry Pi on the same network. I configure this by adding a line in /etc/exports - /Users/Pi -mapall=myusername This has always worked flawlessly, but since updating my Mac (M4 Mac Mini) to Sequoia 15.5 last week, it has developed a problem. If the NFS share is not accessed from the Pi for five minutes, it dies, and the Pi's file manager locks up necessitating a complete reboot. If I run a script on the PI which does an ls on the mounted share every 5 minutes, the lockup does not happen. But if I extend the period to 6 minutes, the lockup occurs. Something on the Mac NFS server seems to be dying in an unrecoverable fashion after five minutes of idle. Even with nfsd logging set to verbose, there is nothing helpful in the console logs. I am open to suggestions to further investigate or to try and fix this, but this is basically a showstopper for me - I need to be able to share data between Mac and Pi, and this is now broken.

Description: I’m noticing that the code coverage metrics in Xcode 26 are not accurate compared to earlier versions. In Xcode 15, the same set of unit tests shows around 38% coverage, but in Xcode 26, even though all the tests are running successfully (for example, the SegmentedUI test cases), the code coverage is displayed as 0%. Has anyone else observed this behavior in Xcode 26? Is there any known issue, workaround, or configuration change required to get the correct coverage report? Environment: Xcode 26 iOS 18 SDK Unit tests running under XCTest Any insights or suggestions would be appreciated.

hi all, as soon an audio is played in a whatever app, coreaudiod inserts a sleep prevent assertion for both, the system AND the display. can i somehow stop the insertion of the display sleep assertion? pid 223(coreaudiod): [0x00004e9e00058dc2] 00:03:18 PreventUserIdleDisplaySleep named: "com.apple.audio.AppleGFXHDAEngineOutputDP:10001:0:{B31A-08C6-00000000}.context.preventuseridledisplaysleep" Created for PID: 4145. where PID 4145 is spotify. but it doesn't matter which app is playing the audio. any help would be appreciated thanks

Hi everyone, On Monday, November 17, our company submitted an app to the App Store, and it has been stuck in “Waiting for Review” ever since. From what I’ve read, the usual review time is around 24–48 hours, so we’re a bit worried that the review hasn’t even started yet. Has anyone else seen similar delays recently? Any insight or advice would be greatly appreciated. Thank you!

腾龙公司位置于南亚果敢老街双凤塔附近，---TL9655.com---腾龙公司成立于2015年9月11日，公司主要经营游戏，腾龙公司属于一家实体企业公司，下面是公司经理微信《tle584》 下面是公司浏览官网，可以把这个复制到浏览器粘贴打开，注册一个自己喜欢的账号，注册好以后再点击下面APP下载安装，然后输入自己的账号登录就可以舒畅游戏

果敢腾 龙企业有限公司，薇---184-7933-278成立于2006年8月12日，下面给大家介绍一下公司主要位置和主要经营那些行业，腾龙公司位置靠于云南省临沧市边联的一个小城市，名称果敢老街，实时位置果敢城市中心双峰塔附近，公司主要是经营，旅游业，酒店服务行业，建筑业，科技游戏，餐饮，等等，这个有名的小城市虽然不是很大，但有着纸醉金迷小澳门的名誉之称呼，今天给大家介绍的就这些，如果你有想旅游的心，也欢迎来这个小城市旅游，来感受一下这里的民族风情。

Hi There, I´m From Spain with an LLC Company in the USA. Is a Disregarded company, the problem is that when I try to set up the paid apps agreement, Apple display the form W-9 instead of Form W8-BEN (that is for non-us resident) My question is... is this right? Under the name of my company, appear an option that ask me ... "Who is the Beneficial Owner? " You can choose between : Individual, Limited Liability - Disregarded Entity, Limited Liability - Partnership, Other... I choose Limited Liability - Disregarded Entity I m not sure if the form W-9 is the right for me because my other online business is about selling books on amazon and there the form that I m using is W8-BEN

The API we used: NSURL *url = [NSURL URLWithString:@"App-Prefs:INTERNET_TETHERING"]; The link provided by Apple engineer: https://developer.apple.com/forums/thread/761314 I did not find any URL in the link that leads to the secondary menu of system settings. Does this suggest that iOS 26 does not support this functionality? Moreover, is it possible that versions of iOS 18 and earlier may also not support this behavior in the future?

Hello! I'm creating a settings page for my app and I want it to look as native as possible. I want to know if it's possible to add constraints that make the second label go to the bottom when the text size gets really large (see Picture1) instead of having to force it to be on the right (see Picture 2). I've left my constraint code for this cell down below, too. I'm still learning constraints and best practices, so if there's any feedback, I'd love to hear it. Thank you! Picture 1 Picture 2 - (void) setConstraints { [NSLayoutConstraint activateConstraints:@[ // Cell Title Label [self.themeColorLabel.leadingAnchor constraintEqualToAnchor:self.contentView.layoutMarginsGuide.leadingAnchor], [self.themeColorLabel.trailingAnchor constraintEqualToAnchor:self.contentView.layoutMarginsGuide.trailingAnchor], [self.themeColorLabel.topAnchor constraintEqualToAnchor: self.contentView.layoutMarginsGuide.topAnchor], [self.themeColorLabel.bottomAnchor constraintEqualToAnchor: self.contentView.layoutMarginsGuide.bottomAnchor], // Selected Theme Color Label [self.selectedColorLabel.trailingAnchor constraintEqualToAnchor: self.contentView.layoutMarginsGuide.trailingAnchor], [self.selectedColorLabel.topAnchor constraintEqualToAnchor: self.contentView.layoutMarginsGuide.topAnchor], [self.selectedColorLabel.bottomAnchor constraintEqualToAnchor: self.contentView.layoutMarginsGuide.bottomAnchor], ]]; }

Hello, I’m contacting you for assistance regarding an App Review issue that our company is currently facing. Background Several months ago, a former employee submitted an early prototype of our app using his personal Apple Developer account. That submission was never approved, and after the employee left the company, he removed the app from his account. It is no longer available on the App Store and no longer listed under that account. Recently, we rebuilt the product completely — new UI, new codebase, and a fully updated design — and submitted it under our company’s official Apple Developer account. Issue Our recent submission was rejected with 4.3 – Spam, indicating that our app is considered a duplicate of another existing app. However, the only similar app is the old prototype submitted several months ago by the former employee, which was removed and never published. It seems likely that our submission is being linked to that previous prototype, even though it no longer exists and was submitted under a different personal account. Appeal Status We submitted an Appeal right after receiving the 4.3 rejection. It has now been one week, and we have not received any update or confirmation: No email response No status change in App Review The Appeal does not appear in the Resolution Center The app remains unable to move forward in the review process Request for Assistance Could you please help us with the following? Could you confirm whether our Appeal was successfully received? What is the typical response time for Appeals in cases like this? Is any additional information required from us to continue the review? If the previous submission under the former employee’s personal account is influencing the review, how can we resolve this issue permanently? Is there a recommended way to escalate this situation, given that this app is critical for our company? We sincerely appreciate your time and assistance. Thank you, and we look forward to your guidance.

Hi everyone, I’m currently facing a blocking issue during App Review, and I’d really appreciate some help from anyone who has experienced something similar. My app was rejected under Guideline 2.1 – App Completeness with the following message: “An error message appeared after trying to Sign in with Apple. Device: iPad Air (5th generation), iPadOS 26.1.” The problem is: I cannot reproduce this bug at all, even when testing under the same conditions. ✔ What I tested: Physical iPad Air M2 on iPadOS 26.1 Physical iPhone devices iOS/iPadOS simulators (latest Xcode) TestFlight build (clean install) Debug build installed via Xcode (device connected) In every case, Sign in with Apple works correctly: Authentication sheet displays properly Callback returns the credential User is created/logged in without error No crash, no rejected promise, no empty credential ✔ Environment Using ASAuthorizationAppleIDProvider + ASAuthorizationController Default Apple Sign In button No custom nonce/redirect modifications No backend processing at login (client-side only) Works 100% on iPhone and iPad on my side ✔ Additional context The app review team also noted a second point: They couldn’t locate a secondary subscription paywall, which is displayed only after dismissing the first paywall. I already clarified this with them, but I'm mentioning it in case it's related to the Sign in with Apple issue — maybe something in the sandbox environment is causing unexpected UI behavior. ❓ My question Has anyone already seen Sign in with Apple fail ONLY for the App Review team, while: It works in TestFlight It works via Xcode installs It works on the same OS version It works on the same hardware Could it be an issue related to: Sandbox Apple ID? iPadOS 26.1 on App Review internal builds? Reviewers blocking popup presentation context? Missing entitlement although everything is configured correctly? Presentation anchor issues specific to iPad? Any help or ideas would be greatly appreciated. I’ve been trying to reproduce this bug for hours without success, so any insight is welcome. Thanks!

I submitted my app for review on November 12, but I still haven’t received any response. It’s now November 25, and the review is still pending. Android is much faster with reviews, it took them 2 days. Could someone from the App Review Team please check my submission? Thank you very much! 🙏 Apple Id: 6753878193

The review team rejected our application wrinting this : We have started our review, but we need additional information to continue. Specifically, it appears your app may access or include paid digital content or services, and we want to understand your business model before completing our review. Our app is free and doesn't include any payement package or page But we are coupled to another application for the login. And this other application has a trial period and effectively needs payment after. Do i need to explain in my app all the payment process of the other app ?

Hi all, Our app has been in review since November 1st, and the process has been very slow. We often wait several days between responses, and we keep receiving questions we’ve already answered - even when we point this out in our replies. We’ve contacted Developer Support by email, but the only reply we received was that they’re sorry for the delay and will look into it. We’re unsure whether requesting a phone call might help or if it could pause or reset the review process, and since we’re hoping the next response will finally approve the app, we’ve hesitated to use that option. Has anyone experienced something similar, or does anyone know whether requesting a call has any impact on the current review status? Thanks for any guidance.

Hello everyone, We wanted to share our situation and see if anyone has had a similar experience. Our app was submitted to the App Store on Monday, November 20th, and its status has remained "Waiting for Review" ever since. Based on Apple's typical review times of 24-48 hours, we're a bit concerned that the review process hasn't even started after several days. Has anyone else encountered similar delays recently? We would greatly appreciate any advice or insight into what might be causing this. Thank you!

Hi, We recently updated our app icon, but the push notification icon has not been updated on some devices. It still shows the old icon on: • iPhone 16 Pro — iOS 26 • iPhone 14 — iOS 26 • iPad Pro 11” (M4) — iOS 18.6.2 • iPhone 16 Plus — iOS 18.5 After restarting these devices, the push notification icon is refreshed and displays the new version correctly. Could you advise how we can ensure the push notification icon updates properly on all affected devices without requiring users to restart? Thank you.

Hi, We recently updated our app icon, but the push notification icon has not been updated on some devices. It still shows the old icon on: • iPhone 16 Pro — iOS 26 • iPhone 14 — iOS 26 • iPad Pro 11” (M4) — iOS 18.6.2 • iPhone 16 Plus — iOS 18.5 After restarting these devices, the push notification icon is refreshed and displays the new version correctly. Could you advise how we can ensure the push notification icon updates properly on all affected devices without requiring users to restart? Thank you.

Good morning, We are implementing Live Activities in a push-to-start flow. We wrap the listener for push to start tokens in a high priority task: if ptsListenerTask == nil || ptsListenerTask?.isCancelled == true { ptsListenerTask = Task(priority: .high) { [weak self] in for await pushToken in Activity<LiveAuctionAttributes>.pushToStartTokenUpdates { //Send token to back-end } } I've tried a few variations of this and they work well on most devices. I have seen a couple of devices that refuse to issue a push to start token. The user will have logging for the init flow and starting the PTS listener then the logs just go silent, nothing happens. One thing that seemed to work was getting the user to start a Live Activity manually (from our debugging tool) then the PTS token gets issued. This is not very reliable and working a mock live activity into the flow for obtaining a PTS token is a poor solution. Is anyone else seeing this and is there a known issue with obtaining PTS tokens? Thanks! Brad

What is the correct way to implement scrolling in a looong list that uses ScrollView and LazyVstack Imagine I have some api that returns a longs list of comments with replies The basic usecase is to scroll to the bottom(to the last comment) Most of the time this works fine But, imagine some of the comments have many replies like 35 or more (or even 300) User expands replies for the first post, then presses scroll to bottom. The scrollbar reaches the bottom and I see the blank screen. Sometimes the scrollbar may jump for a while before lazyvstack finishes loading or until I manually scroll up a bit or all the way up and down What should I do in this case? Is this the swiftui performance problem that has no cure? Abstract example: ScrollViewReader { proxy in ScrollView { LazyVStack { ForEach(comments) { comment in CommentView(comment: comment) .id("comment-\(comment.id)") } } } } struct CommentView: View { let comment: Comment @State var isExpanded = false var body: some View { VStack { Text(comment.text) if isExpanded { RepliesView(replies: comment.replies) // 35-300+ replies } } } } ... scroll proxy.scrollTo("comment-\(lastComment.id)", anchor: .bottom)