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!

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!

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

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.

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.

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 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) } }

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.