Owncloud 10.2.1 incompatibility

[ronbass]

HI,
There was no place where I could find any information about any issue for the market app of Zimbradrive for Owncloud 10.2.1.
I wasted hours trying to fix my Owncloud server after I upgraded it from 10.1 to 10.2 not knowing it was this issue then found that the Zimbradrive version is not compatible with it and it disappeared as well from the Owncloud Market menu in the server but is still offered on https://marketplace.owncloud.com/apps/zimbradrive -v.0.8.22
I downloaded this version but got the same error:
Zimbra Drive 0.8.23 by ZeXtras (AGPL-licensed)
This app cannot be installed because the following dependencies are not fulfilled:
ownCloud 10.0 or lower is required.

I would not have upgraded my server if I knew I would lose Zimbradrive as it is important for my Zimbra email server, now users lost their access to their drive files and I am stuck with it as I cannot downgrade Owncloud!
Will there be any update very soon?
Thank you

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
5 out of 10 committers have signed the CLA.

✅ adrb
✅ bud-mo
✅ ZxUgoPadoan
✅ chbusold
✅ sanchezfauste
❌ ZxCine
❌ Rizzo
❌ davide-baldo
❌ Polpetta
❌ ZeXtrasJay

---

Rizzo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ronbass]

Hi,
I am now using Nextcloud 19.0 with Zimbra, although It shows me that Zimbra drive has a missing update, it is still working, but upgrading today to 19.0.13 did not pass the Integrity check, here are the details:

Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

• zimbradrive
  • INVALID_HASH
    • appinfo/info.xml

Raw output

Array
(
[zimbradrive] => Array
(
[INVALID_HASH] => Array
(
[appinfo/info.xml] => Array
(
[expected] => 99c089a6d9c48b5d7b3af9065eb04a947c683d79e5e56b6e44e64d314508c089e896ee483ef60aa0d16fafe822dd719ef22c1ddc42742d13e3a073f8c560e777
[current] => be79d9721f3b9ec38b88ea1427fd796f24b25fbad09afbd95023aaf6b55f33deb85f3ef0bf62a7bb164c7cec00a56436404b9088180160e50da8d8b7d3296c65_

When I open the signature.json file I see the EXPECTED information and not the CURRENT one, so where should this info be replaced or corrected?

I still hope that the team who built the Zimbra drive app will continue to work on updating it, or transfer the knowledge for someone else to do it as it is part of Zimbra collaborative suite which is now V.9.
Thank you