|
|
|
|
#1 | |
|
Apple Says iOS 6.1 Exchange Bug Fix is on the Way
![]() Just a day after Microsoft offered workarounds for an iOS 6.1 Exchange syncing bug and said that it was working with Apple on a solution, Apple has announced on its support page*(via ZDNet)*that it has identified the problem and is working on a fix. ![]() Quote:
The bug, which caused iOS 6.1 devices to continuously loop when syncing a recurring calendar meeting invitation to Microsoft Exchange, isn't the first bug to stem from the two-week old iOS 6.1. iPhone 4S users were affected by a bug that hampered 3G performance, although that was fixed with Apple's release of iOS 6.1.1 a couple of days ago. There is no timeframe for when the fix for the Exchange bug will be released. Article Link: Apple Says iOS 6.1 Exchange Bug Fix is on the Way |
||
|
|
0
|
|
|
#2 |
|
Lets hope the jailbreak still works.
|
|
|
|
3
|
|
|
#3 |
|
Why would it randomly stop working? The only way it will stop working is if you blindly update.
__________________
There is but one truly serious philosophical problem and that is suicide.
|
|
|
|
0
|
|
|
#4 |
|
|
5
|
|
|
#5 |
|
Yes, I know... but everyone keeps asking that every time there's an update announcement. It's becoming akin to "Safari feels snappier!" =\
__________________
There is but one truly serious philosophical problem and that is suicide.
|
|
|
|
5
|
|
|
#6 |
|
How about a fix for the Mountain Lion Calender Exchange bug that's been going on for ages?
http://forums.macrumors.com/showthread.php?t=1433698 https://discussions.apple.com/thread...art=0&tstart=0 |
|
|
|
0
|
|
|
#7 | |
|
Quote:
It's absolutely nothing like 'Safari feels snappier'. If someone has a jailbroken device and has the exchange bug they need to update to fix the bug - but if that means they lose the jailbreak, where do they stand? |
||
|
|
5
|
|
|
#8 |
|
Maybe he is effected by this bug and wants a jailbreak?
__________________
I wish more wireless service provider owners posted here so talk about tethering would be taboo too. .....Theft is Theft....
Last edited by stridemat; Feb 14, 2013 at 06:38 AM. Reason: Removed insult |
|
|
|
6
|
|
|
#9 | |
|
Quote:
And I should ignore the comments about these comments...
__________________
But it does me no injury for my neighbor to say he has an Android phone, an iPhone or no phone. It neither picks my pocket nor breaks my leg. - Thomas Jefferson |
||
|
|
1
|
|
|
#10 |
|
What type of issues are folks having? I have not notice anything on my 4s.
|
|
|
|
0
|
|
|
#11 |
|
We have 7,000+ users on our Exchange 2010 server (fully up to date). Plenty of iOS 6.1/6.1.1 devices.
Not a single eyebrow has been raised in regards to iOS 6.1/6.1.1 acting any "different". No issues to report, apparently. No increase in traffic, no change in expected functionality, etc. That being said, the admins have said that iOS has never really worked right, and that your should treat your calendar as read only when using iOS. Example situation (verified yesterday): 1) User A creates a recurring event with Outlook, User B and User C are invited. They receive the event confirmation and accept. User A receives acknowledgement of the acceptance from both users. 2) User A later remembers an important detail and updates the recurring event with their iOS device. 3) User B and User C receive an invitation to a "new" recurring event. Similar to the original, but with the new details. This is saved to their calendar as a second event, right next to the first. They accept the event confirmation again. 4) User A receives the acceptance confirmations for the event, but still sees it as just event #1. User B and User C see event #1 and event #2. Expected behavior: iOS devices should update just event #1 (the original), and never create event #2. |
|
|
|
4
|
|
|
#12 |
|
Calendars and Exchange in iOS has always been buggy. Updates don't work right. Accepting events often don't seem to register with the exchange server. As someone else stated, iOS calendars should be used as a read only service.
__________________
That's "Geniuses," not Genii, genius. To err, is PC. |
|
|
|
0
|
|
|
#13 |
|
So, has there been a recent IOS update that didn't break Exchange connectivity?
I understand that in Cupertino they probably all use Apple and unix servers. But the rest of corporate America we use Microsoft exchange and Active Directory on Windows servers. If apple expects to continue to penetrate the corporate market they need to get their act together. |
|
|
|
0
|
|
|
#14 |
|
APPLE: While you're at it, can you return the swoosh sound to *AFTER* negotiation has completed with the smtp server where it should be, and where it used to be with iOS5.
It's annoying and illogical to hear that sound, only to find the send failed later. The swoosh sound before smtp negotiation gives you the false sense the message sent successfully. Anyone else want this restored to where it should be? .
__________________
'10 MBP 13 iP 4S, iP 4, iP 3GS 2G iPod Touch 5G iPod nano 2G aTV Newton 110
|
|
|
|
0
|
|
|
#15 |
|
We've been having active sync issues since iOS 5 - getting about forty times the volumes of transaction logs we should do on Exchange 2010.
I've had a call logged with Microsoft and we've proved it's the iPhones causing it but they basically washed their hands of it after several months of back and forth. I'm in the process of upgrading everyone to 6.1.1 to see if that clears it. If not we may be going for Windows phones next time round
|
|
|
|
1
|
|
|
#16 |
|
This is not the only repeat major security bug in iOS 6.1! I found one last night. You can use universal search to find iMessages that have been deleted!
I was shocked when I found it. I have reported the issue to all the tech sites. I hope one of them will publish it so Apple fixes the issue!!!
__________________
- Steve Jobs' best friend! |
|
|
|
0
|
![]() |
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
All times are GMT -5. The time now is 09:26 AM.










'10 MBP 13
Hybrid Mode
