Before submitting
Area
apps/mobile
Steps to reproduce
- Open the T3 Code app on an iPhone or iPad.
- Open a conversation or session with a long history or a large amount of generated output.
- Scroll upward so that the latest message is no longer visible.
- Try to return to the end of the conversation.
Expected behavior
A floating “Scroll to End” button should appear whenever the user is not near the bottom of the conversation. Tapping it should immediately jump to the latest message or generated output.
The behavior should be consistent with the macOS app, and the button should disappear once the user reaches the end.
Actual behavior
There is no “Scroll to End” or “Jump to Bottom” button in the iPhone and iPad apps. Users must manually scroll through long conversations or generated output to reach the latest content.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
iPhone 17 Pro running iOS 26.5 and iPad Pro 13-inch running iPadOS 26.5 in landscape orientation, using T3 Code app version 1.0.1 from the App Store. The issue reproduces consistently on both devices.
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Before submitting
Area
apps/mobile
Steps to reproduce
Expected behavior
A floating “Scroll to End” button should appear whenever the user is not near the bottom of the conversation. Tapping it should immediately jump to the latest message or generated output.
The behavior should be consistent with the macOS app, and the button should disappear once the user reaches the end.
Actual behavior
There is no “Scroll to End” or “Jump to Bottom” button in the iPhone and iPad apps. Users must manually scroll through long conversations or generated output to reach the latest content.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
iPhone 17 Pro running iOS 26.5 and iPad Pro 13-inch running iPadOS 26.5 in landscape orientation, using T3 Code app version 1.0.1 from the App Store. The issue reproduces consistently on both devices.
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response