Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Seeds Ninth Beta of tvOS 17 to Developers

Find My Remote is back. Not yet working to actually find the remote, probably needs a remote firmware update.

Edit: TVOS 17RC updated the firmware of the remote to version 0x83. Find My remote works now.
 

Attachments

  • IMG_0921.png
    IMG_0921.png
    168 KB · Views: 105
  • IMG_0920.png
    IMG_0920.png
    211.9 KB · Views: 121
Last edited:
  • Like
  • Wow
Reactions: Pinkyyy 💜🍎, Donfor39, MrENGLISH and 1 other person
MistrSynistr said:
Seriously am I going crazy or did they remove that Speech Clarity function after the first Public Beta? Where is it? There used to be a toggle under sound to turn it on for Homepods and it's gone now.
Click to expand...
It's still there for me under Settings-->Audio-->Enhance Dialogue. It disappeared for me a couple betas previously but a restart of the HomePods and Apple TV made it reappear. It also only appears if you have the default audio set to your HomePods on the Apple TV.
 
  • Like
Reactions: Pinkyyy 💜🍎 and MistrSynistr
tehbank said:
Not seeing the Find My button. Latest 4K.
Click to expand...
After updating the Apple TV 4K with the latest beta, unplug the Apple TV. Set the remote aside. Plug in the Apple TV. Use the iPhone remote app to select the Apple TV. Where you selected the Apple TV should be the Find option for the remote you set aside.
 
  • Wow
  • Like
Reactions: Pinkyyy 💜🍎 and srbNYC
Apple is a bit late with the SDK notes today. (10:50 AM to 1:20 PM PST)

Accelerate​

New Features​

Camera and AVFoundation Capture​

Resolved Issues​

  • Fixed: On iPhone 14 and 14 Plus models third-party camera applications might fail to capture images, and the built-in Camera app and third-party applications using the new Deferred Processing API might fail to process final images. (113158045)

Continuity Camera on Apple TV​

Resolved Issues​

  • Fixed: After pausing and resuming the connection from an iPhone or iPad to the connected Apple TV, FaceTime call participants will see audio and video sync is mismatched for the Apple TV user. (105464123)
  • Fixed: Following a reboot of AppleTV or first launch of FaceTime, the preview video of camera feed while connecting your phone might take extra time to show up on the screen. (108283141)
  • Fixed: Center Stage functionality incorrectly defaults to UltraWide rather than Wide. (109387427)
  • Fixed: When using Center Stage in a group Facetime call, people at the edge of the frame will be cropped out. (109850731)
  • Fixed: Unsupported iPads might recieve a Continuity Camera notificaition. (110136942)

Facetime handoff​

Resolved Issues​

  • Fixed: Facetime handoff to another device might result in call drop or no media. (110126569)

FaceTime on Apple TV​

Resolved Issues​

  • Fixed: Guest Pairing doesn’t work if Apple TV is connected via Ethernet. (107163191)
  • Fixed: If a phone is already a Connected Camera, answering a FaceTime call on that phone and then moving to Apple TV might result in a dropped call. (107187159)
  • Fixed: Cannot handoff a call that has a FaceTime link on the Apple TV. FaceTime on tvOS will crash. (108109894)
  • Fixed: Moving the FaceTime call from Apple TV to iPhone by tapping “Switch to phone” might result in a dropped call. (108810085)
  • Fixed: Moving from Split View to PIP during a call on Apple TV results in video being lost and privacy indicator not showing correct state. (109537754)
  • Fixed: Moving call from iPhone to Apple TV can result in failure in congested network environments. (109841121)
  • Fixed: Video effects buttons on self-view during a FaceTime call might not work. (110801792)
  • Fixed: FaceTime call might end suddenly within first minute. (111099303)

FaceTime on AppleTV​

Resolved Issues​

  • Fixed: Duplicate participants might appear when moving a call from iPhone to AppleTV. (110036697)

Localization​

Resolved Issues​

  • Fixed: Some content might appear in English. Some strings might appear clipped. (109393568)

Manual Framing​

Resolved Issues​

  • Fixed: If the user adjusted the zoom factor manually with controls in Control Center, the modified video factor will get incorrectly reset to 1.0 when the user enters the Group FaceTime mode. (110809840)

Maps​

Resolved Issues​

  • Fixed: When using Map, Xcode emits a runtime warning that “Publishing changes from within view updates is not allowed.” (106174743)

Media​

Resolved Issues​

  • Fixed: MP3 files with malformed ID3 tags will fail to play (110230071)

NetworkExtension​

Deprecations​

  • Algorithms DES, 3DES, SHA1-96 and SHA1-160 as well as Diffie-Hellman groups less than 14 are deprecated for IKEv2 VPNs. (109427094)
  • The enum values NEVPNIKEv2EncryptionAlgorithmDES, NEVPNIKEv2EncryptionAlgorithm3DES, NEVPNIKEv2IntegrityAlgorithmSHA96, NEVPNIKEv2IntegrityAlgorithmSHA160, NEVPNIKEv2DiffieHellmanGroup1, NEVPNIKEv2DiffieHellmanGroup2, and NEVPNIKEv2DiffieHellmanGroup5 in NEVPNProtocolIKEv2.h will be deprecated. (109680935)

Networking​

New Features​

  • iPhone and iPad devices running iOS 17 beta support joining wired 802.1X networks. Apple TV devices running tvOS 17 beta also support joining wired 802.1X networks. (12867782)
  • URLSession supports resumable uploads in HTTP. Just like download tasks, upload tasks can now be paused and resumed if the server supports the latest protocol draft. To learn more, see Resumable Uploads for HTTP. (68890505)
  • Apple devices now support connection to 802.1X networks using EAP-TLS with TLS 1.3 (EAP-TLS 1.3). EAP-TLS 1.3 further improves security and privacy by always providing forward secrecy, never disclosing the peer identity, and by mandating use of revocation checking when compared to EAP-TLS with earlier versions of TLS. (74526852)

Resolved Issues​

  • Fixed: For apps linked on or after iOS 17 and aligned OS versions, App Transport Security now requires secure connections to external IP addresses by default. For more information on these requirements, see Preventing Insecure Network Connections. Exceptions can be made using NSExceptionDomains, which now supports exceptions for individual IP addresses and ranges specified in classless inter-domain routing (CIDR) notation. (101967030)
  • Fixed: For apps linked on or after iOS 17 beta, macOS 14 beta, watchOS 10 beta, and tvOS 17 beta, the Transfer-Encodingheader field of a streamed HTTP/1 request is set to chunked instead of Chunked. (107390029)

SharePlay​

Resolved Issues​

  • Fixed: Starting SharePlay content between two Apple TVs results in one TV receiving a notification with “pseud…” as the name for the other TV. This only occurs on first attempt and subsequent SharePlay actions are correct. (108926589)

ShazamKit​

Resolved Issues​

  • Fixed: SHManagedSession.State is unavailable. (109670750)
  • Fixed: SHLibrary.default.items is unavailable. (109670918)

StoreKit​

New Features​

  • Users have access to the new Product.SubscriptionInfo.Status.all sequence to get the status for each of your app’s subscription groups. One can use the new subscriptionStatusproperty on the latest Transaction value for a subscription to access the full status information. (102064614)
  • StoreKit 2 now provides a collection of UI components to help merchandise in-app purchases. Use ProductView, StoreView and SubscriptionStoreView to add in-app purchases to an app with just a few lines of code. (102066107)
  • Users can access in-app purchase product metadata and entitlement information from a SwiftUI view using new view modifier APIs in StoreKit. Declare a view as dependent on a single product or collection of products using storeProductTask(for:priority:action:) or storeProductsTask(for:priority:action:)respectively. Declare a view as dependent on the current entitlement for a product using currentEntitlementTask(for:priority:action:). Declare a view as dependent on the status of a subscription group with subscriptionStatusTask(for:priority:action:). All of the modifiers will start a task to load the data before the view appears, and provide your action with the state of the task as it progresses and whenever the data changes. (102397222)
  • User have access to the new groupLevel property of Product.SubscriptionInfo to understand the level of service of a subscription plan. (103885148)
  • Users have access to the new reason, and storefront properties on Transaction to understand the reason why the transaction was created, and which storefront it is for. The new renewalDateproperty on RenewalInfo to understand if and when a subscription will renew next. (104246730)
  • Users have access to new groupDisplayName property of Product.SubscriptionInfo to get the localized display name of a subscription plan’s group. (105689964)
  • StoreKit ViewsProductView and StoreView have initializers have initializers that give you access to the promotional icon as a SwiftUI view and the various phases of the loading operation. Use initializers such as init(id:icon:placeholderIcon:), [init(_:icon:)](https://developer.apple.com/documentation/storekit/productview/4202214-init), init(ids:icon:placeholderIcon:)](https://developer.apple.com/documentation/storekit/storeview/4203378-init), and [init(products:icon:)` to provide an icon view for each phase. (110470147)
  • The following StoreKit types are renamed:
    • DefaultProductViewStyle is renamed to AutomaticProductViewStyle
    • DefaultSubscriptionStoreMarketingContent is renamed to AutomaticSubscriptionStoreMarketingContent
    • DefaultProductPlaceholderIcon is renamed to AutomaticProductPlaceholderIcon (111185321)

Resolved Issues​

  • Fixed: When testing in the sandbox environment, the groupDisplayName property on Product.SubscriptionInfo might return an empty string if the localization in the current storefront is not in an approved state. When using the SubscriptionStoreView without providing a marketing content view, the automatic view might show the name of the app instead of the subscription group’s display name. (107206601)
  • Fixed issue where StoreView or SubscriptionStoreViewcontent might appear in English, or show a localization key, instead of showing localized text for the App Store storefront. (110734447)

Swift​

New Features​

  • Properties of @observable and @Model types currently always require default values or optionality. (109441094)

Swift Charts​

New Features​

  • Enable scrolling in a chart using view modifier chartScrollableAxes(_:). (70444254)
  • Use chartXSelection, chartYSelection and chartAngleSelection to enable selection on a chart. If needed, use chartGesture to override the default gesture for selection. (79083764)
  • Swift Charts now supports creating pie charts and donut charts using the new SectorMark API. (102309263)
  • Pass an AnnotationOverflowResolution to the annotationmodifier to specify how to align an annotation when it would otherwise overflow the bounds of the chart or the plot. (106009062)
  • Use ChartProxy.plotContainerFrame to obtain the visible portion of the plot in a scrollable chart.
    Chart { ... }
    .chartScrollableAxes(.horizontal)
    .chartOverlay { proxy in
    GeometryReader { geometry in
    if let plotContainerFrame = proxy.plotContainerFrame {
    let frame = geometry[plotContainerFrame]
    Path(frame)
    .stroke(.black, lineWidth: 1)
    .allowsHitTesting(false)
    }
    }
    }

    (109675790)

Resolved Issues​

  • Fixed a crash with certain combinations of chart content. (105197081)
  • Fixed an issue where frequent updates to a chart caused unexpected growth in memory footprint. (107611114)
  • Fixed: When a selection gesture goes out of bounds, the selection binding will now be clamped to the nearest data value rather than set to nil. (108398019)
  • Fixed: Improved performance and CPU usage for charts with selection bindings. (108954531)
  • Fixed: Scrolling charts might behave unexpectedly on right-to-left languages. (109129343)
  • Fixed: Improved animations for charts in a widget. (110035011)
  • Fixed an issue where the compositingLayer chart content modifier caused marks with custom symbols to disappear. (110399956)
  • Fixed an issue where the compositingLayer chart content modifier caused annotation boundary resolutions to behave unexpectedly. (112232314)
  • Fixed: Improved performance and CPU usage for scrolling charts with scroll position bindings. (113149095)

Known Issues​

  • Annotations on a scrollable chart might be clipped. (109164195)

SwiftData​

New Features​

  • Existing @Query property declarations might not always correctly infer the model type for predicate and sort descriptor parameters. (Note: the @Query attribute is now resolved as a macro, instead of as a property wrapper.)
    For example, specifying a filter predicate as a parameter to the @Query attribute will now require explicitly providing the model type used in the predicate, i.e. #Predicate<ModelType> { … }instead of #Predicate { … }:
    @Query(filter: #Predicate<Person> { ... }) var people: [Person]

    Another example: passing a sort descriptor or key path will now require explicitly providing the model type used for the root type of the key path, i.e. \ModelType.property instead of \.property:
    @Query(sort: [SortDescriptor(\Person.name)]) var people: [Person]

    @Query(sort: \Person.name) var people: [Person]

    In all cases, the model type used in the filter: and sort:parameters is still required to be the same type used as the element in the query’s wrapped array type, and will emit a build error if not. (109433172)

Resolved Issues​

  • Fixed: Properties with default values are not initialized correctly. (107887871)
  • Fixed: @Query results can appear stale or fail to refresh. (108385553)
  • Fixed: Case value is not stored properly for a string rawvalue enumeration. (108634193)
  • Fixed: Schema migration can fail when nesting non-optional properties inside an optional containing struct. (108854663)
  • Fixed: Properties with .externalStorage are not being stored in peripheral files. (108972391)
  • Fixed: Scene modifier isUndoEnabled does not propagate correctly. (109373617)
  • Fixed: Modeled enum properties with default values won’t compile unless they are fully qualified values. (109421492)
  • Fixed: SwiftData queries will not work with #Predicate { true } and #Predicate { false } will cause a crash. (109425342)
  • Fixed: The default platform container directory is not available on tvOS and accessing it will result in a sandbox violation that causes a crash. (109487314)
  • Fixed: Conflicting writes from other processes sharing the same file can cause a crash. (109488127)
  • Fixed: #Predicate does not support UUID, Date, and URL properties. (109539652)
  • Fixed: @Query using SortDescriptors based on .reversesorting on strings can fail to fetch results. (109572633)
  • Fixed: Creating a @Query with a sortdescriptor that uses a relationship keypath will crash. (109626376)
  • Fixed: willSet and didSet observers will prevent @Model from properly transforming those stored properties and they will not persist. (109664186)
  • Fixed: SwiftData queries don’t support some #Predicate flatmapand nil coalescing behaviors. (109723704)
  • Fixed: Xcode code generation for SwiftData Models from CoreData xcdatamodels will refer to originalName instead of renamingIdentifier. (109782236)
  • Fixed: Unsigned applications using Document API without a proper app container might overwrite the default container. (109784405)
  • Fixed: After deleting an item, SwiftUI might attempt to reference the deleted content during the animation causing a crash. (109838173)
  • Fixed: Custom schema migrations with SchemaMigrationPlan will fail. (110114696)
  • Fixed in beta 7: Apps using SwiftData that are built with Xcode 15 beta 6 have known issues when running on tvOS 17 beta 6. (113971504)

Known Issues​

  • SwiftData models with implicitly unwrapped optional properties will generate a compiler error that all stored properties were not set. (114140139)
    Workaround: Set the value of non-relationship stored properties in the initializer, and mark relationship properties as optional.

SwiftUI​

New Features​

  • RoundedRectangle now defaults to the continuous corner style. (63246947)
  • .onChange has new overloads where the closure takes 0 or 2 arguments, these new versions will call the new version of the closure (i.e. after the specified value has changed), so any captured properties will have up to date values. The previous overload (which calls the old version of the closure) has been deprecated. (67344857)
  • Spring animations will now default to being critically damped (i.e. a bounce of 0). (75149732)
  • Lists using the SidebarListStyle hosted in primary column of a UIKit UISplitNavigationController were previously rendering with an insetGrouped appearance. With this change they will render as the expected sidebar appearance similar to if the Listwere hosted in a SwiftUI NavigationSplitView. (96909195)
  • Use the buttonRepeatBehavior(_:) view modifier to make buttons repeatedly trigger their actions on prolonged interactions. Apply this to buttons that increment or decrement a value or perform some other inherently iterative operation. Interactions such as pressing-and-holding on the button, holding the button’s keyboard shortcut, and holding down the space key while the button is focused trigger this repeat behavior. (102156410)
  • Animation.default now uses a spring animation equivalent to Animation.spring. In addition, Animation.default is now only equal to itself when using ==, allowing users to differentiate between animations that were intentionally chosen and those that use the default animation. (103169056)
  • During gesture change callbacks, velocity will automatically be tracked so that it can be applied to animations that finish when the gesture finishes. (103371523)
  • When two Text are vertically adjacent (for example in a VStack with no spacer in between) SwiftUI will automatically calculate appropriate spacing. To opt-out if this behavior either place a Spacer or specify spacing parameter to the container view. (104782785)
  • For apps built using the macOS 14 SDK, using DismissAction to close a window will default to using DismissBehavior.interactive. (105406945)
  • A NavigationSplitView collapses into a single column in some situations, such as on iPhone, Apple Watch, or iPad in slide-over. When this happens the columns of the split view are arranged into a stack. By default, the split view automatically decides which column appears as the top of this stack based on the contents of the columns. It considers whether any embedded List views have selections and whether any embedded NavigationStack views have non-empty paths.
    NavigationSplitView provides new initializers that give users control over which column of the split view appears on top. Use initializers like NavigationSplitView(preferredTopColumn:sidebar:content:detail:) or NavigationSplitView(preferredTopColumn:sidebar:detail:) and provide a binding specifying the column that should be visible when the split view is collapsed into a stack. When using an app pops the stack, SwiftUI updates the binding. (106241051)
  • When using @Environment(\.self) to capture an entire EnvironmentValues, SwiftUI will now track which properties are accessed to only invalidate the property when those properties change. (106310433)
  • Use the new navigationDestination(item:destination:)overload to present a navigation destination when a bound item is non-nil, or to dismiss the destination when the bound item becomes nil again. (106319528)
  • Shapes now default to mirroring when in a right to left layout direction. (107405880)
  • Changing from one Gradient value to another will now animate, but only once apps are rebuilt against the new SDK. (107408691)
  • All Sections inside List and Table can be configured to be collapsible using new initializers on Section. Previously all Sections inside Lists using the SidebarListStyle received outline disclosure indicators in every header. Section headers will no longer render this control by default. An outline disclosure will only be provided in the header if the Section is initialized with an isExpanded binding to a bool. This bool represents the isExpandedstate of the Section. Sections created with an isExpanded binding inside a Table on macOS will now provide a default outline disclosure indicator to collapse or expand the Section. (107592493)

Resolved Issues​

  • Fixed: NavigationSplitView reuses view controllers in more cases, resulting in significantly improved performance. This might change the behavior of code that relies on the life cycle messages sent to UIHostingController because such controllers will be created less often. (88880547)
  • Fixed: Scroll environment properties like isScrollEnabled and scrollDismissesKeyboardMode are no longer propagated past nested scroll views. (99195890)
  • Fixed: Previously it was possible for views animating their removal via a transition to be drawn above a view with the same zIndex that has not yet been removed. This was unintentional and has now been updated: views transitioning out of the view hierarchy are always drawn below non-removed views with the same zIndex. (101085960)
  • Fixed: LazyVGrid or LazyHGrid has an improved layout when used with fixedSize(). (103075945)
  • Fixed: The new .navigationDestination(item:content:)modifier now works correctly both inside a NavigationStack and outside a stack but inside a column of a NavigationSplitView.
    Inside a stack, setting the bound item to a non-nil value will push a view onto the stack immediate above the view containing the modifier. Setting the bound item to a nil value will pop the view.
    Outside a stack but inside a column of a NavigationSplitView, setting the bound item to a non-nil value will replace the root view of the subsequent column. Setting the bound item to a nil value will restore the original root view. (106106406)
  • Fixed: In some circumstances, the first view pushed onto a NavigationStack or collapsed NavigationSplitView might fail to animate. (106602046)
  • Fixed: When a flexible frame modifier (e.g. frame(minHeight: 100, maxHeight: 200)) is used inside a scroll view the modified view could end up truncating content. This would most often be visible with the content view being a VStack with multiline text. (107014454)
  • Fixed: When scrolling to the end of a scroll view using ScrollViewReader, the final offset will be clamped to the scroll view’s total content size and no longer overscroll. (107558652)
  • Fixed: Removed a spurious warning, “NavigationLink presenting a value must appear inside a NavigationContent-based NavigationView. Link will be disabled.” (107877668)
  • Fixed: ScrollView when used with the searchable modifier has an improved transition when presenting or dismissing search on iOS and iPadOS. (109265624)
  • Fixed: Two NavigationSplitView initializers taking columnVisibility as a value rather than a Binding. (109426553)

Known Issues​

  • On iOS, using an Observable object’s property as a selection value of a List inside NavigationSplitView may cause a “Simultaneous accesses to …” error when a list selection is made via tap gesture. (113978783)
    Workaround: There is no current workaround for Observableproperties. Alternatives include factoring out the selection value into separate state stored outside the object, or using ObservableObject instead.

Symbol Effects​

Resolved Issues​

  • Fixed: In the objective-C API in Symbols.framework, requesting effectWithWholeSymbol on NSSymbolPulseEffect and NSSymbolBounceEffect will result in the effect being configured to animate by layer instead. (109284710)

TipKit​

Resolved Issues​

  • Fixed: Tips and TipKit views will not display on Apple TV hardware. (108286122)

UIKit​

New Features​

  • The query rects passed in to -layoutAttributesForElementsInRect: will be more specific to the collection view’s frame, and the rect might intersect with previously queried frames. If subclassing a UIKit vended layout and modifying the frames of elements by applying offsets, make sure that the same offset is applied to the rect passed in to -layoutAttributesForElementsInRect: as well, or the user might see items disappearing when they shouldn’t be. (108663389)

Resolved Issues​

  • Fixed: Prior to iOS 17 and tvOS 17, UIGestureRecognizer would set its state to UIGestureRecognizerStateFailed in the base implementation of - (void)pressesBegan:withEvent: if there are no active touches. In iOS 17 and tvOS 17, this behavior has been fixed. On tvOS, UIGestureRecognizer allows UIPressTypeSelect by default, thus custom UIGestureRecognizers that do not set allowedPressTypes might have been relying on this behavior to put themselves into a terminal state after they receive a UIPress of type UIPressTypeSelect. UIGestureRecognizers that receive events but do not reach a terminal state will block gesture recognizer dependency graphs from resetting, which can cause an app’s interface to become unresponsive. It is important to for custom UIGestureRecognizers on tvOS 17 to either either set allowedPressTypes to an empty array if they do not handle UIPressTypeSelect, or to implement the UIPressesEvent response methods in UIGestureRecognizerSubclass.h, and set themselves to a terminal state as appropriate. (111175673)

Vision​

Resolved Issues​

  • Fixed: VNDetectHumanBodyPose3DRequest now returns results for images/frames of people without depth metadata or camera intrinsics explicitly provided. (109723859)
  • Fixed issue with cameraOriginMatrix so a 180 rotation around x axis is no longer required. Please reference updated sample code for WWDC Session 111241. (110726503)

Wi-Fi​

Resolved Issues​

  • Fixed: While a Mac has active traffic via Wi-Fi, you might experience difficulty discovering and connecting to Continuity Camera. (109954955)
 
  • Like
Reactions: Pinkyyy 💜🍎
Solver said:
After updating the Apple TV 4K with the latest beta, unplug the Apple TV. Set the remote aside. Plug in the Apple TV. Use the iPhone remote app to select the Apple TV. Where you selected the Apple TV should be the Find option for the remote you set aside.
Click to expand...
Unplugged it, didn’t help. Think it’s still a some have it (unfuntional) some not thing.
 
Solver said:
After updating the Apple TV 4K with the latest beta, unplug the Apple TV. Set the remote aside. Plug in the Apple TV. Use the iPhone remote app to select the Apple TV. Where you selected the Apple TV should be the Find option for the remote you set aside.
Click to expand...
Could not replicate it this way. 🙁
 
Last edited:
On Sonoma the TV app finally shows and even has 4K HDR in the Library sidebar. If a movie is tagged as 4K, it shows up there and (4K) is appended to the movie name in the Finder. This is a new feature.

Why does the 4K movie Still Not appear in the ATV Computers app when it's tagged? When you create a smart playlist of 4K movies, the playlist won't show up in the Computers app. Why?
 
macmac30 said:
I have developed a problem with my latest gen Apple TV with tvOS17 which is connected to a 75" 2019 Samsung TV (UN75RU8000FXZA) with firmware 1401. Sound is directed to a Vizio soundbar with woofer. After several days of watching Youtube, Netflix, Plex, and Apple TV - All sound is missing when I try to watch Netflix or Plex. Apple TV and Youtube apps have sound. If I select a HomePod for sound output, I get sound on that device but not when I switch back to the default. If I reboot the Apple TV, it doesn't help. The fix is to power cycle the TV. What's weird is this TV hasn't had any firmware updates for well over a year but this problem just started a few months ago with tvOS17. Any ideas??? It's hugely annoying! I just installed the latest 354a tvOS17 update.
Click to expand...
I had this issue and found switching out the HDMI cable got my soundbar working again. I’ve had sound issues on and off for months now and it’s only ever with the ATV
 
tehbank said:
Unplugged it, didn’t help. Think it’s still a some have it (unfuntional) some not thing.
Click to expand...
So after some extra testing, the Find option shows up every time my Apple TV remote is "not connected" to my Apple TV 4K second generation using the Remote app on my iPhone 12. It does not show up on an iPad 7 or an iPad Pro 3, both updated with the latest betas.
 
spazzcat said:
RC isn't a GM.

Edit: We should get an RC this week.
Click to expand...
Apple no longer uses the term "GM." Release Candidate has replaced that term.
There will be no release candidate until next week; this does not necessarily mean that there won't be another beta this week, though that is unlikely. The release candidate would likely reveal iPhone 15 features in advance, so it won't be released until the phones have been announced.
 
  • Like
Reactions: Pinkyyy 💜🍎, sos47, Huck and 1 other person
sjsharksfan12 said:
If TVOS updates are minor in scope, why are they officially released with everything else. That basically leads me to the question of why are there 9 betas for a TVOS release. It doesn't seem like this software changes that much and I would think releasing something that is minor first (maybe a week before everything else) would be much better to not overwhelm the servers.
Click to expand...

At the core of all of the non-macOS and non-iOS forks is either macOS and/or iOS. So when they get updates, the whole bunch of the rest of them get updates. There are obviously cores in them shared back to the original two.

And while I'm a massive AppleTV fan and have been since gen 1, the thing just always has some bugs... as evidenced by this seemingly random dropping of audio others report in this thread. Do a search for that and you'll find many more references to the same... so it's not user, not any particular HDMI cable, not <blame anything & everything other than Apple>, etc. Apparently, something in recent updates has caused consistent audio reliability to various HDMI-connected speakers & sounders to have issues for some.

I've not seen it with my own setup but I'm not routing the audio through TV to audio (mine is AppleTV to Receiver and then Receiver splits video to TV and audio to wired speakers). But I've seen enough posts of people with AppleTV to TV to Soundbars (various brands) having issues with audio working fine and then randomly failing. Various reboots- sometimes several times- will make it work again until it fails again. The general theme is that it was not doing this in prior version of tvOS. Given the volume (of people posting) and variety of hardware and cables (generally working fine before recent updates), this is almost certainly a tvOS bug(s). Hopefully Apple fixes it.
 
  • Like
Reactions: Pinkyyy 💜🍎
chrfr said:
Apple no longer uses the term "GM." Release Candidate has replaced that term.
There will be no release candidate until next week; this does not necessarily mean that there won't be another beta this week, though that is unlikely. The release candidate would likely reveal iPhone 15 features in advance, so it won't be released until the phones have been announced.
Click to expand...
While I know Apple no longer uses GM, it is still a standard used in development and a way to state the version that will ship to all end users.
 
HobeSoundDarryl said:
And while I'm a massive AppleTV fan and have been since gen 1, the thing just always has some bugs... as evidenced by this seemingly random dropping of audio others report in this thread. Do a search for that and you'll find many more references to the same... so it's not user, not any particular HDMI cable, not <blame anything & everything other than Apple>, etc. Apparently, something in recent updates has caused consistent audio reliability to various HDMI-connected speakers & sounders to have issues for some.
Click to expand...
The dropping of Audio, is that an Apple TV thing or a Homepod thing. I get a lot of the audio dropping and a message saying Airplay can't connect to the speaker, try again. I always thought that was an issue with the Homepod. I really haven't seen that many bugs with the Apple TV, or I don't know what to look for.
 
Won't be holding my breath that this will finally fix the "you haven't purchased any movies or TV shows" in the library section of the TV app, even though I own 2,700+ movies, and x,xxx TV shows.
 
  • Wow
Reactions: Pinkyyy 💜🍎
sjsharksfan12 said:
The dropping of Audio, is that an Apple TV thing or a Homepod thing. I get a lot of the audio dropping and a message saying Airplay can't connect to the speaker, try again. I always thought that was an issue with the Homepod. I really haven't seen that many bugs with the Apple TV, or I don't know what to look for.
Click to expand...
Lots of search results point to a new AppleTV bug and it affects various speaker types including soundbars of various types and brands. Obviously there’s a wide variety of cables linking them, so the “solution” of new HDMI cable is not necessarily a remedy for all, even if some say it has solved it for them.
 
Last edited:
  • Like
Reactions: Pinkyyy 💜🍎
Alan Gordon said:
Won't be holding my breath that this will finally fix the "you haven't purchased any movies or TV shows" in the library section of the TV app, even though I own 2,700+ movies, and x,xxx TV shows.
Click to expand...

Bail on the TV app- which mostly revolves around selling or renting you something- and try the Computers app instead. It might solve that one. If so, let us all know.
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back