Assuming you’re living in a country with decent consumer rights laws, I’d return the device to the seller. It’s no longer fit for purpose.
Apple TV prompt requires another Apple device
21–30 of 345 posts
Re: Apple TV prompt requires another Apple device
#22Earlier quoted context omitted.
You're missing the point though. The device should be usable on its own. This is extremely anti-consumer, it doesn't matter if there's a simple solution
These devices are pointless "on their own". What would an Apple TV do without any external dependencies? Play the pre-loaded screen savers?
Re: Apple TV prompt requires another Apple device
#23Apple won't let you use "find my device" on airpods unless you have an iPhone either, iirc. Its shitty behavior, but sadly unsurprising.
Re: Apple TV prompt requires another Apple device
#24[flagged]
Re: Apple TV prompt requires another Apple device
#25Apple won't let you use "find my device" on airpods unless you have an iPhone either, iirc. Its shitty behavior, but sadly unsurprising.
Re: Apple TV prompt requires another Apple device
#26Re: Apple TV prompt requires another Apple device
#27Re: Apple TV prompt requires another Apple device
#28I saw the tweet and assumed it’s just an annoying prompt but doesn’t impede functionality. Does he say he can’t use the Apple TV?
Re: Apple TV prompt requires another Apple device
#29(I should note that clicking on the remote causes the annoying message to disappear, then repeat once, then goes away for...a day? Long enough to watch whatever I wanted to watch, anyway.)
Re: Apple TV prompt requires another Apple device
#30Earlier quoted context omitted.
These devices are pointless "on their own". What would an Apple TV do without any external dependencies? Play the pre-loaded screen savers?
What? You can watch Netflix, Hulu, Disney+, and do a ton of other things that absolutely don’t require an iOS or macOS device to activate it.
Worse, you need a working payment method with Roku to use the device.
Personally, I find that a bit more egregious. EDIT Nevermind this last bit. I didn't see that the top level workaround... doesn't work around the issue.