Search results for

“iPhone 16 pro”

80,715 results found

Post

Replies

Boosts

Views

Activity

Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
5
0
217
2w
Mac Assigning NSManagedObject to NSPersistentStore
Hello, I have a iOS app I was looking at porting to Mac. I'm having an issue with both the Mac (Designed for iPad) and Mac Catalyst Destinations. I can't test Mac due to too many build issues. I'm trying to assign a new NSManagedObject into a NSPersistentStore. let object = MyObject(context: context) context.assign(object, to: nsPersistentStore) This works fine for iOS/iOS Simulator/iPhone/iPad. But on the Mac it's crashing with FAULT: NSInvalidArgumentException: Can't assign an object to a store that does not contain the object's entity.; { Thread 1: Can't assign an object to a store that does not contain the object's entity.
6
0
259
3w
When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
This is the full logging: libsystem_kernel.dylib`__pthread_kill: 0x2502f71c8 <+0>: mov x16, #0x148 ; =328 0x2502f71cc <+4>: svc #0x80 -> 0x2502f71d0 <+8>: b.lo 0x2502f71f0 ; <+40> 0x2502f71d4 <+12>: pacibsp 0x2502f71d8 <+16>: stp x29, x30, [sp, #-0x10]! 0x2502f71dc <+20>: mov x29, sp 0x2502f71e0 <+24>: bl 0x2502f2900 ; cerror_nocancel 0x2502f71e4 <+28>: mov sp, x29 0x2502f71e8 <+32>: ldp x29, x30, [sp], #0x10 0x2502f71ec <+36>: retab 0x2502f71f0 <+40>: ret
5
0
102
3w
TestFlight install fails with “The requested app is not available or doesn’t exist” after successful upload (Flutter app)
Hello, I’m facing an issue installing my app from TestFlight on a physical iPhone device. App & Environment App: Desi Charades Framework: Flutter Distribution: TestFlight Build status: Upload completed Device: iPhone 7+ iOS version: 15.6 Tester type: Internal Apple Developer Program: Paid account Issue Description After uploading a build successfully to App Store Connect and adding it to TestFlight, the app appears in TestFlight with the Install button. However, when I tap Install, I receive the following error on the device: “Could not install Desi Charades App. The requested app is not available or doesn’t exist.” The build is visible in TestFlight, but installation fails immediately. Upload Warnings During archive upload, App Store Connect shows the following warnings: Upload Symbols Failed The archive did not include a dSYM for: ffmpegkit.framework libavcodec.framework libavdevice.framework The app uses ffmpeg-kit (Flutter plugin), which ships precompiled frameworks. Steps Already Ch
1
0
246
3w
Latest Beta Version Breaks Xcode Testing Builds on Physical devices.
This is a grave issue I am facing while testing my apps on my personal device. This is the error I seem to be getting: The application could not be launched because the Developer App Certificate is not trusted. And on the phone side, this is the message: Unable to Verify App. An internet connection is required to verify the trust of the developer Apple Development... Before I receive any recommendations, such as deleting Xcode or restarting my device, I would like to clarify that I have already taken all necessary precautions. The application I was testing appeared to function correctly in the morning a few hours prior to the update. However, after upgrading to the latest beta builds, iOS 26.4 beta and the latest macOS beta, this issue has become a recurring problem. I would greatly appreciate your assistance in resolving this matter, as it is of utmost importance to me.
2
0
110
3w
RealityKit - Full 3D experience
I have a question I guess more for the Apple team. But why are there no totally 3D experiences for the Vision Pro lineup? I know they have given us tools to implement unity 3D games into iPhone and I guess you can also build it in RealityKit. But why at this moment are 3D games limited to just iPad and iPhone and can't you bring that into Vision Pro? Just to explain. When I say a totally 3D game, I mean games like Gorn. I mean the Vision Pro is definitely powerful enough, but it just feels limited to tabletop games and AR games. Is this something Apple is thinking about implementing?
1
0
1.4k
3w
Reply to RealityKit - Full 3D experience
Thought I'd just post this here for future readers, but Apple has been trying to push more in this direction with Unity. https://developer.apple.com/visionos/ Article: https://www.apple.com/za/newsroom/2025/06/visionos-26-introduces-powerful-new-spatial-experiences-for-apple-vision-pro/
Topic: Graphics & Games SubTopic: RealityKit Tags:
3w
Reply to App group broken on Sequoia
OK, I've successfully changed the app group to iOS style (group.com.myorg.MyApp)... and it hasn't fixed the problem. It's working on older versions, but still failing on Sequoia. To confirm: Both the main app and extension have an explicit app ID (com.myorg.MyApp and com.myorg.MyApp.EMPFileProvider, respectively). I have added an App Group identifier on the website for group.com.myorg.MyApp -- the website won't let me add one in the old macOS format (I understand this is normal). On the website, in the Identifier entry for each component, I've added group.com.myorg.MyApp to the existing App Group set. This has required me to re-generate the provisioning profiles. On the Profiles page, I regenerated the profiles (by choosing Edit and then Save rather than deleting and re-creating them). I downloaded and installed the new profiles. The resulting app works fine on a pre-Sequoia machine. But on the Sequoia one, the main app runs successfully (and can log to the Group Container), and the FileProvider also runs, bu
Topic: Code Signing SubTopic: Entitlements Tags:
3w
Reply to Is this normal while developing an app on the watch?
Developing on the watch is stupid fragile. Seriously. XCode needs to set up a secure tunnel to the watch using wifi but the watch regularly turns off or looses its wifi. There is so much magic here that like I said, embarassing to the watch team at apple. Here are options that work for me: The watch will often disconnect from the router even though it is on. My first solution is to go into Settings -> WiFi and make sure it is connected to the router. This works about 70% of the time. If it doesnt, you can try toggling developer mode on the watch to get to the Trust Computer which sometimes works. Turn on your hotspot on your phone, then connect your mac and your watch to it and hope this works. You have about a 50% chance here. If your home network is a mesh network, then make sure that the APs have handed off so that all the devices are on the same AP. I can not prove this other than through observation. So yes, turn on and off the wifi on all the devices. Supposedly, you can actually turn on you
3w
Is this normal while developing an app on the watch?
I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical Why This error message reveals that the iss
8
0
662
3w
Reply to Is this normal while developing an app on the watch?
Well here we are and I have encountered the same Issue. Disconnected the watch from Xcode, rebooted Xcode, rebooted the phone, the watch and everything else connected to the Mac. For some odd reason the watch re-paired to Xcode and initially there was a message on the Devices and Simulators saying that there was something wrong with the Tunnel (I've probably got that wrong but it was not happy) but then inexplicably the message Copying blah blah blah appeared in the Xcode devices window so now I am just waiting for that to finish. I'm now about an hour into this palaver and hopeful that I can finally update my App.
3w
cannot run app on external iPhone
I changed something with Bundle Identifier... since then I cannot trust the certificate anymore on iPhone. It just won't show up. I reinstalled new profile, new bundle id, completely reinstalled iPhone... created new certificates, downloaded... nothing... I thinks it needs internet connection, but connection works just fine Unable to Verify App An internet connection is required to verify trust of the developer Apple Development: My Name (22YBQVQJZK). This app will not be available until verified. this makes me crazy.. I lost like 5 hours on this.. still it does not work... Apple Intelligence tried like everything .. didn't help
1
0
56
3w
Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
Replies
5
Boosts
0
Views
217
Activity
2w
Mac Assigning NSManagedObject to NSPersistentStore
Hello, I have a iOS app I was looking at porting to Mac. I'm having an issue with both the Mac (Designed for iPad) and Mac Catalyst Destinations. I can't test Mac due to too many build issues. I'm trying to assign a new NSManagedObject into a NSPersistentStore. let object = MyObject(context: context) context.assign(object, to: nsPersistentStore) This works fine for iOS/iOS Simulator/iPhone/iPad. But on the Mac it's crashing with FAULT: NSInvalidArgumentException: Can't assign an object to a store that does not contain the object's entity.; { Thread 1: Can't assign an object to a store that does not contain the object's entity.
Replies
6
Boosts
0
Views
259
Activity
3w
When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
This is the full logging: libsystem_kernel.dylib`__pthread_kill: 0x2502f71c8 <+0>: mov x16, #0x148 ; =328 0x2502f71cc <+4>: svc #0x80 -> 0x2502f71d0 <+8>: b.lo 0x2502f71f0 ; <+40> 0x2502f71d4 <+12>: pacibsp 0x2502f71d8 <+16>: stp x29, x30, [sp, #-0x10]! 0x2502f71dc <+20>: mov x29, sp 0x2502f71e0 <+24>: bl 0x2502f2900 ; cerror_nocancel 0x2502f71e4 <+28>: mov sp, x29 0x2502f71e8 <+32>: ldp x29, x30, [sp], #0x10 0x2502f71ec <+36>: retab 0x2502f71f0 <+40>: ret
Replies
5
Boosts
0
Views
102
Activity
3w
TestFlight install fails with “The requested app is not available or doesn’t exist” after successful upload (Flutter app)
Hello, I’m facing an issue installing my app from TestFlight on a physical iPhone device. App & Environment App: Desi Charades Framework: Flutter Distribution: TestFlight Build status: Upload completed Device: iPhone 7+ iOS version: 15.6 Tester type: Internal Apple Developer Program: Paid account Issue Description After uploading a build successfully to App Store Connect and adding it to TestFlight, the app appears in TestFlight with the Install button. However, when I tap Install, I receive the following error on the device: “Could not install Desi Charades App. The requested app is not available or doesn’t exist.” The build is visible in TestFlight, but installation fails immediately. Upload Warnings During archive upload, App Store Connect shows the following warnings: Upload Symbols Failed The archive did not include a dSYM for: ffmpegkit.framework libavcodec.framework libavdevice.framework The app uses ffmpeg-kit (Flutter plugin), which ships precompiled frameworks. Steps Already Ch
Replies
1
Boosts
0
Views
246
Activity
3w
Reply to MacOS 26.4 beta “Failed to prepare software update”
I am reciving the same issue on my m1 pro (MK183LL/A).
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
3w
Latest Beta Version Breaks Xcode Testing Builds on Physical devices.
This is a grave issue I am facing while testing my apps on my personal device. This is the error I seem to be getting: The application could not be launched because the Developer App Certificate is not trusted. And on the phone side, this is the message: Unable to Verify App. An internet connection is required to verify the trust of the developer Apple Development... Before I receive any recommendations, such as deleting Xcode or restarting my device, I would like to clarify that I have already taken all necessary precautions. The application I was testing appeared to function correctly in the morning a few hours prior to the update. However, after upgrading to the latest beta builds, iOS 26.4 beta and the latest macOS beta, this issue has become a recurring problem. I would greatly appreciate your assistance in resolving this matter, as it is of utmost importance to me.
Replies
2
Boosts
0
Views
110
Activity
3w
RealityKit - Full 3D experience
I have a question I guess more for the Apple team. But why are there no totally 3D experiences for the Vision Pro lineup? I know they have given us tools to implement unity 3D games into iPhone and I guess you can also build it in RealityKit. But why at this moment are 3D games limited to just iPad and iPhone and can't you bring that into Vision Pro? Just to explain. When I say a totally 3D game, I mean games like Gorn. I mean the Vision Pro is definitely powerful enough, but it just feels limited to tabletop games and AR games. Is this something Apple is thinking about implementing?
Replies
1
Boosts
0
Views
1.4k
Activity
3w
Reply to RealityKit - Full 3D experience
Thought I'd just post this here for future readers, but Apple has been trying to push more in this direction with Unity. https://developer.apple.com/visionos/ Article: https://www.apple.com/za/newsroom/2025/06/visionos-26-introduces-powerful-new-spatial-experiences-for-apple-vision-pro/
Topic: Graphics & Games SubTopic: RealityKit Tags:
Replies
Boosts
Views
Activity
3w
Reply to App group broken on Sequoia
OK, I've successfully changed the app group to iOS style (group.com.myorg.MyApp)... and it hasn't fixed the problem. It's working on older versions, but still failing on Sequoia. To confirm: Both the main app and extension have an explicit app ID (com.myorg.MyApp and com.myorg.MyApp.EMPFileProvider, respectively). I have added an App Group identifier on the website for group.com.myorg.MyApp -- the website won't let me add one in the old macOS format (I understand this is normal). On the website, in the Identifier entry for each component, I've added group.com.myorg.MyApp to the existing App Group set. This has required me to re-generate the provisioning profiles. On the Profiles page, I regenerated the profiles (by choosing Edit and then Save rather than deleting and re-creating them). I downloaded and installed the new profiles. The resulting app works fine on a pre-Sequoia machine. But on the Sequoia one, the main app runs successfully (and can log to the Group Container), and the FileProvider also runs, bu
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
3w
Reply to Is this normal while developing an app on the watch?
Developing on the watch is stupid fragile. Seriously. XCode needs to set up a secure tunnel to the watch using wifi but the watch regularly turns off or looses its wifi. There is so much magic here that like I said, embarassing to the watch team at apple. Here are options that work for me: The watch will often disconnect from the router even though it is on. My first solution is to go into Settings -> WiFi and make sure it is connected to the router. This works about 70% of the time. If it doesnt, you can try toggling developer mode on the watch to get to the Trust Computer which sometimes works. Turn on your hotspot on your phone, then connect your mac and your watch to it and hope this works. You have about a 50% chance here. If your home network is a mesh network, then make sure that the APs have handed off so that all the devices are on the same AP. I can not prove this other than through observation. So yes, turn on and off the wifi on all the devices. Supposedly, you can actually turn on you
Replies
Boosts
Views
Activity
3w
Is this normal while developing an app on the watch?
I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical Why This error message reveals that the iss
Replies
8
Boosts
0
Views
662
Activity
3w
Reply to Is this normal while developing an app on the watch?
Well here we are and I have encountered the same Issue. Disconnected the watch from Xcode, rebooted Xcode, rebooted the phone, the watch and everything else connected to the Mac. For some odd reason the watch re-paired to Xcode and initially there was a message on the Devices and Simulators saying that there was something wrong with the Tunnel (I've probably got that wrong but it was not happy) but then inexplicably the message Copying blah blah blah appeared in the Xcode devices window so now I am just waiting for that to finish. I'm now about an hour into this palaver and hopeful that I can finally update my App.
Replies
Boosts
Views
Activity
3w
cannot run app on external iPhone
I changed something with Bundle Identifier... since then I cannot trust the certificate anymore on iPhone. It just won't show up. I reinstalled new profile, new bundle id, completely reinstalled iPhone... created new certificates, downloaded... nothing... I thinks it needs internet connection, but connection works just fine Unable to Verify App An internet connection is required to verify trust of the developer Apple Development: My Name (22YBQVQJZK). This app will not be available until verified. this makes me crazy.. I lost like 5 hours on this.. still it does not work... Apple Intelligence tried like everything .. didn't help
Replies
1
Boosts
0
Views
56
Activity
3w
Reply to "Unable to verify app" cannot verify trust of developer
I have the same issue. I reinstalled the Application, checked all Targets , Unadded and added my Dev Profil, turned Devmode on and off on my iPhone, deleted Derivated Files . cleaned the Project and tried it with Wifi Off+Cellular. I personally thing its due to a malfunction of a server. The appllications all work on the Simulator
Replies
Boosts
Views
Activity
3w
Reply to ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device
Same here on Vision Pro. Reinstalled everything on a clean headset with same results: “This app can't run and must be verified.” Lost 4 hours!!
Replies
Boosts
Views
Activity
3w