Is this reproducible in iSO 13+? I'm also facing WKWebView causing app crash over a period on loading web content

Did you get any comments from Apple on this?

I'm just bought a newest macbook Pro 13" with a Razer Core X and am AMD 5700xt.. Unfortenly I did everything to make it work in Boot Camp but nothing works.

I'm so disapointed spending so money with so high tech to do not work.

I'm using the Catalina

Please Apple, help us.

Hi,

Still reproduced on Xcode 11.3 / iOS 13.3 Simulator. Any feedback from Apple?

Another voice in support of this

For kVTCompressionPropertyKey_DataRateLimits to work correctly you will also need to specify AVVideoExpectedSourceFrameRateKey.

fwiw, I am seeing the same issue with my Mac mini 6,1 running 10.14.6. My device is an Airport Express running 7.8.1 firmware.

I have now disabled AVB/EAV on my Ethernet interface.

Has this been officially fixed by Apple? Tested on 11.4 and it seems to be fixed but want to confirm if it's fully fixed on all later version and stable. Any update/link to announcement appreciated!

I would love to see this as well!

The same is true in certain countries in Europe, for instance we have our apps live in Belgium; however the App Store Connect will either allow you to pick French or Dutch, but then you cross the Netherlands and France territories with the same screenshots, metadata and so forth. That is not flexible enough to target specific markets as intended.

Verified, "-webkit-text-size-adjust" doesn't work in iPadOS 13.3

We had a similar issue with webview and SMS code autofill (the same stacktrace) which was:

• Deactivate "Predictive" in Settings > General > Keyboards
• Receive a SMS with a second factor authentication code
• Start by entering some digits (first 3)
• tap on the one time code from messages.

Result: the app will crash

By swizzling NSString stringByReplacingCharactersInRange:withString: the crash no longer occurs for those steps and the original steps of this radar.

https://gist.github.com/kyle-ilantzis/00f4685462a150506481a15ac2af7259

The attached project can be found here: https://drive.google.com/open?id=1TeJGvCPaLVzBaAh7zIponnjdsC0k40Sl

This code patch no longer exists in iOS 13.

Can you validate that this crash happens in case of low memory? My conclusion comes from the crash report where the SIGSEGV exception occurs when code attempts to access memory that has recently been freed. I assume that the VectorKit tries to access an invalid memory which not mapped to object (SEGV_MAPERR) or has invalid permissions for mapped object SEGV_ACCERR. It depends on low memory because periodically our app has a heavy map-drawing process. Did you have this experience in your tests?

Apple closed this as an internal dupe. It is also fixed in Catalina.

This error no longer exists because you can change between required and non-required priorities now.

Apple closed this as a dupe on Feb 14, 2019. It also appears to be fixed, based on my testing.

Thank you for contributions towards making the bug filing process at Apple better. As a result of your feedback and the feedback of your peers, we have replaced Bug Reporter with Feedback Assistant for Developers, which introduces many new features and improvements to make submitting feedback easier, more efficient, and more effective.

Since Bug Reporter has been retired, we are closing this legacy report. We welcome your continued feedback about Feedback Assistant on the web, and on your iOS, iPadOS, and macOS devices.