[horde] Activesync : call for testing II

[Torben Dannhauer]

Great to hear! May I ask which database you use for your Horde and Activesync? SQL? Mongo? Which SQL?

Regards,
Torben

Von unterwegs gesendet
Sent from mobile


> Am 09.06.2026 um 03:30 schrieb Brent <impuser at bitrealm.com>:
> 
>  I flipped my production instance to this db and "loops" version of ActiveSync. It's only been a few hours, but the log files look like they are doing ok. Things are so far staying in sync. So...much better than beta3. I also switched to version 16.0, so not an apples-to-apples comparison, but I thought I should give it a shot.
> 
> brent
> 
> Quoting Torben Dannhauer <torben at dannhauer.info>:
> 
>> Hi together,
>> 
>> Finally the polishing of ActiveSync is done! There were multiple Independent reasons invalidating the sync keys:
>> Race conditions between workers, shared data model where it should be separated, a bug in Horde/Db handling data in edge situations etc..
>> 
>> Once the Horde/Db fix is released (next 24h), or if you switch to the latest git for horde/Db, I would appreciate testing Activesync, in 14.0/1 and 16.0.
>> 
>> The issues described by Brent and powercycle were visible on my end as well.
>> They are solved now in my Tests and Setup
>> 
>> Procedere to get it:
>> Composer require horde/Db:dev-FRAMEWORK_6_0
>> composer require horde/ActiveSync:dev-fix/ActiveSync_loops
>> vendor/bin/horde-db-migrate # to get the latest SQL Schema Update as well.
>> 
>> Procedere to Test it:
>> 1. Wipe serveside sync states in the AS admin Panel
>> 2. Re-setup account on device
>> 
>> Looking forward to your Feedback😊
>> 
>> Von unterwegs gesendet
>>