Post not yet marked as solved
I recently had a build go into the system for Test Flight distribution and got the automated message:
"ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in Contents/MacOS/: UIMarkupTextPrintFormatter."
I've been using UIMarkupTextPrintFormatter for a long time, and it appears to be a very-public API. I don't even see it as being marked obsolete/deprecated.
Is anyone else getting this message? Is this just a goof on Apple's part, or will I need to find some alternative to UIMarkupTextPrintFormatter?
Post not yet marked as solved
I'm getting an issue where compiling both my macOS and iOS frameworks in Release modes (i.e., Archive) in Xcode 10.2. This happens with both Swift 4.2 and with Swift 5. I can get it to stop hanging by either:Changing Compilation Mode from Whole Module to IncrementalChanging Optimization Level from Optimize for Speed to either Optimize for Size or No OptimizationDoes anyone know what may be going on here? Is there a likely culprit in my codebase or is this just a compiler bug?
Post not yet marked as solved
Running 10.14 Beta 11, Xcode 10 GM.I've been diligently updating my apps to support dynamic Dark/Light Mode, but I've run into a problem that has me a bit baffled. I've been following the instructions presented at WWDC to make sure all of my custom views and controls with custom layers get the appropriate color updates when a user switches between Light and Dark Mode. This all seems to be working quite well. However, on controls that have animations in response to mouse events (e.g., Mouse Over) - I seem to end up with the layers reverting back to their previous effective appearance upon mouseover.The sequence will go like this:1. Set the Appearance of macOS to Light Mode2. Start my App - everything looks appropriate - in light mode.3. Switch the Apperanace of macOS to Dark Mode - all of my custom controls/views switch their apperance and things look appropriate - in dark mode4. Mouse over my custom controls - my layers suddenly revert back to their light mode appearance even though they looked fine a second ago and I'm still in dark modeIt's like there is some sort of Core Animation layer caching going on that I'm not updating when switching to Dark Mode. I only seem to have this problem when deaing with mouse events. However, I didn't see anything about such a notion when watching the WWDC videos. Anyone have any idea?
I'm trying to get my macOS project all updated for Swift 4, but I'm running into a problem trying to reference CBPeripheral.identifier. It looks like, as of Swift 4, this property is now attributed with "@available(OSX 10.13, *)" (it's actually from the CBPeer protocol). I can no longer target earlier versions of macOS when using `identifier`, and I can find no suitable replacement for using identifier. It looks like this has been the case since Xcode 9 was released, so I'm wondering if this change is intentional?Ironically, the documentation still seems to show that `identifier` is the correct mechanism for differentiating peripherals:"The CBPeripheral class represents remote peripheral devices that your app—by means of a central manager (an instance of CBCentralManager)—has discovered advertising or is currently connected to. Peripherals are identified by universally unique identifiers (UUIDs), represented by NSUUID objects. Peripherals may contain one or more services or provide useful information about their connected signal strength."Any advice on what I should be using if I want to target 10.12, but build with Swift 4?
JacobJ84.