Belated conclusion for this thread: I finally did host a space last night, and with no problems. I have also by now been a speaker in a space or two with no problems. I therefore suspect that the lockup I experienced, that made me start this thread, was caused either by a fluke or by an accidental dismissal of me from a space after I requested to speak. I have not tested being removed from a space yet to distinguish between the two.
On Mon, Aug 15, 2022 at 02:48:57PM -0500, joseph hudson wrote: Hi Doug, no I've never seen this but it's somewhat quite interesting. I would recommend having him trying to host another space, and see how well that goes again. After you've done all those resets. > On Aug 15, 2022, at 4:55 AM, Doug Lee <d...@dlee.org> wrote: > > I recently tried to join the speakers in a Twitter space from my iPhone X. > This is what happened, and I'm > wondering if anyone has seen or could explain this, so I can be more prepared > for my next attempt. In summary, > I wonder if I was removed (likely an accident) or if Twitter experienced a > technical glitch (I was told by the > host that it was some sort of technical error); and for both of those and any > other case, if the VO crash > could have been the result of a popup dialog that didn't speak, as can > briefly happen for emergency alerts in > my experience. I am using the native iOS Twitter app. > > The sequence of events: > > I joined the space and listened for a while. > > I double-tapped Request to Speak and got a popup dialog advising me that the > space might be recorded. This > dialog contained another Request to Speak button. > > I doubled tapped this new button. I believe things were normal for a few > seconds thereafter. > > Then the volume of the space suddenly decreased markedly, so I tried to turn > up my phone's volume. This made > me wonder if I was audible, though I was not expecting to be since the host > asked us to raise hands after > pressing Request to Speak, and I had yet to find a button for that. > > A few seconds later, all sound on my phone stopped, including the space and > VoiceOver speech. This lasted for > close to a minute if I recall correctly. > > During this outage, I made a few attempts to restart VO using the triple > press of the power button. This > finally succeeded. > > On getting VO back, I found myself no longer in the space. Attempts to > rejoin, before and after I restarted > the Twitter app, were met with a message saying "This space is not > available." This even persisted after the > host once DM'd me saying "Try again now." The host finally told me I might > not be able to join that session > again, which appeared to be true. The comment about it being a "technical > error" came to me much later. > > Again, my main questions are whether anyone has seen this sort of freeze and > whether it is likely the result > of a popup dialog that I could not read. > > Thanks much for any info. -- Doug Lee d...@dlee.org http://www.dlee.org No one alive is beyond hope; every second of life is a chance. (08/29/02) -- The following information is important for all members of the Mac Visionaries list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/macvisionaries@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/macvisionaries/20220906232314.qswakpgbzlspao5y%40mini.home.
