bump >.<

@schmittjoh ping

Is the issue here that internally $index changes when an ACE is removed? I had a similar problem and solved it by iterating through the ACE's in reverse order.

iterating through the array backwards worked.

$classACEs = $currentAcl->getObjectAces();
for ($i=(sizeof($classACEs)-1); $i>=0; $i--)
{
    $currentAcl->deleteObjectAce($i); 
}

its not ideal, but hey ho.

@samsamm777 is that normal that when wanting to iterate through classes ACEs you perform a

$classesACEs = $currentAcl->getObjectAces();

(and then iterating on the object aces) instead of doing a

$classesACEs = $currentAcl->getClassAces();

?

I prefer to ask because at this point I wonder whether I'm mistaking or not using acls.

I got this error today.
The problem is, that if the ace order is broken - in my case [0, 2] - this error occures. I don't know why the order was broken, after fix the order manualy in the database, everything works fine.

I am also experiencing this issue. Symfony 2.1

I had this same issue. In fact my indexes were ok, but when multiple indexes were deleted in one pass, it failed. Solved by reversing the order of the loop as described by @yoannch above

@Codepadawan what symfony version are you using?

2.4.2

Closing this issue as ACLs are not part of Symfony Core anymore (see #14718 for the initial discussion). It the issue still exists, you can create an issue on symfony/security-acl or symfony/acl-bundle. Thanks.