iPhone 16 pro

Hello, we are developing hardware that needs to connect to an iPhone via Wi-Fi to send requests to a server. On Android, we have managed to create a programmatic local hotspot within the app to facilitate connection and improve the user experience. On iOS, however, Personal Hotspot must be manually enabled from the system settings, and the user must manually enter the SSID and password, which significantly degrades the UX. My questions are: Is there a workaround, unofficial method, or private API to generate a local hotspot from an app on iOS, similar to what can be done on Android? Is there an alternative within the MFi program or through specific frameworks to facilitate a quick and automatic connection between the hardware and the iPhone without relying on the manual Personal Hotspot? Are there any best practices for improving the local Wi-Fi connection experience between an accessory and an iPhone in the absence of hotspot controls? I would appreciate any guidance, experience, o

Hello, we are developing hardware that needs to connect to an iPhone via Wi-Fi to send requests to a server. On Android, we have managed to create a programmatic local hotspot within the app to facilitate connection and improve the user experience. On iOS, however, Personal Hotspot must be manually enabled from the system settings, and the user must manually enter the SSID and password, which significantly degrades the UX. My questions are: Is there a workaround, unofficial method, or private API to generate a local hotspot from an app on iOS, similar to what can be done on Android? Is there an alternative within the MFi program or through specific frameworks to facilitate a quick and automatic connection between the hardware and the iPhone without relying on the manual Personal Hotspot? Are there any best practices for improving the local Wi-Fi connection experience between an accessory and an iPhone in the absence of hotspot controls? I would appreciate any guidance, experience, o

Hello, this may not be the correct place to ask this question so I apologize in advance if this is the case. I am currently running into two specifc issues while continuing to implement the app.managed configuration which are quite frustrating and I will detail them below Unlike MDM where an application could be reinstalled, by sending an install application command down for the same app DM does not have a similar mechanism which causes some issues as (while inconsistent) devices do not always respect the configuration sent down, and will not begin downloading VPP applications. They can be seen in the configuration when checking under VPN & Device Management but they do not return on a status report, alternatively and app will install but will have a cloud symbol next to it requiring a download (which I believe would be impossible on supervised devices without apple accounts/have restricted apple accounts associated to them). These apps are also reported incorrectly, as they return a managed response whil

I'm experiencing a persistent iOS Simulator app installation failure when running automated tests using Appium/XCUITest. The error occurs consistently across different simulator configurations and appears to be related to metadata handling during app installation. Error Details Primary Error: An error was encountered processing the command (domain=IXErrorDomain, code=2): Simulator device failed to install the application. Failed to create promise. Underlying error (domain=IXErrorDomain, code=2): Failed to set metadata for org.adblockplus.AdblockPlusSafari Failed to create promise. Host info: host: 'Client641', ip: 'fe80:0:0:0:18b4:d9ba:1e92:bc37%en0' Build info: version: '4.26.0', revision: '8ccf0219d7' System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '26.0', java.version: '22.0.2' Driver info: io.appium.java_client.ios.IOSDriver Command: [null, newSession {capabilities=[Capabilities {appium:app: /Users/n.bhadoria/IdeaProje..., appium:automationName: XCUITest, appium:deviceName: iPhone 16

Our app has absolutely no integration with DiDi login. We only integrate WeChat, QQ, carrier, and Apple ID login, and all related login entry icons are local resources. On an iPhone 16 Pro Max device with iOS system version 18.7, there was one isolated incident where the Apple ID login entry icon mysteriously changed to the DiDi app icon. What could be the possible iOS system-level causes for this?

The app I'm developing is experiencing the following watch dog crash issue. This issue appears to be internal to the OS. Incident Identifier: 989945DB-39FA-45B7-B659-764B8DAF5166 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-23 10:28:24.4515 +0900 Launch Time: 2025-09-23 10:23:28.3571 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 :340 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( Elapsed total CPU time (seconds): 14.700 (user 4.730, system 9.970), 22% CPU, Elapsed application

I'm having a watchdog crash issue in the app I'm developing, and it seems to be occurring from inside the combine module. Incident Identifier: 498E4709-01D9-4334-8218-4F5CAB99B504 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-22 10:55:30.4415 +0900 Launch Time: 2025-09-22 10:34:41.0221 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001a4459c38 Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [4209] Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 Combine 0x1a4459c38 Publishers.Catch.Inner.receivePre(_:) + 284 1 Combine 0x1a4459b10 Publishers.Catch.Inner.UncaughtS.receive(_:) + 24 2 MyApp 0x10cda

The app I'm developing is experiencing the following watch dog crash issue. This issue appears to be internal to the OS. Incident Identifier: 989945DB-39FA-45B7-B659-764B8DAF5166 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-23 10:28:24.4515 +0900 Launch Time: 2025-09-23 10:23:28.3571 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 :340 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( Elapsed total CPU time (seconds): 14.700 (user 4.730, system 9.970), 22% CPU, Elapsed application

Hi I experience this problem after update to the newest developer beta software on my iphone 17 pro: blackmagic camera said storage full although it is not final cut camera said close and open the app again It still works with prores (not raw). Anyone has the same problem as mine? I did try uninstall and reinstall the app and also restart the phone, try using different external ssd drive but nothing works.