Issue Description:
overwolf.extensions.io.getStoragePath(overwolf.extensions.io.enums.StorageSpace.videos,console.log)
does not represent the path where recordings are stored if the app’s display name is not the same as the internal name in manifest.json
Can you reproduce it (exact steps to reproduce):
- create an App (let’s call it “Demo”)
- change display-name of the app (let’s say to DemoChanged)
- record a highlight
- check
overwolf.extensions.io.getStoragePath(overwolf.extensions.io.enums.StorageSpace.videos,console.log)
You will find that the highlight is stored in a sub-folder with DemoChanged
while in 4) you will receive the folder with the name Demo
Impact for my app:
High - due to internals that are checking against the overwolf storage path we get each highlight duplicated because the API is not working as expected.
The implementation in a “future proof way” which was supposed to catch when the storage path changes now fails because the display name of our app changed ( and with that the ACTUAL storage path of the highlights), while this is not reflected by the call of overwolf.extensions.io.getStoragePath(overwolf.extensions.io.enums.StorageSpace.videos,console.log)
Do you currently have a workaround?
Yes, changing our internal implementation. But I would like to prevent changing our internals to something hard-coded unless this is working as intended.
So please let me know if this is going to be fixed/changed.