Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved Missing Custom Tones in iOS 17 [MERGED]
- Thread starter FireFish
- Start date
-
- Tags
- ios 17
- Sort by reaction score
I'm guessing it'll get fixed in a next major build (maybe 17.1, maybe 17.0.3)? 17.0.2 was weird in that it was released today for almost all devices, but has been out for iPhone 15/15 Pro since last Thursday, alongside 17.0.1. That seems like way too short of a turnaround for it to get fixed.
I'm guessing if you really want to see progress, get on the public beta cycle and then see if/when it appears there?
I'm a developer who is on the public beta cycle and development build cycle.
Frankly, it worked as one would expect during the BETA build releases and it wasn't until the public release that they broke it.
It's also custom tones. I made mine and imported them. Not one tone that I put on my phone has an analog in the tone store. Lets hope they don't just fix it for purchased tones.
Strange that this wasn’t an issue on all of the iOS 17 betas all summer.
Seems like a long turnaround for something like this. My Mom even texted me asking why her custom tone for me wasn't listed anymore. She saw it on my Contact Card but then when she went to try another one to test and then go back to her custom tone, it's gone... Maybe us "tech savvy" folks here in these forums would understand that this might be a bug or that Apple might fix this, but at least one 75 year old woman thinks Apple just doesn't want that as an option because she did the update and Apple removed it. I told her it's probably a bug, she said yeah sure.
My apologies on that—thanks for your work so far! It seems that there was a lot of "why didn't Apple fix _" posts with iOS 17.0.2 today, even though it's been out for a few days for 15/15 Pro users. My guess is that it was released so that all devices are on similar builds going forward, which may help track progress of this.
Then again, I've been following the Apple Watch battery drain/Weather issues and the Series 9/Ultra 2 got 10.0.2 today, while the others are on 10.0.1. 10.0.2 doesn't seem to have really fixed the Weather issue, but I'm betting we'll see a similar "this didn't work" once they bring all the other Watch models into the same release cycle.
It feels a bit weird, as there have always been device-specific updates with new devices, but generally Apple has skipped that release for everyone else.
I gave them some feedback, and I wasn't nice. 
Also, does anyone else notice that the iOS version drop-down on the feedback page never lists the current iOS version? It's always behind. Today, the latest version is 17.0 (yesterday, it was 16.6):
![Apple_feedback_iOS_version.JPG]( "Apple_feedback_iOS_version.JPG")
Anyway, I'm going to try the HowToGeek method to see if I can get the tones back on the phone - it's how I got them on there to start with, 3-4 years ago. I use a bunch of old BlackBerry tones for emails, texts, meeting announcements, etc. (I used a Curve 8900 from 2009-2013) because they're very short, versus Apple's long and generally annoying tones.
Also, does anyone else notice that the iOS version drop-down on the feedback page never lists the current iOS version? It's always behind. Today, the latest version is 17.0 (yesterday, it was 16.6):
Anyway, I'm going to try the HowToGeek method to see if I can get the tones back on the phone - it's how I got them on there to start with, 3-4 years ago. I use a bunch of old BlackBerry tones for emails, texts, meeting announcements, etc. (I used a Curve 8900 from 2009-2013) because they're very short, versus Apple's long and generally annoying tones.
This seems like an easy bug for for Apple to fix. In the meantime, there is a workaround that a lot of people have verified works:
. I've verified it works on iOS 17.0.1.
It’s great that a workaround does work, but only us geeks would be able to or even attempt this. If this was never an issue in all the iOS17 betas then something Apple changed for whatever reason caused it. As I tell many I know who complain about this, submit feedback to Apple.
All of my custom (self-made) tones are still on my phone as ringtones - all that needs to be done is let us choose ringtones as alert tones again, a la pre-iOS17RC
iOS 17.1 beta 1 has removed the new tones and allows use of custom alerts again. I would imagine they will add the new sounds back in a later beta to use in addition to the custom sounds. Hopefully they are making all the new tones louder.
I can finally assign my custom text messages tones to specific contacts.
The new iOS 17.1 beta seems to have rolled back the sounds to the way they were before as the new sounds are gone and custom tones work. I wouldn't consider it fixed until the new sounds are re-added without breaking anything else but it's looking positive.
I agree. But it is a really positive sign that Apple rolled things back, because it suggests that the change to not allow custom text tones was either accidental (my assumption) or they are rethinking that change. How hard could it be to add the new ringtones/alert tones and also allow people to select custom text tones?
Apple had already split the branch of 17.1 off before the 17.0RC released. More than likely they will have the new tones merged back in, in beta 2 or 3.