Experiencing the same issue in macOS 10.13.6 (17G5019) / XCode Version 10.1 (10B61).

Trying to add a button to the system status bar that triggers a popover. The popover's contentViewController is set to a ViewController instantiated from code from the Main storyboard. That ViewController has its own NSMenu for an NSTableView.

When I click the button in the system status bar and the popover is about to show I get:

[General] Placeholder for identifier 'UpstreamPlaceholder-fac-fe-Kyh' was set to ' Title: Supermenu: 0x0 (None), autoenable: YES Items: ( "", "", "", "" )', but the object was deallocated. Is it missing a strong reference in the storyboard/nib?

I'm using the same ViewController elsewhere in the app (via Storyboard segues) and it works fine. In this case however I get this issue all the time.

I was hoping that holding a strong reference for the Storyboard would help but that is not the case.

Adding a strong reference to the menu in the ViewController's code does indeed help but it doesn't feel right - it should not depend on whether the VC was instantiated via storyboard segues or manually added to a popover (unless I'm overlooking anything).

Resolved an issue that affected app compatibility with iOS 9.0, 9.1, and 9.2 when distributing an app for local or enterprise distribution. App asset catalogs built using Xcode 10 with a deployment target of iOS 9.0, 9.1 or 9.2 produced content incompatible with the runtimes of those iOS versions when distributed using local or enterprise distribution. Rebuilding the app with Xcode 10.2 resolves this issue.

Peter West Aug 6 More information. Here's some junk mail. First image is how it appears in Mail. The next image is how it appears in Outlook, where it is in the Junk folder. The next image shows how the display of this message changes. What triggers the change I don't know, but now opening the same message shows the contents of the following message, as can be seen in the following image.

Meanwhile, in Outlook, I have a message in reply to an earlier thread, as shown in the next screenshot. But this reply does not appear at all in Mail, even though the message from the 3rd August is in the Inbox. This is absolutely disastrous. Screen Shot 2018-08-06 at 2.29.47 pm.pngattached 113.63 KB

Screen Shot 2018-08-06 at 2.14.00 pm.pngattached 285.65 KB

Screen Shot 2018-08-06 at 2.27.02 pm.pngattached 322.52 KB

Screen Shot 2018-08-06 at 2.28.46 pm.pngattached 307.63 KB

Screen Shot 2018-08-06 at 2.24.33 pm.pngattached 1.28 MB

Apple Developer Relations Aug 6 Engineering has determined that your bug report is a duplicate of another issue 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/. Peter West Sep 8 How am I supposed to know when I can safely use Apple Mail again? I can't see what's going on with the original bug (for no good reason except to hide problems with Apple's software, it seems) so I can't tell whether the bug is just arbitrarily closed, or whether there has been a fix. Let me just stress: this bug means that I am obliged to use Outlook. This is a serious bug. What is going on with Apple? Apple Developer Relations Sep 22 Thank you for contacting us. It has not been determined how or when the issue will be resolved.

The original report on this issue, Bug ID 17334851, is still under investigation. We will notify you when it is closed.

Please note that you will not be able to directly view the original report in order to keep its information confidential.

We will do our best to keep you informed as new information becomes available. Please check release notes regularly for changes affecting this issue.

If you have further questions about this issue or wish to check on the status, please update your report again using the Apple Bug Reporter http://bugreport.apple.com. Peter West 1d Can you tell me whether this bug is present in Mojave? Apple Developer Relations 14h Thank you for contacting us.

The original report on this issue, Bug ID 17334851, is still under investigation. We don't know what the status is in Mojave yet.

We will do our best to keep you informed as new information becomes available. Please check release notes regularly for changes affecting this issue.

If you have further questions about this issue or wish to check on the status, please update your report again using the Apple Bug Reporter http://bugreport.apple.com.

DUPLICATE OF 42834883

I totally agree. The animations is very annoying indeed. For me the few seconds every day is not the issue, but I am getting annoyed every time I have to wait for the animations to finish. The point about Xcode being our professional tool and not a toy is perfectly valid!

DUPLICATE OF 46671538

https://bugs.swift.org/browse/SR-9918

Attachments:

• https://www.icloud.com/iclouddrive/0yGZkVJljFQJMrSycQUdndGUA#Safely
• https://www.icloud.com/iclouddrive/0uVzsnjflEL-yV5y7MMy0m9xg#Simulator_Screen_Shot_-_iPhone_Xs_Max_-_2019-02-11_at_11.43

Closed as a dup of https://openradar.appspot.com/45247730

Using NSScreenDisableUpdates as a workaround is possible, but windowWillResize: is not a good enough signal

https://codereview.qt-project.org/#/c/252659/

Attachments:

https://www.icloud.com/iclouddrive/0qxI_d2wKWaK--EZzdPkruegQ#Layout https://www.icloud.com/iclouddrive/0PwCUpjYpmDe_f7HA-d6kyttw#card-bad

I have discovered that if I drag the Books window from the external display controlled by the eGPU to the built-in display of the MacBook Pro, the text becomes visible. If I then drag the window back to the eGPU-controlled display, the text disappears again.

Closed as duplicate to 35007040

Reply form Apple "Engineering has determined that your bug report (46931249) is a duplicate of 47220458 and will be closed. "

Got an email this morning that it was closed as a dupe of rdar://6451211 - will try to check it out in future betas of Xcode 10.2, I suppose.

This is issue seems to be fixed on the compiler Swift but Xcode appears to still need to be updated to write its command line arguments to a @params file in order for it to work. Please add Xcode support.

The bug is still present in iOS 12.

This issue is still present as of Xcode 9.4.1, iOS 11.4.1 on iPhone X

However, disabling Personal Hotspot in settings seems to have fixed it for me (https://stackoverflow.com/a/38872531)

Same also applies for .bundle input and output paths.

I am getting this error for network calls mostly in iOS 12.