Sample is at https://github.com/PSPDFKit-labs/radar.apple.com/tree/master/33026752%20-%20UICollectionView%20lift%20animation%20intermittently%20stops%20working%20when%20registered%20for%203D%20touch%20previewing

Engineering has determined that your bug report is a duplicate of another issue (32290126) and will be closed. The open or closed status of the original report your bug was duplicated to appears in a text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to. If you have any questions or concerns, please update your report directly at this link: https://bugreport.apple.com/.

bug still present in Xcode 9 beta 2 (9M137d)

More info as requested by an Apple engineer: unfortunately our toilet paper rolls are not fancy, and they are not Bluetooth- or NFC-enabled, nor do they have accelerometers. My roommate needs a way to manually enter data points into Apple Health/HealthKit.

Radars referenced:

http://www.openradar.me/radar?id=5042055197753344 http://www.openradar.me/radar?id=4994347640553472

Referenced radar(s):

http://www.openradar.me/radar?id=5042055197753344

https://bucket.waldowski.me/Swift-bug-tracker-Summer-2017-hOLtOUgnBG.jpeg

June 26 2017, 8:23 PM We'll need a sysdiagnose after this issue reproduces in order to investigate further. If appropriate, please also provide a screenshot/screen recording of this happening. Please use this command in a terminal window: sudo sysdiagnose -f ~/Desktop Mail Please collect this either while the issue is occurring, or as soon after as possible (for example, take it after a reboot if necessary). Please let us know what you were doing that caused the issue, so we can correlate your actions with the diagnostic output in sysdiagnose. Please try to focus on one or two actions that cause an issue. If you perform many different actions, it will be difficult for us to determine which action caused the sysdiagnose output. More on running sysdiagnose: 1. Launch Terminal.app 2. Enter this command: sudo sysdiagnose -f ~/Desktop Mail 3. Enter your admin password 4. When sysdiagnose has completed (may take several minutes), locate the new sysdiagnose file. Upload that file.

Oh and the Xcode version I was using was "Version 8.3.2 (8E2002)", with swift "Apple Swift version 3.1 (swiftlang-802.0.53 clang-802.0.42)". It also reproduces with the Xcode 9 beta tools.

Example project: https://github.com/PSPDFKit-labs/radar.apple.com/tree/master/32980288%20-%20SearchBarLayoutIssue

https://github.com/PSPDFKit-labs/radar.apple.com/tree/master/32976447%20-%20FileURLCoordinationExample

https://github.com/PSPDFKit-labs/radar.apple.com/tree/master/32976151%20-%20FilePresenterCallbacksExample

The title is a bit misleading in retrospect. My expectation+hope is setting the badge to 0 would not clear items in Notification Center regardless of how the badge is set (local, remote, or directly via applicationIconBadgeNumber).

June 23 2017, 11:23 AM panic(cpu 6 caller 0xffffff8025d6c0df): initproc exited -- exit reason namespace 2 subcode 0xb description: none It sounds like the install was interrupted and then the user tried to reboot. I suggest doing a fresh install and letting it go all the way through. Please provide your response or results by updating your bug report. If uploading files, please compress first.

June 25 2017, 1:23 PM Thank you for suggestion. Xcode panic was during app install—I never tried to reboot, just happened. If it happens again I'll update report. Now on beta 2 so this may be resolved.

https://github.com/michaelochs/radars/tree/master/32971926%20-%20UIBezierPath-clamps-radius

Problem does not exist in Xcode 9 beta 1

I've been trying to access the icon file for about 500 different types in the last hour and a half. I'm glad I'm not the only one that's been bitten by this. The not-so-nice response from Apple is kind of strange. Oh well. Thanks for opening this!

Happens in xc9b2 too.

The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential.

The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential. If you have further questions about this issue, please update your report using the Apple Bug Reporter http://bugreport.apple.com.