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

Error ParseCellContent #51

Closed
pakhiAish opened this issue Apr 2, 2019 · 5 comments
Closed

Error ParseCellContent #51

pakhiAish opened this issue Apr 2, 2019 · 5 comments
Assignees

Comments

@pakhiAish
Copy link

I am getting an error while reading excel sheet cell content.
using this method to read content. file.parseSharedStrings()
getting an error this "Expected to decode String but found SharedBox instead."
SampleExcel.xlsx

@MaxDesiatov MaxDesiatov self-assigned this Apr 7, 2019
@MaxDesiatov
Copy link
Collaborator

hi @pakhiAish, thank you for reporting this and sorry for the delayed reply.

This issue is currently blocked by CoreOffice/XMLCoder#89, but that's going to be merged in the next few days as soon as maintainers of XMLCoder repository are able to review that PR. Then I'll be able to bump XMLCoder version here and resolve it in CoreXLSX. Thanks for understanding 🙏

@MaxDesiatov
Copy link
Collaborator

Hi @pakhiAish, this issue has been fixed in the master branch and I was able to verify it with your file. Would you be able to confirm it? Thanks and sorry again for the delay!

@MaxDesiatov MaxDesiatov assigned pakhiAish and unassigned MaxDesiatov Apr 16, 2019
@pakhiAish
Copy link
Author

Hello,
I am still getting the same error message.
Like This-- debugDescription: "Expected to decode String but found SharedBox instead."
I update my pod file. But cannot read excel file.

@MaxDesiatov
Copy link
Collaborator

I've just released version 0.5.0. Could you please update your Podfile/Cartfile/Package.swift to 0.5.0 and run a corresponding update command for your package manager? I'm able to reproduce the issue with the old version with the file you attached, but not with the new 0.5.0 version, so I'm still hoping there was a problem of installing not too fresh version from master. Pretty sure that installing 0.5.0 fixes this. Please let me know how that goes for you @pakhiAish

@pakhiAish
Copy link
Author

pakhiAish commented Apr 23, 2019 via email

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

2 participants