Today, we found a critical bug about posts query result.
But yesterday it work properly.
Production and Development ACS has same problem.
ACS id : 9296c7e5-fe54-4502-a600-0757a581a7bf
Reproduce step
1. request query for posts (via 'ti.cloud' module or rest api)
Expected result (work properly until yesterday)
Every post object has user object.
Actual result (This occur from today morning)
Some posts has user object, some post has only user_id as string instead of user object.
Please check attached json file which is actual result of my 'Bogoyo' ACS account(id:9296c7e5-fe54-4502-a600-0757a581a7bf)
In addition to that, acs management page (
http://cloud.appcelerator.com/9296c7e5-fe54-4502-a600-0757a581a7bf/posts) show edit button of some posts. (screenshoot attached)
Our beta tester can't get any result on bogoyo app with this issue! Please check this ASAP. :(
Whqts your app key
what's the json_depth_level you are using? the user_id is for photo object which is one level deeper. I see all the post objects with user object
Actually I am able to reproduce the issue
[~yomybaby] We have identified and resolved the problem. Can you please give it a try and let us know if it works and if you see any other issue?
yes, i can reproduce the following issue and is investigating: " post_id in Production. 531f6741da5ba0076e0050df 531417b6da5ba00766004025 5310300eda5ba0076600379d When you query without where, you can't get these posts event per_page 100000. But with query with where or show method, you can get these!! "
[~ngupta] [~xzhang] I found a ANOTHER CRITICAL BUG. :( Please check this : TC-3890
[~yomybaby],i am investigating this issue.
[~yomybaby], i have added my comments for TC-3890, it is not ACS issue, it is due to the photo was not processed, after the photo was processed , we can see the urls.
[~yomybaby] For the missing 3 posts, you have two custom fields which are longer than 1024k so it is not indexed properly. This is a mongodb limitation. and we are working with thme to come up a workaround
[~yomybaby] Thank you for reporting these issues. Much appreciated. We have deployed fixes for these issues in the production environment so please verify all of your reported issues and let us know if you any issue persists or if you see a new issue.