libgit2.dylib compiled after being modified. Don't forget to change the permissions. If you want to do it yourself, just leave your contact.

https://drive.google.com/file/d/19oyv33Saa4hXjaNmT0PJSJerx11kQa9E/view?usp=sharing

+100, it's been causing a couple of failures for us as well. Combined with the build system, which often does not actually complain when the app is compiled for tests in our pre-push hooks, this creates long delays in our pipeline.

Steps to reproduce:

• Have a collection view with allowsSelection and allowsMultipleSelection set to YES.
• Implement a dummy collectionView(_:shouldBeginMultipleSelectionInteractionAt:) delegate method which always returns NO.
• Drag your finger across collection view elements. Notice how they are all selected as you drag along.

This has resulted in several build issues for my team because XCode assumed a certain dependency which was not even linked to the project. An option to disable this would allow us to not have to double check commits for randomly placed imports.

Thank you.

So there is this feature in Xcode Version 13.2.1 (13C100) BUT it's sooo bad. I want to turn it off. Proof: https://stackoverflow.com/questions/69839535/xcode-13-turn-off-auto-import-feature/69917221

Hey @ncreated! How were you able to make this work?

I've tested with Xcode 13.2 and iOS 15.2 and the request still fails with the same error. Any updates on this issue?

I can confirm that it is still an issue in iOS 15.1

Fixed in Xcode 13.2

Fixed in tvOS 15.2

I've had the very same problem. It turned out that the private key of the certificate was not available in the System keychain, but only in my login keychain. After I moved it to the System keychain, it worked again.

For signing to work properly, both the certificate and its private key must be available in the System keychain!

So the actual bug seems to be that just any other certificate is picked and used instead of displaying an appropriate error message.

Available on GitHub: https://github.com/defagos/radars/tree/master/button-style-tvos-accessibility-issues

As of iOS 15 the limit has been raised to 50MB. This is much more manageable and probably sufficient.

I'm going to close this issue (if I can figure out how).

We reviewed your report and determined the behavior you experienced is currently functioning as intended.

Thank you for your feedback.

Engineering has provided the following information regarding this issue:

This is most likely due to the fact that the executable's pages have been created via an mmap() mapping, so they're marked as "wpmapped". Since we can't always easily determine if all the writable mappings are gone, a page marked as "wpmapped", i.e. a page that has been mapped for write access in the past, is considered as tainted, so it will fail code-signing verification even if it matches its signature. That's because if there's still a writable mapping somewhere, that mapping could taint the page at any time, including after we validate its signature and start executing from it.

We could potentially try and mitigate this by resetting the page's "wpmapped" when we're absolutely sure that it's safe to do so but that might not cover all the cases and could possibly open some security holes.

The work-around is to use write() instead of mmap() to create/copy the file.

May also be related ... https://openradar.appspot.com/FB9163579#ag9zfm9wZW5yYWRhci1ocmRyFAsSB0NvbW1lbnQYgICAqtOU9AgM

This bug appears to be fixed in Monterey (macOS 12)

I think this https://openradar.appspot.com/radar?id=5041527457841152 might be related. Is the problem still happening in on iOS?

Still present in macOS 12.01 and Xcode 13.1.

Still buggy in 12 beta 4 / iOS 14 beta 4:

Open project in Xcode 12 beta 4 Launch app in iPhone SE (2nd generation simulator) (might have to tap back to get back to Master) Make there be 2 rows on the table. Swipe the first row. Swipe the second row and immediately after the swipe tap the reload button.

What expect to happen. Row 1 should have animated away

What happens. Row 1 animates back out as if it was swiped and then animates away. (see attached video Screen Recording 2020-08-17 at 11.34.07.mov)