rename EncryptionCompatTest.kt to CompatibilityTest.kt to keep in sync with the class name
Note that the tests are not automatically executed by the ci and have to be run manually.
we have a rate limit on the server, but it's easy to run into and the
resulting suspension will cause a 30s wait.
This new method should limit the request rate (from one client) to just
under the limit the server has, without feeling slow for the vast
majority of users.
When mails before the cutoff were updated and a user received
entityUpdates for these mails, after prefetching, these mails were
immediately deleted from the offline storage again by the
MailOfflineCleaner. However, the MailIndex re-downloads these very same
mails afterward again. To fix this issue, we move the execution of the
MailOfflineCleaner after the MailIndexer.
Co-authored-by: das <das@tutao.de>
Co-authored-by: jomapp <17314077+jomapp@users.noreply.github.com>
When loading mails by opening the inbox folder using the
ConversationListModel or MailListMode, we were not updating the
processingState for those mails correctly. This lead to a
re-application of the inbox rules on every inbox folder load.
Co-authored-by: abp <abp@tutao.de>
In order to avoid layout issues within the event invitation preview banner
we keep the length of the text to a minimum.
The idea is that the expander should only show "x conflicts" and doesn't show a
preview of which type of conflict it is. The concrete type of the conflict (all day or simultaneous)
can seen by expanding the conflict section.
After upgrading to the new NDK/SDK/Gradle versions, our android.js
build script stopped working as expected. The shared object (.so)
files for tutasdk were only being copied during Debug builds or
when builds were triggered from Android Studio. As a result,
Release builds were missing the necessary shared libraries,
causing runtime errors when invoking code from the SDK.
This commit introduces a new Gradle task responsible for copying the
shared libraries into the jniLibs folder within the tutasdk project.
It also makes the preBuild and all merge tasks depend on copyRustLibs,
ensuring that the default jniLibs path is used and that all shared
objects are properly included in every build variant.
The Android compileSdk version in the tutasdk build.gradle.kts has been
wrongly set to a different compileSdk version 34, instead of version 36
as with the other gradle artifacts (mail, calendar, shared). This
version discrepancy caused, when running the Android release build,
to not bundle the "libtutasdk.so" file correctly, leading to an
Android APK file without native rust code.
Co-authored-by: abp <abp@tutao.de>
Co-authored-by: das <das@tutao.de>
