My game opens up find on the first playthrough. I can play on every map and level and everything is fine. However after closing out the app and going back in everything map/level crashes when I try to load into it. This also happens sometimes when I’m on the app for to long. Clearing the data for the app and restarting fixes the issue. What’s going on with my app is it using up to much ram? My app is made with ue5 and is on iOS 17.

I recently upgraded my iPhone 13 PM to iOS 18 Dev Beta 4 and iPhone 11 PM to iOS 18 Public Beta 1 and now my Mac (on Sequoia 15 Beta) with Xcode 16 Beta 4 won't connect to my iPhone to build apps to. The iPhones won't even show up in the Devices and Simulators view. It shows up in Finder fine, though. I have already tried Clearing Trusted Computers from the phones and also unpairing the devices through Xcode, and now it won't even show up (previously it was telling me to enable developer mode on my iPhone which I already had, and I also disabled and enabled it several times to make sure it wasn't the issue) my iPad on iPadOS 18.1 Beta also won't connect and also upgrading my Mac to MacOS Sequoia 15.1 Beta didn't help. I was browsing the forums the other day and noticed that someone said you need to have the same exact build of iOS on the Xcode simulator runtime you have installed as the phone you are attempting to connect to, and I noticed a discrepancy between the versions: Simulator: iOS 18.0 beta 4 (22A5316f) SDK + iOS 18.0 beta 4 (22A5316j) Simulator iPhone 1: iOS 18.0 Beta 4 (22A5316k) iPhone 2: iOS 18.0 Public Beta 1 (22A5307i) iPad: iPadOS 18.1 Beta 1 (22B5007p) The newest simulator runtime seems to be older than the iOS versions on my phones. What should I do? I don't even know if this is the issue though, so I would like help in any way possible. Thank you so much everyone!

Hello everyone, I was wondering if I downgrade my iPhone to iOS 18 developer beta 1 from developer beta 4 (rereleased) version, what will happen to my Apple Watch Series 6 running watchOS 11 beta 4? I seen people say that their Apple Watches unpaired and they could not pair them again when the iPhone is downgraded from 18 beta to 17.5.1. Though it is within the same iOS version in question, will I still need to get my Apple Watch downgraded as well if I use an IPSW containing the 1st developer beta of iOS 18?

When I try and run my app on my phone (iPhone 14 iOS version 17.5.1) in XCode 15.4 I get the following: Previous preparation error: The developer disk image could not be mounted on this device.. You don’t have permission to save the file “DADFD0D2-1ED9-4F56-AAAE-310E8BF60870” in the folder “CoreDevice_DDI_Staging_503”. Domain: com.apple.dt.deviceprep Code: -10 Recovery Suggestion: Previous preparation error: The developer disk image could not be mounted on this device.. You don’t have permission to save the file “DADFD0D2-1ED9-4F56-AAAE-310E8BF60870” in the folder “CoreDevice_DDI_Staging_503”. User Info: { DVTRecoveryBlockKey = "<NSMallocBlock: 0x600010ba62b0>"; NSLocalizedRecoveryOptions = ( Cancel ); NSRecoveryAttempter = "<_DVTErrorRecoveryHandler: 0x6000586d8530>"; } System Information macOS Version 14.5 (Build 23F79) Xcode 15.4 (22622) (Build 15F31d) Timestamp: 2024-07-29T19:05:07-07:00

My device constantly restarts with ISO 18 beta 3, as well as 1 and 2, which makes it practically impossible to operate the device.

Hi, I'm seeking assistance with finding the correct version of Xcode to test an emulator running iOS 17.5.1 for the iPhone 14 Pro and iPad Air (5th Generation). I am experiencing issues with publishing my app to the App Store and receiving a Guideline 2.1 rejection. Although the app functions correctly on TestFlight and other devices, it crashes (white screen) when opened on the specified device and iOS version. I have tested the app on multiple devices, and it works fine on those, but the Apple review team has reported crashes specifically on the aforementioned device and iOS version. Could someone guide me on how to resolve this or direct me to the appropriate XCode version for testing? Thank you for your help.

Hello, I am testing Configuration Profiles' Passcode policy in an MDM environment. After setting the 'maxFailedAttempts' property to 5 and deploying the Passcode payload via MDM to iPhones, some iPhones are not wiped after exceeding 5 failed passcode attempts. Could you please advise on the possible reasons for this issue? Devices affected: iPhone 11 (iOS 16.4.1), iPhone 12 mini (iOS 16.5).

With iOS 18 there are now five ways for a caller to be blocked/silenced: the caller can be blocked via the Live Caller ID extension the caller can be blocked via the Call Kit extension the caller can be blocked via Block Caller via the call history recents the call could be silenced via Silence Junk Callers the call could be silenced via Silence Unknown Callers These are all totally separate and there's no way of reconciling all of them and presenting a holistic overview and management system to the user. Call blocking applications have no way of knowing which numbers will be blocked by 3) or silenced by 4) or 5), or even of determining 4) and 5) are enabled. And iOS doesn't indicate to users what will be blocked by 1) or 2). Currently users have no way of knowing what's been blocked/silenced where. Neither via call blocking apps nor via the OS. From users' perspectives its a confusing and frustrating mess. If the OS exposed which numbers have been blocked via 3) to applications and exposed if Silence Unknown Callers and Silence Junk Callers are enabled then call blocking applications could present a unified way for users to see and manage what's going on with their device holistically.

I'm working on a mobile app that keeps crashing on launch since updating to iOS 18 Beta 3 and 4. The splash screen is shown and afterwards the app is crashing. The stack trace is very general and it's very hard to pinpoint where it's going wrong. Does someone experience the same behavior? The app was working on iOS 18 Beta 2. In the stack trace you can see that is goes wrong at OurObject. This is an object that inherits from UIStackView. Background information .NET8.0 iOS MVVMCross Stacktrace 2024-07-24 09:29:05.110 ***.iOS[9804:731403] Unhandled managed exception: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[OurObject initWithCoder:]: unrecognized selector sent to instance 0x300bb2ec0 Native stack trace: 0 CoreFoundation 0x000000019f0ba098 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 540824 1 libobjc.A.dylib 0x000000019c3c2698 objc_exception_throw + 76 2 CoreFoundation 0x000000019f1bf810 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 1611792 3 CoreFoundation 0x000000019f057728 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 137000 4 CoreFoundation 0x000000019f057050 _CF_forwarding_prep_0 + 96 5 UIKitCore 0x00000001a1b89308 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3756808 6 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 7 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 8 UIKitCore 0x00000001a1b85ec4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3743428 9 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 10 UIFoundation 0x00000001aab3b0bc D893DC98-0766-3DA9-BDD8-73614C11B808 + 82108 11 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 12 UIKitCore 0x00000001a1b894b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3757236 13 UIKitCore 0x00000001a1c6aa48 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4680264 14 UIKitCore 0x00000001a19836c4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1636036 15 UIKitCore 0x00000001a184c49c D2E47210-1C46-3CA7-BBC2-35021B146A13 + 361628 16 UIKitCore 0x00000001a226c7a8 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10979240 17 UIKitCore 0x00000001a226cc20 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10980384 18 UIKitCore 0x00000001a2a5baa0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 19298976 19 UIKitCore 0x00000001a194b590 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1406352 20 UIKitCore 0x00000001a1bf2ab4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4188852 21 UIKitCore 0x00000001a18047b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 67508 22 QuartzCore 0x00000001a0b3a6d8 EC26DDF2-2731-3CF2-A310-543557961180 + 489176 23 QuartzCore 0x00000001a0b3a264 EC26DDF2-2731-3CF2-A310-543557961180 + 488036 24 QuartzCore 0x00000001a0b92edc EC26DDF2-2731-3CF2-A310-543557961180 + 851676 25 QuartzCore 0x00000001a0b10560 EC26DDF2-2731-3CF2-A310-543557961180 + 316768 26 UIKitCore 0x00000001a19a95f0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1791472 27 CoreFoundation 0x000000019f09c218 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 418328 28 CoreFoundation 0x000000019f08a4c0 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 345280 29 CoreFoundation 0x000000019f089b84 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 342916 30 CoreFoundation 0x000000019f089368 CFRunLoopRunSpecific + 572 31 GraphicsServices 0x00000001eb27c1c4 GSEventRunModal + 164 32 UIKitCore 0x00000001a1bd69b0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4073904 33 UIKitCore 0x00000001a1c84d54 UIApplicationMain + 340 34 ***.iOS 0x0000000102fdc5f4 xamarin_UIApplicationMain + 60 35 ***.iOS 0x000000010332f340 do_icall + 316 36 ***.iOS 0x000000010332dc40 do_icall_wrapper + 348 37 ***.iOS 0x000000010332264c mono_interp_exec_method + 2784 38 ***.iOS 0x0000000103320218 interp_runtime_invoke + 236 39 ***.iOS 0x00000001032eee9c mono_jit_runtime_invoke + 1116 40 ***.iOS 0x0000000103296600 mono_runtime_invoke_checked + 148 41 ***.iOS 0x000000010329c8fc mono_runtime_exec_main_checked + 116 42 ***.iOS 0x00000001032f449c mono_jit_exec + 356 43 ***.iOS 0x0000000103008ffc xamarin_main + 2336 44 ***.iOS 0x00000001033e7874 main + 64 45 dyld 0x00000001c52c4734 94AF19E0-4F2A-332F-A08C-04B9B7CB6FAC + 210740 (ObjCRuntime.ObjCException) at ObjCRuntime.Runtime.ThrowException(IntPtr gchandle) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/ObjCRuntime/Runtime.cs:line 2594 at UIKit.UIApplication.UIApplicationMain(Int32 argc, String[] argv, IntPtr principalClassName, IntPtr delegateClassName) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 60 at UIKit.UIApplication.Main(String[] args, Type principalClass, Type delegateClass) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 94 at ***.iOS.Application.Main(String[] args) in /Users/***/***/***/sources/iOS/Main.cs:line 7 Question for the administrators: Can you remove my previous post from July 16?

Throughout the IOS 18 update feature, my iPhone has been working extraordinary well and there seems to be no issues with the update for the latest gen iPhones/apple products. The only issue I’ve experienced these few months include the torch feature. after the IOS 18 Beta Version 3 dropped, my iPhone seems to have problems when it comes to turning the torch on. It mostly bugs out, like when i turn the torch on, it turns on for a split second and immediatly turns off again. It seems as though now my IPhone 14 Pro Max is unable to run the torch feature. Even after the Version 4 of Beta IOS 18, my iPhone is still unable to run the flashlight and it does the same thing since the last version for now.

Hi Everyone, Our app crashes in real device with the following error but works in simulator. Please suggest. We are using iOS 17 in device and xcode 15.4 Date/Time: 2024-06-21 11:41:41.4618 -0500 Launch Time: 2024-06-21 11:41:41.1161 -0500 Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$s8SAPFiori27FUISegmentedControlFormCellC15reuseIdentifierSSvgZTj Referenced from: &lt;05282F21-2C2D-3AE6-B45B-251164285297&gt; /Volumes/VOLUME//AssetManagerVDP.app/Frameworks/MapFramework.framework/MapFramework Expected in: /Volumes/VOLUME//AssetManagerVDP.app/Frameworks/SAPFiori.framework/SAPFiori (terminated at launch; ignore backtrace) Triggered by Thread: 0 Thread 0 Crashed: 0 dyld 0x1b8275e90 __abort_with_payload + 8 1 dyld 0x1b827e0e4 abort_with_payload_wrapper_internal + 104 2 dyld 0x1b827e118 abort_with_payload + 16 3 dyld 0x1b823c70c dyld4::halt(char const*, dyld4::StructuredError const*) + 304 4 dyld 0x1b820

Ever since I went and upgraded my system to the newest iOS I kept experiencing this and my system becomes unresponsive hence when this spiral black screen occurs all my apps freeze and then stop working after it ends and the icons don't show for the app for a few seconds. I am on my iPhone 13 Pro Max and it has 1tb of storage. I wanted to ask is there any way I can fix this, I’ve been having a black screen every day since iOS 15 it was only at least once a day. Now it’s every few minutes.

Hello, I am trying to submit my app to the app store and I want to make sure that my app is only installed by iPhones with a true depth camera. I have tried including the "iPhone / iPad Minimum Performance A12" in the the minimum required devices capabilities tab in info.plist but it seems to not work. I can still open my app with a phone that does not have the true depth camera. Is there a way of setting the minimum requirement to have the true depth camera through the info.plist or can I also hard code it in my app?. Your assistance is greatly appreciated.

I just downloaded iOS 18 beta public and was able to customize my apps on one of my profiles. But when I went to one of my other Lockscreen/Homescreen profiles the apps where the same color as the original profile.

On iOS 18 public beta, user issues with photo quality being degraded when taken in the camera app and getting error message of failing to produce high resolution image.

I didn’t back up my phone and now I want to update from IOS 18 Developer Beta to IOS 18 Public Beta. Will my information (apps, data, etc..) stay intact? Or will it be erased?

For some reason since I’ve downloaded iOS 18e etc I have noticed my phone has gone from 256gb to 255gb. Wonder why?

"bug_type":"210","timestamp":"2024-06-01 14:21:43.00 +0400","os_version":"iPhone OS 16.7.4 (20H240)","roots_installed":0,"incident_id":"2D658 A3E-807D-4239-A262-1560CDB5A77F"} { "build" : "iPhone OS 16.7.4 (20H240)", "product" : "iPhone10,6", "socId" : "8015", "socRevision" : "11", "incident" : "2D658A3E-807D-4239-A262-1560CDB5A77F", "crashReporterKey" : "b9deae4c29b808d36d6d04c34edc95561cd25808", "kernel" : "Darwin Kernel Version 22.6.0: Tue Nov 7 21:41:17 PST 2023; root:xnu-8796.142.1.702.91/RELEASE_ARM64_T8015", "date" : "2024-06-01 14:21:43.37 +0400", "panicString" : "panic(cpu 2 caller 0xfffffff01d52a4fc): userspace watchdog timeout: no successful checkins from thermalmonitord\nservice returned not alive with context : is_alive_func returned unhealthy : current 7fffffffeff, mask 67fffffffff, expected 67fffffffff. SD: 0 BC: 0 RC: 0 BS: 0, Missing sensor(s): TP0Z \nservice: backboardd, total successful checkins in 225 seconds: 17, last successful checkin: 0 seconds ago\nservice: SpringBoard, total successful checkins in 176 seconds: 15, last successful checkin: 0 seconds ago\nservice: mediaserverd, total successful checkins in 225 seconds: 17, last successful checkin: 0 seconds ago\nservice: logd, total successful checkins in 225 seconds: 19, last successful checkin: 0 seconds ago\nservice: thermalmonitord, no successful checkins in 225 seconds\nservice: runningboardd, total successful checkins in 225 seconds: 19, last successful checkin: 0 seconds ago\nservice: wifid, total successful checkins in 225 seconds: 19, last successful checkin: 0 seconds ago\nservice: configd, total successful checkins in 225 seconds: 18, last successful checkin: 0 seco\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 20H240\nKernel version: Darwin Kernel Version 22.6.0: Tue Nov 7 21:41:17 PST 2023; root:xnu-8796.142.1.702.91/RELEASE_ARM64_T8015\nKernelCache UUID: 52E07559182379151E59E4DE1C565312\nKernel UUID: C5429369-571A-3EAE-9CFB-8985A9637045\nBoot session UUID: 2D658A3E-807D-4239-A262-1560CDB5A77F\niBoot version: iBoot-8422.142.2.700.1\nsecure boot?: YES\nroots installed: 0\nPaniclog version: 14\nKernel slide: 0x0000000016954000\nKernel text base: 0xfffffff01d958000\nmach_absolute_time: 0x142240dd9\nEpoch Time: sec usec\n Boot : 0x665adb4d 0x00079646\n Sleep : 0x665af29e 0x00084228\n Wake : 0x665af60f 0x0008bd33\n Calendar: 0x665af616 0x0000b21a\n\nZone info:\n Zone map: 0xffffffdc007dc000 - 0xffffffe20

What is the latest IOS beta developer out

One week before I encountered the problem, I excitedly installed the beta version of iOS 18 to my iPhone XR. Little did I know that that was the beginning of a nightmare for me. A week or so after the installment, my iPhone's screen suddenly went black and in a few seconds into a process that I found other people have described as a boot loop. This means that my iPhone will attempt to start by getting into the logo screen but then either will it start just for a few seconds before it turns off again or will it just go off. and then the process is repeated again and again. I found that this seems to be a common problem for many people out there who also installed the beta version of this software. I also tried to get help in an Apple Store but they just said that my phone was dead and there was nothing they could do. This is just outrageous! Can't believe that a company as rich as Apple will just release software with this kind of deleterious bugs out there and won't try to help their clients after such a huge mess the cause. Will never buy an iPhone again. You should really try to do better.