When running the ui it creates the needed config files in appdata and points the data location to the same. But as a user, I want to change the data location (my c drive isn't large and can't hold tons and tons of data).
So after the ui creates the folders a user shuts down the ui, opens the config file located in appdata, and sets the data location to where they want it. Then they rerun the app expecting it to run fine and start syncing. Instead, they get an infinite loading screen.
I just downloaded the ui, launched it (gave an error about ui folder not existing in appdata), relaunched it (created the files itself), closed it, changed the config file to point to my second drive just for the data storage part, and finally relaunched the app. It gave me an infinite loading screen that went nowhere. No errors, nothing but "loading...".
I thought I broke something and deleted everything and restarted the process. Again got infinite loading.
Decided maybe the app can't handle when the folder doesn't exist (since it crashes on the first run for the same reason) and copied the existing sia folder from the appdata to the new location (leaving everything else in appdata) and relaunched the app. This time it worked, though it took a long time to load. It gave me a message about loading takes longer if you upgrade the app then started fine awhile later.
There seems to an issue where the UI can't handle config changes very well. I expected it to read the location, see it doesn't exist, and then create it like it does the second time your run it (yes that would restart the sync from 0% but that's what I expect and want as a user). That or give a warning that "Hey! I need the folder to exist first!" so I know to create it or copy the old one.
When running the ui it creates the needed config files in appdata and points the data location to the same. But as a user, I want to change the data location (my c drive isn't large and can't hold tons and tons of data).
So after the ui creates the folders a user shuts down the ui, opens the config file located in appdata, and sets the data location to where they want it. Then they rerun the app expecting it to run fine and start syncing. Instead, they get an infinite loading screen.
I just downloaded the ui, launched it (gave an error about ui folder not existing in appdata), relaunched it (created the files itself), closed it, changed the config file to point to my second drive just for the data storage part, and finally relaunched the app. It gave me an infinite loading screen that went nowhere. No errors, nothing but "loading...".
I thought I broke something and deleted everything and restarted the process. Again got infinite loading.
Decided maybe the app can't handle when the folder doesn't exist (since it crashes on the first run for the same reason) and copied the existing sia folder from the appdata to the new location (leaving everything else in appdata) and relaunched the app. This time it worked, though it took a long time to load. It gave me a message about loading takes longer if you upgrade the app then started fine awhile later.
There seems to an issue where the UI can't handle config changes very well. I expected it to read the location, see it doesn't exist, and then create it like it does the second time your run it (yes that would restart the sync from 0% but that's what I expect and want as a user). That or give a warning that "Hey! I need the folder to exist first!" so I know to create it or copy the old one.