Participant

Question

Frequency of updates for shared files is out of control

Forum|Forum|5 years ago
November 3, 2020
5 replies
2576 views

Has anyone else found it pretty abrasive how frequent XD's updates have been recently? Specifically, the lack of backwards compatibility for shared files across versions has been a huge pain point for my design team.

For instance, with multiple updates per week, all it takes is one team member on an old version of XD to render a shared file functionally unusable until they update their program. In the scope of things, this is a minor headache, but when it happens multiple times per week it seems pretty unnecessary for an application focused on collaboration? Couldn't there be a way to roll changes that break collaboration functions into larger updates, less frequently?

This topic has been closed for replies.

D

default88kp4yeg49u4

Participant

One year later, still a productivity blocker and major annoyance.

E

evefromlv

Participant

I agree. Please, bundle updates! All our designers are using the same CVI library for asset sharing, which disrupts their work every time you launch an update. We work with presenting XD files during meetings because we have remote team members, so when it's not possible to open a file without updating Adobe XD during a meeting, it simply makes us designers look unprepared. Can't you make some updates "optional" without making the XD files inaccessible? Or let us choose when to update like other systems do? It is a very drastic "My way or the highway" updates policy you enforce on us...

I

Isak KnivslandAuthor

Participant

Bumping this thread again just to highlight a use case that has happened to me multiple times since posting this thread about a week ago. Here, I'm in a file, and see my coworker has joined (indicated by "D" icon)

But this is the message they receive:

But I never get a notice that they are unsuccessful joining, or that my version of XD is out of date compared to what other users of a shared file are using. If weekly updates (or multiple updates per week) are going to be a reality, this feels like a pretty essential feature to have.

elainecc

Community Manager

We're definitely working on some notification that lets you know that someone is trying to enter the document with a newer version of the document. Of course, we also need to balance out for situations where people might not be able to stop what they're doing to upgrade (an example is in the middle of a client presentation, or other high stakes meeting). You can expect to see some improvements in this area soon!

elainecc

Community Manager

Hi there! I wanted to follow up on Rishabh's comment on this. We try to limit the number of releases we do in a cycle (it's pretty expensive for us to do, after all), but we did release a second dot release to address a critical quality issue. If it's any reassurance, we do recognize the disruption involved and are working on some longer range solutions to make documents a little more flexible so as to minimize the impact in the future.

Hope that helps!

Elaine Chao

Sr. Product Manager, Adobe XD

I

Isak KnivslandAuthor

Participant

Hey @elainecc, glad to hear that this is a documented issue – and I can appreciate the immense complexity involved in managing collaborative features at scale. I will confirm though, per @monterxz comments, that this has been much more common than a one-time thing.

Because I can’t help but solution a bit... a few thoughts come to mind:

If this is truly unavoidable, could there be some ways to nudge all users to turn on auto-updates for XD specifically, in-app rather than requiring messing with CC settings?
The messaging when an XD version conflict is detected is prompted on the machine of the user who just tried to open a file, but not on the machine of the user who is causing the conflict if they already have the file open.

Something like “you’re preventing a user from opening a file” (but worded in a less
shameful way) for the user who is a version behind could at least help align versions without requiring back and forth messages of “hey, please let me in”

monterxz

Inspiring

Got it. That's not the expected behavior, and I'd love to dig into this more with your team. If you can have your coworker who tried to upgrade but couldn't get it run the Creative Cloud Log Collector Tool, that would really help me try to escalate this to the right team. (It's not XD, unfortunately!) You can either send me a link to the .zxp it creates on your Desktop or upload it to Adobe Support and send me the name of the ZXP as it shows in the tool for us.

If you can get me the logs and the time and date that this happened (plus your time zone), it would really help us make sure this doesn't happen again.

Hi

My co-worker uploaded her logs:

"Dear User,

The following file has been uploaded on Adobe LogCollector Portal:

File: AdobeLogs_20201105_114503_533-mac.zip

Please use the above filename as a reference when contacting Adobe Customer Care."

This happened on Monday, Nov 2. We are both in UTC+1 (Central European Time). As I mentioned before I've started at about 11:00am and already got an update. She finally got it somewhere around 4:30pm.

Hope this will help

Rishabh_Tiwari

Community Manager

Hi there,

We're so sorry to hear about the trouble. I understand your concern, collaboration may get affected if the collaborators are not on the latest version and frequent updates can cause such a situation. Regarding the frequent updates, we are committed to enhancing the performance that's why we keep pushing updates regularly. Having said that, I'll share your feedback with the Engineering team.

Regards

Rishabh

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded