vinicioanthone
commented
5 years ago Dear LINE Platform user,
Thank you for taking the time to report this issue. Unfortunately, we're unable to follow up on it right now. The reason is that we've created too many feedback channels to track and solve issues as effectively as we want. That's why we've decided to do the following:
- On February 15, 2019, we'll be archiving this repository, including all issues.
- We'll close all open issues, regardless of whether they've been solved.
We'll keep the repository public so you can still read it. However, you won't be able to report new issues or edit existing ones here on GitHub. Instead, you can report LINE Platform issues on our LINE Developers forum. Please feel free to report your existing issue again if it hasn't been solved. We'll do our best to respond promptly.
We apologize for responding to your issue in such a disappointing way. User feedback is truly important to us — which is why we want to make sure we can follow up on it effectively. Reducing the number of feedback channels is part of that. We hope you understand and look forward to seeing you on the forum.
Sincerely,
The LINE Platform team
Dear Line Team, According to API reference, I attempt to access content field in JSON format on receive message after upgrade to API version 2, but now I cannot access after content field . This is hierarchy of access JSON format . Am I right ?
result->content->events-> array of events
Thank you