This morning I finally got an answer to this problem. Sadly it is like almost all answers I have received so far from PRT. They always blame somebody else!! Either it is my code, IG or whatever. 🙁
Here is the answer i received. Please also keep in mind that this is the first answer I received after about 2 months and after I reported the same error again and gain and asked for an answer. If I had gotten this answer after a few days, fine but if this is what comes after 2 months…
This situation has been caused by an error located on IG side. We have reported this situation and awaiting for their correction. We invite you to contact them if you continue to encounter such issues.
In the meantime, our developers are working to define a workaround in order to avoid this issue.