You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the macOS app is not sandboxed, NSSearchPathForDirectoriesInDomains returns paths in the ~/Library (Application Support, Caches...), and CachingManager creates a directory ~/Library/Application Support/GrowthBook-Cache with a FeatureCache.txt file in it.
Unfortunately, CachingManager has no interface to change the cache directory with a path string or URL that will not be linked to the root ~/Library. And since filenames are hardcoded too and we can't add path to the filenames.
The text was updated successfully, but these errors were encountered:
@vazarkevych , I forgot to mention that this will lead to the situation when 2 non-sandboxed apps with integrated GrowthBook SDK use the same file on a machine, and the cache state will be wrong.
Hi.
If the macOS app is not sandboxed,
NSSearchPathForDirectoriesInDomains
returns paths in the~/Library
(Application Support
,Caches
...), and CachingManager creates a directory~/Library/Application Support/GrowthBook-Cache
with a FeatureCache.txt file in it.Unfortunately, CachingManager has no interface to change the cache directory with a path string or URL that will not be linked to the root
~/Library
. And since filenames are hardcoded too and we can't add path to the filenames.The text was updated successfully, but these errors were encountered: