The app gets stuck after login on an iOS 18 device

the simulator shows failed to initialize deferred reclamation buffer (46)

That’s unlikely to be relevant. This log entry is coming from the system memory allocator. It’s triggered because the allocator is trying to use a kernel feature that’s not supported on your system (46 is KERN_NOT_SUPPORTED). This is not uncommon with the simulator, where the simulated operating system is out of sync with the macOS kernel on which it’s running.

As to you main issue, it’s hard to say what’s going on. When you say “The app gets stuck”, does that mean that:

• It becomes completely unresponsive? That is, it stops updating the UI and buttons don’t respond to taps.

• Or that it just never makes progress?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

@DTS Engineer Yes, it becomes completely unresponsive when we click on the button. At that time, the page gets stuck.

we are now encountering a new issue where the application gets stuck after login and gives an error as “An element could not be located on the page using the given search parameters”. We were working on a solution, but the issue is still unresolved could you please assist us to get it resolved ? We have 2 different Mac machines, and we could replicate the issue on of the macs where the latest Sonoma OS and supported Xcode and Appium is installed. Please refer below details for the same: Mac machine and iOS device details:

• Mac machine: admin’s Mac mini
• macOS: Sonoma 14.4 and 14.7
• Xcode: 15 and 16
• Device: iPad 17, 17.7, 18.0.1
• Appium: 2.0.1 and 2.11.5
• ipa file: Created on Xcode 15.4 and 16
• Issue: The page goes blank and gets stuck after login.

Attempts to resolve the issue:

We have tried updating Xcode, Appium, XCUITest, and macOS to the required versions for iOS 18 devices. A new Touch build was created and tested, but the automation test still fails after login, resulting in the page getting stuck.

You’ve mentioned a bunch of web technologies here. This is a native app, right? Is it built using Apple’s tools and frameworks? Or built using web technologies that are run by a third-party framework?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

@DTS Engineer Thank you for your support and guidance!

To clarify, the app is primarily native, built using Apple's tools and frameworks, such as Xcode and Swift/Objective-C. However, during testing, we use Appium and WebDriverAgent to automate the app's interactions, which include switching to WebView for testing specific components.

Here's the process we follow during testing:

• Launch the app using Appium.
• Wait for the WebView to load (this is essential for parts of the app like the login flow or dynamic content).
• Use Appium's context-switching feature to switch from the default NATIVE_APP context to the WEBVIEW context.

While the core functionality is implemented natively, some features of the app utilize WebView to render dynamic content powered by web technologies. This requires us to handle both native and WebView elements during testing.

Let me know if additional details or clarifications are needed. Thank you again for your assistance!

@DTS Engineer I am using a hybrid application, and when we execute the .IPA on an iPhone 18.0 with Xcode 16.1, the application launches successfully. However, after logging in, the application gets stuck and freezes.

Observations:

After login, the application context switches from Native to WebView, and we process further steps based on WebView selectors.

Expected Behavior: The same application is running successfully on a Mac 13.5 with the following configurations:

macOS: Ventura 13.5 Xcode: 15 Device: iOS 17, 17.7 Appium: 2.0.1 IPA file: Created on Xcode 15.4

Issue Details:

The issue occurs with the following configuration:

macOS: 15.1 Appium version: 2.11.5 npm version: 10.5.2 Xcode: 16.1 Appium-XCUITest-Driver: 7.27.0 Framework version details:

Selenium-Java: 3.141.59 Appium Client: 7.2.0 Device details:

iPhone version: 18.0

Request:

Could you please help us resolve this issue? Could you clarify if this is an application-side issue or related to our automation setup? Let me know if you need any additional details to investigate further.

Looking forward to your guidance.

Thanks for the explanation of how your app is constructed.

One more quick question: You originally tagged this thread with APNS, which stands for Apple Push Notification Service. Are push notifications involved in this at all?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

@DTS Engineer Thank you for pointing that out!

Yes, push notifications (APNS) are involved in the app.

Please let me know if you need any additional details to investigate further.

Thanks for confirming that.

Debugging problems like this is going to be tricky because there are so many different components involved. When your app gets stuck, are you able to attach to it with the Xcode debugger. That is, in Xcode open your project and then choose Debug > Attach to Process.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"