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

No value associated with key CodingKeys(stringValue: \"dimension\", intValue: nil) #28

Closed
cemolcay opened this issue Dec 10, 2018 · 4 comments
Assignees

Comments

@cemolcay
Copy link

I'm getting this error while trying to read a sheet from a parsed xlsx file.
I think the error is happening on the Worksheet file, where it has CodingKeys enum and a dimension case.
It looks like related with #12, #15 and #24 issues.

Fatal error: Error raised at top level: 
Swift.DecodingError.keyNotFound(CodingKeys(stringValue: "dimension", intValue: nil),
Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: \"dimension\", intValue: nil) (\"dimension\").", underlyingError: nil))
@cemolcay
Copy link
Author

cemolcay commented Dec 10, 2018

OK, I made some progress.

  • First of all, I made the dimension on Worksheet to optional.
  • Then made all Pane values to optional.
  • Lastly, I had an error related to formula in Cell
CodingKeys(stringValue: "f", intValue: nil)
      - debugDescription : "Expected to decode String but found a dictionary instead."

So, I commented out formula and its related CodingKeys.formula case, then it worked.

@cemolcay
Copy link
Author

New update, again. I was using the last release 0.3.0 but updated it to the version on the master branch. I still need to make dimension optional.
Now, I'm getting the same error "Expected to decode String but found a dictionary instead." on shared string's text property as well.

@MaxDesiatov
Copy link
Collaborator

Hi @cemolcay, sorry for the delay. Is this reproducible for you in CoreXLSX 0.4.0?

@MaxDesiatov MaxDesiatov assigned hodovani and cemolcay and unassigned hodovani Feb 7, 2019
@cemolcay
Copy link
Author

cemolcay commented Feb 8, 2019

No, I think it fixed, thanks!

@cemolcay cemolcay closed this as completed Feb 8, 2019
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

3 participants