TL;DR:
Try to avoid pinning any extensions on a new device’s Brave Browser before syncing is finished or it will take away any of your old pins.
Sometimes it can take a while for the sync chain to update on a mobile device in case you need to delete it or something. Just wait and it will clear eventually.
–
Detailed:
I recently was putting Brave on a new device and wanted to sync it with my sync chain. It’s been ages since I’ve done this and when I tried I got an error that said I was using a sync chain created on a deprecated version of Brave.
Finding out I needed to delete my sync chain and create a new one was easy enough. Creating a new one was fine as well and it worked just fine on my new device.
The strange interaction was that my pinned extensions used my new device rather than my old one. I’m guessing it’s a feature since I did install an extension on the new device’s Brave Browser in order to grab the sync code.
From skimming through how the sync chain works I’m pretty sure since my new device was the most recently edited when it came to pinned extensions (I did pin the only extension I installed) it saw it as being the one to propagate.
I know how I can avoid the issue in the future. Just need to not pin any extensions or maybe even not install any just in case. Not a big deal.
The other issue I had was that after deleting the old sync chain and trying to update it on my phone it was still there and trying to delete it wouldn’t work and made Brave crash.
Whether that was trying to remove the devices or pushing the button to delete the sync chain it would just accept the “Ok” button and do nothing. It didn’t crash right away but a few minutes later it did.
I think it took about thirty minutes before eventually going to the settings showed that syncing was cleared and was ready to be setup.
Not sure if the issue was because of using an old sync chain or that it just takes a long time to update the chain on a phone. Either way it does work itself out eventually.
Just wanted to post this in case anyone else has the same issue.