Search results for

“iPhone 16 pro”

80,716 results found

Post

Replies

Boosts

Views

Activity

Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK
Topic: App & System Services SubTopic: Drivers Tags:
3w
Reply to LaunchAgent (Mac) as peripheral doesn't show a pairing request.
Hi @pnelson, this is Argun, Quinn's Bluetooth colleague (while I don't have a transceiver in my head, it is not for lack of trying) I have been discussing your issue with the Bluetooth team, and while we are not dismissing the possibility of a bug, it is possible that the pairing process in different app contexts are behaving differently. Except we are not able to understand what exactly the conditions are when your app works, and when it doesn't, and when it gets the one error, and when it gets the other. There are also other conditions that might effect the issue, like whether both the Mac and the phone are logged in to the same iCloud account or not (changes pairing details) To that end, we would like some more info with a sample app, and exact repro steps, and some logs. So, first please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for macOS and iOS to install a logging profile on each of your devices. Then, once the logging profile
3w
Foundation models not detectable in Xcode simulator
I'm building an app which runs around the Foundation model framework. My expected output is generated when testing on a real device or in preview in Xcode but it throws Foundation Model error when I try running it on the simulator. I'm using a Macbook M1 air and have apple intelligence turned on and my simulator run destination is also an iPad Pro M5 (26.0). Any solution for this as this is my submission for the SSC so I need to make it work on the simulator iPad. Thank you👾
6
0
438
3w
Reply to Foundation models not detectable in Xcode simulator
I'm seeing a similar issue as well. Seems like the Foundation model is just not available for iPhone and iPad simulators anymore. To test it out I created a simple playground (similar to https://developer.apple.com/events/resources/code-along-205/) and just used basic code: import FoundationModels import Playgrounds #Playground { // Create a new session with the language model. let session = LanguageModelSession() // Asynchronously generate a response from a text prompt. let response = try await session.respond(to: Generate a 3-day itinerary to Paris.) } For macOS simulator it works, but for iPhone and iPad simulators it gives either error: Apple Intelligence is not enabled. The operation couldn’t be completed. (FoundationModels.LanguageModelSession.GenerationError error -1.) I've tried Xcode 26.2. 26.3, 26.4 beta 1 & 2 versions. iPhone Simulators 26.2, 26.3 and 26.4 beta and none of them works. This is on a M4 Macbook pro I also have an old M1 Macbook pro I ha
3w
Problems with iPad Pro M4 13 inch
We have an iOS/iPadOS (mixed use of UIKit/SwiftUI) app on the App Store since a couple of years. Over the last month or so, we are receiving many user reports complaining about app freezing and behaving very bad generally. The common denominator for all of these users (~10) is that they are using iPad Pro M4, 13 inch, and they are on at least iPadOS 26.2 - some have updated to 26.2.1, 26.3 etc but the problems remain. Some of the users say that they were using our app normally, until the release of 26.2, or perhaps 26.2.1, from when the problems seem to have started. Some report the problems that go away when they use another WiFi, or when they hold the device in portrait mode (it seems that many complaints seem to suggest that the problem is in when holding the device in landscape). Other say the app works fine if they start it without network enabled, and after enabling network, continue in the app. While we currently do not have an iPad Pro M4 13 inch to test with, we haven't been able to
3
0
253
4w
Rosetta 2 Deadlock on M4 Pro
Rosetta 2 Deadlock on M4 Pro January 2026 Blizzard update causes a deadlock in Rosetta 2 on M4 chips. CodeWeavers (the developer of CrossOver) has analyzed the issue and identified it as a Rosetta translation failure, not a CrossOver application-level bug. Hardware: M4 Pro Mac Book Pro System: Tahoe 26.2 Impacted Software: CrossOver 25.1.1 Diablo II: Resurrected
17
0
3.7k
4w
Frequent System Reboots (bug_type 210) on MacBook Pro with M4 Pro during Emulation Development
Environment: Device: MacBook Pro (Mac16,7) Chip: M4 Pro (SoC ID 6040, Revision 11) OS: macOS 15.2 (24C101) Kernel: Darwin Kernel Version 24.2.0; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 Summary: I am developing a Windows emulator on the MacBook Pro M4 Pro platform. During testing with certain applications, the system frequently triggers an instantaneous reboot. This issue appears to be highly specific to the M4 Pro hardware and current OS version. Observation & Diagnostic Challenges: Upon reboot, the system generates a bug_type 210 (SoC Watchdog Reset) report. The panic string indicates: Unexpected SoC (system) watchdog reset occurred after panic diagnostics were completed. The primary difficulty in debugging is that the hardware reset happens so rapidly that the kernel fails to capture a stackshot or any detailed panic trace. We have practically no actionable information from the standard diagnostic reports. However, we did find the following recurring entrie
1
0
239
4w
Reply to Issues with diacritics in filename on iOS when the system main language is not English
The short answer is that I tried everything (I could think of) and everything I tried fails. in the Files app, simple tap on the file: opens QuickLook (iOS 16) or the Preview app (iOS 26) for files without diacritics in their name. Doesn't do anything for files with diacritics (it's like I didn't tap on the file at all). in the Files app, long press on the file to get the contextual menu, scroll to Quick Look (Coup d'œil since I'm still in a non-English language), I get a blank screen that says Document PDF. opening the file using the documents browser from the Preview app (iOS 26) or PDF Viewer (iOS 26, iOS 16): does not display the file (it's like I didn't tap at all). previewing the file from inside the app using UIDocumentInteractionController(url: url).presentPreview(animated: false): blank screen that says Document PDF. opening the file by calling another app from inside the app using an UIActivityViewController: nothing happens on iOS 26, I get the error message (You do not have permi
Topic: App & System Services SubTopic: Core OS Tags:
4w
XCode Update
Hi, I recently updated my Mac to macOS Sequoia 15.7.2, and then updated my Xcode packages right afterward. However, when I try to open Xcode, I receive the message: “You can’t open the application because it is being updated.” I contacted Apple Developer Support (software) by phone and went through their troubleshooting steps, but the issue persists. They confirmed that everything appears fine on their end. In System Settings, both macOS and Xcode show as fully up to date. However, when I manually check in the App Store, it says Xcode needs to be updated. When I press Update, I get the following error: “Xcode could not be installed. Please try again later.” I’m fairly new to Xcode, but it seems there may be an incomplete update or verification loop preventing the installation from finishing properly. Could you please advise on how to resolve this so I can open Xcode again?
1
0
161
4w
BLE characteristic values swapped
Several of my users are reporting on at lest recent and current versions of iOS the value from one characteristic can be swapped with another. Originally I thought this was a library issue but it doesn't happen on Android and now a user with two iPhones using the exact same app and iOS 26.3 on both has the issue on one phone but not the other. I've gone into more detail here which also includes a little data dumping to prove the values between characteristics can be mixed up. https://github.com/dotintent/react-native-ble-plx/issues/1316 One user reported cycling Bluetooth on/off fixed the issue but the latest user says it does not. For the peripheral the services can only change if the device enters firmware update mode (in which case the service UUID is different). Otherwise the characteristics on a service never change. This would make it a strange one to be caching related since the cache should always be correct.
3
0
84
4w
Reply to BLE characteristic values swapped
My initial thought right at the start were it a race condition in (my) code. While I was confident my JavaScript was correct the translation that ReactNative does is under-the-hood and I couldn't validate this directly. This is why I then added additional logging into production to dump the characteristics/values, which proved it was not a race issue (with my code or its translation) but what is coming back from the library or iOS/CoreBluetooth. I then moved onto it being an issue with the react-native library, which is still a possibility, but the odds have reduced somewhat by the behaviour below. What made me increasingly suspect it's an iOS issue is two iPhones, one a 13 and the other a SE (later model) running 26.3 running the same App at the same time try to connect to the peripheral (which supports multiple connections). One iPhone is successful, the other swaps the values between the two characteristics and so fails. I haven't been able to replicate this myself, it's an error in produ
Topic: App & System Services SubTopic: Core OS Tags:
4w
Reply to When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
I added @main to the AppDelegate and the situation changed; now I have: libswiftCore.dylib`swift_willThrow: -> 0x181cb27ec <+0>: pacibsp 0x181cb27f0 <+4>: str x19, [sp, #-0x20]! 0x181cb27f4 <+8>: stp x29, x30, [sp, #0x10] 0x181cb27f8 <+12>: add x29, sp, #0x10 0x181cb27fc <+16>: adrp x8, 429908 0x181cb2800 <+20>: add x8, x8, #0x660 ; _swift_willThrow 0x181cb2804 <+24>: ldapr x8, [x8] 0x181cb2808 <+28>: cbnz x8, 0x181cb2818 ; <+44> 0x181cb280c <+32>: ldp x29, x30, [sp, #0x10] 0x181cb2810 <+36>: ldr x19, [sp], #0x20 0x181cb2814 <+40>: retab 0x181cb2818 <+44>: mov x0, x21 0x181cb281c <+48>: mov x19, x21 0x181cb2820 <+52>: blraaz x8 0x181cb2824 <+56>: mov x21, x19 0x181cb2828 <+60>: b 0x181cb280c ; <+32>
4w
Reply to When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
Ok, I clarify myself a bit. There seems the code lacks an entry point, from another part of the crash log: iPuja`abort_could_not_find_entry_point___debug_dylib: 0x102ab1440 <+0>: stp x29, x30, [sp, #-0x10]! 0x102ab1444 <+4>: mov x29, sp 0x102ab1448 <+8>: bl 0x102ab1620 ; symbol stub for: abort Then it seems it keeps on finding a entry point until it crashes. iPuja`getDebugDylibEntryPoint: 0x102ab05d4 <+0>: sub sp, sp, #0x70 0x102ab05d8 <+4>: stp x26, x25, [sp, #0x20] 0x102ab05dc <+8>: stp x24, x23, [sp, #0x30] 0x102ab05e0 <+12>: stp x22, x21, [sp, #0x40] 0x102ab05e4 <+16>: stp x20, x19, [sp, #0x50] 0x102ab05e8 <+20>: stp x29, x30, [sp, #0x60] 0x102ab05ec <+24>: add x29, sp, #0x60 0x102ab05f0 <+28>: adrp x8, 8 0x102ab05f4 <+32>: ldr x8, [x8, #0x8] 0x102ab05f8 <+36>: ldr x8, [x8] 0x102ab05fc <+40>: str x8, [sp, #0x18] 0x102ab0600 <+44>: adrp x24, 12 0x102ab0604 <+48>: ldrb w8, [x24] 0x102ab0608 <+52>:
4w
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
2
0
142
4w
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
3w
Reply to LaunchAgent (Mac) as peripheral doesn't show a pairing request.
Hi @pnelson, this is Argun, Quinn's Bluetooth colleague (while I don't have a transceiver in my head, it is not for lack of trying) I have been discussing your issue with the Bluetooth team, and while we are not dismissing the possibility of a bug, it is possible that the pairing process in different app contexts are behaving differently. Except we are not able to understand what exactly the conditions are when your app works, and when it doesn't, and when it gets the one error, and when it gets the other. There are also other conditions that might effect the issue, like whether both the Mac and the phone are logged in to the same iCloud account or not (changes pairing details) To that end, we would like some more info with a sample app, and exact repro steps, and some logs. So, first please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for macOS and iOS to install a logging profile on each of your devices. Then, once the logging profile
Replies
Boosts
Views
Activity
3w
Foundation models not detectable in Xcode simulator
I'm building an app which runs around the Foundation model framework. My expected output is generated when testing on a real device or in preview in Xcode but it throws Foundation Model error when I try running it on the simulator. I'm using a Macbook M1 air and have apple intelligence turned on and my simulator run destination is also an iPad Pro M5 (26.0). Any solution for this as this is my submission for the SSC so I need to make it work on the simulator iPad. Thank you👾
Replies
6
Boosts
0
Views
438
Activity
3w
Reply to Foundation models not detectable in Xcode simulator
I'm seeing a similar issue as well. Seems like the Foundation model is just not available for iPhone and iPad simulators anymore. To test it out I created a simple playground (similar to https://developer.apple.com/events/resources/code-along-205/) and just used basic code: import FoundationModels import Playgrounds #Playground { // Create a new session with the language model. let session = LanguageModelSession() // Asynchronously generate a response from a text prompt. let response = try await session.respond(to: Generate a 3-day itinerary to Paris.) } For macOS simulator it works, but for iPhone and iPad simulators it gives either error: Apple Intelligence is not enabled. The operation couldn’t be completed. (FoundationModels.LanguageModelSession.GenerationError error -1.) I've tried Xcode 26.2. 26.3, 26.4 beta 1 & 2 versions. iPhone Simulators 26.2, 26.3 and 26.4 beta and none of them works. This is on a M4 Macbook pro I also have an old M1 Macbook pro I ha
Replies
Boosts
Views
Activity
3w
Problems with iPad Pro M4 13 inch
We have an iOS/iPadOS (mixed use of UIKit/SwiftUI) app on the App Store since a couple of years. Over the last month or so, we are receiving many user reports complaining about app freezing and behaving very bad generally. The common denominator for all of these users (~10) is that they are using iPad Pro M4, 13 inch, and they are on at least iPadOS 26.2 - some have updated to 26.2.1, 26.3 etc but the problems remain. Some of the users say that they were using our app normally, until the release of 26.2, or perhaps 26.2.1, from when the problems seem to have started. Some report the problems that go away when they use another WiFi, or when they hold the device in portrait mode (it seems that many complaints seem to suggest that the problem is in when holding the device in landscape). Other say the app works fine if they start it without network enabled, and after enabling network, continue in the app. While we currently do not have an iPad Pro M4 13 inch to test with, we haven't been able to
Replies
3
Boosts
0
Views
253
Activity
4w
Rosetta 2 Deadlock on M4 Pro
Rosetta 2 Deadlock on M4 Pro January 2026 Blizzard update causes a deadlock in Rosetta 2 on M4 chips. CodeWeavers (the developer of CrossOver) has analyzed the issue and identified it as a Rosetta translation failure, not a CrossOver application-level bug. Hardware: M4 Pro Mac Book Pro System: Tahoe 26.2 Impacted Software: CrossOver 25.1.1 Diablo II: Resurrected
Replies
17
Boosts
0
Views
3.7k
Activity
4w
Reply to Frequent System Reboots (bug_type 210) on MacBook Pro with M4 Pro during Emulation Development
Has anyone encountered similar SoC watchdog reset issues on M4 Pro with macOS 15+? Any help would be appreciated.
Replies
Boosts
Views
Activity
4w
Frequent System Reboots (bug_type 210) on MacBook Pro with M4 Pro during Emulation Development
Environment: Device: MacBook Pro (Mac16,7) Chip: M4 Pro (SoC ID 6040, Revision 11) OS: macOS 15.2 (24C101) Kernel: Darwin Kernel Version 24.2.0; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 Summary: I am developing a Windows emulator on the MacBook Pro M4 Pro platform. During testing with certain applications, the system frequently triggers an instantaneous reboot. This issue appears to be highly specific to the M4 Pro hardware and current OS version. Observation & Diagnostic Challenges: Upon reboot, the system generates a bug_type 210 (SoC Watchdog Reset) report. The panic string indicates: Unexpected SoC (system) watchdog reset occurred after panic diagnostics were completed. The primary difficulty in debugging is that the hardware reset happens so rapidly that the kernel fails to capture a stackshot or any detailed panic trace. We have practically no actionable information from the standard diagnostic reports. However, we did find the following recurring entrie
Replies
1
Boosts
0
Views
239
Activity
4w
Reply to Issues with diacritics in filename on iOS when the system main language is not English
The short answer is that I tried everything (I could think of) and everything I tried fails. in the Files app, simple tap on the file: opens QuickLook (iOS 16) or the Preview app (iOS 26) for files without diacritics in their name. Doesn't do anything for files with diacritics (it's like I didn't tap on the file at all). in the Files app, long press on the file to get the contextual menu, scroll to Quick Look (Coup d'œil since I'm still in a non-English language), I get a blank screen that says Document PDF. opening the file using the documents browser from the Preview app (iOS 26) or PDF Viewer (iOS 26, iOS 16): does not display the file (it's like I didn't tap at all). previewing the file from inside the app using UIDocumentInteractionController(url: url).presentPreview(animated: false): blank screen that says Document PDF. opening the file by calling another app from inside the app using an UIActivityViewController: nothing happens on iOS 26, I get the error message (You do not have permi
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
4w
XCode Update
Hi, I recently updated my Mac to macOS Sequoia 15.7.2, and then updated my Xcode packages right afterward. However, when I try to open Xcode, I receive the message: “You can’t open the application because it is being updated.” I contacted Apple Developer Support (software) by phone and went through their troubleshooting steps, but the issue persists. They confirmed that everything appears fine on their end. In System Settings, both macOS and Xcode show as fully up to date. However, when I manually check in the App Store, it says Xcode needs to be updated. When I press Update, I get the following error: “Xcode could not be installed. Please try again later.” I’m fairly new to Xcode, but it seems there may be an incomplete update or verification loop preventing the installation from finishing properly. Could you please advise on how to resolve this so I can open Xcode again?
Replies
1
Boosts
0
Views
161
Activity
4w
BLE characteristic values swapped
Several of my users are reporting on at lest recent and current versions of iOS the value from one characteristic can be swapped with another. Originally I thought this was a library issue but it doesn't happen on Android and now a user with two iPhones using the exact same app and iOS 26.3 on both has the issue on one phone but not the other. I've gone into more detail here which also includes a little data dumping to prove the values between characteristics can be mixed up. https://github.com/dotintent/react-native-ble-plx/issues/1316 One user reported cycling Bluetooth on/off fixed the issue but the latest user says it does not. For the peripheral the services can only change if the device enters firmware update mode (in which case the service UUID is different). Otherwise the characteristics on a service never change. This would make it a strange one to be caching related since the cache should always be correct.
Replies
3
Boosts
0
Views
84
Activity
4w
Reply to BLE characteristic values swapped
My initial thought right at the start were it a race condition in (my) code. While I was confident my JavaScript was correct the translation that ReactNative does is under-the-hood and I couldn't validate this directly. This is why I then added additional logging into production to dump the characteristics/values, which proved it was not a race issue (with my code or its translation) but what is coming back from the library or iOS/CoreBluetooth. I then moved onto it being an issue with the react-native library, which is still a possibility, but the odds have reduced somewhat by the behaviour below. What made me increasingly suspect it's an iOS issue is two iPhones, one a 13 and the other a SE (later model) running 26.3 running the same App at the same time try to connect to the peripheral (which supports multiple connections). One iPhone is successful, the other swaps the values between the two characteristics and so fails. I haven't been able to replicate this myself, it's an error in produ
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
4w
Reply to When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
I added @main to the AppDelegate and the situation changed; now I have: libswiftCore.dylib`swift_willThrow: -> 0x181cb27ec <+0>: pacibsp 0x181cb27f0 <+4>: str x19, [sp, #-0x20]! 0x181cb27f4 <+8>: stp x29, x30, [sp, #0x10] 0x181cb27f8 <+12>: add x29, sp, #0x10 0x181cb27fc <+16>: adrp x8, 429908 0x181cb2800 <+20>: add x8, x8, #0x660 ; _swift_willThrow 0x181cb2804 <+24>: ldapr x8, [x8] 0x181cb2808 <+28>: cbnz x8, 0x181cb2818 ; <+44> 0x181cb280c <+32>: ldp x29, x30, [sp, #0x10] 0x181cb2810 <+36>: ldr x19, [sp], #0x20 0x181cb2814 <+40>: retab 0x181cb2818 <+44>: mov x0, x21 0x181cb281c <+48>: mov x19, x21 0x181cb2820 <+52>: blraaz x8 0x181cb2824 <+56>: mov x21, x19 0x181cb2828 <+60>: b 0x181cb280c ; <+32>
Replies
Boosts
Views
Activity
4w
Reply to When I compile my app I get a funny link error on libsystem_kernel.dylib`__pthread_kill:
Ok, I clarify myself a bit. There seems the code lacks an entry point, from another part of the crash log: iPuja`abort_could_not_find_entry_point___debug_dylib: 0x102ab1440 <+0>: stp x29, x30, [sp, #-0x10]! 0x102ab1444 <+4>: mov x29, sp 0x102ab1448 <+8>: bl 0x102ab1620 ; symbol stub for: abort Then it seems it keeps on finding a entry point until it crashes. iPuja`getDebugDylibEntryPoint: 0x102ab05d4 <+0>: sub sp, sp, #0x70 0x102ab05d8 <+4>: stp x26, x25, [sp, #0x20] 0x102ab05dc <+8>: stp x24, x23, [sp, #0x30] 0x102ab05e0 <+12>: stp x22, x21, [sp, #0x40] 0x102ab05e4 <+16>: stp x20, x19, [sp, #0x50] 0x102ab05e8 <+20>: stp x29, x30, [sp, #0x60] 0x102ab05ec <+24>: add x29, sp, #0x60 0x102ab05f0 <+28>: adrp x8, 8 0x102ab05f4 <+32>: ldr x8, [x8, #0x8] 0x102ab05f8 <+36>: ldr x8, [x8] 0x102ab05fc <+40>: str x8, [sp, #0x18] 0x102ab0600 <+44>: adrp x24, 12 0x102ab0604 <+48>: ldrb w8, [x24] 0x102ab0608 <+52>:
Replies
Boosts
Views
Activity
4w
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
Replies
2
Boosts
0
Views
142
Activity
4w