raven.api.chat.get_channel_members built each Open-channel member's row by
indexing straight into the Raven User lookup result without checking it was
found, unlike the identical branch 10 lines below for non-Open channels. A
workspace member whose Raven User record is missing (e.g. left behind by a
direct cleanup that skipped RavenUser.on_trash's own cascade) crashes the
whole whitelisted endpoint with AttributeError instead of just being omitted.
Extracted the row-building into build_member_entry(), which returns None for
an unmatched member so both branches skip it the same way. Added
raven/tests/test_chat_channel_members.py (pure-function coverage plus an
IntegrationTestCase reproducing the stale-membership state) following this
repo's existing test conventions.
Verified: apps/web vitest (480/480) and tsc -b are unaffected and pass; the
new Python tests need a Frappe bench (DB-backed test runner) this sandbox
does not have, so they are written to the repo's established
IntegrationTestCase pattern but not executed here.
README: rewritten to the brand voice, with the new logo, Pilot as the
recommended install and a Frappe Cloud button. The old PNG logo is gone.
iPad: the primary rail now pads the status bar inset itself, since it
sits beside <main> and never got it. The bridge view controller overrides
supportedInterfaceOrientations because Capacitor builds its mask from the
iPhone list in Info.plist only, which pinned the iPad to portrait.
Android release: a signing config read from a gitignored
keystore.properties, and scripts/playstore.sh, which builds the signed
bundle the same way testflight.sh archives for iOS. Both are wired to
yarn native:playstore.
Build number 314 for both platforms.
Store screenshot tooling and the demo site seed are ignored; they are
local tooling, not part of the app.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The chosen site users were filtered afresh each render, so the preview
effect fired every time, set state in the page, and re-rendered the step
again. Memoized on the list and the selection.
Giving someone Raven access saves their User, which needs System
Manager. Setup admits Raven Admins too, and everyone starts ticked, so
their first Add raised for the whole batch, including people already in
Raven who only needed a membership. People still needing access are now
offered but not addable to a caller who can't write Users, and the row
says so.
Install no longer adds every system user it can and skips the rest.
Raven ships Raven User and Raven Admin role profiles, and the team step
opens a searchable picker, with Select all, over everyone on the site;
a single person gets a checkbox. One helper now gives Raven access
everywhere: a user whose roles come from a role profile gets Raven's
profile alongside, which the Framework keeps across saves; on Frappe 15,
where a user has one profile, they're shown but not addable. Someone
whose Raven access was taken away is offered again.
The setup funnel is reported as the Framework wizard reports its own:
each step completed or skipped with the time spent, going back, starting
and leaving. The web app posts them to one endpoint that passes known
events and properties to the Framework's capture.
A public photo on the User is used as it is on the Raven User; the old
copy fetched the file from the site itself, which fails on a dev server
and was swallowed. Setup also falls back to the User's photo.
The HR step's copy is rewritten.
Found while walking a new site through setup:
- The DM sidebar showed only "No conversations yet" when there were no
DMs. The start-a-conversation rows were the virtual list's footer, so
they never rendered for an empty list. They now show in that case too;
the empty state is kept for when there's no one to suggest.
- The command menu's "Users" heading rendered over nothing on a site with
no DMs, as cmdk only hides an empty group while searching.
- "Select a conversation" now sits in the page's island, where the chat
would be, instead of floating on the canvas.
- Icons on "Select a conversation" and "No messages yet".
- The channel sidebar's empty state is sized for the narrow column, held
near the top, and offers a Create a channel button.
After the last step the form gives way to a check that draws itself and
"All done", which fades out and is replaced by "Now, send a raven." in
Newsreader, the rest of the line following the "Now,". Both lines share
one slot so nothing shifts. The preview then grows into the app as
before. The finale timers now run through one helper.
get_single_value reads nothing for a single with no stored rows, and
Frappe stores defaults only after after_install, so the import skipped
everyone on a fresh site. Read the setting through the document, which
applies its default.
The app's slim boot carries setup_complete only under sysdefaults, so
the gate sent pending admins to the Desk wizard on sites already set up.
The slim boot also gains is_fc_site, which the gate and the password
step read.
The app serves every site from one origin, so the done flag, the saved
progress and the boot-cache update were shared across sites. All three
now use the site-scoped key. The workspace step also prefills the company
in the fetch's onSuccess instead of an effect.
A blank flag on a fresh install already means "not set up", so the
installer no longer stores settings just to raise one. Sites already
running Raven are marked completed by a patch instead.
Frappe Cloud opens a new site on /raven before the Framework wizard. The
gate now lets those sites into Raven's flow, the profile step asks the
first admin for a password since no wizard did, and finishing Raven's
setup completes the Framework wizard with the region Frappe Cloud stored.
Sites with ERPNext or HRMS still go through the real wizard first.
The v15 gate made older sites keep the default "Raven" workspace and skip
setup. Nothing in the flow needs Frappe 16, so every new site now starts
with setup pending and no default workspace.
The web app, the native bundle and the store versions move to 3.1.0.
A 3.1.0 site asks apps older than that to update, and the app refuses
sites below 3.1.0 in the picker: the native boot endpoint and the CORS
hook only ship from there, so an older site could not open anyway.
Every share wrote a new folder into the app group and nothing removed
it. The page now deletes each copy once its bytes are in memory, and the
extension clears the previous share before writing a new one, as the
Android shell already does. Only the latest share is ever readable, so
nothing reachable is lost.
The share extension loaded each file-backed item into Data before
writing it to the app group, which breached the extension's memory
limit on large videos and ended the share. The copy now streams through
the file manager; Data is kept only for items that exist nowhere on disk.
The share page stashed files globally as soon as it loaded, so backing
out left them for the next composer to attach in any conversation. The
page now keeps the files until a conversation is picked and stashes them
for that channel alone; a composer takes only files addressed to it.
The rotation listener was only installed when push was already on at
startup, so a session that enabled push for the first time kept a dead
token on the server until the next restart. One watcher now serves both
paths, and it only syncs while push is on for the site, so a rotation
after turning push off does not subscribe the device again.
hooks.py registered set_cors twice after the merge; develop already has
it. The X-Raven-App comment now says what the header is for: it marks a
request as the app's, and the origin allowlist is what actually limits
CORS.
* fix: do not allow sending messages to disabled users
* fix: message action toolbar position in left-right mode
* fix: show timestamp for continuation messages
* fix: do not enforce max length on password fields
* fix: Raven logo sizing and welcome text
* fix: limit raven document notifications to stop at cacading error logs
* fix: do not leave channel references in notifications when channel is deleted
* fix: handle raven user deletion by removing role
* fix: set dm_user_1 and 2 to None explicitly
* fix: in-desk integration
* fix: allow Cyrillic characters in channel name
* fix: cap width to container
* fix: enable user via roles