I'm still having the same issue.
Anyone have an idea on the reason of that error?
Is there a better place to post this kind of issues?
Andrea, my apologies didn't see this thread. I'm following you now, if you can DM me your APP Id, I'll pass this through to the Apps team to see if we can track down the issue. Also, if you can try this one more time ... so we can get a recent occurrence of the issue that would help as well.
Update: If there are any logs on your end you can send us that would help as well...specifically any noticeable errors that are relevant to the issue.