Setting `storage` to `'none'` still sets some local storage values

[ordishg]

Expected Behavior

When the storage option is set to 'none', amplitude should not set any cookies or local storage.

Current Behavior

Amplitude still sets the amplitude_unsent_* and amplitude_unsent_identify_* values.

If this is expected behaviour, then it would be helpful for this to be documented on the storage option.

Steps to Reproduce

1. Initialise Amplitude with the option storage: 'none'
2. Visit the page with Amplitude running on it
3. Check local storage
4. Find that there are local storage values set by amplitude

Environment

• JS SDK Version: 8.21.9
• Installation Method: yarn
• Browser and Version: Firefox 133.0.3 (64-bit)

[Mercy811]

Hi @ordishg, config.storage is for metadata (identity info) only https://github.com/amplitude/Amplitude-JavaScript/blob/a9ff3247829bba9fccb60dcf83337809e83f1c04/src/metadata-storage.js. Unsent events are always saved in local storage and it's not configurable. If you'd like to not save unsent events, you can migrate to Browser 2.0 which supports setting config.storageProvider.

[ordishg]

Hi @Mercy811, thanks for clarifying. It seems to me like setting saveEvents to false should avoid saving unsent events to local storage, even without migrating to Browser 2.0. Am I misunderstanding what that config option does?

[Mercy811]

saveEvents should work!