chandantul:

I am getting an error after few times running the code

"JSON error at line 1, byte 1/156: Unexpected character 'C' parsing in
+itial state: expecting whitespace: 'n', '\r', '\t', ' ' or start of s
+tring: '"' or digit: '0-9' or minus: '-' or start of an array or obje
+ct: '{', '[' or start of literal: 't', 'f', 'n' at All-users-Apps.pl 
+line 158."
[download]

Please let me know is this is a code issue or network issue.

With an error like this, it's not likely to be either a code or network issue. The error message is telling you that it's having trouble parsing the JSON data, so it's almost certainly a data issue. Since it tells you where in the data the error is, you should look at the JSON data to see what it looks like, and see if there's an obvious data problem.

Normally when I see a JSON error, it comes down to one of the following:

• There was an error on the server and instead of it sending JSON, it sent an error message and my code failed to check for errors before parsing the JSON.
• Someone created the JSON by just pasting strings together rather than a JSON library, and they created some bogus JSON with an error like:
  
  • A text string contained a newline, so the JSON record was unterminated.
  • A text string contained a quote breaking the JSON quoting rules.
  • The sender got some trace/debug messages mixed up in the JSON string.
  • . . . other cases I don't recall off hand . . .
• There's a mismatch in the encoding/decoding (for unicode, HTML entities, or other) that's butchered the JSON. This is one of the cases where it's more likely to be a code issue than a data issue, as the code steps on the data.
• Congratulations! you've found a bug in a JSON routine... Note: Very unlikely if you're using a decent JSON package, as it would be used by many thousands of people in many applications. I won't say impossible as I've found a couple compiler bugs in several decades of programming, but I'd take a hard look at the incoming JSON code, my own code that processed the data long before I'd start suspecting a bug in a well-used / well-tested JSON library. I've never actually encountered this situation, I just included it for completeness.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

2020-11-09 Athanasius fixed over-long line.

---

In reply to Re^3: Not an ARRAY reference by roboticus
in thread Not an ARRAY reference by chandantul

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.