ITunes 11.4 bug when used with OS 10.6.8 - won't sync or backup iPhone

Question

I actually just wanted to post this in case Apple monitors these boards. iTunes 11.4 says it's compatible with OS 10.6.8 or later, but there is a bug in it when you're running OS 10.6.8 that prevents you from backing up or synching your iPhone (in my case, a 5s). Doesn't matter what iOS you're running. If you attempt to backup in iTunes 11.4, it immediately ends the backup and only displays "Other" content being stored on your phone. Also, the "Sync" button is greyed out, so you can't even attempt to sync.
No amount of restoring (even a DFU restore) or reinstalling iTunes 11.4 will fix this. The solution is to delete iTunes 11.4 and its related files and to reinstall iTunes 11.3.1, at least until Apple gets the bug corrected. After hours of restores trying to resolve it, I followed this process and it completely solved my problem in about ten minutes. I found the solution with instructions in this thread:
Upgraded to iTunes 11.4 and now it won't sync my iPhone 5s-sync button is greyed out.
Thanks to cwa2, enee and Zak for supplying the solution. I've also summarized the steps here.
(1) Use this link to download a copy of iTunes 11.3.1:
http://www.v3.co.uk/v3-uk/download-review/1957301/apple-itunes-for-mac-1110
(2) Delete the following iTunes 11.4 components (they will be replaced when you install iTunes 11.3.1) by dragging them to the Trash:
/Applications/iTunes.app
/Library/Frameworks/iTunesLibrary.framework
/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/MobileDevices.bun dle
/System/Library/Extensions/AppleMobileDevice.kext
/System/Library/Extensions/AppleUSBEthernetHost.kext
/System/Library/PrivateFrameworks/AirTrafficHost.framework
/System/Library/PrivateFrameworks/CoreFP.framework
/System/Library/PrivateFrameworks/DeviceLink.framework
/System/Library/PrivateFrameworks/iTunesAccess.framework
/System/Library/PrivateFrameworks/MobileDevice.framework
(3) Some people have had trouble seeing the contents of the CoreTypes.bundle to get to the MobileDevices.bundle. You can access it this way:
In the Finder, select Go To Folder under the Go To menu (or Shift+ Cmd+ G)
Type in: /System/Library/CoreServices/CoreTypes.bundle/Contents/Library/
The MobileDevices.bundle will be displayed; drag it to the Trash.
(4) Empty your Trash.
(5) Install iTunes 11.3.1, and go back to living your life. Remember, do not upgrade to iTunes 11.4 again until you're certain the bug has been resolved.

Answer 1

In Reply to all fellow Apple fans: It is great that someone found a work-around to the iTunes 11.4 no syncing problem. I think that is fine for the short term. And  I am really glad that we customers have a forum to share information and experiences regarding Apple's products. However, as someone here said, we are all customers; and posting a problem here "IN HOPES THAT APPLE READS THESE POSTS" is NOT a way to resolve this issue or any issue.
PLEASE CONTACT APPLE: Apple Service Center: 1-800-275-2273   - Once you get a ticket number then and only then is this documented and then Apple can follow-through and alert the engineers who will fix this.
The "CWA2" work-around band-aid does several things in addition to reverting back to iTunes 11.3.1. :
1) It ensures that Apple continues to know nothing of the problem.
2) It ensures that the faulty code that is within 11.4 remains there and is perpetuated into future versions.
3) It ensures that YOU can never upgrade to future versions. (If the resident faulty code remains and perpetuates)
So once you have reverted back to 11.3.1, the problem APPEARS to have gone away (FOR YOU) but you have not solved the problem.
Again, respectfully,
1) Sending feedback to apple (using the "Report Bugs To Apple" menu item in Safari will get the information to someone, somewhere and add it to the pile of issues, complaints, suggestions, etc.
2) CALLING the Apple service/support Center at  1-800-275-2273 will put you in touch with a real APPLE person who will begin the process of documenting and forwarding this issue on to those who will fix it.
and
3) emailing Apple directly will make sure that they get the information.
lets get this fixed !!!!!!!!!