This is a hotfix release.

• Fix a bug that might cause MMKV to become dead-locked for other threads after decoding container-type values. The affected platforms and value types are listed below. So don't be surprised if you find no update on the unaffected platforms.

• Fix a bug that MMKV might become dead-locked for other threads after decodeStringSet() / decodeNumberSet / decodeBoolSet or decoding TypedArray.

• Fix the bug on HarmonyOS NEXT listed above. A version named v2.0.1 was added to fix the Android version conflict between the LTS series & v2.0. Thanks to the federated plugins framework, only the underlying mmkv_ohos plugin is upgraded, the mmkv plugin stays the same.

• Fix a bug that MMKV might become dead-locked for other threads after decoding std::vector<T> or std::span<T> values.

This release is a breaking change release, especially for Android.

• Add readonly mode support.
• Fix a compile error when MMKV_DISABLE_CRYPT is defined and MMKV is built by source in DEBUG.

• Support 16K page size for Android 15.
• Drop the support of 32-bit ABI.
• Bump the mini SDK level to API 23.

• Add Mac Catalyst support

• Add add log/error/content-change callback.

• Add add log/error/content-change callback.
• Support obfuscation. For the time being, you will have to manually copy the content of MMKV's consumer-rules.txt into your App's obfuscation-rules.txt.

• Replace random() with rand() to fix a compile error.

This is a Long Term Support (LTS) release.

• Fix a data corruption bug on an encrypted MMKV with only one key value stored.
• Make encryption more resilient from brute force cracking.
• Fix a bug that pthread_mutex is not being destroyed correctly.

• Use an alternative way to get the process name to avoid potential App review issues.
• Upgrade to NDK 26.3.11579264.

• Add support for HarmonyOS NEXT. In fact, a temp version named v1.3.8 adds this support with the native lib of v1.3.7. To avoid potential confusion, bump both versions to v1.3.9.

This Long Term Support (LTS) release primarily reintroduces support for the ARMv7 architecture and lowers the minimum SDK version requirement to 21. Please note that only critical bug fixes will be applied to the 1.3.x series. New features will be introduced in version 2.0 and later, which will discontinue support for 32-bit architectures and raise the minimum SDK version requirement to 23.

This is exactly the same as v1.3.6, so don't be surprised if you don't see this version in CocoaPods or OHPM.

• The Core library now upgrades the C++ standard from C++17 to C++20 to make the most of morden C++ feature such as Concept & unordered containers with std::string_view as key. From now on, if you build MMKV by source (iOS, Windows, POSIX, etc), you will need a C++ compiler that supports the C++20 standard. If you only use MMKV in binary (Android, OHOS, etc), this upgrade of the C++ compiler is not required.
• The key type changes from std::string to std::string_view, to avoid unnecessary string construction and destruction when the key is a raw string.

• Use the latest ashmem API if possible.
• Use the latest API to get the device API level.

• MMKV will try to load libmmkv.so before Dart code, to reduce the error of loading library in Android.

• Fix a bug that a String value might get truncated on encoding.
• MMKV returns undefined when a key does not exist, previously a default value of the type (false for boolean, 0 for number, etc) is returned.
• Add the feature to encode/decode a float value.
• Add the feature to encode/decode a TypedArray value.
• Support encoding a part of an ArrayBuffer.

• Hide the default NSObject.initialize() from Swift/ObjC to prevent potential misuse.

• Support encode/decode std::vector<T> or std::span<T> values, with T as primitive types.
• Fix a compile error on Linux env.
• Fix a compile error on the GNU compiler.
• Fix a compile error with some old version of zlib (on CentOS).

• Python now runs on Windows. Check out the latest wiki for instructions.

• Support encode/decode std::vector<T> or std::span<T> values, with T as primitive types.
• Python now runs on Windows. Check out the latest wiki for instructions.

• This is the first official support of HarmonyOS NEXT.
• Most things actually work!
• Checkout the wiki for more.

• Migrate to federated plugins to avoid the iOS rename headache. From now on, no more renaming from mmkv to mmkvflutter is needed.
• Bump iOS Deployment Target to iOS 12.
• Bump Android minSdkVersion to 23.

• Avoid using so-called privacy APIs (lstat(), fstat(), NSUserDefaults).
• Bump iOS Deployment Target to iOS 12.

• Bump minSdkVersion to 23.
• Drop armv7 & x86 support.

• Use the embedded libz when libz can not be found.
• Fix compile error when building with gcc.

• Support x64 architecture.

• Make trim() more robust in multi-process mode.

• Support visionOS.

• Fix a compile error on ::unlink().

• Add removeStorage() static method to safely delete underlying files of an MMKV instance.
• Add protection from a potential crash of a multi-process MMKV loading due to the MMKV file not being valid.
• Add back the lazy load feature. It was first introduced in v1.2.16. But it was rollbacked in v1.3.0 of potential ANR & file corruption. Now it's clear that the bug was caused by something else, it's time to bring it back.
• Optimize loading speed by using shared inter-process lock unless there's a need to truncate the file size, which is rare.
• Make these two lately added features more robust: customizing the initial file size & optimizing write speed when there's only one key inside MMKV.

• Fix a bug that null is returned when the value is in fact an empty ByteArray.
• Fix AGP >= 8 package namespace error.
• Fix the FastNative naming conflict.
• Upgrade to SDK 34.
• Upgrade androidx.annotation to v1.7.1.

• On the Xcode 15 build, an App will crash on iOS 14 and below. Previously we have recommended some workarounds (check the v1.3.2 release note for details). Now you can use Xcode 15.1 to fix this issue.
• Fix a bug that the multi-process mode won't configure correctly. It was introduced in v1.3.2.
• Fix a macro naming conflict.
• Avoid using a so-called privacy API when creating temp files.

• Fix a compile error on memcpy().

• Fix a compile error when MMKV_DISABLE_CRYPT is on.

Among most of the features added in this version, the credit goes to @kaitian521.

• Add the feature of customizing the initial file size of an MMKV instance.
• Optimize write speed when there's only one key inside MMKV, the new key is the same as the old one, and MMKV is in SINGLE_PROCESS_MODE.
• Optimize write speed by overriding from the beginning of the file instead of append in the back, when there's zero key inside MMKV, and MMKV is in SINGLE_PROCESS_MODE.
• Add the feature of clearAll() with keeping file disk space unchanged, reducing the need to expand file size on later insert & update operations. This feature is off by default, you will have to call it with relative params or newly added methods.
• Add the feature of comparing values before setting/encoding on the same key.
• Fix a potential bug that the MMKV file will be invalid state after a successful expansion but a failure zeroFill(), will lead to a crash.
• Fix a potential crash due to other module/static lib turn-off RTTI, which will cause MMKV to fail to catch std::exception.
• Fix several potential crash due to the MMKV file not being valid.

• Use the -O2 optimization level by default, which will reduce native lib size and improve read/write speed a little bit.
• Experimantal use @fastNative annotation on enableCompareBeforeCompare() to speed up JNI call.

• Optimize auto-clean logic to reduce lock waiting time.
• Turn-off mlock() protection in background on iOS 13+. We have verified it on WeChat that the protection is no longer needed from at least iOS 13. Maybe iOS 12 or older is also not needed, but we don't have the chance to verify that because WeChat no longer supports iOS 12.

• On Xcode 15 build, App will crash on iOS 14 and below. The bug is introduced by Apple's new linker. The official solutions provided by Apple are either:
  • Drop the support of iOS 14.
  • Add -Wl,-weak_reference_mismatches,weak or -Wl,-ld_classic options to the OTHER_LDFLAGS build setting of Xcode 15. Note that these options are not recognized by older versions of Xcode.
  • Use older versions of Xcode, or wait for Xcode 15.2.

This is a hotfix version. It's highly recommended that v1.2.16 & v1.3.0 users upgrade as soon as possible.

• Fix a critical bug that might cause multi-process MMKV corrupt. This bug was introduced in v1.2.16.
• Add the ability to filter expired keys on count() & allKeys() methods when auto key expiration is turn on.
• Reduce the msync() call on newly created MMKV instances.

• Fix a bug that NSKeyedArchive object might fail to decode when auto key expiration is turn on.

• Add auto key expiration feature. Note that this is a breaking change, once upgrade to auto expiration, the MMKV file is not valid for older versions of MMKV (v1.2.16 and below) to correctly operate.
• Roll back the lazy load optimization due to reported ANR issues. It was introduced in v1.2.16.

• Fix a potential memory leak on setting a new value for an existing key.
• Upgrade min support target to iOS 11 / macOS 10.13 / tvOS 13 / watchOS 4.

• Fix a bug that might fail to truncate the file size to a smaller size in some cases.

• The version of MMKV for Flutter is now the same as the MMKV native library.
• Starting from v1.3.0, Flutter for Android will use com.tencent:mmkv. Previously it's com.tencent:mmkv-static. It's the same as com.tencent:mmkv starting from v1.2.11.

• Optimization: The actual file content is lazy loaded now, saving time on MMKV instance creation, and avoiding lock waiting when a lot of instances are created at the same time.
• Fix a bug when restoring a loaded MMKV instance the meta file might mistakenly report corrupted.

• Optimization: Remove unnecessary binder call on main process instantiation.

• Fix a crash on decoding an empty list.
• Remove deprecated dependence.
• Make the script more robust to fix the iOS Flutter plugin name.

• Fix a string format bug on the MinGW64 environment.

• Fix a build error on 32-bit OS.

• Log handler now handles all logs from the very beginning, especially the logs in initialization.
• Log handler register method is now deprecated. It's integrated with initialize().
• Fix a bug that lock()/unlock()/try_lock() is not thread-safe.

• Reduce the privacy info needed to obtain android sdkInt, avoid unnecessary risk on Android App Review.

• Fix a compile error on macOS.
• Fix a bug that some ObjC exceptions are not being caught.
• Add assert on nil MMKV base path, protect from mis-using MMKV in global variable initialization.
• Starting from v1.2.15, one must call +[MMKV initializeMMKV:] manually before calling any MMKV methods.

• Fix a compile error on GCC.

• Support CMake project on Windows.

• Fix a bug that MMKV.getXXX() may return invalid results in multi-process mode.

• Return [] instead of null on empty StringSet from MMKV.decodeStringSet() methods.
• Upgrade Android Compile & Target SDK to 32.

• Protect from the crash in -[MMKV getObject:forKey:] method when the key-value doesn't exist.

• Fix crash on using Ashmem while MMKV_DISABLE_CRYPT macro is defined.

• Add ability to retrieve key existece while getting value, aka -[MMKV getXXX:forKey:hasValue:] methods.

• Add ability to retrieve key existece while getting value, aka MMKV::getXXX(key, defaultValue, hasValue) methods.

• Add ability to retrieve key existece while getting value, aka MMKV::getXXX(key, defaultValue, hasValue) methods.

• Fix a bug that a subsequential clearAll() call may fail to take effect in multi-process mode.
• Hide some OpenSSL symbols to prevent link-time symbol conflict, when an App somehow also static linking OpenSSL.

• Upgrade compileSdkVersion & targetSdkVersion from 30 to 31.

• Due to increasing report about crash inside STL, we have decided to make MMKV static linking libc++ by default. Starting from v1.2.11, com.tencent:mmkv-static is the same as com.tencent:mmkv.
• For those still in need of MMKV with shared linking of libc++_shared, you could use com.tencent:mmkv-shared instead.
• Add backup & restore ability.

• Add backup & restore ability.
• Support tvOS.
• Fix a compile error on some old Xcode.

• Add backup & restore ability.

• Add backup & restore ability.
• Fix a compile error on Gentoo.

• Add backup & restore ability.

This version is mainly for Android & Flutter.

• Complete JavaDoc documentation for all public methods, classes, and interfaces. From now on, you can find the API reference online.
• Drop the support of armeabi arch. Due to some local build cache mistake, the last version (v1.2.9) of MMKV still has an unstripped armeabi arch inside. This is fixed.
• Change MMKV.mmkvWithID() from returning null to throwing exceptions on any error.
• Add MMKV.actualSize() to get the actual used size of the file.
• Mark MMKV.commit() & MMKV.apply() as deprecated, to avoid some misuse after migration from SharedPreferences to MMKV.

• Bug Fixed: When building on iOS, occasionally it will fail on symbol conflict with other libs. We have renamed all public native methods to avoid potential conflict.
• Keep up with MMKV native lib v1.2.10.

This version is mainly for Android & Flutter.

• Drop the support of armeabi arch. As has been mention in the last release, to avoid some crashes on the old NDK (r16b), and make the most of a more stable libc++, we have decided to upgrade MMKV's building NDK in this release. That means we can't support armeabi anymore. Those who still in need of armeabi can build from sources by following the instruction in the wiki.

We really appreciate your understanding.

• Bug Fixed: When calling MMKV.encodeString() with an empty string value on Android, MMKV.decodeString() will return null.
• Bug Fixed: After upgrading from Flutter 1.20+ to 2.0+, calling MMKV.defaultMMKV() on Android might fail to load, you can try calling MMKV.defaultMMKV(cryptKey: '\u{2}U') with an encrytion key '\u{2}U' instead.
• Keep up with MMKV native lib v1.2.9.

This will be the last version that supports armeabi arch on Android. To avoid some crashes on the old NDK (r16b), and make the most of a more stable libc++, we have decided to upgrade MMKV's building NDK in the next release. That means we can't support armeabi anymore.

We really appreciate your understanding.

• Migrate MMKV to Maven Central Repository. For versions older than v1.2.7 (including), they are still available on JCenter.
• Add MMKV.disableProcessModeChecker(). There are some native crash reports due to the process mode checker. You can disable it manually.
• For the same reason described above (native crashed), MMKV will now turn off the process mode checker on a non-debuggable app (aka, a release build).
• For MMKV to detect whether the app is debuggable or not, when calling MMKV.initialize() to customize the root directory, a context parameter is required now.

• Min iOS support has been upgrade to iOS 9.
• Support building by Xcode 12.

• Support null-safety.
• Upgrade to flutter 2.0.
• Fix a crash on the iOS when calling encodeString() with an empty string value.

Known Issue on Flutter

• When calling encodeString() with an empty string value on Android, decodeString() will return null. This bug will be fixed in the next version of Android Native Lib. iOS does not have such a bug.

• Fix a compile error on Visual Studio 2019.

Happy holidays everyone!

• Fix a bug when calling sync() with false won't do msync() asynchronous and won't return immediately.

• Fix an null pointer exception when calling putStringSet() with null.
• Complete review of all MMKV methods about Java nullable/nonnull annotation.
• Add API for MMKV.initialize() with both Context and LibLoader parammeters.

• Fix a crash on the iOS simulator when accessing the default MMKV instance.
• Fix a bug on iOS when initing the default MMKV instance with a crypt key, the instance is still in plaintext.

Add golang for POSIX platforms. Most things actually work!. Check out the wiki for information.

• Fix a file corruption when calling reKey() after removeKeys() has just been called.

• Fix compile error when MMKV_DISABLE_CRYPT is set.
• Add a preprocess directive MMKV_DISABLE_FLUTTER to disable flutter plugin features. If you integrate MMKV by source code, and if you are pretty sure the flutter plugin is not needed, you can turn that off to save some binary size.

Add MMKV support for Flutter on iOS & Android platform. Most things actually work!
Check out the wiki for more info.

This is a pre-version for Flutter. The official Flutter plugin of MMKV will come out soon. Stay Tune!

• Fix an assert error of encrypted MMKV when encoding some <NSCoding> objects.
• Fix a potential leak when decoding duplicated keys from the file.
• Add +[MMKV pageSize], +[MMKV version] methods.
• Add +[MMKV defaultMMKVWithCryptKey:], you can encrypt the default MMKV instance now, just like the Android users who already enjoy this for a long time.
• Rename -[MMKV getValueSizeForKey:] to -[MMKV getValueSizeForKey: actualSize:] to align with Android interface.

• Fix a potential crash when getting MMKV instances in multi-thread at the same time.
• Add MMKV.version() method.

This is a hotfix mainly for iOS.

• Fix a decode error of encrypted MMKV on some devices.

• Fix a potential issue on checking rootDir in multi-thread while MMKV initialization is not finished.

• Fix a potential crash on 32-bit devices due to pointer alignment issue.
• Fix a decode error of encrypted MMKV on some 32-bit devices.

• Fix a potential crc32() crash on some kind of arm64 devices.
• Fix a potential crash after calling +[MMKV onAppTerminate].

• Fix a rare lock conflict on checkProcessMode().

Add MMKV support for Python on POSIX platforms. Most things actually work!
Check out the wiki for more info.

• Add auto clean up feature. Call +[MMKV enableAutoCleanUp:] to enable auto cleanup MMKV instances that not been accessed recently.
• Fix a potential crash on devices under iPhone X.

• Add multi-process mode check. After so many issues had been created due to mistakenly using MMKV in multi-process mode in Android, this check is added. If an MMKV instance is accessed with SINGLE_PROCESS_MODE in multi-process, an IllegalArgumentException will be thrown.

• Add support for armv7 & arm64 arch on Linux.

This is a hotfix release. Anyone who has upgraded to v1.2.0 should upgrade to this version immediately.

• Fix a potential file corruption bug when writing a file that was created in versions older than v1.2.0. This bug was introduced in v1.2.0.
• Add a preprocess directive MMKV_DISABLE_CRYPT to turn off MMKV encryption ability once and for all. If you integrate MMKV by source code, and if you are pretty sure encryption is not needed, you can turn that off to save some binary size.
• The parameter relativePath (customizing a separate folder for an MMKV instance), has been renamed to rootPath. Making it clear that an absolute path is expected for that parameter.

• -[MMKV mmkvWithID: relativePath:] is deprecated. Use -[MMKV mmkvWithID: rootPath:] instead.
• Likewise, -[MMKV mmkvWithID: cryptKey: relativePath:] is deprecated. Use -[MMKV mmkvWithID: cryptKey: rootPath:] instead.

This is the second major version of MMKV. Everything you call is the same as the last version, while almost everything underneath has been improved.

• Reduce Memory Footprint. We used to cache all key-values in a dictionary for efficiency. From now on we store the offset of each key-value inside the mmap-memory instead, reducing memory footprint by almost half for (non-encrypt) MMKV. And the accessing efficiency is almost the same as before. As for encrypted MMKV, we can't simply store the offset of each key-value, the relative encrypt info needs to be stored as well. That will be too much for small key-values. We only store such info for large key-values (larger than 256B).
• Improve Writeback Efficiency. Thanks to the optimization above, we now can implement writeback by simply calling memmove() multiple times. Efficiency is increased and memory consumption is down.
• Optimize Small Key-Values. Small key-values of encrypted MMKV are still cached in memory, as all the old versions did. From now on, the struct MMBuffer will try to store small values in the stack instead of in the heap, saving a lot of time from malloc() & free(). In fact, all primitive types will be store in the stack memory.

All of the improvements above are available to all supported platforms. Here are the additional changes for each platform.

• Optimize insert & delete. Especially for inserting new values to existing keys, or deleting keys. We now use the UTF-8 encoded keys in the mmap-memory instead of live encoding from keys, cutting the cost of string encoding conversion.
• Fix Xcode compile error on some projects.
• Drop the support of iOS 8. thread_local is not available on iOS 8. We choose to drop support instead of working around because iOS 8's market share is considerably small.

• It's known that GCC before 5.0 doesn't support C++17 standard very well. You should upgrade to the latest version of GCC to compile MMKV.

• Fix a potential crash after trim() a multi-process MMKV instance.
• Improve clearAll() a bit.

• Support WatchOS.
• Rename +[MMKV onExit] to +[MMKV onAppTerminate], to avoid naming conflict with some other OpenSource projects.
• Make background write protection much more robust, fix a potential crash when writing meta info in background.
• Fix a potential data corruption bug when writing a UTF-8 (non-ASCII) key.

• Fix a crash in the demo project when the App is hot reloaded.
• Improve wiki & readme to recommend users to init & destruct MMKV in the Application class instead of the MainActivity class.

• Fix two compile errors with some compilers.

This is the first major breaking version ever since MMKV was made public in September 2018, introducing bunches of improvement. Due to the Covid-19, it has been delayed for about a month. Now it's finally here!

• Improved File Recovery Strategic. We store the CRC checksum & actual file size on each sync operation & full write back, plus storing the actual file size in the same file(aka the .crc meta file) as the CRC checksum. Base on our usage inside WeChat on the iOS platform, it cuts the file corruption rate down by almost half.
• Unified Core Library. We refactor the whole MMKV project and unify the cross-platform Core library. From now on, MMKV on iOS/macOS, Android, Windows all share the same core logic code. It brings many benefits such as reducing the work to fix common bugs, improvements on one platform are available to other platforms immediately, and much more.
• Supports POSIX Platforms. Thanks to the unified Core library, we port MMKV to POSIX platforms easily.
• Multi-Process Access on iOS/macOS. Thanks to the unified Core library, we add multi-process access to iOS/macOS platforms easily.
• Efficiency Improvement. We make the most of armv8 ability including the AES & CRC32 instructions to tune encryption & error checking speed up by one order higher than before on armv8 devices. There are bunches of other speed tuning all around the whole project.

Here are the old-style change logs of each platform.

• Adds multi-process access support. You should initialize MMKV by calling +[MMKV initializeMMKV: groupDir: logLevel:], passing your app group id. Then you can get a multi-process instance by calling +[MMKV mmkvWithID: mode:] or +[MMKV mmkvWithID: cryptKey: mode:], accessing it cross your app & your app extensions.
• Add inter-process content change notification. You can get MMKV changes notification of other processes by implementing - onMMKVContentChange: of <MMKVHandler> protocol.
• Improved File Recovery Strategic. Cuts the file corruption rate down by almost half. Details are above.
• Efficiency Improvement. Encryption & error checking speed are up by one order higher on armv8 devices(aka iDevice including iPhone 5S and above). Encryption on armv7 devices is improved as well. Details are ahead.
• Other speed improvements. Refactor core logic using MRC, improve std::vector push_back() speed by using move constructors & move assignments.
• +[MMKV setMMKVBasePath:] & +[MMKV setLogLevel:] are marked deprecated. You should use +[MMKV initializeMMKV:] or +[MMKV initializeMMKV: logLevel:] instead.
• The MMKVLogLevel enum has been improved in Swift. It can be used like MMKVLogLevel.info and so on.

• Improved File Recovery Strategic. Cuts the file corruption rate down by almost half. Details are above.
• Efficiency Improvement. Encryption & error checking speed are up by one order higher on armv8 devices with the arm64-v8a abi. Encryption on armeabi & armeabi-v7a is improved as well. Details are ahead.
• Add exception inside core encode & decode logic, making MMKV much more robust.
• Other speed improvements. Improve std::vector push_back() speed by using move constructors & move assignments.

• Improved File Recovery Strategic. Cuts the file corruption rate down by almost half. Details are above.
• Add exception inside core encode & decode logic, making MMKV much more robust.
• Other speed improvements. Improve std::vector push_back() speed by using move constructors & move assignments.

• Most things actually work! We have tested MMKV on the latest version of Linux(Ubuntu, Arch Linux, CentOS, Gentoo), and Unix(macOS, FreeBSD, OpenBSD) on the time v1.1.0 is released.

What's new

• Fix a bug that MMKV will fail to save any key-values after calling -[MMKV clearMemoryCache] and then -[MMKV clearAll].
• Add +[MMKV initializeMMKV:] for users to init MMKV in the main thread, to avoid an iOS 13 potential crash when accessing UIApplicationState in child threads.
• Fix a potential crash when writing a uniquely constructed string.
• Fix a performance slow down when acquiring MMKV instances too often.
• Make the baseline test in MMKVDemo more robust to NSUserDefaults' caches.

What's new

• Fix flock() bug on ashmem files in Android.
• Fix a potential crash when writing a uniquely constructed string.
• Fix a bug that the MMKVDemo might crash when running in a simulator.

• Fix a potential crash when writing a uniquely constructed string or data.

What's new

• Fix a potential security leak on encrypted MMKV.

What's new

• Fix a potential security leak on encrypted MMKV.
• Fix filename bug when compiled on Windows environment.
• Add option for decoding String Set into other Set<> classes other than the default HashSet<String>, check decodeStringSet() for details.
• Add putBytes() & getBytes(), to make function names more clear and consistent.
• Add notification of content changed by other process, check the new MMKVContentChangeNotification<> interface & checkContentChangedByOuterProcess() for details.

What's new

• Fix a potential security leak on encrypted MMKV.
• Fix CriticalSection init bug.

What's new

• Fix a bug that MMKV will corrupt while adding just one key-value, and reboot or clear memory cache. This bug was introduced in v1.0.21.

What's new

• Fix a bug that MMKV will corrupt while adding just one key-value, and reboot or clear memory cache. This bug was introduced in v1.0.21.

What's new

• Fix a bug that MMKV will corrupt while adding just one key-value, and reboot or clear memory cache. This bug was introduced in v1.0.21.

What's new

• Fix a bug that MMKV might corrupt while repeatedly adding & removing key-value with specific length. This bug was introduced in v1.0.20.

What's new

• Fix a bug that MMKV might corrupt while repeatedly adding & removing key-value with specific length. This bug was introduced in v1.0.20.

What's new

• Fix a bug that MMKV might corrupt while repeatedly adding & removing key-value with specific length. This bug was introduced in v1.0.20.

What's new

• Fix a bug that MMKV might crash while storing key-value with specific length.
• Fix a bug that -[MMKV trim] might not work properly.

What's new

• Migrate to AndroidX library.
• Fix a bug that MMKV might crash while storing key-value with specific length.
• Fix a bug that trim() might not work properly.
• Fix a bug that dead-lock might be reported by Android mistakenly.
• Using RegisterNatives() to simplify native method naming.

• Fix a bug that MMKV might crash while storing key-value with specific length.
• Fix a bug that trim() might not work properly.
• Fix a bug that clearAll() might not work properly.

What's new

• Support Swift 5.
• Add method to get all keys -[MMKV allKeys];
• Add method to synchronize to file asynchronously -[MMKV async].
• Fix a pod configuration bug that might override target project's C++ setting on CLANG_CXX_LANGUAGE_STANDARD.
• Fix a bug that DEFAULT_MMAP_SIZE might not be initialized before getting any MMKV instance.
• Fix a bug that openssl's header files included inside MMKV might mess with target project's own openssl implementation.

What's new

• Support Android Q.
• Add method to synchronize to file asynchronously void sync(), or void apply() that comes with SharedPreferences.Editor interface.
• Fix a bug that a buffer with length of zero might be returned when the key is not existed.
• Fix a bug that DEFAULT_MMAP_SIZE might not be initialized before getting any MMKV instance.

What's new

• Fix a bug that defaultValue was not returned while decoding a NSCoding value.
• Fix a compile error on static linking MMKV while openssl is static linked too.

What's new

• Introducing Native Buffer. Checkout wiki for details.
• Fix a potential crash when trying to recover data from file length error.
• Protect from mistakenly passing Context.MODE_MULTI_PROCESS to init MMKV.

• Fix a potential crash when trying to recover data from file length error.

What's new

• Redirect logging of MMKV is supported now.
• Dynamically disable logging of MMKV is supported now.
• Add method migrateFromUserDefaults to import from NSUserDefaults.

What's new

• Redirect logging of MMKV is supported now.
• Dynamically disable logging of MMKV is supported now.
  Note: These two are breaking changes for interface MMKVHandler, update your implementation with wantLogRedirecting() & mmkvLog() for v1.0.17. (Interface with default method requires API level 24, sigh...)
• Add option to use custom library loader initialize(String rootDir, LibLoader loader). If you're facing System.loadLibrary() crash on some low API level device, consider using ReLinker to load MMKV. Example can be found in mmkvdemo.
• Fix a potential corruption of meta file on multi-process mode.
• Fix a potential crash when the meta file is not valid on multi-process mode.

• Redirect logging of MMKV is supported now.
• Dynamically disable logging of MMKV is supported now.
• Fix a potential corruption of meta file on multi-process mode.

What's new

• Customizing root folder of MMKV is supported now.
• Customizing folder for specific MMKV is supported now.
• Add method getValueSizeForKey: to get value's size of a key.

What's new

• Customizing root folder of MMKV is supported now.
• Customizing folder for specific MMKV is supported now.
• Add method getValueSizeForKey() to get value's size of a key.
• Fix a potential crash when the meta file is not valid.

MMKV for Windows is released now. Most things actually work!

What's new

• Storing NSString/NSData/NSDate directly by calling setString/getSring, setData/getData, setDate/getDate.
• Fix a potential crash due to divided by zero.

What's new

• Fix a stack overflow crash due to the callback feature introduced by v1.0.13.
• Fix a potential crash due to divided by zero.

MMKV for Windows in under construction. Hopefully will come out in next release. For those who are interested, check out branch dev_Windows for the latest development.

What's new

• Setting nil value to reset a key is supported now.
• Rename boolValue(forKey:) to bool(forKey:) for Swift.

What's new

• Parcelable objects can be stored directly into MMKV now.
• Setting null value to reset a key is supported now.
• Fix an issue that MMKV's file size might expand unexpectly large in some case.
• Fix an issue that MMKV might crash on multi-thread removing and getting on the same key.

What's new

• Special chars like / are supported in MMKV now. The file name of MMKV with special mmapID will be encoded with md5 and stored in seperate folder.
• Add callback for MMKV error handling. You can make MMKV to recover instead of discard when crc32 check fail happens.
• Add trim and close operation. Generally speaking they are not necessary in daily usage. Use them if you worry about disk / memory / fd usage.
• Fix an issue that MMKV's file size might expand unexpectly large in some case.

Known Issues

• Setting nil value to reset a key will be ignored. Use remove instead.

What's new

• Add static linked of libc++ to trim AAR size. Use it when there's no other lib in your App embeds libc++_shared.so. Or if you already have an older version of libc++_shared.so that doesn't agree with MMKV.
  Add implementation 'com.tencent:mmkv-static:1.0.13' to your App's gradle setting to integrate.
• Special chars like / are supported in MMKV now. The file name of MMKV with special mmapID will be encoded with md5 and stored in seperate folder.
• Add callback for MMKV error handling. You can make MMKV to recover instead of discard when crc32 check fail happens.
• Add trim and close operation. Generally speaking they are not necessary in daily usage. Use them if you worry about disk / memory / fd usage.

Known Issues

• Setting null value to reset a key will be ignored. Use remove instead.
• MMKV's file size might expand unexpectly large in some case.

What's new

• Fix mlock fail on some devices
• Fix a performance issue caused by mistakenly merge of test code
• Fix CocoaPods integration error of macOS

What's new

• Fix remove() causing data inconsistency on MULTI_PROCESS_MODE

What's new

• Port to macOS
• Support NSCoding
  You can store NSArray/NSDictionary or any object what implements <NSCoding> protocol.
• Redesign Swift interface
• Some performance improvement

Known Issues

• MMKV use mmapID as its filename, so don't contain any / inside mmapID.
• Storing a value of type A and getting by type B may not work. MMKV does type erasure while storing values. That means it's hard for MMKV to do value-type-checking, if not impossible.

What's new

• Some performance improvement

Known Issues

• Getting an MMKV instance with mmapID that contains / may fail.
  MMKV uses mmapID as its filename, so don't contain any / inside mmapID.
• Storing a value of type A and getting by type B may not work.
  MMKV does type erasure while storing values. That means it's hard for MMKV to do value-type-checking, if not impossible.
• registerOnSharedPreferenceChangeListener not supported.
  This is intended. We believe doing data-change-listener inside a storage framework smells really bad to us. We suggest using something like event-bus to notify any interesting clients.

• Initial Release