Fixed in a later rev of tvOS.

Note that my App, built 2 years ago, does print plaintext OK, on Mac Catalyst and iOS. It’s only when re-compiled today using Xcode 15.2 on Sonoma that printing fails, on Mac Cat and iOS BTW. On print failure this is what my App's traceback looks like: #0 0x00000001b070ee34 in _UITextViewEnablingCompatibilityMode () #16 0x000000022a343348 in -[UIPrintInteractionController presentFromRect:inView:animated:completionHandler:] () #17 0x0000000102845518 in __23-[Common printTextView]_block_invoke_2 at /Users/sol/Private/Developer/ ... Poking around further I see this: 0x1b070eec0 <+140>: add x3, x3, #0x286 ; "UITextView %{public}p is switching to TextKit 1 compatibility mode because its layoutManager was accessed. Break on %{public}s to debug.” This was a trigger, because 2 years ago when the App last went on the App Store I found that I could only print plaintext files, not HTML, so I settled on using as the print formatter an instance of UISimpleTextPrintFormatter. So I just switched to UIMarkupTextPrintFormatter, and, amazingly, it worked, no crash. Of course plaintext files look pretty ugly, but HTML now works and looks great. This hack for plaintext works for me, YMMV: printText = [printText stringByReplacingOccurrencesOfString:@"\n" withString:@"<br>"];

Yes, yes, yes. On all accounts except that my images come (came) from Affinity Photo. My 3-layer images have worked for years, but now fail, in various, inconsistent, mysterious ways. Thank you for reporting this. The version on the App Store works, with the identical assets. (Aside: I've stopped working on this and moved on to my screen saver, but its location services no longer work. So I stopped working on that and moved onto a Mac catalyst app, but it also no longer works either, been a rough week here.) I spent a lot of time working on this but have no good news for you, it previews just fine in Xcode and Parallax Viewer. I tried even more layers to no avail. I don't have the nerve to put the tvOS App up for review, I want the iOS and macOS versions to be consistent.

I see behavior as well. And FYI location services appears to be broken: no delegate methods are ever called, which grounds my saver completely.

SOB! I've been trying to debug this on many catalyst apps for months - many thanks to you. What I do to see the help book is archive the maccat app, then export using the Copy option, then drag that copy to Applications. This is required for every change to the help book. While I'm ranting about recent maccat changes, you can no longer use Credits.html for your About box info, that file must now be rich text Credits.rtf.

Sample project which runs perfectly on iOS 14/15 on simulator and device, fails on tvOS 15 on device only, else works on simulator, and for tvOS 14 works on device and simulator: secureHTTP / www dot bigcatos dot com / Downloads / SettingsTestFail.zip

Hmmmm, guess I cannot post a URL to the Xcode project? How do I do that ...

I have a small Xcode project with two targets: tvOS and iOS. The iOS build works on the simulator and device. The tvOS build works on the simulator but not a device running tv OS 15. It does work properly on a tvOS 14 device. [SettingsTestFail.zip) When run all the code does it store an NSUserdefaults value which is then displayed in a UILabel. This value should be reflected in the Settings App for the test App, SettingsTest. The value will match what is diplayed for iOS, tvOS simulator, but not tvOS device.

Just to highlight my comment above, the pictures in question are not in a Shared album.

Thanks for your response. I have an HP-25c simulator and I'm trying to replicate its BCD results. Doubles work, mostly, NSDecimalNumber works better in some situations, but obviously not here. I just assumed NSDecimalNumber would magically work better, but it may be that is true only for "small" numbers less than e+-13 or so, more experimenting required.

The suggested solution works, but I notice that icons are no longer rounded. I assume that the previous behavior was inherited from iOS, and that if you want round macCat icons you do it yourself.

Thank you KMT, my forum hero, for listening. I would assume it had to have been a mistake, but nevertheless I made a movie that showed me connecting to my DNS providers record for my "company", which showed my name as owner of the domain. I moved on to my hosting provider and showed all the Apache configs and files that are served and that clearly showed all the web content related to the App in question. I did not go so far as to film the Xcode project. And that worked, the tvOS App was just approved. I've had my fair share of review rejections (rightly!) over the years but this one was, well, just different. Had the movie failed I suppose I would have appealed, something I've never had to do. Thanks again.

I wasn't particularly clear in my previous reply, here is the important fact: but the key is an App prefix that is not the same as the Team ID If the App prefix matches the Team ID then no entitlement (apparently) prohibits a MacCat App from uploading to Connect. However, Apps with a non-matching App prefix / Team ID will not upload when certain entitlements are present - I know iCloud is one such entitlement, and now it appears that there are others. And this is a relatively recent change, because prior to the June-ish timeframe this scenario worked - perhaps the recent App Connect upgrade is the cause?

I have the exact same issue, and have been unable to upload a new App version since June. After much work, this is my latest reply to DTS: I've pretty much confirmed it's the iCloud entitlement that is the root cause of the problem. I have absolutely no idea how to fix it. You may recall I wiped my MacBook Pro's disk and did a fresh install of Catalina. I copied my unmodified *** workspace over and, as always, the *** App upload failed. I then simply deleted the iCloud entitlement and the upload works. Image 1) show the entitlements file diff, with the original in the right pane, and 2) shows a successful upload. So maybe the issue is: Mac Catalyst App iCloud entitlement ( fails even without kvstore checked ) old fashioned App prefix which does not match Team ID I too have no idea how to proceed, but the key is an App prefix that is not the same as the Team ID. This App is from a project created 11 years ago.

Same issue here. "Fixed" it by deleting all screenshots and re-uploading. Painful, but you can right-click an image in the Connect record then Save Image As to a folder, I named them f1.png ... f10.png, saving you from having to actually re-created the images. My App is now waiting for review.