You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launching the app on both macOS and iOS, the subscription UI appears for a split second before Tact seems to recognize the account and proceed to the last open chat.
Environment
Tact version: Version 1.10.1 (541)
Hardware: M1 MacBook Pro, iPhone 13 mini
OS version: macOS Sonoma 14.7.2, iOS 18.2 (Build 22C152)
To reproduce
Steps to reproduce the behavior:
Close or force-quit the app if it's already running
Launch Tact
Don't blink 😉
Expected behavior
Tact should recognize immediately that I have an active subscription and take me right to the last chat.
Observed behavior
The subscription UI appears just long enough for me to wonder if Tact has somehow forgotten that I have a subscription.
Before I can read the words on the screen, Tact recovers and shows me my chats.
Sometimes this happens very fast, and other times the subscription UI seems to linger a bit longer.
I grabbed a stopwatch to time it today, but it was over before I could start/stop the timer, so less than a second.
The text was updated successfully, but these errors were encountered:
Describe the bug
When launching the app on both macOS and iOS, the subscription UI appears for a split second before Tact seems to recognize the account and proceed to the last open chat.
Environment
To reproduce
Steps to reproduce the behavior:
Expected behavior
Tact should recognize immediately that I have an active subscription and take me right to the last chat.
Observed behavior
The subscription UI appears just long enough for me to wonder if Tact has somehow forgotten that I have a subscription.
Before I can read the words on the screen, Tact recovers and shows me my chats.
Sometimes this happens very fast, and other times the subscription UI seems to linger a bit longer.
I grabbed a stopwatch to time it today, but it was over before I could start/stop the timer, so less than a second.
The text was updated successfully, but these errors were encountered: