I have verified that the incorrect behavior no longer exists in Xcode 11; following the "Steps to Reproduce" results in the line reading "12354" as expected.

I updated my phone to 13.1.2. The phone seems to download changes from web iCloud notes and my computer fine. But changes made on the phone DO NOT SYNCH back to iCloud. They don't show up on the web version of iCloud notes or the computer. I can even make additional changes to the same note on Icloud, and those will synch back to the phone. But the changes made on the phone do not synch back out. So the version on the phone will have all the changes from iCloud mixed with the changes from the phone. It is very buggy and strange.

Please have a look at this issue as soon as possible

This was fixed in ios 13.2 beta 2.

Xcode 11 doesn't suffer from this issue (tested on macOS 10.15). Apple has not closed the radar.

Summary

• OCSP requests cannot be intercepted by NSURLProtocol as they are performed out of process. We have submitted a bug report for this.

• Simply calling SecTrustPolicies() will remove any policies previously set on the trust. In our case we were unknowingly removing the hostname check. Fixed here: https://github.com/Psiphon-Labs/OCSPCache/commit/18bd7eea0f702268d965ca90e53f007002a10c1d.

• Calling SecTrustEvaluate() with SecPolicyCreateRevocation(kSecRevocationOCSPMethod | kSecRevocationNetworkAccessDisabled) will check if there is a pinned OCSP response.

• kSecRevocationRequirePositiveResponse only applies when OCSP requests are made by the system; as this flag refers to the status code in the response.

• Since the OCSP code varies across iOS versions, testing is the best way to determine the underlying functionality.

Intermediate Certificates

There are two solutions for making OCSP requests for intermediate certificates

Option 1. Plaintext OCSP requests made by the system

If we are OK with intermediate OCSP requests going in the clear, we could enable network access for the revocation check after attaching an OCSP response for the leaf; since the attached response should be used and then the system will make the intermediate checks in the clear.

Option 2. Make all OCSP requests ourselves

If we want to handle all of the OCSP requests ourselves, we could:

1. Attach OCSP response for the leaf and call SecTrustEvaluate(). This step will download all the intermediate certificates. If this check fails, stop here.
2. Download all the intermediate OCSP data and attach it.
3. Do SecTrustEvaluate() again.

Affects both an iOS app when building with Xcode 11 and running on iOS 13, and a Mac Catalyst app.

Per tweet from Tyler Fox (Engineer on UIKit), the app receives a trait collection change and then back to take the snapshot when app enters background: https://twitter.com/smileyborg/status/1175199999367368704

I wonder if deliberately "slowing down" that trait collection request temporarily solves this issue?

If the user downloads your app from the App Store, the system will begin downloading apple-app-site-association files as soon as soon as your app is installed or updated. If your app is developer ID-signed, the system will not begin these downloads until the user has launched your app at least once.

Source: https://developer.apple.com/videos/play/wwdc2019/717/

I can confirm that this has not yet been implemented on iOS 13.

I can confirm this radar is still present on iOS 13

Can anyone verify this still happens on iOS13? I opened an official bug and Apple asked me to re-verify but I hadn't had time yet.

See my rant on twitter: https://twitter.com/altimac/status/1176788944886915072

Take a look at: https://developer.apple.com/documentation/localauthentication/lacontext/1514150-evaluatedpolicydomainstate?language=objc

The data returned by that method changes every time there is some change to the TouchID or FaceID underlying structure. It is not clear, by design, when it changes but we have tested it and we know that at least it changes when fingers are added / removed.

We believe this issue is resolved.

Please test this issue with the latest iOS 13 beta release and update your bug report at https://bugreport.apple.com/ with your results.

iOS betas: https://developer.apple.com/download/

If the issue continues, please update any logs: https://developer.apple.com/bug-reporting/profiles-and-logs/

Has this issue been fixed for you?

Same issue :-( Is someone found a fix?

Thank you, the issue is resolved!

We believe this issue is resolved.

Please test this issue with the latest Xcode 11 beta release and update your feedback report with your results by logging into https://feedbackassistant.apple.com or by using the Feedback Assistant app.

Xcode: https://developer.apple.com/download/

If the issue continues, please update any logs: https://developer.apple.com/bug-reporting/profiles-and-logs/

I have the same problem with NSAttributedString being set to UILabel.attributedText (iOS 13.1)