Androidacy / MagiskModuleManager

Previously known as Fox's Magisk Module Manager (FoxMMM), this app helps users find, install "Magisk Modules" - powerful little zips/apps for your device that plug into the Magisk framework.
https://www.androidacy.com
GNU Lesser General Public License v3.0
957 stars 34 forks source link

Bump ly.count.android:sdk from 24.1.1 to 24.7.1 #146

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps ly.count.android:sdk from 24.1.1 to 24.7.1.

Release notes

Sourced from ly.count.android:sdk's releases.

24.7.1

  • ! Minor breaking change ! Unsupported types for user properties will now be omitted, they won't be converted to strings.

  • Added support for mixed type of immutable lists, arrays to client given segmentations and user properties.

  • Added array, list and JSONArray support to the user properties.

  • Mitigated issues where:

    • session was ending with device ID change without merge, when consent was not required and manual session control was enabled.
    • session was not starting after device ID change without merge, when consent was not required and automatic sessions were enabled.

24.7.0

  • ! Minor breaking change ! User properties will now be automatically saved under the following conditions:

    • When an event is recorded
    • During an internal timer tick
    • Upon flushing the event queue
  • Added array, List, and JSONArray support to all user-given segmentations. They will support only mutable and immutable versions of the primitive types. Which are:

    • String, Integer, int, Boolean, bool, Float, float, Double, double, Long, long
    • Keep in mind that the float array will be converted to a double array by the JSONArray
  • Mitigated an issue where remote config values caching was changing due to a device ID change, but it is not anymore. It is linked to the configuration "enableRemoteConfigValueCaching" now.

  • Mitigated an issue related to the device ID by creating an internal migration.

  • Resolved a problem where revoked consents were sent after changes without merging.

  • Fixed a bug that caused the device ID to be incorrectly set after changes with merging.

  • Mitigated an issue where, on consent revoke, remote configuration values were cleared, but they are not anymore.

  • Change device id with merge not reporting session duration anymore.

24.4.1

  • ! Minor breaking change ! Mitigated an issue where internal SDK limits did not apply

  • Added support for Feedback Widget terms and conditions

  • Added a new function "setID(newDeviceId)" which internally handles merge/non-merge selection while changing the device ID

  • Mitigated an issue where the session duration could have been calculated wrongly after a device ID change without merge

  • Mitigated an issue where a session could have continued after a device ID change without merge

24.4.0

  • ! Minor breaking change ! If a manual session is already started, it will not be possible to call "BeginSession" without stopping the previous one

  • ! Minor breaking change ! If a manual session has not been started, it will not be possible to call "UpdateSession"

  • ! Minor breaking change ! If a manual session has not been started, it will not be possible to call "EndSession"

  • ! Minor breaking change ! Setting for enabling/disabling for native crash dumps will be always enabled

  • Added an extended way of crash filtering

  • Added SDK internal limits configuration interface

  • Deprecated the following calls from "CountlyConfig":

    • "setMaxSegmentationValues(maxSegmentationValues)" instead use "sdkInternalLimits.setMaxSegmentationValues(maxSegmentationValues)"
    • "setMaxBreadcrumbCount(maxBreadcrumbCount)" instead use "sdkInternalLimits.setMaxBreadcrumbCount(maxBreadcrumbCount)"
    • "setCrashFilterCallback(crashFilterCallback)" instead use "crashes.setGlobalCrashFilterCallback(globalCrashFilterCallback)"

... (truncated)

Changelog

Sourced from ly.count.android:sdk's changelog.

24.7.1

  • ! Minor breaking change ! Unsupported types for user properties will now be omitted, they won't be converted to strings.

  • Added support for mixed type of immutable lists, arrays to client given segmentations and user properties.

  • Added array, list and JSONArray support to the user properties.

  • Mitigated issues where:

    • session was ending with device ID change without merge, when consent was not required and manual session control was enabled.
    • session was not starting after device ID change without merge, when consent was not required and automatic sessions were enabled.

24.7.0

  • ! Minor breaking change ! User properties will now be automatically saved under the following conditions:

    • When an event is recorded
    • During an internal timer tick
    • Upon flushing the event queue
  • Added support for array, List and JSONArray to all user given segmentations. They will support only mutable and ummutable versions of the primitive types. Which are:

    • String, Integer, int, Boolean, bool, Float, float, Double, double, Long, long
    • Keep in mind that float array will be converted to the double array by the JSONArray
  • Mitigated an issue where remote config values caching was changing by device id change, not anymore. It is linked to the configuration "enableRemoteConfigValueCaching" now.

  • Mitigated an issue related to the device ID by creating an internal migration.

  • Resolved a problem where revoked consents were sent after changes without merging.

  • Fixed a bug that caused the device ID to be incorrectly set after changes with merging.

  • Mitigated an issue where on consent revoke, remote config values were cleared, not anymore.

  • Change device id with merge not reporting session duration anymore.

24.4.1

  • ! Minor breaking change ! Mitigated an issue where internal SDK limits did not apply

  • Added support for Feedback Widget terms and conditions

  • Added a new function "setID(newDeviceId)" which internally handles merge/non-merge selection while changing the device ID

  • Mitigated an issue where the session duration could have been calculated wrongly after a device ID change without merge

  • Mitigated an issue where a session could have continued after a device ID change without merge

24.4.0

  • ! Minor breaking change ! If a manual session is already started, it will not be possible to call "BeginSession" without stopping the previous one

  • ! Minor breaking change ! If a manual session has not been started, it will not be possible to call "UpdateSession"

  • ! Minor breaking change ! If a manual session has not been started, it will not be possible to call "EndSession"

  • ! Minor breaking change ! Setting for enabling/disabling for native crash dumps will be always enabled

  • Added an extended way of crash filtering

  • Added SDK internal limits configuration interface

  • Deprecated the following calls from "CountlyConfig":

    • "setMaxSegmentationValues(maxSegmentationValues)" instead use "sdkInternalLimits.setMaxSegmentationValues(maxSegmentationValues)"
    • "setMaxBreadcrumbCount(maxBreadcrumbCount)" instead use "sdkInternalLimits.setMaxBreadcrumbCount(maxBreadcrumbCount)"
    • "setCrashFilterCallback(crashFilterCallback)" instead use "crashes.setGlobalCrashFilterCallback(globalCrashFilterCallback)"

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
CLAassistant commented 3 months ago

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

dependabot[bot] commented 3 months ago

Superseded by #149.