Twitterrific Issues

By Andrew, 3 July, 2021

Forum
iOS and iPadOS

I was using the Twitterrific app yesterday when all of a sudden the app closed and when I went to reopen it it was completely inaccessible. I have closed the app in my app switcher and reopened it, and I have even deleted the app and re-downloaded it with no success. When I open the app voiceover’s focus shifts to the status bar and I can only hear the items in the status bar when flicking. When I try and move around within the app when it is open voiceover says nothing. I have even tried turning voiceover off and then back on with the app open and am still not getting any voiceover feedback. My sighted wife says she can see the timeline just fine and was even able to play something within my timeline feed with voiceover off. I have also installed the most recent app update from the App Store that I received today, which stated that it is supposed to fix crashing for some users. This update did not resolve any issues as I am still experiencing the same issues with voiceover. Is anyone else experiencing issues with Twitterrific at this time? I have never had an issue with Twitterrific and voiceover.

Options

Comments

By Nikola Jovic on Sunday, July 25, 2021 - 10:20

Hello,
you have probably turned on screen recognition.
When turned on inside already accessible apps, it can cause such problems.
Try opening Twiterrific and seeing if it appears in your rotor. If so, turn it off that way.
If not, open the app switcher and focus on Twiterrific. That way, it should appear when going through your rotor and you should be able to turn it off for Twiterrific.
If all of that fails, go to Voiceover settings / Voiceover recognition / screen recognition. There, press the apply to apps button, and unselect Twitterrific from the list that opens.

By Andrew on Sunday, July 25, 2021 - 10:20

After reading a previous post about screen recognition I went into the app switcher put focus on Twitterrific, used the rotor to navigate to screen recognition and swiped down to turn it off. Then I reopen the app and poof it was working properly again. I don’t know how I screwed this up in the first place but my issue has been resolved.