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)

I had a very similar issue occur, only I was building an App Clip for an existing app. I wasn't able to compile with the release scheme nor archive for distribution.

The solution was to include the Preview Content directory under the development assets of the parent app's target, not the App Clip target itself. That way, I got it to work in all cases such as SwiftUI previews, release builds, and archiving.

This issue does not occur on iOS 15 anymore.

The status of this issue was updated with: `Recent Similar Reports:Less than 10 Resolution:Potential fix identified - For a future OS update `

If you close the home screen after a short time the MFI Accessory disconnects. We need to process the data in the background. So this is a serious bug.

Thanks a lot an00na for your bug report in the first place, it oriented me toward the proper solution. As of iOS 15, the bug is still present (and it was already present on iOS 11).

However, the actual bug is that: - the layout uses minimumLineSpacing for displaying - but it uses minimumInteritemSpacing for computing the contentSize.

The solution is therefore to set both to the same value. It explains why you were misled thinking it only works when minimumLineSpacing is 10: that is the default value of minimumInteritemSpacing.

Apple updated the status to "Potential fix identified - In Xcode 13". I confirm - it works now. Closing this feedback.

base64 --decode <<< 'H4sIAFPvgmECA42TbW/aMBDH3+dT3DJtClEotKv2ojxMU8ekSqiVytA2AYpM4oC1YCPboa1a vnvvEkjCxtrmRRKf73734L9bPkQpkwto/mRpim+utdJgQ8NkPFf3JxE0VbUEv+U474WM0izm 0EXnk2W/ZkgiadND0x50aLSxUP+YUjEnmyOkhV1YKKSw4Z2wy3DNNFtxy7XxoiXTEClpLPhr rRKR8sCB154MuZ/PQwtJyhbmDQH1NMWnqmEyeyvA9/OZzrOk0Sl6WzEhPfphehEFOy/830xm DXhErEjAoz3owhk8PeV+0IfzYhcgWWsMTzycGbIDcDPDFvwCPhjoqjWXzTWzyz5M8EjVXb6Y TaUbQJ6jPcM6iKK5zbSEwa+rH+H3r1fD8e2ANraOc6x14oaEgl7BOZ11jjrmSWue1MUn+FID XBSAMwQ4r00ZGY9uhaQmykUA1+PhcEtlGMusiI6xCnlAb3darrdBrlASThs4k9Iac/kAMU9Y ltqDjTwdEKOpOYubWBiLmWXgmWyetzN1W1O3QUEALR+swskalW44mIdVKuQfQ9fmPzy/4nh5 34irOiQugctJF1oytCYB6Q3O58Wrsr8e0A5qcw3gYwHKpUByQ9K7HrT3CsPde6+uDBTZS3lI e3g2NWguI6oxibFGOnyvVEAAN+Htt5vr4e8yP3p1D9L/nZ2C3YpcF+9ofHk5GI06ztZ5Boxt DAfQBAAA' | gunzip > t_sandbox.c

Failed in Xcode Version 13.1 (13A1030d), on 5th run of tests:

t =    11.12s             Find: Elements matching predicate '"onboarding not seen" IN identifiers'

UserDefaultsBug/DefaultsBugUITests/DefaultsBugUITests.swift:20: error: -[DefaultsBugUITests.DefaultsBugUITests test1FromNotSeenToSeen] : Failed to get matching snapshot: No matches found for Elements matching predicate '"onboarding not seen" IN identifiers' from input {( Button, label: 'onboarding seen' )}

Correction: "Expected: After reading the accessibility label/traits, VoiceOver should only read image descriptions when the feature is turned on. This is what is implied by the description and legalize of the the "Image Descriptions" text."

In a Swift project with only one main.swift file, Xcode disregards the provided PRODUCT_MODULE_NAME in the Xcode project settings and uses -module-name main.

This is discussed on the forums, here: https://forums.swift.org/t/is-this-a-swiftc-bug-error-module-name-foo-is-not-a-valid-identifier/53119