Sync Broken in Current Snapshot
-
perhaps the sync was disabled on server-side to protect users from syncing broken data.
-
That's possible. Nothing had changed browser-side before it happened. The only thing I can think of is that I added a couple of bookmarks in the stable version on my work laptop, and after that, sync disconnected on my personal laptop.
-
@katherine1 same thing its the reason i came here
-
Surely it's a server-side issue? The last snap was released 4 days ago but it's only today people have noticed this?
-
There's a problem on some machines with Bookmark sync in snapshots right now. It's being worked on. It's not server-side.
-
-
Same issue here. Just came in to report
-
Same issue for the past 3 days.
-
@gaderderian It was announced in the snapshot blog. Sync in Snapshots is disabled until some fixes are made.
-
@ayespy I came to report that I was having this issue as well. I'm patient though! Thanks for the update.
-
@ayespy I've installed stable version on my android phone and it crashes every time I try to log into the synchronisation.
Android 11, Samsung Galaxy A71, Vivaldi v 4.0.2313.19
-
@aladinrun said in Sync Broken in Current Snapshot:
@ayespy I've installed stable version on my android phone and it crashes every time I try to log into the synchronisation.
Android 11, Samsung Galaxy A71, Vivaldi v 4.0.2313.19
I'm afraid I can't account for that. Stable sync works on all platforms (W7, W10, LinuxMint, Android) here.
-
@aladinrun said in Sync Broken in Current Snapshot:
@ayespy I've installed stable version on my android phone and it crashes every time I try to log into the synchronisation.
Android 11, Samsung Galaxy A71, Vivaldi v 4.0.2313.19
My guess: you ran sync from a snapshot first... a snapshot breaks the sync data which then crashes any other place you try and log in - that's why they stopped snapshots from using sync!
If you have a stable version with up to date bookmarks etc. then you can use that to reset sync - otherwise you just have to disable sync until this is fixed.
-
@ayespy + team, it's been over a week now that this sync issue arose with the snapshots for desktop and mobile. Meanwhile many many users are stumbling, struggling and wondering as can be read in this forum section.
What I truly cannot understand is that the users, Vivaldi's most precious asset, are kept in the dark about the status and progress on the fixing of this serious issue. I'd say to the Vivaldi team: keep your friends close and up to date. Inform us! -
@s_paternotte It's apparently fixed internally. The next snapshot should contain the fix. Developers do not publish their status/work/progress on unfinished fixes. There's no time.
-
@ayespy said in Sync Broken in Current Snapshot:
Developers do not publish their status/work/progress on unfinished fixes. There's no time.
I see. (heavy British undertone here)
As the Vivaldi user base is growing, maybe this could be reconsidered. Particularly in situations where something has seriously gone amiss.
I got annoyed to the point of uninstalling Snapshot and switching to Stable.I know, you're not the team. But I assume someone will notice this.
-
@s_paternotte I don't think they can reconsider how much time there is in the day. The size of the team vs the size of the job simply means they are always backlogged, and almost nothing gets done on time. That and, Jon's teams, in the more than two decades I have been observing them, have never issued progress reports to anyone - even when he had a team of over 200 (of course, then, he had been growing that project for 20 years or so, and had over 50M users, so devs-per-user was actually even a worse ratio than at present.)
-
@s_paternotte said in Sync Broken in Current Snapshot:
What I truly cannot understand is that the users, Vivaldi's most precious asset, are kept in the dark about the status and progress on the fixing of this serious issue.
I can't say I share the same feeling. Although it's true that there is often very little information about what's planned to do or when it's planned to be released, more often than not serious bugs like this one usually get lots of feedback.
Just from what I've been reading in the posts here in the forum in the last days, I found out that:
- the problem was detected (new builds were corrupting the sync profile or something like that)
- sync was disabled at server side for the faulty builds to avoid corrupting any further profiles
- yesterday a new build was launched that should fix the issue. The know issues section even explains what to do in case your profile had been corrupted: https://vivaldi.com/blog/mobile/android-4-1-2350-3/
I think it can be argued that this information could have been presented in a more organized fashion. What happened was dozens of posts inquiring about the problem (many of them created because people simply don't search before they ask - or at least don't use the right search terms - as in many cases the answer came within minutes pointing them to other posts or to the know issues section in the desktop build blog posts and the users acknowledging that they should have searched better). And the new information, when it arrived, was scattered through those posts, often being posted in the most recent one or something like that. But there was definitely information circulating around, some of which even came from people who have contact with "the team" or are part of the team themselves.
Maybe for scenarios like this, when a critical bug has occurred (and is likely to be fixed soon, as is usually the case with critical bugs), and multiple posts start showing up about it, one of the first posts should be pinned or something similar, so that people would find it more easily and new which one to refer to, avoid asking in multiple places... or creating a new issues section for desktop builds... or one of those forum wide messages, like when there's a downtime scheduled or something similar...
I don't know, just leaving some food for thought. -
@pauloaguia I think rather than just hiding a known issue about it in the description of the desktop snapshot where the issues started - much later than when most people originally read the snapshot announcement! - there should have been a dedicated thread in the "announcements" blog/forum with notifications linking to it in the "support & troubleshooting" forum and at the top of the Vivaldi website.
-
While I agree that the issue was high-impact, we all have to keep in mind that it was in the snapshot releases.
I think we all understand the risks that come when not using the main branch of an application. Vivaldi's team has always been responsive and engaging in the forums.
So then again, don't lose focus that by using the snapshot you should be comfortable with some risks.