Long articles often failed to start: the stream had to produce decodable
audio within a fixed 10 s, while tts.folo.is takes several seconds to send
the first bytes of a long text. The timeout didn't stop the WebView, which
kept downloading and later played audio the app no longer tracked, and
playEntryTts fell back to downloading the whole file, which could start
playing over a newer stream minutes later.
- The start timeout is a 15 s stall timer that WebView progress events
(response headers, then chunks) restart, and it stops the WebView.
- Bridge events carry the request id, so events of a replaced or stopped
request are ignored, and a play command always starts over instead of
toggling the entry that is playing.
- Each WebView playback is isolated, so work left over from a replaced one
can't stop or report on the one that replaced it.
- A superseded or stopped request never falls back and its fallback
download is aborted. The player's stop button cancels a loading request.
- Segments start after the audio already queued (desktop got this in
4ab06f42b), a paused stream stays paused while more audio decodes, and
the last decode of a stream is no longer dropped.
- TTS and native playback no longer overlap: a starting stream pauses the
native player, and native playback (a podcast, the lock screen) stops
TTS unless that TTS request is the newer one.
- A stream whose download stalls after it started reports an error once
its queued audio ran out, and a WebView whose content process the system
killed is recreated instead of swallowing every later request.
- Cached TTS files are pruned once the player is set up and before each
fallback download, keeping the file the player still holds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
trackFetch removed its abort listener as soon as the headers arrived, so
aborting the caller's signal could no longer cancel a body that was still
downloading. Every fetch in the app goes through it (the global fetch, the
API client and the TTS service), so all of them ignored aborts after the
headers, unlike a plain expo fetch. The listener now stays until the
response is finalized.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On iPad, Android and iOS before 26 the player bar lives in the JS tab bar,
which screens pushed onto the root stack cover. Starting TTS from an
article or a folder timeline gave no feedback and no way to pause or stop
it until returning to a tab root.
Render a floating player bar through the root portal while a pushed screen
is on top. It hides behind modals and the lightbox, which the root portal
host is drawn above on Android, and the article and feed screens keep
their content clear of it. iPhone on iOS 26+ keeps the native tab bar and
its glass player bar unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The shared Autocomplete always set aria-label "Select Category", which
was wrong for the feed search in the list settings. Callers now pass a
label that matches their purpose. The list search reuses
lists.select_feeds, whose zh-CN copy drops a stray period and zh-TW
copy uses the Taiwan word for "current".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The OPML import form rendered no FormMessage, so a file over 500KB or
with another extension failed silently on Import.
- UnifiedDiscoverForm checked RSSHub routes inside the search mutation
and never rendered the error. The check now lives in the form schema,
so the message shows under the input and Preview stays disabled. RSS
and RSSHub previews open from onSubmit, which drops an RSS check that
could never fail and the "No feeds found" line shown after a preview.
- Failed searches on the discover page and in the sidebar discover
dialog now show a toast.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nothing imports CustomIntegrationValidator, DiscoverForm (replaced by
UnifiedDiscoverForm), TimelinePromptSection (taken off the AI settings
page in 691307925) or AiOnboardingModal. URLSchemeHandler.getExamples,
the CustomIntegrationManager validate helpers, formatFileSize and
withDisplayStateHandler have no callers. Remove them along with the
locale keys only they used.
The aiTimelinePrompt setting stays because the server still reads it
when it scores the AI timeline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the hard-coded English left in the desktop renderer, the Electron
main process, the mobile app and the shared packages to i18next, with
en, zh-CN, zh-TW, ja and fr-FR translations. SSR share pages are
unchanged.
- Fill every namespace in every language, delete keys no code reads
(server error codes stay) and update translations left behind by
later English changes.
- Stop HTML-escaping interpolated values in the desktop renderer.
React already escapes text, so names with & or quotes showed entities.
- Render error boundary fallbacks as components so they can use hooks.
- Localize zod validation messages with the app language.
- Throw ClipboardError from the clipboard helpers and show translated
toasts. formatEstimatedMins takes a formatter so callers localize the
units.
- Use one glossary term per concept in ja, fr-FR and zh-TW.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Electron never loads locales at runtime: every language is bundled in
default-resource.electron.ts. The ai namespace of zh-CN and zh-TW still
pointed at the English placeholder added before those translations
existed, so the AI settings and chat panel stayed in English.
- Import the real ai locale files, and test the Electron map against
locales/ for every supported language and namespace.
- Skip the localStorage locale cache in Electron and start i18next in the
user's language. Only builds from before June 2025 wrote that cache and
nothing refreshes it, so it could only shadow the bundled resources.
- Translate the zh-TW plan settings titles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Until 1.6.0 the settings sync sent every appearance, general and AI setting
except the device-local keys each domain lists: interface language, voice,
launch at startup, anonymous data, fonts and the like. 93e4a3b48 read those
lists as the keys to send and swapped omit for pick, on desktop and mobile,
so since then only the device-local keys synced across devices and nothing
else did, the action language and the AI settings included. Its e2e test
checked that the interface language syncs.
The lists name the device-local keys again and are renamed to say so. The
appearance domain also leaves the spotlight keys in its tab to the spotlight
domain, which still syncs only those. actionLanguage and personalizePrompt,
which b0f555266 added to the lists, are out of them again, so they sync.
The server kept what the clients sent before 1.6.0, so once per account
each device first queues the settings it changed from their defaults, before
it takes any from the server. While a local change to a tab waits,
applyRemoteSettings now leaves that tab alone, as the change log already
did; settings still at their defaults take the account's values afterwards.
The e2e test now syncs the action language.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The server adds the general actionLanguage and the AI personalizePrompt
settings to the AI chat system prompt, but neither was in the server sync
whitelist, so both stayed on the device and AI chat ignored them: a French
action language still got English answers. Desktop now syncs both, and
mobile syncs actionLanguage, the only one of the two it has.
A value set before this change reaches the server the next time it is
changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Entry titles and settings labels went through title-case unconditionally,
but it applies English capitalization rules, so with a French UI and French
feeds titles rendered as "Pourquoi Votre Café Est Une Arme De Défense" and
settings labels as "Afficher Le Nombre De Non Lus". CJK titles were also
touched ("iOS 27 beta" became "IOS 27 Beta").
titleCaseIfEnglish in @follow/utils only applies title case when the
language is English (en, en-US, en_GB, or franc's eng). On desktop, entry
titles use the entry language and translated titles the translation
language, falling back to the UI language when unknown; settings labels
and section titles use the UI language. Mobile grouped list cells use the
UI language too. AI chat tool names keep title case since they are English
identifiers.
Mobile no longer imports title-case directly, so the dependency moves to
@follow/utils.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The line was added by hand without the markers that the
@react-native-firebase/app config plugin writes, so every
`expo prebuild --no-clean` inserted a second, tagged copy of it. Wrap it
in the plugin's generated markers so prebuild leaves the committed
Podfile unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The follow-rnfb-ios-compat block was inserted a fixed 7 lines after
`post_install do |installer|`. In the Expo SDK 57 template that hook is
only the react_native_post_install call and its `end`, so a regenerated
Podfile got the block after the `end`, referenced `installer` outside
the hook and failed `pod install`.
Anchor on the `end` that closes post_install instead, so the block is
always the last thing in the hook and runs after
react_native_post_install. mergeContents now accepts an anchor function
for this. Podfiles that already contain the tagged block are still
updated in place.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
All tab screens stay mounted in release builds, and each
SafeNavigationScrollView wrote the shared tab bar background opacity on
layout, content size changes and scroll. A hidden tab whose content fits the
screen, such as Settings, reported that it was scrolled to the end and made
the React Native tab bar transparent over the visible tab, so its icons were
drawn straight over the content. This affects the tab bar used on iPad and on
systems before iOS 26.
Only the focused tab screen now updates the background. useTabScreenIsFocused
returns false outside a tab screen instead of throwing, which replaces
useInTabScreen.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When the app is linked against the iOS 27 SDK, UITabBarController hosts its
tab bar in a new container where setting isTabBarHidden to false no longer
clears tabBar.isHidden. CustomTabbarController hid the bar unconditionally
and only unhid it through isTabBarHidden, so the Liquid Glass tab bar never
appeared on iOS 27. Builds linked against the iOS 26 SDK still use the old
container and were not affected.
Only hide the native bar where React Native renders its own tab bar
(iPad and systems before iOS 26).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Apps linked against the iOS 27 SDK (Xcode 27) stop at launch on iOS 27 in
_UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption unless they use
the scene-based life cycle. Enable expo-build-properties'
ios.enableSceneSupport (Expo 57.0.23+) and apply the same changes to the
committed native project, so a prebuild reproduces it:
- AppDelegate conforms to ExpoReactNativeFactoryProvider and no longer
creates the window or starts React Native.
- Info.plist declares a scene manifest that points at Expo's
EXExpoAppSceneDelegate, which creates the window and starts React Native.
Builds made with Xcode 26 keep working with the scene life cycle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When the OAuth callback failed, the auth session followed Better Auth's
default error page, which production redirects to the folo.is homepage,
so the login sheet never reached folo:// and the app kept waiting with
no session. On real iPhones this happened to every Google sign-in that
had to go through the Google login form.
Run the Expo authorization proxy session from the app with
errorCallbackURL set to the app scheme: a rejected callback now closes
the sheet and shows a toast, and a denied consent screen counts as a
cancellation. The flow is otherwise the Expo plugin's: same proxy URL
and cookie storage.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every cron sync since 2026-09-23 exceeded the Worker memory limit. The
GitHub release list changes whenever download counts do, so each run
downloaded and fully decompressed every OTA archive on the first page
(a 58 MB desktop archive plus five mobile ones) into memory again.
- Skip releases whose stored record already matches, and only rewrite
the record when just the metadata changed; latest pointers are still
reconciled.
- Stream the archive through the zstd decompressor and tar extractor
with backpressure and upload each verified file as it is extracted,
so memory stays bounded by the largest referenced file. The download
is cancelled as soon as extraction fails.
- Sync each release independently so one broken release no longer
blocks the others; failures still fail the run and keep the stored
ETag so the next run retries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Markdown export imports mdast-util-gfm-strikethrough directly; declare it instead of relying on the hoisted copy from remark-gfm.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
push-receiver 4.3.1 parsed MCS messages recursively and could crash the main process with "Maximum call stack size exceeded" (#4457); 4.4.0 parses them in a loop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A `/reads` recount taken while new-entry hints were still hidden behind a
stale KV head already counted those entries; when the hints arrived with
the next pull their increments were added on top, and the reads that
followed left the hint values behind as phantom unread counts.
The engine now keeps the sync id an unread snapshot reflects
(`unreadSnapshotSyncId`, from the `/reads` answer or `/sync/state` read
just before) and applies the counter part of `N`, `U` and `inbox_entry`
`D` actions only above it. A refresh the user asks for recounts through
the engine, and the list-versus-counter check also fires when a fully
loaded unread-only list shows fewer unread entries than the counter.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A local simulator build raised CFBundleVersion in Info.plist and the change
slipped into the previous commit; the bump had set it to 13.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signing out (and the other runtime reloads) crashed the app with SIGSEGV on
the expo.modules.fetch.RequestQueue thread. Expo's native fetch keeps a
closure that owns the JS promise until the response reaches a terminal state;
reloading while a request was pending destroyed that closure against the
torn-down runtime. Sign-out always had requests pending: clearing the cookie
refetches the session queries and popping to the root loads the guest timeline.
Expo also installs its fetch as the global `fetch`, so every request in the app
goes through it. `network-activity.ts` wraps the global fetch (from the
polyfill entry) and the explicit `expo/fetch` imports, tracks each request
until the native response reports `readyForJSFinalization`, and can abort them
all. `reloadApp` cancels the queries, aborts the in-flight requests, waits for
the network to go idle (three seconds at most) and only then reloads. Every
`reloadAppAsync` call site goes through it.
Verified with the Maestro iOS auth journey against production: register, sign
out and log in pass with no crash report.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
(cherry picked from commit a662c0872710ff128880b97f0795dbeaf43310b1)
Signing out (and the other runtime reloads) crashed the app with SIGSEGV on
the expo.modules.fetch.RequestQueue thread. Expo's native fetch keeps a
closure that owns the JS promise until the response reaches a terminal state;
reloading while a request was pending destroyed that closure against the
torn-down runtime. Sign-out always had requests pending: clearing the cookie
refetches the session queries and popping to the root loads the guest timeline.
Expo also installs its fetch as the global `fetch`, so every request in the app
goes through it. `network-activity.ts` wraps the global fetch (from the
polyfill entry) and the explicit `expo/fetch` imports, tracks each request
until the native response reports `readyForJSFinalization`, and can abort them
all. `reloadApp` cancels the queries, aborts the in-flight requests, waits for
the network to go idle (three seconds at most) and only then reloads. Every
`reloadAppAsync` call site goes through it.
Verified with the Maestro iOS auth journey against production: register, sign
out and log in pass with no crash report.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The settings list grew, so the last row now stops underneath the floating tab
bar when Maestro scrolls until it is visible, and the tap landed on the tab bar
instead of the sign-out row.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Xcode 27 refuses the iOS 9.0 and 12.0 deployment targets that older pods still
declare on their resource bundle targets, and its Swift compiler rejects
react-native-ios-context-menu, which uses UIAction.subtitle behind an iOS 15
availability check. The app requires iOS 16.4, so the Podfile now raises every
pod target to at least ios.deploymentTarget in post_install; the config plugin
generates the block and the checked-in Podfile carries it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
After the API bridge moved to `net.fetch`, several main-process requests still used
Node's `fetch`, which ignores the app's proxy settings: the update manifest and policy,
the main-process API client, file downloads, text-to-speech, page fetching for the
reader, and the Eagle, qBittorrent and custom integration requests. They now go through
`net.fetch` as well. The readability package takes a `fetch` implementation for that;
downloads hand it to ky. Requests that manage cookies by hand pass
`credentials: "omit"`, so Chromium does not keep them too.
A failed CLI login sync used to be logged with the whole command line, token included.
The command is now described with the token redacted, and the command's output is
scrubbed the same way.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The main process sent the renderer's API requests with Node's `fetch`, which knows
nothing about the app's proxy settings: with only a system proxy configured, every API
request went out directly while images and pages went through the proxy. On networks
that need the proxy the API was unreachable.
`net.fetch` uses Chromium's network stack and therefore the session's proxy: the system
proxy, PAC files and SOCKS alike. Cookies stay attached by hand from the managed auth
cookies, so Chromium's own cookie handling is switched off for these requests. Verified
in a real main process: the proxy is resolved and used, a manual `Cookie` header is sent,
`Set-Cookie` is exposed through `getSetCookie()`, and `credentials: "omit"` leaves the
cookie store untouched.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
DIYgod