7

Question in point: Does placing a lid on a pot affect the rate of boiling?.

I should have sufficient reputation to be allowed to answer - and I can, on the normal site. However when I view this question through the iOS app, the "answer" button does not appear for me - on two separate devices.

On other (unprotected) questions there is no problem. I don't recall noticing this behavior before...

And submitting this with just "iOS-app" and "bug-reports" tag generated an error. When I tried adding the "bug" tag and resubmitted I was told I could not submit my change for another 23 seconds. What gives?

Improve this question
5
  • 1
    Yup, reproduced here on MSE as well so it's not site specific. As for the "could not submit my change for another 23 seconds" it's by design, an API rate limiting that is not related to the bug.
    – Shadow Wizard
    Commented Mar 9, 2015 at 12:02
  • Comment for the dev team: don't forget to ignore association bonus in case you will add a manual reputation check.
    – Shadow Wizard
    Commented Mar 9, 2015 at 12:04
  • @ShadowWizard thanks for the response, and for confirming I have not gone completely nuts. I don't understand why "you did not use the right tag; add this one" forces me to wait before submitting the correctly formed question. If that is the design, the design is screwy; but I suppose that makes the second half of the question a "feature request related comment"...
    – Floris
    Commented Mar 9, 2015 at 12:27
  • No problem, as for "why" it's because the app submits the contents to the server for validation, hence bound to rate limiting. There is existing bug report about it, I've bumped it now with a bounty.
    – Shadow Wizard
    Commented Mar 9, 2015 at 12:35
  • Related (Android, same issue): meta.stackexchange.com/questions/242281/…
    – Jason C
    Commented Mar 22, 2015 at 5:04

1 Answer 1

Reset to default
1

This will be fixed in 1.4.3.5.

The iOS app doesn't have direct information on user privileges so it was blindly checking for (!closed && !locked && !protected). I've added a field to the API that uses the same logic as the web for whether you can answer.

The app will be a little more optimistic than the web though, since can_answer == NO for sites you're not a member of and "Add an answer" is one of the mechanisms for joining a site. The new logic is: can_answer || (!closed && !locked && !protected)

Improve this answer
1
  • Thanks for the follow-up and explanation. Glad it will be fixed.
    – Floris
    Commented Jan 7, 2016 at 20:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .