iPadOS 17.7.7

Very interesting... I had a similar issue:Opened two different scenes of my app in Mac Catalina and when dragging an item from one window1) If I drop the item in another scene, in the destination - (BOOL) dropInteraction:(UIDropInteraction *)interaction canHandleSession:(id<UIDropSession>)session API_AVAILABLE(ios(11.0)) { - (void) dropInteraction:(UIDropInteraction *)interaction performDrop:(id<UIDropSession>)session API_AVAILABLE(ios(11.0)) {...the UIDropSession is always nil.2) If I drop the item in the same exact window from where I started the dragging the <UIDropSession> object is NOT nil.3) Everything works well on iPadOS.

There's not much more code I can show. Just create a simple new project with a TableViewController as the rootview controller. Use the following (complete) code for this view controller. The code just creates a few empty dummy cells and sets an empty dummy SearchResultsUpdater. Run the App on an iPad (iPadOS 13.1.3) and you'll see the problems.Problem 1:While pulling down the table, the navigation toolbar will change its color (the icons and title keeptheir original color), so when the search field is fully visible, the navigation bar shows a whitebackground with white buttons and title, making the navigation toolbar completely unusableTapping into the search field immediatelly changes the colors of the navigation toolbar again to itsoriginal dark appearance. Canceling the search immediatelly turns the navigation toolbar all white again.This is only an issue on a real iPad device (iOS 13.1.3), there's no problem on the simulator (iPadOS 13.0)Problem 2:Once the search field was made visible,

Thanks, that works now.So, I tested with your set up:Problem 1:While pulling down the table, the navigation toolbar will change its color (the icons and title keeptheir original color), so when the search field is fully visible, the navigation bar shows a whitebackground with white buttons and title, making the navigation toolbar completely unusableTapping into the search field immediatelly changes the colors of the navigation toolbar again to itsoriginal dark appearance. Canceling the search immediatelly turns the navigation toolbar all white again.This is only an issue on a real iPad device (iOS 13.1.3), there's no problem on the simulator (iPadOS 13.0)If you set the navigation bar tint to system gray color instead of Default, and not translucent, it seems the problem disappear.You may have to set the coloor of text field navigationItem.searchController?.searchBar.searchTextField.backgroundColor = .whiteOk for you ?Problem 2:Once the search field was made visible, you can no longer hide it. Hiding

This problem persist in iPadOS 13.2

I know this is a little old by now, but if you hadn't found a solution to the issue yet (or anyone who stumbles across this from Google), iPadOS appears to have changed the default User-Agent to be a desktop User-Agent.. Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko). You can try and either set the customUserAgent on the webview to something closer to the iPhone's default User-Agent so the HTML5 video player you're using detects an iPad and modifies itself accordingly. The following worked for me and fixed up other websites that were having issues playing videos.webview.customUserAgent = Mozilla/5.0 (iPad; CPU iPhone OS 13_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko)

Hello.Still no news about an iPadOS 13 simulator in Xcode ?It's very annoying beause I need to test my App on this OS version since it's the one used by the people who make the review of my App when I submit it on the Apple Store.

See the release notes for 11.2.1: it is fixed.https://developer.apple.com/download/Xcode 11.2.1 GM seedXcode 11.2.1 includes everything you need to create amazing apps for all Apple platforms. Includes the latest SDKs for macOS, iOS, watchOS, and tvOS.This update fixes a critical issue that could cause apps using UITextView to crash when run on previous versions of iOS, iPadOS, or tvOS. Please see the release notes.

My programmer and I are having the same exact problem. He has been using Xcode 11.2 without issue to this point and we successfully uploaded to TestFlight last night. When we try to upload the same exact binary to iTunes we get Invalid Binary errors. Apple wanted to charge us a support ticket to bring errors with Xcode to their attention! The people you call into and speak with have no clue what you are talking about, in my opinion they need better training.We are now getting this warning msg:App Store Connect Operation WarningWARNING ITMS-90703: Deprecated Xcode Build. Due to resolved app archive issues, we have deprecated Xcode 11.2 on November 5, 2019. Download Xcode 11.2.1 or newer, rebuild your app and resubmit.I googled this and found out much more information than Apple's own developer department knew. They should know this! Apple has just released an emergency Xcode 11.2.1 update for developers — the tool used to create iOS, macOS, watchOS and tvOS apps. ... According to the company, today's update fi

I see this in iOS 13.2.3 (I just checked) as well as iPadOS 13.3 beta 2. I'm begining to think this is a debug statement accidentally left in production code...

Seems the issue is still persistent in 13.3 Beta 3 and 3rd party cookies are still blocked besides “Block all Cookies” turned off and “Prevent cross-site Tracking” turned off. Filed a bug with Apple as this prevents several websites that cross connect for login purposes from being usable in iOS and iPadOS. Problem also persists in Chrome as it seems they use the same WebKit.

I cannot test it because Xcode 11.2.1 stays stuck endlessly on Preparing debugger support for my iPhone SE with iOS 13.2.3. The same Xcode version does not have any problems on my iPad Air 2 with iPadOS 13.2.3.