-
Notifications
You must be signed in to change notification settings - Fork 18
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
Unexpected token < in JSON at position 0 #80
Comments
Hi, could you please post the json file causing the problems. I've spent most my time re-writing the pdf-exporter, but I can at least see if there's anything wrong with the file itself. |
Thanks for the quick response! Some friends and I intend to start an The unnumbered file was an attempt to save after the error occurred. I On Tue, Jun 7, 2016 at 6:45 PM, Arthur Moore [email protected]
|
Hello EA the described issue looks like the one I encountered some time ago.See issue #71 . |
So, I honestly don't have the expertise to know how to apply the listed fix.
|
If you'll attach the affected file we can take a look at it. |
Sorry HumboldJoker my post was addressed at EmperorArthur to give him one possible hint whre to look for the problem. |
Hi, I have a similar issue, maybe my JSON save can help. Tested with Firefox 47. |
I tested @matthiasschoger's Abel3.4.2.5alpha2-20160304-211728.json, and discovered that that his error was caused by PHP running out of memory. GET http://eclipsephase.next-loop.com/Creator/version4/secondary-choice/backgrounds.php Returns [...] |
Sorry busy weekend. I'll try to see what's wrong with the file soon.
Here's the Abel file decoded from json to a readable form. |
As you can see the |
Hi. Can confirm this issue with the attahed json. |
After saving and then attempting to load a character, I've run into problems. Most info screens now indicate parsrerror syntaxerror "Unexpected token < in JSON at position 0". The half made character is now stuck in the settings and cannot be changed or reset. Meanwhile, the unending load bar mocks me.
Thanks in advance for the help.
The text was updated successfully, but these errors were encountered: