Conversation
kradalby
force-pushed
the
kradalby/taildrop-first-transfer
branch
2 times, most recently
from
September 30, 2026 14:47
a0fa2fa to
14c34eb
Compare
First Taildrop on a fresh install blocks on the folder picker. MainActivity woke it before setUri, so the transfer could resume on filesDir: sender got "500 Invalid URI". Seen intermittently by headscale's Android suite (juanfont/headscale#3488). setUri now publishes, then wakes; ready gate reads savedUri, not prefs. Test checks the root at wake time, so wake-before-publish fails every run. Updates tailscale/corp#22362 Signed-off-by: Kristoffer Dalby <kristoffer@dalby.cc>
kradalby
force-pushed
the
kradalby/taildrop-first-transfer
branch
from
September 30, 2026 15:49
14c34eb to
0b33094
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First Taildrop on a fresh install blocks on the folder picker.
MainActivity woke it before setUri, so the transfer could resume on
filesDir: sender got "500 Invalid URI". Seen intermittently by
headscale's Android suite (juanfont/headscale#3488).
Might be more of a "flaky test" than a real scenario.
setUri now publishes, then wakes; ready gate reads savedUri, not prefs.
Test checks the root at wake time, so wake-before-publish fails every run.