-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]Searching for text results in "Catastropic Failure" message #577
Comments
Same here |
Update: Now clicking on anything in the Trending lists results in same "Catastrophic Failure" message. |
same here! It happens when you click on a result in the trends or when searching for tweets. searching for persons works fine. The issue affects both the stable version and the beta version. A few days ago everything worked fine the exact error message is: "Catastrophic failure running latest graohene OS in pixel 6 |
Same here too |
This should be fixed now. Sorry for the delay - I haven't been able to spend as much time as I'd like on Fritter recently 🙁 |
Thanks buddy. We really appreciate your work on this app even if it takes some time to update. ❤️ |
I'm still getting the same errors. ? Any advice, when you get a chance. Thanks! |
The patch works for me on the new CI build. |
Not sure if something else need to happen for fdroid to pickup fix or if its something in my settings. Not seeing new builds after beta5 |
Describe the bug
A clear description of what the bug is.
When I try to do a search (by clicking on the Search icon and typing in text) I get the message Catastrophic Failure/Missing or invalid url parameter. This only happens if I click on the Replies icon; searches still work if I click on the Accounts icon.
*Edited to add: I uninstalled the 2.16.3 version and installed v3.0.0-beta5+20221126 version and the problem persists.
To Reproduce
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots to help explain your problem.
Device
Samsung Galaxy Note 9
OS version 10
En_US
English
2.16.3. AND v3.0.0-beta5+20221126
The text was updated successfully, but these errors were encountered: