Alternatively, I found a workaround of applying the .popoverTip modifier to the Button / NavigationLink label itself located inside the label closure of the button / link.

Forgive me as I'm not super well versed in tvOS. Assuming this is a SwiftUI view, have you tried playing with the methods of such like a VStack and building out your view in that manner? TextField(text: <String>, prompt: <Text?>, label: <() -> View>) Form { VStack { Text("Custom Message Title") .font(.title) Text("This is your custom message to your user? See what the outcome is with this.") TextField("Address", text: $address) } }

It appears that the fix is to apply the .popoverTip to the Menu's label contents, not the .toolBarItem itself. For example: Menu { // Menu Actions } label: { Text("This is my fancy button!") .popoverTip(MenuTipView()) } This seems as the appropriate method because a user sees the label, therefore the Tip anchors itself to the view, which in this case is the label.

Forgive me as I'm just sort of spitballing here... the short answer is no I don't think so. The Apple Documentation on the colorSchemeContrast environment variable tells us if the user is using increased contrast setting on their device. What you could do is increase the contrast on the color using the .contrast modifier to that specific views color. However it is important to test the edge case that if a user has the A11Y setting which is to increase the contrast enabled, how will that effect your view? Maybe you use a combination of the environment variable, and the contrast modifier to only apply the increased contrast if the user does not have increased contrast enabled? I do hope that this helped guide you in some manner.

Alright so updating to Xcode 15.0.1 provided me with a much clearer error message upon attempting to upload. The cause to my error was that I had a v in my Version v2.0.1. The error provided me with that information that it must be decimals only with no letters.

Alright so updating to Xcode 15.0.1 provided me with a much clearer error message upon attempting to upload. The cause to my error was that I had a v in my Version v2.0.1. The error provided me with that information that it must be decimals only with no letters.

Also looking for a solution, running into the same issue.

Quinn, you mention the following... Cool. Using these APIs in internal tools like this is perfectly OK. I get worried when folks try to use them in their shipping app. Is there any recommended API in which one could use for a shipping their application to obtain this information? This would be for a device monitoring application. I am asking as this post is 4 years old and well, Apple likes to add fresh technologies once a year!

Hi OopsCommander, I too am actively attempting to find a way to do this. Not sure if this helps but I found this Apple forum post - https://developer.apple.com/forums/thread/659748 about what we're trying to do with an apparent positive outcome. I wanted to share this with you. I understand this post is 6mo old, if you found a great solution please share!

2020-10-11 18:59:08.680 Xcode[34078:994651] [MT] DVTPlugInLoading: Failed to load code for plug-in com.apple.dt.IDE.IDEiOSSupportCore (/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin), error = Error Domain=NSCocoaErrorDomain Code=3588 "dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 265): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle couldn’t be loaded., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, NSDebugDescription=dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 265): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found, NSBundlePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin, NSLocalizedDescription=The bundle “IDEiOSSupportCore” couldn’t be loaded.}, dyldError = dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 0): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found 2020-10-11 18:59:08.682 Xcode[34078:994651] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-17518/IDEFoundation/Initialization/IDEInitialization.m:355 Details: Xcode failed its initial plug-in scan, error = Error Domain=DVTPlugInErrorDomain Code=2 "Loading a plug-in failed." UserInfo={DVTPlugInIdentifierErrorKey=com.apple.dt.IDE.IDEiOSSupportCore, DVTPlugInExecutablePathErrorKey=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, NSLocalizedRecoverySuggestion=The plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled., DVTPlugInDYLDErrorMessageErrorKey=dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 0): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found, NSLocalizedDescription=Loading a plug-in failed., NSFilePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin, NSLocalizedFailureReason=The plug-in “com.apple.dt.IDE.IDEiOSSupportCore” at path “/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin” could not be loaded. The plug-in or one of its prerequisite plug-ins may be missing or damaged., NSUnderlyingError=0x7f85d00379c0 {Error Domain=NSCocoaErrorDomain Code=3588 "dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 265): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle couldn’t be loaded., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, NSDebugDescription=dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore, 265): Library not loaded: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice  Referenced from: /Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore  Reason: image not found, NSBundlePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin, NSLocalizedDescription=The bundle “IDEiOSSupportCore” couldn’t be loaded.}}} Function: BOOL _IDEInitializePlugInManager(IDEInitializationOptions, NSError *__autoreleasing *) Thread:  <NSThread: 0x7f85ce509270>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.

So I have made it through the first two videos (Lectures 1 & 2). I recently did a large portion of a tutorial that I paid quite a bit of money for, I'm afraid I wasted my money. This basic approach changed quite a bit of my views on how to construct applications... if what I've gathered is correct then the following applies.. 1 View - This is what the user sees. Numerous View Models - This is what handles the interpretation of what is going on behind the scenes and what the user gets to see. Model - This is what is going on behind the scenes, this is your back end data. Now my questions are... do you have multiple models / back end data files? How would you decide what is what? Also, how do you decide what view models you will use and so on? Your response was both a blessing and a curse as it will likely cause me to recreate my entire app lol