6.0.0-beta1
8/18/25

[#13578] Requesting device reset gets stuck in a loop
Summary Requesting device reset gets stuck in a loop
Queue Synchronization
Queue Version FRAMEWORK_5_2
Type Bug
State Resolved
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester tim.odriscoll (at) lambrookschool (dot) co (dot) uk
Created 09/17/2014 (3988 days ago)
Due
Updated 09/17/2014 (3988 days ago)
Assigned 09/17/2014 (3988 days ago)
Resolved 09/17/2014 (3988 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/17/2014 05:15:29 PM Michael Rubinsky Comment #7
State ⇒ Resolved
Reply to this comment
Added the same text to the preference view as in the admin view.
09/17/2014 05:13:55 PM Git Commit Comment #6 Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2):

commit 5ab0db0259c7528ba7e915885ada66e1f1128502
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Wed Sep 17 13:09:12 2014 -0400

     Use the same template to render the preference version of EAS info.

     Bug: 13578

     Conflicts:
             horde/templates/prefs/activesync.html.php

  horde/lib/Prefs/Special/Activesync.php    |   13 +++++++++-
  horde/templates/prefs/activesync.html.php |   39 ++--------------------------
  2 files changed, 15 insertions(+), 37 deletions(-)

http://github.com/horde/horde/commit/5ab0db0259c7528ba7e915885ada66e1f1128502
09/17/2014 05:10:01 PM Git Commit Comment #5 Reply to this comment
Changes have been made in Git (master):

commit 90a929ed44f52bdfc463d22d75467931a8aaee78
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Wed Sep 17 13:09:12 2014 -0400

     Use the same template to render the preference version of EAS info.

     Bug: 13578

  horde/lib/Prefs/Special/Activesync.php    |   13 ++++++++-
  horde/templates/prefs/activesync.html.php |   41 ++--------------------------
  2 files changed, 15 insertions(+), 39 deletions(-)

http://github.com/horde/horde/commit/90a929ed44f52bdfc463d22d75467931a8aaee78
09/17/2014 02:37:10 PM Michael Rubinsky Comment #4 Reply to this comment
  Having thought about it a little more, it's probably better to keep 
wiping the device each time it tries to reconnect anyway because the 
only reason you're going to be wiping the device is if it's lost or 
stolen.
Exactly.
09/17/2014 02:30:40 PM tim (dot) odriscoll (at) lambrookschool (dot) co (dot) uk Comment #3 Reply to this comment
Apologies, I didn't see the message in the admin screen because I 
tried it out as a normal user. Having thought about it a little more, 
it's probably better to keep wiping the device each time it tries to 
reconnect anyway because the only reason you're going to be wiping the 
device is if it's lost or stolen.

Tim
09/17/2014 01:45:06 PM Michael Rubinsky Comment #2
State ⇒ Assigned
Assigned to Michael Rubinsky
Reply to this comment
This is by design, and is explicitly stated in the administration 
screen, when a device's status is WIPED. However, it looks like it's 
missing from the user-facing prefs screen.
09/17/2014 12:53:40 PM tim (dot) odriscoll (at) lambrookschool (dot) co (dot) uk Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Requesting device reset gets stuck in a loop
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
If you request a device to be wiped through the 'user 
preferences/activesync devices' page, the device is indeed wiped the 
next time it syncs. However if you then set that device up again to 
sync to the Horde ActiveSync server the device will wipe itself again 
after the account is added, and every other time the account is added 
on that particular device.

A work around is to reset the devices' state through the 'user 
preferences/activesync devices' page once the initial wipe is complete.

Tested on an Apple iPad iOS 7.0.4

Tim

Saved Queries