Cannot load group description, there are also reports that links cannot be clicked in group descriptions.
I've included the groups description in this card as I suspect they're related; if it turns out not to be please split this into a new card.
Steps to reproduce
Visit the Help and Support group
Try to see description
If you can see it, try to click link in description
Platform information
reported v3.10.1 iOS IPhone XL
replicated S10, Android 9.0. v3.12.0
What is the current bug behavior?
Cannot load group description, there are also reports that links cannot be clicked in group descriptions.
What is the expected correct behavior?
Should load description, and links should be clickable, ideally warning users of navigation away from the app.
Relevant logs and/or screenshots
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Let's try changing mobile so it functions like web and calls api/v1/groups/group
Edited
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Hey @brianhatchet, @benhayward.ben! I checked this again. It appears to be the same old problem, endpoint not returning description for that group. I logged the call that get all the groups that user is subscribed to (api/v1/groups/member), this is (part of) what we get:
Also checked this same call on the web, and this endpoint is returning brief_description='' for H&S too.
The difference is that in the web, when user click on the group to navigate, api/v1/groups/group/ is called, this endpoint does return brief_description and in the app, when user tap on the group to navigate, api/v2/entities/ is called, this endpoint does NOT return brief_description.
We need to implement a separate loader for groups because api/v2/entities isn't fully hydrating the help and support group. So long we're calling the same endpoints as front, we should get back all
We should add a new Entity Resolver on api/v2/entities that maps urn:group:123123 to the right entity with all the needed values exported correctly without having a different URL for this kind of objects.
@msantang78@juanmsolaro have you added any error handling in that could have caused something that was previously silently erroring, to now display an error? If so #1921 (closed) may be a duplicate.
Should I label up and schedule both of the others?