6.Change Log

Description of changes and detected errors of Falcon Analytic through versions (from 2.0.0)

• 3.0.9:

  • Add log IDFV for IOS

  • Fix the flow to get IDFA for IOS, prevent to get string, returned 000000-00000

• 3.0.7:

  • Improvements to suit new abTest

• 3.0.0:

  • Restructure SDK, performance optimized

• 2.2.4:

  • Changed Singleton -> FSingleton according to Core package

• 2.2.3:

  • Adjusted functions to check the length limit of strings, limit values of numbers, etc

  • Adjusted concurrency, patched API_ID duplication error in version 2.2.0

  • Patched ActionLog error in version 2.2.1

  • Error log functions, instead of being set to log.warning, are now changed to log.error as users often do not pay attention to log.warning; at the same time, the log function will try to bring the user's values back to the correct format to log instead of discarding them as before

  • Removed the limit on the number of times a message sends an error, patched the message interval error in version 2.2.0

  • Added clientCreatedDate for DWHMessage

• 2.2.2:

  • Increased timeout of messages sent to server

  • Adjusted the name of the RemoteConfig ActionLog variable

  • Adjusted the inapp log calling function

• 2.2.1:

  • Added sessionId for ActionLog, adjusted the constructor of ActionLog

  • Limited the sending of ActionLog via RemoteConfig

  • Moved AnalyticParams from Analytic plugin to Core and renamed it to PlayerParams

  • Moved FalconAbTesting from FalconAnalytic to FalconCore

  • Bug:

    • The limitation of ActionLog was not thorough as it did not consider the case of Json Serialize

• 2.2.0:

  • Completely optimized FalconAnalytic, fixed lingering errors from previous versions (unknown version of origin), including:

    • Level error in ActionLog

  • Consolidated all variants of DwhSimplifyLog, DWHLog, DwhLogCache into one

  • Opened API allowing users to change player's statistical parameters (AnalyticParams)

  • Sent clearer messages on the console to help users recognize if the log has been sent

  • Bug:

    • Messages sent were spaced out, duplicated API_ID

• 2.1.7:

  • Sent the last session log at the end of each game session

• 2.1.6:

  • Experimented with automatically sending a log session every 10 seconds about the total play time of the player

• 2.1.5:

  • Preprocessed inapp log price string

• 2.1.4:

  • Added Docs for some functions in the SDK

• 2.1.3:

  • Corrected the field names of property log and action log

• 2.1.2:

  • Optimized the management of multithreading

  • Adjusted operation when saving data and logging of the SDK, switched from log.error -> log.warning to avoid user confusion

  • Bug:

    • Multithreading management was not optimized, causing overheating during use

• 2.1.1:

  • Renamed FalconGameObject back to FalconGameObjectUtils

• 2.1.0:

  • Adjusted support mechanism for multithreading

  • Bug:

    • Changing the name of FalconGameObject made some plugins incompatible

• 2.0.7:

  • Adjusted Analytic to be compatible with IL2CPP build high stripping

• 2.0.6:

  • Added DwhLogCache

• 2.0.5:

  • Opened API to adjust Account ID in data analysis

• 2.0.4:

  • Switched C# version back to 5, optimizing support for multiple Unity versions

• 2.0.3:

  • Synchronized with FalconCore 2.0.1, fixed application hanging error

• 2.0.1:

  • Limited string length of itemID of resourceLog

• 2.0.0:

  • Updated SDK Analytic from version 1.4.4 following FalconCore 2.0.0, enhancing system stability

  • Bug:

    • Did not limit string length of itemID of resourceLog