metabolist / metatext

A free, open-source iOS Mastodon client.
https://metabolist.org/metatext
GNU General Public License v3.0
726 stars 101 forks source link

Searching for a User Throws Modal SSL Error While Trying to Type #147

Open pkscout opened 2 years ago

pkscout commented 2 years ago

Describe the bug If I try and type a username into the search bar, as soon as I put in any characters after the second @ symbol, MetaText starts trying to resolve it and generates errors in modal dialogs that disrupt my typing. Most often it says "Remote SSL Certificate couldn't be verified."

To Reproduce Steps to reproduce the behavior:

  1. Go to Explore
  2. start typing a user account (i.e. @somthing@ma)
  3. See error

Expected behavior MetaText shouldn't throw up a modal dialog box while I'm trying to type the information that would allow it to actually have the information it needs to complete the search.

Screenshots IMG_0492

(please complete the following information):

Additional context Add any other context about the problem here.

codebykat commented 2 years ago

Came here to report this. Mine says "Remote data could not be fetched" and it allows me to type a full word after the @ symbol (e.g. the "mastodon" part of "mastodon.social"). The error happens consistently when I go to type a period (hitting the punctuation button on keyboard), as well as occasionally when the text field loses keyboard focus for some other reason.

pkscout commented 2 years ago

Yea, I got some of those too. Of course when I went to put the issue in I couldn't get it to give me that error again. Glad I'm not going crazy anyway.

eggdropsoap commented 2 years ago

Came here to report this issue too.

Expected behaviour:

  1. No ‘hard’ UI feedback is necessary or wanted when the only failure is that there are no results (“Remote data could not be fetched”), and should not result in a modal. The empty results are the only feedback necessary, and would improve usability by not interrupting input (such as correcting typing mistakes).
  2. Other search failures (SSL cert failure, etc) should still result in a modal, but time between identical modal errors should be much more, and the modal should be suppressed if it is sooner. (There are probably UX best practices on how much time between identical error message modals is ideal.)