Apple has sent an email out to developers informing them that iTunes Match music libraries in iCloud will once again be wiped on Thursday, October 27th. Apple instructs developers to turn off iTunes Match on their computers and iOS devices during that time.
The wipe may be in preparation for the public launch of iTunes Match. The service was originally to be launched alongside iOS 5 but was pushed to the "end of October". iTunes Match remains in beta testing with developers, and there's been evidence that Apple has been quietly preparing for its public launch.
Last week, an iTunes Match toggle has appeared in the iOS 5 Music Settings pane, which directs users to subscribe to the service using iTunes. Apple has not yet publicly released an updated version of iTunes that allows users to sign up for this feature.
iTunes Match is a $25/year subscription service that will match your existing iTunes library with 256-Kbps versions in the iCloud. These songs will become available for download on your other Macs or iOS devices through iCloud.
Here’s how it works: iTunes determines which songs in your collection are available in the iTunes Store. Any music with a match is automatically added to your iCloud library. Since there are more than 20 million songs in the iTunes Store, most of your music is probably already in iCloud. All you have to upload is what iTunes can’t match. Which is much faster than starting from scratch. Once your music is in iCloud, you can stream and store it on any of your devices. Even better, all the music iTunes matches plays back from iCloud at 256-Kbps AAC DRM-free quality — even if your original copy was of lower quality
I hope for all Itunes Match users' sake that Apple is fixing this screwed-up system so that non-destructive upgrades are supported.
It's "amateur hour" to have to wipe the database for an upgrade.
This isn't even tolerable for the beta - non-destructive upgrades should have been designed in from day one.
You were told this from day one. It's a DEVELOPER PREVIEW, and Apple consistently states that you should never use developer environments for production data. Besides, for buying into the Dev version Apple gave you 15 months for the price of 12. Quit your childish whining.
But why, unless you're more concerned with the logo on a product than its specs and performance?
Oops, never mind, Apple forum.
That's churlish troll talk. Can you give it a rest?
----------
I completely disagree.
If you plan to support upgrades in the product, the Beta should support and test upgrades.
Anything less is lazy programming.
If your tools can't move the beta database to the production servers without "porting problems over", then your tools are bad.
"Itunes Match" has "train wreck" written all over it - how many times have they wiped the database to date? Why should we not take that as a warning that the design has fundamental flaws?
Spoken as someone who definitely doesn't rely on a dev/production model to make his living...
I hope for all Itunes Match users' sake that Apple is fixing this screwed-up system so that non-destructive upgrades are supported.
It's "amateur hour" to have to wipe the database for an upgrade.
This isn't even tolerable for the beta - non-destructive upgrades should have been designed in from day one.
Dude, you don't even know what they are doing. Maybe they are moving to production servers and don't want to have problems ported over that may have sprung up during testing. You always want to go to a clean slate when you are going from Beta to Production.
Actually, detecting duplicate playlists would be rather simple.
Have you ever written code using an "IF" statement?
And you don't know about the software that I wrote that you use every day, nor about the patents that I have been granted, or how to design maintainable software. (Hint: if you intend to support upgrading the released software - consider supporting upgrades of the alpha software. By the time it reaches beta, you'll have it working.)
You may write software, but I do QA for a living. If you guys wrote flawlessly from the start, I wouldn't have a job. So thanks. :)
I'm not surprised Match is being wiped several times. We often have our backends reset when we migrate from Alpha->Beta->Live, and we're not even a large outfit.
Actually, detecting duplicate playlists would be rather simple.
Have you ever written code using an "IF" statement?
Ha, you make me laugh! The "if" statement? Really?
It is not that simple, not only would you have to create playlist objects but check the data in that playlist object to make sure it is the same, and within that data (songs) there is more that you have to compare to make sure it is the same object. And when you are comparing lets say 30 songs per playlist, with 20 playlists, and 1,000 duplicates you are creating > 600,000 "if" statements for a single user. (You obviously wouldn't use an if statement) And that is just going by lets say a track name. If you have to compare 2 tracks in order to see if it is the same song you would have to compare at least 5 more things. (Title, artist, time, composer, release date, other) and that would make > 3,000,000 comparisons.
This is just some stupid example I made up.
If your tools can't move the beta database to the production servers without "porting problems over", then your tools are bad.
You have no idea what you are talking about, if during development you have a bug that replicates a users playlist 1,000 times you DO NOT want to bring that data over to a production server. It would be almost impossible to port the data over reversing the effects of the bug.
Spoken as someone who definitely doesn't rely on a dev/production model to make his living...
Just ignore him, obviously he is not a developer or knows anything about programming.
Tuesday October 24, 2017 2:03 pm PDT by Juli Clover
A bug in the built-in Calculator app in iOS 11 is getting some major attention this week, despite the fact that it's been around since iOS 11 was in beta testing.
At issue is a calculator animation that causes some symbols to be ignored when calculations are entered in rapid succession. You can try it for yourself: Type 1+2+3 and then the equals sign into the Calculator app quickly.
Due to...
Apple has been involved in a long-running iPhone trademark dispute in Brazil, which was revived today by IGB Electronica, a Brazilian consumer electronics company that originally registered the "iPhone" name in 2000.
IGB Electronica fought a multi-year battle with Apple in an attempt to get exclusive rights to the "iPhone" trademark, but ultimately lost, and now the case has been brought to...
With the launch of Apple's iPhone 13 lineup believed to be just a few weeks away, we have compiled all of the coherent rumors from our coverage over the past year to build a full picture of the features and upgrades coming to the company's new smartphones.
For clarity, only explicit improvements, upgrades, and new features compared to the iPhone 12 lineup are listed. It is worth noting that...
To commemorate the tenth anniversary of the iPhone, Apple marketing chief Phil Schiller sat down with tech journalist Steven Levy for a wide-ranging interview about the smartphone's past, present, and future.
The report first reflects upon the iPhone's lack of support for third-party apps in its first year. The argument inside Apple was split between whether the iPhone should be a closed...
The iPhone 13 will feature low earth orbit (LEO) satellite communication connectivity to allow users to make calls and send messages in areas without 4G or 5G coverage, according to the reliable analyst Ming-Chi Kuo.
In a note to investors, seen by MacRumors, Kuo explained that the iPhone 13 lineup will feature hardware that is able to connect to LEO satellites. If enabled with the relevant...
New MacBook Pro models are coming at WWDC, according to leaker Jon Prosser who has a mixed track record when it comes to predicting Apple's plans.
Subscribe to the MacRumors YouTube channel for more videos. Prosser provided no additional information, but there are new 14 and 16-inch MacBook Pro models in the works. The new MacBook Pros will feature the most radical redesign to the MacBook Pro ...
A normal-looking Lightning cable that can used to steal data like passwords and send it to a hacker has been developed, Vice reports.
The "OMG Cable" compared to Apple's Lightning to USB cable. The "OMG Cable" works exactly like a normal Lightning to USB cable and can log keystrokes from connected Mac keyboards, iPads, and iPhones, and then send this data to a bad actor who could be over a...
The iPhone 12 and iPhone 12 Pro arrived last October in a range of color options, with entirely new hues available on both devices, as well as some popular classics. The 12 and 12 Pro have different color choices, so if you have your heart set on a particular shade, you might not be able to get your preferred model in that color.
iPhone 12 mini and iPhone 12
The iPhone 12 mini and iPhone 12...
The finish line is in sight! Apple's annual iPhone event is likely just a week or so away and all eyes will be on the company as it unveils the next version of its most popular product line. With any luck, we'll also see the next-generation Apple Watch and perhaps even some new AirPods.
Other news this week saw Apple making some more changes to its App Store policies in response to a...
The upcoming 14-inch MacBook Pro is set to be more expensive than the current 13-inch MacBook Pro and both the 14 and 16-inch models will offer the same performance, according to the leaker known as "Dylandkt."
The leaker shared the information on Twitter, explaining that both of the upcoming MacBook Pro models, expected to come in 14 and 16-inch sizes, will feature the same performance due...
When Apple released iOS 14.5 in April, it introduced the ability to unlock your iPhone with Face ID while wearing a mask, as long as you are wearing an Apple Watch. Here are some troubleshooting tips.
New features for FaceTime calls, tools to reduce distractions, a new notifications experience, added privacy features, complete redesigns for Safari, Weather, and Maps, and more.
/article-new/2011/10/match_email.png?lossy "match_email")
/article-new/2011/10/itunes_match-500x314.png?lossy)
Top Rated Comments
You were told this from day one. It's a DEVELOPER PREVIEW, and Apple consistently states that you should never use developer environments for production data. Besides, for buying into the Dev version Apple gave you 15 months for the price of 12. Quit your childish whining.
That's churlish troll talk. Can you give it a rest?
----------
Spoken as someone who definitely doesn't rely on a dev/production model to make his living...
Streaming AND downloading.
Dude, you don't even know what they are doing. Maybe they are moving to production servers and don't want to have problems ported over that may have sprung up during testing. You always want to go to a clean slate when you are going from Beta to Production.
You may write software, but I do QA for a living. If you guys wrote flawlessly from the start, I wouldn't have a job. So thanks. :)
I'm not surprised Match is being wiped several times. We often have our backends reset when we migrate from Alpha->Beta->Live, and we're not even a large outfit.
Ha, you make me laugh! The "if" statement? Really?
It is not that simple, not only would you have to create playlist objects but check the data in that playlist object to make sure it is the same, and within that data (songs) there is more that you have to compare to make sure it is the same object. And when you are comparing lets say 30 songs per playlist, with 20 playlists, and 1,000 duplicates you are creating > 600,000 "if" statements for a single user. (You obviously wouldn't use an if statement) And that is just going by lets say a track name. If you have to compare 2 tracks in order to see if it is the same song you would have to compare at least 5 more things. (Title, artist, time, composer, release date, other) and that would make > 3,000,000 comparisons.
This is just some stupid example I made up.
Good try.
You have no idea what you are talking about, if during development you have a bug that replicates a users playlist 1,000 times you DO NOT want to bring that data over to a production server. It would be almost impossible to port the data over reversing the effects of the bug.
Just ignore him, obviously he is not a developer or knows anything about programming.