Hi, Am using fastlane to upload into TestFlight. Am able to successfully upload the build without any issues. For Testing Internally , I want to upload the build into App Store Connect but I should restrict it on submitting to App Store. ( This is possible when i distribute the app via TestFlight Internal Only from XCode -> Organizer -> Distribute App (Select option with TestFlight Internal Only). I want to achieve the same using either Transporter/ fastlane. I tried setting buildAudienceType to INTERNAL_ONLY as per https://developer.apple.com/documentation/appstoreconnectapi/buildaudiencetype but it is not working. Can you suggest how i can achieve this via fastlane?

I have been trying to sign up for Apple Developer for many days. I fill in the details, provide my valid card, and they say they will get back to me in 2 days. However, I have never received a response. I need to launch an app, and this is holding me back.

Can iOS support Bluetooth trackpad?

For 9 Glorious Months, My MacBook Pro & J5 Create JCD543 HUB Were Best Friends… Until I Updated macOS For nearly a year, my MacBook Pro 14” (2023, M2 Pro, 16GB RAM) worked flawlessly with my J5 Create JCD543 HUB, allowing me to run: ✅ 4 External Displays (Samsung, LG, Insignia, Samsung) A setup that worked perfectly… until I updated macOS. Then Came the Update… and the Issues Began First, I updated last week. Two of my four displays stopped working. No big deal, I thought—I’ve dealt with display quirks before. Then, like an optimist ignoring red flags, I updated again last night to 15.4 Beta (24E5222f) and… well, now things are completely broken. My Once-Perfect Setup (Now a Display Disaster) JCD543 HUB → 2 HDMI displays (not working) JUD380 HUB → 1 HDMI display (partially working, unstable) MacBook HDMI port → 1 HDMI display (working, but feeling abandoned) JCA365 USB-C to Dual HDMI Adapter (Not part of my setup, but tested—also not working) What I’ve Tried (aka My Troubleshooting Journey) ✔ Restarted my Mac multiple times ✔ Uninstalled and reinstalled J5 drivers ✔ Swapped cables, unplugged/replugged everything, tested known-working HDMI cables (they work fine on other devices) ✔ Deleted /Library/Preferences/com.apple.windowserver.displays.plist (this fixed a similar issue in the past, but the file no longer exists in this update) The Likely Culprit? It seems to be a J5 driver issue triggered by the macOS update—and I’m not alone. Others are reporting similar problems. Apple… Any Fixes? I just want my four screens back. The setup worked flawlessly for 9 months, so it’s hard to believe it was never meant to work. If anyone has a workaround, I’m open to testing any solution—whether it’s a driver update, system tweak, or hidden macOS setting that might bring my displays back to life. Any advice would be greatly appreciated! Thanks in advance. (P.S. Apple, if you’re reading this—please look into this issue!)

Macos15照片app需要点击一下，不能直接进入，点击一次后，还要再点击一下，才能看到照片，希望能修复一下

I’m just trying to find someone who know what the diagnostic logs o my apple watch are for like sysdouagnos and the Bridge Pair Performance obviously I understand what a diagnostic logs are but it’s looks as if I need to download them still why wouldn‘t it already be running

When I use the screenshot feature, I find that the screenshot becomes darker in color compared to the original image, this seems to be a bug in iOS 18. can anyone help me?

“At this rate, I’m starting to get frustrated. I’ve registered for the developer program twice, but they’re still asking me for the registration fee, and my registration is not being approved. Moreover, I haven’t received any response to my emails, and since the information is limited in English, I can’t search for solutions. Could someone please take care of this issue now?”

Hello, I am currently working on integrating Meta Audience Network (Meta) with Google AdMob using bidding mediation for an iOS app. The goal is to show ads through meta , with AdMob acting as the mediation layer. I have successfully set up both the Meta SDK and Google AdMob SDK, as well as the GoogleMobileAdsMediationFacebook adapter. My AdMob and Meta accounts are both linked for mediation, and I have configured the correct placement IDs for Meta within AdMob. Currently i am creating a demo project with demo accounts i haven't added app live link as my app isn't on AppStore and haven't added any payment method. However, I am encountering a couple of issues and need some guidance: 1. Test Ads Work, but Real Ad Unit Fails: • When using test AdMob ad unit IDs, everything works fine, and ads are shown as expected. • But when I use my original AdMob ad unit ID, I get the error: “Publisher data not found.” • Does this mean my app is not fully set up or is there something else I might be missing in my configuration? • Is it necessary to go live on the App Store to get ads from the real ad unit, even for testing purposes? 2. Meta Ads via Bidding Mediation: • I have integrated Meta through AdMob’s bidding mediation system. But i am showing ads using GADBannerView is it right way to show meta ads that are mediated with google admob. If i have to show ads with FBAdView from where to get withBidPayload value for this function adView.loadAd(withBidPayload: "what_here") 3. Payment Method Requirements: • My app is still in the demo/testing phase and is not live on the App Store. I have not added any payment methods in either AdMob or Meta. • Is it necessary to add a payment method for testing purposes, or is this only required when I start monetizing and going live? I would appreciate any advice or pointers to ensure the setup is correct and to understand why the original ad unit ID isn’t working during testing. Thank you for your time and assistance!

After doing a software update I can only view iMessages older than 12hrs (from a single contact) if the other person replies to and older message. Every time I leave the Massages app and go back in the issue occurs again.

I am trying to create a phone app that can receive incoming call notifications using CallKit, as described in Apple's CallKit documentation. Added the com.apple.developer.calling-app entitlement in my .entitlements file. Implemented CXProvider and set up the delegate methods (provider:perform: and providerDidReset). Added UIBackgroundModes with voip in Info.plist. Configured CXProviderConfiguration to support phone numbers. I expected to receive incoming call notifications when my app was set as the default calling app. However, I am not receiving any notifications when an incoming call arrives. How can I properly detect and handle incoming calls in my default calling app? Is there any additional configuration required for iOS 18.2+?

I have the following questions that need official answers: 1: Whether the Bluetooth scanning cycle can be controlled through the software level. If it can be controlled, please tell me how to control it. 2: Now the IOS mobile phone scanning strategy, how long is the scanning cycle, and what is the scanning duty cycle in this scanning cycle

As explained above only ended up being about to use voice and text

I installed the new developer beta 26 yesterday, but since that I only have problems with my iPhone. Besides not being able to update the software bc an error appears, I also don‘t have the abbility to use mobile data. If I try to, it only says „could not activate mobile data network“. I already tried to restart the phone, to reset it or to take the SIM out and in

The following is my code, which runs successfully and is recommended to succeed, but it still does not show Siri's suggestion to users in the system sharing in Safari import AppIntents import Contacts import CoreSpotlight import Intents import UIKit class TestViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() self.view.backgroundColor = UIColor.white DispatchQueue.global().async { self.donateMessageInteraction(recipientName: "张三", phoneNumber: "+8613812345678") } } func donateMessageInteraction(recipientName: String, phoneNumber: String) { INPreferences.requestSiriAuthorization { status in guard status == .authorized else { return } // 1. 创建接收者 let recipientHandle = INPersonHandle(value: phoneNumber, type: .phoneNumber) let recipient = INPerson( personHandle: recipientHandle, nameComponents: nil, displayName: recipientName, image: nil, contactIdentifier: nil, customIdentifier: "com.yourapp.recipient.\(phoneNumber)" ) // 2. 创建发送者（你的应用身份） let senderHandle = INPersonHandle(value: "15210639372@163.com", type: .emailAddress) let sender = INPerson( personHandle: senderHandle, nameComponents: nil, displayName: "我的应用", image: nil, contactIdentifier: nil, customIdentifier: "com.yourapp.sender" ) // 3. 创建消息意图 let intent = INSendMessageIntent( recipients: [recipient], outgoingMessageType: .outgoingMessageText, content: "最近怎么样？", // 常用消息内容 speakableGroupName: nil, // 群组名称（一对一设为nil） conversationIdentifier: "com.yourapp.conversation.\(phoneNumber)", // 唯一会话ID serviceName: "My Chat Service", // 你的消息服务名称 sender: sender, // 发送者身份 attachments: nil ) // 4. 配置意图参数 intent.setImage(INImage(named: "user0"), forParameterNamed: \.sender) // 5. 创建并捐赠交互 let interaction = INInteraction(intent: intent, response: nil) interaction.direction = .outgoing interaction.donate { error in error.map { print("捐赠失败: \($0)") } } print("捐赠代码执行完成") } } }

In the actual development, I found that I could not complete the setting of my icloud+ customised email domain name SMTP. I tried to configure the SMTP of iCloud custom email according to Apple's document (https://support.apple.com/en-us/102525) but the error I looked through Apple's support file, but I didn't find the specific configuration of iCloud + customised email SMTP.

IOS 18.3 Beta This started at BETA 18.2 Only when plugged in to an external power bank. Ideas or workaround? Or just wait till the next BETA version?

Unable to select the desired build in App Store Connect; clicking on the build has no effect. Steps to reproduce: 1.I select my app 2.I choose which build to add 3.I try to select the build Expected result: I should be able to select the build Actual result: Nothing happens Browsers Tested: Google Chrome (both PC and mobile), safari mobile Supporting Video: https://www.loom.com/share/cd9c831920fb43518ef461c9a697f09f?sid=9ce60f81-0a7c-44f4-b88a-74dcc9820e14, https://drive.google.com/file/d/1PJEixy8IpFTEEDLjBMQjV-b9U8zUM2S0/view?usp=sharing Screenshots: https://gyazo.com/e390a5ddaa142ac9e5cbb2a6757abee8, https://gyazo.com/08ac242fbfd61d375766da04f7eb209c

I updated my Apple Watch Series 6 before Apple withdrew beta 11.4 as an option. I see on forums that I am not alone with this issue. Many series 6 watches are now stuck in a boot loop. I hope Apple can resolve the issue for those of us that pushed the update to our watches before the issue was identified. Support were unable to assist.

I’m trying to register an Apple Developer Account for my company. I uploaded all the required documents, but my initial application was rejected, and I was asked to provide notarized translations of my documents. I translated them and submitted everything for review on April 1. After a week without a response, I contacted Apple Support. They replied that the documents had been received and were under review. However, as of today, April 24, my account is still under review. I’ve sent five follow-up emails to Support asking for a status update on my case, but I haven’t received any replies. Has anyone faced a similar situation and could suggest what I can do to get a status update and finally complete the registration? If anyone from Apple Support is reading this, my case number is 20000098634973 and my Enrollment ID is J34432JQFC. Thank you in advance for your help.