Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with Sketch Cloud #142

Open
stephannielsen opened this issue Dec 10, 2019 · 1 comment
Open

Integration with Sketch Cloud #142

stephannielsen opened this issue Dec 10, 2019 · 1 comment

Comments

@stephannielsen
Copy link

stephannielsen commented Dec 10, 2019

We are working as a team and share our designs via Sketch Cloud with others. We are running into the problem that we often have to upload an entirely new version which receives a new generated link in the Sketch Cloud.

After a little bit of research, the problem seems to be that Sketch writes some kind of identifier into the (binary) sketch file after the upload. This is used to identify the prototype on next update. It seems this identifier is not included in the JSON files that are committed to the repository and only available in the local .sketch file. Then, each time the local .sketch files is re-generated from the exploded JSON files, the identifier is lost and the version in the cloud cannot be updated.

When working as a team, this creates a lot of problems:

  • New links have to be distributed
  • Losing versions in Sketch Cloud
  • Only one person can update (whoever published the last version and still has the same local file)

Do you think it is possible to include the identifier in the JSON files and correctly include it in the generated .sketch file?

I found this issue raised in the Abstract forum, describing the same issue.

https://spectrum.chat/abstract/bugs/new-sketch-cloud-link-after-every-upload~f8e8b308-76e6-4e06-8c0a-676a34105946

Looks like they have no workaround either. One difference is that they also commit the .sketch files. This creates other problems though with merging etc., also causing to lose the identifier.

@stephannielsen
Copy link
Author

*push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant