Agfdhyk

You're receiving HTML (or XML) back from the server, but the dataType: json is telling jQuery to parse as JSON. Check the "Network" tab in Chrome dev tools to see contents of the server's response.

This ended up being a permissions problem for me. I was trying to access a url I didn't have authorization for with cancan, so the url was switched to users/sign_in. the redirected url responds to html, not json. The first character in a html response is <.

In my case, I was getting this running webpack, and it turned out to be some corruption somewhere in the local node_modules dir.

rm -rf node_modules

npm install

...was enough to get it working right again.

I experienced this error "SyntaxError: Unexpected token m in JSON at position", where the token 'm' can be any other characters.

It turned out that I missed one of the double quotes in the JSON object when I was using RESTconsole for DB test, as {"name: "math"}, the correct one should be {"name": "math"}

It took me a lot effort to figure out this clumsy mistake. I am afraid others would run into similar bummers.

I my case the error was a result of me not assigning my return value to a variable. The following caused the error message:

return new JavaScriptSerializer().Serialize("hello");

I changed it to:

string H = "hello";

return new JavaScriptSerializer().Serialize(H);

Without the variable JSON is unable to properly format the data.

I had the same error message following a tutorial. Our issue seems to be 'url: this.props.url' in the ajax call. In React.DOM when you are creating your element, mine looks like this.

ReactDOM.render(

    <CommentBox data="/api/comments" pollInterval={2000}/>,

    document.getElementById('content')

);

Well, this CommentBox does not have a url in its props, just data. When I switched url: this.props.url -> url: this.props.data, it made the right call to the server and I got back the expected data.

I hope it helps.

My problem was that I was getting the data back in a string which was not in a proper JSON format, which I was then trying to parse it. simple example: JSON.parse('{hello there}') will give an error at h. In my case the callback url was returning an unnecessary character before the objects: employee_names([{"name":.... and was getting error at e at 0. My callback URL itself had an issue which when fixed, returned only objects.

This error occurs when you define the response as application/json and you are getting a HTML as a response. Basically, this happened when you are writing server side script for specific url with a response of JSON but the error format is in HTML.

In my case, for an Azure hosted Angular 2/4 site, my API call to mySite/api/... was redirecting due to mySite routing issues. So, it was returning the HTML from the redirected page instead of the api JSON. I added an exclusion in a web.config file for the api path.

I was not getting this error when developing locally because the Site and API were on different ports. There is probably a better way to do this ... but it worked.

<?xml version="1.0" encoding="UTF-8"?>



<configuration>

    <system.webServer>

        <rewrite>

        <rules>

        <clear />



        <!-- ignore static files -->

        <rule name="AngularJS Conditions" stopProcessing="true">

        <match url="(app/.*|css/.*|fonts/.*|assets/.*|images/.*|js/.*|api/.*)" />

        <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />

        <action type="None" />

        </rule>



        <!--remaining all other url's point to index.html file -->

        <rule name="AngularJS Wildcard" enabled="true">

        <match url="(.*)" />

        <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />

        <action type="Rewrite" url="index.html" />

        </rule>



        </rules>

        </rewrite>

    </system.webServer>

</configuration>

This might be old. But, it just occurred in angular, the content type for request and response were different in my code. So, check headers for ,

 let headers = new Headers({

        'Content-Type': 'application/json',

        **Accept**: 'application/json'

    });

in React axios

axios({

  method:'get',

  url:'http://  ',

 headers: {

         'Content-Type': 'application/json',

        Accept: 'application/json'

    },

  responseType:'json'

})

jQuery Ajax:

 $.ajax({

      url: this.props.url,

      dataType: 'json',

**headers: { 

          'Content-Type': 'application/json',

        Accept: 'application/json'

    },**

      cache: false,

      success: function (data) {

        this.setState({ data: data });

      }.bind(this),

      error: function (xhr, status, err) {

        console.error(this.props.url, status, err.toString());

      }.bind(this)

    });

  },

After spending a lot of time with this, I found out that in my case the problem was having "homepage" defined on my package.json file made my app not work on firebase (same 'token' error).
I created my react app using create-react-app, then I used the firebase guide on the READ.me file to deploy to github pages, realized I had to do extra work for the router to work, and switched to firebase. github guide had added the homepage key on package.json and caused the deploy issue.

Protip: Testing json on a local Node.js server? Make sure you don't already have something routing to that path

'/:url(app|assets|stuff|etc)';

On a general level this error occurs when a JSON object is parsed that has syntax errors in it. Think of something like this, where the message property contains unescaped double quotes:

{

    "data": [{

        "code": "1",

        "message": "This message has "unescaped" quotes, which is a JSON syntax error."

    }]

}

If you have JSON in your app somewhere then it's good to run it through JSONLint to verify that it doesn't have a syntax error. Usually this isn't the case though in my experience, it's usually JSON returned from an API that's the culprit.

When an XHR request is made to an HTTP API that returns a response with a Content-Type:application/json; charset=UTF-8 header which contains invalid JSON in the response body you'll see this error.

If a server-side API controller is improperly handling a syntax error, and it's being printed out as part of the response, that will break the structure of JSON returned. A good example of this would be an API response containing a PHP Warning or Notice in the response body:

<b>Notice</b>:  Undefined variable: something in <b>/path/to/some-api-controller.php</b> on line <b>99</b><br />

{

    "success": false,

    "data": [{ ... }]

}

95% of the time this is the source of the issue for me, and though it's somewhat addressed here in the other responses I didn't feel it was clearly described. Hopefully this helps, if you're looking for a handy way to track down which API response contains a JSON syntax error I've written an Angular module for that.

Here's the module:

/**

 * Track Incomplete XHR Requests

 * 

 * Extend httpInterceptor to track XHR completions and keep a queue 

 * of our HTTP requests in order to find if any are incomplete or 

 * never finish, usually this is the source  of the issue if it's 

 * XHR related

 */

angular.module( "xhrErrorTracking", [

        'ng',

        'ngResource'

    ] )

    .factory( 'xhrErrorTracking', [ '$q', function( $q ) {

        var currentResponse = false;



        return {

            response: function( response ) {

                currentResponse = response;

                return response || $q.when( response );

            },

            responseError: function( rejection ) {

                var requestDesc = currentResponse.config.method + ' ' + currentResponse.config.url;

                if ( currentResponse.config.params ) requestDesc += ' ' + JSON.stringify( currentResponse.config.params );



                console.warn( 'JSON Errors Found in XHR Response: ' + requestDesc, currentResponse );



                return $q.reject( rejection );

            }

        };

    } ] )

    .config( [ '$httpProvider', function( $httpProvider ) {

        $httpProvider.interceptors.push( 'xhrErrorTracking' );

    } ] );

More details can be found in the blog article referenced above, I haven't posted everything found there here as it's probably not all relevant.

For me, this happened when one of the properties on the object I was returning as JSON threw an exception.

public Dictionary<string, int> Clients { get; set; }

public int CRCount

{

    get

    {

        var count = 0;

        //throws when Clients is null

        foreach (var c in Clients) {

            count += c.Value;

        }

        return count;

    }

}

Adding a null check, fixed it for me:

public Dictionary<string, int> Clients { get; set; }

public int CRCount

{

    get

    {

        var count = 0;

        if (Clients != null) {

            foreach (var c in Clients) {

                count += c.Value;

            }

        }

        return count;

    }

}

just something basic to check, make sure you dont have anything commented out in the json file

//comments here will not be parsed and throw error

Just to add to the answers, it also happens when your API response includes

<?php{username: 'Some'}

which could be a case when your backend is using PHP.

In python you can use json.Dump(str) before send result to html template.
with this command string convert to correct json format and send to html template. After send this result to JSON.parse(result) , this is correct response and you can use this.

For some, this may help you guys:
I had a similar experience with Wordpress REST API. I even used Postman to check if I had the correct routes or endpoint. I later found out that I accidentally put an "echo" inside my script - hooks:

Debug & check your console

Cause of the error

So basically, this means that I printed a value that isn't JSON that is mixed with the script that causes AJAX error - "SyntaxError: Unexpected token r in JSON at position 0"

This might cause due to your javascript code is looking at some json response and you received something else like text.

I was having same problem. I am using a simple node.js server to send response to a client made in Angular 7. Initially I was sending response.end('Hello world from nodejs server');
to client but somehow angular was unable to parse it.