When rendering 2 'div' components with 'display:flex' placed on top of each other, the preceding one sometimes comes up. The 'position:absolute' has been set and the second 'div' component is being generated after the first one. However, when inspecting the iOS webview in Safari, I enable-disable the 'display:flex' property, everything starts working again. This is possibly a bug in the layout engine. I tried the same process in iOS 16.4 and there are no issues at all.

I am trying to automate Web app on iOS Safari for e2e test. Even though following code worked for emulator in iOS 17 beta, it seems not working on Real Device(iPhone 12, iOS 16.6). code for test describe("test0", () => { const getDriver = async () => { const options = new safari.Options() const capabilities = webdriver.Capabilities.safari() capabilities.setPlatform('ios') capabilities.set('safari:deviceType', 'iphone') capabilities.set('safari:useSimulator', false) const driver = new Builder().forBrowser('safari').withCapabilities(capabilities).setSafariOptions(options).build() return driver } let driver beforeAll(async () => { driver = await getDriver() }, 10000000) afterAll(async () => { await driver.quit(); }); test("test", async () => { await driver.get("https://google.com"); }, 1000000); }); Following error will happen when testing through real device while device is listed on Device and Simulators opened by Xcode > Window > Device and Simulators. SessionNotCreatedError: Could not create a session: Some devices were found, but could not be used: - iPhone (***-xxxxxxx): Remote Automation is turned off (turn it on via Settings > Safari > Advanced > Remote Automation) - [unknown wireless device]: device is not paired at Object.throwDecodedError (../node_modules/selenium-webdriver/lib/error.js:524:15) at parseHttpResponse (../node_modules/selenium-webdriver/lib/http.js:601:13) at Executor.execute (../node_modules/selenium-webdriver/lib/http.js:529:28) What I tried I turned on Safari > Advanced > Web Inspector, Safari > Advanced > Remote Automation, Developper > Enable UI Automation on iOS setting. I enabled safaridriver running safaridriver --enable. Versions XCode: 15.0 beta iOS: 17 beta

0 I integrate with safriService (SFSafariViewController) to log in through a single sign-on password, the problem was the first time I log in using SFSafariViewController but the authentication follow not complete the first time so the safari browser still appear & can not direct into my app after authentication follow to become a success, another behavior is when I login again the authentication follow work fine & get the token then directed into my app fine so the main problem is the first time I login SFSafariViewController does not catch the user auth if let url = URL(string: "url") { let safariVC = SFSafariViewController(url: url) safariVC.delegate = self safariVC.dismissButtonStyle = .done present(safariVC, animated: true, completion: nil) } extension DouWebViewVC: SFSafariViewControllerDelegate { func safariViewController(_ controller: SFSafariViewController, didCompleteInitialLoad didLoadSuccessfully: Bool) { if didLoadSuccessfully { print("didLoadSuccessfully") // Do something with the URL here } } //initialLoadDidRedirectTo func safariViewController(_ controller: SFSafariViewController, initialLoadDidRedirectTo requestUrl: URL) { let absoluteUrl = requestUrl.absoluteString print("requestUrl(requestUrl)") } func safariViewControllerDidFinish(_ controller: SFSafariViewController) { print("safariViewControllerDidFinish") } }

I'm curious if there is a limit to number of PWA push notifications that can be sent. We estimate roughly 10,000 pushes a day. If anyone has any insight it would be greatly appreciated.

Hey, I am loading a link on my app using SFSafariViewController and that link asking camera and location permission. Camera permission pop-up showing and accessible but for location permission it is not doing anything even not showing location permission pop-up. I need to know is there any way to get location permission pop-up on SFSafariViewController.

I am currently utilizing local servers to facilitate interactions with local resources. However, I am exploring if there are solutions that would enable direct file access through the file:// protocol. I cannot access the developer tools and feature flags. Specifically, the option "Show features for web developers" seems to be deactivated. This is happening within the ASan WebKit build. I am running this using Tools/Scripts/run-safari. Any insights or potential solutions to these issues would be greatly appreciated.

I am using appauth pods for authentication (https://github.com/openid/AppAuth-iOS) and was wondering how Safari webkit is managing the application context for the cookies saved while authentication. I made sure I have a successful authentication then I tried few combinations to understand failed authentication behavior and tried to compare with my mac safari developer tools. What caught me off guard was that the safari webkit cookies were not visible to me programmatically. I am using below code to get the cookies. HTTPCookieStorage.shared.cookies(for: URL(string: "https://(targetDomain)")!) I also tried using developer console for mobile safari kit but as soon as the authentication flow gets completed the view is destroyed and information gets lost. So has anyone have come across this situation and figured how safari web kit isolates the cookies visibility.

I am trying to get console logs from iPhone safari on my MacBook safari. I have connected iPhone to MacBook via USB. It doesn't display logs, it just displays errors. Few days back, both logs and errors were showing up...

Hi all, As of a few days ago, I can no longer capture the console logs from my iPhone onto macOS. Is anyone else experiencing the same issue?

It appears a lot of useful WWDC session videos from previous years have been scrubbed from the developer.apple.com? I cannot find the WWDC session "Customized Loading in WKWebView" from 2017 in the Developer app nor on the developer website. There are lots of other videos that would be useful to watch, even from years ago. Am I just not looking in the right place?

According to the release notes of STP, OffscreenCanvas has been implemented for a while. However, when I run JavaScript code, it fails because OffscreenCanvas is not a recognized command. I feel I’m missing something obvious here. Any help?

Is it because file cannot be opened because it is from an unidentified developer. I have a MacBook Air I have installed TomCat My application will be using servlets I can not get the simplest servlet to compile and execute. I downloaded javax and was not sure where to put it. Thought it should go into Library/Java/Extensions I suspect that Mac will not allow opening the file When is compile in terminal stephenghebert@Stephens-MacBook-Air myapp % javac HelloWorld.java HelloWorld.java:10: error: cannot find symbol public class HelloWorld extends HttpServlet { ^ symbol: class HttpServlet HelloWorld.java:11: error: cannot find symbol public void doGet(HttpServletRequest request,

My environment: * Safari Technology Preview Release 51 (Safari 11.2, WebKit 13606.1.6) * iPad with ios11.3 (15e5216a) * mac os 10.13.3I can debug service worker in mac desktop.I can debug service worker in Android mobile device.But I could not found out how to debug service worker in ios11.3 mobile device?I wonder if it should belong to "Safari Developer Tools " or "iOS Web Apps"

I am using Selenium 3.141 with SafariDriver included with Safari 13.0.1 (14608.2.11.1.11).I have problems with interacting with elements, in this case clinking on a button.1) Create a new SafariDriver 2) Navigate to a page with a button element3) Find the button element4) Click on the button elementRESULT: The click is not performed on the button element but any element below the button element.This is not working from the recent update to safari 13.0.1.

In the Release Notes of Safari 17 Beta it is mentioned that it is already available for certain macOS versions. Where do I find the link to macOS Ventura? https://developer.apple.com/documentation/safari-release-notes/safari-17-release-notes

In the notes it is stated that "Safari 17 beta is available for macOS Monterey, macOS Ventura, macOS Sonoma beta, iPadOS 17 beta, and iOS 17 beta." Where do I find the download link for macOS Ventura?

I posted in the other but they removed it and told me to Post here but anyone know what might have changed or what new experimental feature was added to the list for safari the last two updates? I have been having massive slow or lagging and glitches with my games and safari after this last update. So trying to see which was was newly added.

Hello everyone, I'm currently having an issue with Safari's developer tools on my Mac. I'm working on a WebGL application with a large amount of code. When I try to analyze the timeline of the code, the developer tools crash every time I try to start or stop recording. Here's some more specific information about my situation: MacBook Pro 13-inch, 2020, 2GHz Intel Core i5, Intel Iris Plus Graphics 1536MB, 32 GB 3733 MHz LPDDR4x, Ventura 13.1 Safari 16.2 (18614.3.7.1.5) Here's the specific steps I've been taking: connect my mobile device to my Mac. open the page on my mobile device in Safari. select the webpage I need to analyze from the Develop menu in Safari. click record in the Timeline. I would really appreciate any help or suggestions on what could be causing this issue and how to resolve it. Thank you in advance!

Hello, since the update to macOS enter 13.3 (few days ago) I'm experiencing a new behavior in Safari developer tools. I guess it's an unexpected behavior and I can't find the way to stop it. When I open developer tools (default elements tab) and I start to inspect an element in the page, a new row appears automatically in the bottom part of elements tab; this row is related to the console (which is normally in the other tab). If I close that row by the proper button. Each time I inspect something else on the page, it appears again. How can I disable this feature? I find no setting for this in the developer tools settings. Keep in mind that this behavior started to appear just after the update to macOS 13.3. Before I has 13.2.1 and developer tools worked as expected. I had a talk to Apple Developer Support via phone, they suggested me to open this thread here. I attach a screenshot to show which button I'm clicking to close it. Any help is appreciated.