RE: Features within post dropdown are not working properly[eSteem v2 ios]
Hi @face2face, thanks for making this contribution.
Unfortunately, this report is a duplicate of an earlier submitted issue. The behaviors you described in this post were also listed. Here's the ticket - https://github.com/esteemapp/esteem-mobile/issues/560
Note that this application is cross platform, so the same native code runs on both the android Os and IOS. Thus, it is very understandable that they both will have the same bugs regardless of the platform.
I apologise for any inconvenience as a result. Do not be deterred by this review :) We look forward to your next report.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Chat with us on Discord.
@fego there is nothing to deterred but one thing i would like to say that esteem developer team has taken it separately, if both code were same then why they did not merge that in iOS first release, while issue was informed 11 days ago for android version?
The same commit was used for the two issues, the reason they were referenced under the same post.
The issue opened 11 days ago was only fixed a day ago in this pull request -https://github.com/esteemapp/esteem-mobile/pull/607, there was no separate merge for each of the opened issues, just one single merge . There have been similar fixes to other pressing issues and these changes would only reflect in the next release. Or you can personally build them from the repo to check.
PS:
If the codes were different, they would be in separate repos. And each repo will accept just issues affecting the platform in question.
The same commit was used for the two issues, the reason they were referenced under the same post.
The issue opened 11 days ago was only fixed a day ago in this pull request -https://github.com/esteemapp/esteem-mobile/pull/607, there was no separate merge for each of the opened issues, just one single merge . There have been similar fixes to other pressing issues and these changes would only reflect in the next release. Or you can personally build them from the repo to check.
PS:
If the codes were different, they would be in separate repos. And each repo will accept just issues affecting the platform in question.
Yes they have combined both issues in one (they have mentioned my issue number too) but you have considered it as one which was 11 days ago a history.
Thank you for your review, @fego! Keep up the good work!