@robby28: Bosian's solution worked for me. My code also needed to only include references to the framework when not building for simulator, like so:#if ! TARGET_IPHONE_SIMULATOR
#import <myDeviceOnlyFramework>
#endifThat should prevent linking failure errors.
Post not yet marked as solved
I realize that this is an old thread, but for others who are searching for this:https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/wa/jumpTo?page=fiscalcalendar
Post not yet marked as solved
FYI, just got the MBP back from AppleCare. They replaced the logic board and touchID board.
Post not yet marked as solved
FYI, just got the MBP back from AppleCare. They replaced the logic board and touchID board.
Post not yet marked as solved
My 2018 MacBook Pro was bricked by the downgrade attempt. It would not boot at all.I contacted AppleCare and they are currently repairing it under warranty.Prior to sending it off, we tried resetting the SMC and restoring the T2 firmware using the Apple Configurator 2 utility (as per the helpful link from luniacdevel)-- neither of which helped. The Configurator got pretty far along, then displayed an error message saying that T2 firmware could not be restored.Once I get the MBP back, I'll stay on Mojave until Catalina is out of beta for a few weeks. I initialliy installed Catalina in order to try building a macOS version of my iPad app (which fails because several of the third party libraries I use will need to be recompiled first). Meanwhile, Xcode 11 beta runs fine with Mojave on my iMac Pro.
Post not yet marked as solved
My 2018 MacBookPro was also bricked by the downgrade attempt. I contacted AppleCare and they are currently repairing it under warranty.Prior to sending it off, we tried resetting the SMC and restoring the T2 firmware using the Apple Configurator 2 utility-- neither of which helped. The Configurator got pretty far along, then displayed an error message saying that T2 firmware could not be restored.
