... also handy for making sure parallax or other similar button motion is working correctly. AFAIK, there is no way to "wiggle" or swipe in Device Hub for Apple TV...

I figured out the problem was that I had a custom button class with pressesBegan:withEvent:. When working on an actual keyboard (now required with Xcode 27 Device Hub since they removed the virtual Siri Remote), I needed to add a [super pressesBegan:presses withEvent:event]; in the class method for the Apple TV Simulator to work normally.

The navigation issue seems to be related to parallax buttons. Once focus is on a custom button configured in code for parallax, I can no longer navigate away from the button. I should also note this is an older project with Objective C code.

This is testing in my own app. Details in FB report #FB24589446

Same in tvOS 27

Hi - thanks for asking. My app will download a JSON file which contains a list of image urls which are downloaded and stored in the NSCachesDirectory. I understand the NSCachesDirectory can get deleted by the OS when the app is not running, so on subsequent launch, the app will check for the presence of these files in NSCachesDirectory and will redownload them if they are not available. This has worked pretty reliably in production for nearly two years. With tvOS 26, there are now inconsistent and sporadic instances when the app exhibits behavior as if these files have been deleted. ie. the images are either missing from the playlist page, or the app uses an onboard backup "failsafe" JSON file to populate a playlist with temporary data if it cannot find or load the JSON file. I suspect something is getting corrupted because once this issue occurs, the only way to get the app to perform normally again is to delete and reinstall the app. Simply relaunching the app will not fix the issue, as programmed in my app logic and used with success up to this point. I realize this info is still pretty vague but I am pressed to recreate this issue aside from letting the app "sit" in the background for hours & days during normal Apple TV usage. Is there any way I can trigger tvOS 26 to force-quit my app while it is in the background so I can perform some additional testing? Thanks.

Be sure to file a bug report with Apple. Despite filing my report and sample project over a year ago, the file says there are "no similar reports." I wonder if I should copy and re-submit my original report as the title mentions tvOS 18...?

Here you go, under "Edit Subscription Renewal Rate": https://developer.apple.com/help/app-store-connect/test-in-app-purchases/manage-sandbox-apple-account-settings/

Looking like StoreKit UI will not load or respond in tvOS 18.2 unless there is a Navigation Controller present AND you ONLY use a Push segue to get to your paywall viewController. Been playing with adding a Navigation controller and hiding the tabBar in code on subsequent viewController push (as a workaround), but the push animation is not in time with the viewController. (Not as smooth a visual transition)

Update 11-14-24; I have determined this failure occurs when the paywall (which calls the purchase(options:) method in my "store manager" class) is not a primary viewController window. ie. Tab Bar Controller -> 1st viewController as paywall DOES work. Tab Bar Controller -> 1st viewController -- --> 2nd viewController as paywall DOES NOT work. Any clues or insight why this may be happening would be greatly apprecaiated. Thanks!

Additional info: From my own paywall viewController: try await store.makePurchase(productToPurchase) And in my NSObject store helper class: func makePurchase(_ product: Product) async throws { let result = try await product.purchase() //ERROR OCCURS HERE (See error message below) Xcode Console message: "Could not get confirmation scene ID for [insert my IAP id here]" Why is the is tvOS 18.2 API looking for a scene ID? (Again, works fine for 18.1 and on iOS 18.2)

UPDATE: This is a Simulator bug. tvOS 18 tab bar appears at correct y coordinate on physical device/actual TV screen.

PS. Feedback case number is FB14835294

I have the same issue. But it works perfectly fine with Xcode and sandbox users, so I figure it must be a problem with TestFlight (which is what the reviewers user, no?) At any rate, I figure if I get a rejection, I will pull the feature and use the old-fashioned "manage subscription URL" instead.

Any progress on this? I have a subscription which I submitted too early (new app business model) and now it is locked. I uploaded a new binary, but am not sure how to "unlock" the subscription so I can add it to the app to submit for review...