iPhone 16 pro

I'm at my wit's end with a problem I'm facing while developing an app. The app is designed to send video captured on an iPhone to a browser application for real-time display. While it works on many older iPhone models, whenever I test it on an iPhone 17 Pro or 17 Pro Max, the video displayed in the browser becomes a solid green screen, or a colorful, garbled image that's mostly green. I've been digging into this, and my main suspicion is an encoding failure. It seems the resolution of the ultra-wide and telephoto cameras was significantly increased on the 17 Pro and Pro Max (from 12MP to 48MP), and I think this might be overwhelming the encoder. I'm really hoping someone here has encountered a similar issue or has any suggestions. I'm open to any information or ideas you might have. Please help! Environment Information: WebRTC Library: GoogleWebRTC Version 1.1 (via CocoaPods) Signaling Server: AWS Kinesis Video Streams Problem Occurs on: Model: iP

iPhoneで撮影した映像をブラウザのアプリへ送信して画面に映す機能を持ったアプリを開発しています。 iPhone 17 Pro, 17 Pro Maxでこのアプリを利用するとブラウザ側に表示される映像が緑一色や、緑がメインのカラフルな映像になってしまいます。 調べてみると17Proと17ProMaxで超広角カメラと望遠カメラの画素数が変更になっている（1200万画素→4800万画素）ためエンコーディングで失敗しているのではないかと疑っています。 なんでも情報下さい。 環境情報 WebRTCライブラリ： GoogleWebRTC バージョン 1.1 (CocoaPodsで導入) シグナリングサーバー： AWS Kinesis Video Streams 問題が発生するデバイス： モデル名: iPhone18,1, OS: 26.0 モデル名: iPhone18,1, OS: 26.1 問題が発生しないデバイス： iPhone17,5 以前の多数のモデル モデル名: iPhone18,1, OS: 26.0 モデル名: iPhone18,3, OS: 26.0

Hi Team, For last 24 hours one of our team members is unable to login to apple dev portal due to two factor authentication not being sent. Error we are getting is Verification codes can't be sent to this phone number at this time. Please try again later

Hi there - I have an Issue everytime an app uses the Frontcamera, it crushes. I tried all the basic steps to help such as newstart of the phone, newest updates of the apps, reset all settings etc. nothing helps. I am now in IOS 26.1. Any Ideas?

I have a workflow where I want to specifically run some tests in the iOS 18 simulator. All while using Xcode 26 on Xcode Cloud. In my Xcode Cloud workflow I can set the iOS version, but just iOS 16, 17 and 26, but no 18? I'm very confused here Not sure which is the right channel anyway to request support to Xcode Cloud too

Under iPadsOS 26.0 and 26.1, if a view controller is presented with a presentation style of fullScreen or pageSheet, and the view controller is setup with a UISearchController that has obscuresBackgroundDuringPresentation set to true, then when cancelling the search the view controller is being dismissed when it should not be. To replicate, create a new iOS project based on Swift/Storyboard using Xcode 26.0 or Xcode 26.1. Update ViewController.swift with the following code: import UIKit class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .systemBackground title = Root navigationItem.rightBarButtonItems = [ UIBarButtonItem(title: Full, primaryAction: .init(handler: { _ in self.showModal(with: .fullScreen) })), UIBarButtonItem(title: Page, primaryAction: .init(handler: { _ in self.showModal(with: .pageSheet) })), UIBarButtonItem(title: Form, primaryAction: .init(handler: { _ in self.showModal(with: .formSheet) })), ] } private func showModal(with sty

Hello, We have developed a hardware product that embeds an FTDI USB-serial converter, and an application on MacOS that communicates with this device. We would like to port our application to iPadOS. I can see that when I plug the device into the iPad, it is recognized as a serial port, based on its console logs. When I attempt to enumerate serial ports on iPadOS using IOKit, I can see matching IOSerialBSDClient services, but the properties are sandboxed, including the IOCalloutDevice property, for example: 0 error 16:36:10.922450-0700 kernel Sandbox: ***(662) deny(1) iokit-get-properties iokit-class:IOUserSerial property:IOTTYSuffix Is there an entitlement that can be applied that allows access to the serial port properties of an attached USB device? Or do I need to implement my own USBDriverKit driver for this device, as seems to be implied in these forum threads: https://developer.apple.com/forums/thread/795202 https://developer.apple.com/forums/thread/655527

We are integrating Xcode Cloud into a larger CI/CD pipeline and ran into a serious limitation that makes proper build status reporting nearly impossible. Currently, Xcode Cloud provides only the following custom script phases: • ci_post_clone.sh • ci_pre_xcodebuild.sh • ci_post_xcodebuild.sh However, if a build fails during the actual Xcode build phase (for example, due to a compilation error, unit test failure, or signing issue), the ci_post_xcodebuild.sh script does not run. This means there is no guaranteed way to execute cleanup steps or send external notifications (e.g., updating build status in Bitbucket, Slack, or any external CI system). In any robust CI/CD setup, it’s critical to have a “finally” or “always run” hook that executes regardless of build success or failure — similar to post blocks in Jenkins, finally steps in GitHub Actions, or after_script in GitLab CI. Without such a mechanism, we cannot reliably integrate Xcode Cloud with the rest of our automation and monitoring ecosystem. This effec

Estou encontrando dificuldades em conseguir aprovar meu primeiro app na loja da apple. a equipe de review ja rejeitou duas vezes pelo mesmo motivo, mesmo eu arrumando. 1 - fotos do ipad, na conclusao da equipe trata-se de um iphone esticado porem nao é, foi feito pela nossa equipe de marketing, com prints da tela de um ipad original. 2 - outro motivo é nome da minha empresa, eu sou responsavel pelo desenvolvimento do app, a razao social esta em meu nome mesmo, porem o nome fantasia esta no nome do meu app, só que mesmo assim a equipe alega que nao. abri um chamado e estou aguardando retorno. mesmo assim queria saber se alguem ja passou por isso e pode me ajudar a solucionar esse problema.

Hi. I am looking for a UIKit solution that allows me to “prevent” screen recording and sharing on certain pages in application. By “preventing” I mean that the distributed result should be a black content. Me as a user should still see the pages’s content as it is, but the recording or shared screen footage should show a black screen. I have already checked out the workaround solutions with UITextField, but those does not work for me. So I am looking for other suggestion. (Btw I know that nothing stops a user from taking a video of an app with another phone, but I still need a solution to the issue I have described above)

I am trying to run the simple demo app from xcode on my Apple Watch SE 1st gen, which has WatchOS 10.6 This turned out to be an impossible mission. I have xcode 16.1 installed, can't downgrade to 15.4 (which is the latest that supports this os) since it won't run on my OS (Sequoia), using parallels I installed Sonoma and xcode 15.4 but it won't recognize my iphone or my watch. Asking ChatGPT it seems that it is possible to use the DeviceSupport watchOS 10.6 image if I get it from someone, but loading it up the right way on my machine turned out to be impossible. Any recommendations / help / link to this file where I can download it?

[Question] Inconsistent Call Directory number matching across regions (Japan, Taiwan, U.S.) We’re developing a Call Directory extension and observed inconsistent number matching depending on carrier region and number format. Environment Device: iPhone (iOS 26.0) Call Directory Extension: Custom implementation Carrier A: Japan carrier SIM Carrier B: Taiwan carrier SIM Numbers added to Call Directory patterns: +81 120 580 2XXX +81 704 336 2XXX Observed Behavior (Japan Carrier SIM) Incoming call from +81 120 580 2XXX → Caller name not displayed (Call Directory match failed). Entering 0120 580 2XXX in the Phone app dialer → Name displayed correctly. Incoming call from +81 704 336 2XXX → Caller name displayed correctly. Entering 070 4336 2XXX in the Phone app dialer → Name displayed correctly. Observed Behavior (Taiwan Carrier SIM) Entering +81 120 580 2XXX in the dialer → Name not displayed until the call button is pressed. Entering +81 704 336 2XXX in the dialer → Name displayed immedi