Already a few issues about this. They are closed by some reason but we've been hitting this error on and off which feels kinda unstable.
Any thoughts or plans to fix it for good?
Thanks
Today I have noticed that the most recent dSYM in our Sentry is dated 2 months ago 馃槺 (we have only had a few releases yet).
Nothing has changed in the project setup or in the dSYMs upload script, and it was working just fine before. But currently, I always get a dreaded EOF while parsing a value at line 1 column 0 error, no matter what I do or how I run the script. Note that the same error issued even when dSYMs folder parameter is omitted...
Any suggestions or workaround? There is no other way to upload dSYMs to Sentry, and without dSYMs Sentry is pretty much useless to us 馃槥
Please help 馃檹

@kamilogorek still no news ?
I've got the same problem, and as said by @SergejLogis :
There is no other way to upload dSYMs to Sentry, and without dSYMs Sentry is pretty much useless to us
Uploads started to work few days after we first hit the issue, without any changes from our side. However, today we have released a new version of our app and the issue resurfaced. 馃槙 Again, without any changes from our side...
The upload worked when I did "cd DSYM_FOLDER" and then used "./" in the sentry-cli command instead of the full path.
Most helpful comment
Today I have noticed that the most recent dSYM in our Sentry is dated 2 months ago 馃槺 (we have only had a few releases yet).

Nothing has changed in the project setup or in the dSYMs upload script, and it was working just fine before. But currently, I always get a dreaded
EOF while parsing a value at line 1 column 0error, no matter what I do or how I run the script. Note that the same error issued even when dSYMs folder parameter is omitted...Any suggestions or workaround? There is no other way to upload dSYMs to Sentry, and without dSYMs Sentry is pretty much useless to us 馃槥
Please help 馃檹