Skip to content
This repository has been archived by the owner on Feb 13, 2019. It is now read-only.
This repository has been archived by the owner on Feb 13, 2019. It is now read-only.

Scripts Error 'PridelandDocumentError error 0' #129

Closed
jamiejenkins opened this issue Apr 24, 2018 · 16 comments
Closed

Scripts Error 'PridelandDocumentError error 0' #129

jamiejenkins opened this issue Apr 24, 2018 · 16 comments
Assignees
Labels
bug Something isn't working

Comments

@jamiejenkins
Copy link

jamiejenkins commented Apr 24, 2018

I have latest beta on an iPad and iPhone and get the error when trying to open up scripts on both. Additionally the script I managed to create before the error started is still there but doesn't show up as when I try to create a new one with name 'test' it says it already exists. I've got it set to iCloud Storage on both devices.

badddd76-f052-4ed1-a76c-3d40caea07a3

@jamiejenkins
Copy link
Author

manually deleting the contents of ~/.scripts/ directory seems to fix the issue.

@shaun-h
Copy link

shaun-h commented Apr 26, 2018

I am also seeing this, I created a script on my iPad and I get this error on my iPhone

@alessaba
Copy link
Contributor

alessaba commented Apr 26, 2018

Can confirm this bug. I think it has to do with iCloud syncing

@louisdh louisdh added the bug Something isn't working label Apr 26, 2018
@alessaba
Copy link
Contributor

UPDATE: It seems to sync the .scripts folder just fine, and it knows what scripts are in there (i tried re-importing a previously imported example and it says it's duplicated), but it still doesn’t show ant scripts in the view controller.

@alessaba
Copy link
Contributor

Also, running the cub command manually returns
Missing file ".scripts/a.prideland/contents/.1.cub.icloud"

Which to me seems like the file hasn’t been downloaded yet from iCloud.
Is there a way to download all the .scripts contents from icloud at app launch?

Sent with GitHawk

@alessaba
Copy link
Contributor

Build 35 doesnt seem to have fixed the issue :-/

@jamiejenkins
Copy link
Author

On the device where the script is created there is a .1.cub file and the device it is syncing to there is the placeholder .1.cub.icloud file. So I think you are right and it is not actually synching the file data itself. I just tested again on Build 35 as well.

@louisdh
Copy link
Owner

louisdh commented May 16, 2018

Thanks for the info, build 36 (available on TestFlight now) should fix this.

@louisdh louisdh self-assigned this May 16, 2018
@alessaba
Copy link
Contributor

😭GitHawk Upload by filippocld

Sent with GitHawk

@louisdh
Copy link
Owner

louisdh commented May 16, 2018

At least the improved error handling works! It's now clear that there's a problem with syncing the metadata.plist from your a.prideland.

@jamiejenkins
Copy link
Author

Yes, still an issue on build 36. I deleted everything in .scripts, started app on iPad and imported a script, started app on iPhone and got error when looking at the scripts. On the iPhone it has .metadata.plist.icloud instead of .metadata.plist

@louisdh
Copy link
Owner

louisdh commented May 16, 2018

Does build 37 fix it by any chance?

@alessaba
Copy link
Contributor

Yep! It fixed it!
Thank you so much 😊

@louisdh
Copy link
Owner

louisdh commented May 16, 2018

@jamiejenkins If you can confirm that it's fixed I will close this issue.

@jamiejenkins
Copy link
Author

I can confirm that it is working now! 👍🏻

@louisdh
Copy link
Owner

louisdh commented May 16, 2018

Awesome, thank you all so much for testing!

@louisdh louisdh closed this as completed May 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants