mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-11-22 19:58:26 +00:00
dbd3fd7ca5efd27ea5bd1942f3613309a88e71ee
6
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
c2d66c9d1d |
core, ios: complete XFTP uploads after the app leaves the foreground (#7966)
* core: delete agent file after every terminal XFTP upload event * ios: spec for XFTP uploads during suspension * core: pin simplexmq to evgeny-simplex fork for CI * core: skip agent file deletion for XFTP errors without file ID * ios: spec for counted XFTP uploads during suspension * docs: plan for agent file deletion after XFTP uploads * docs: revise plan for agent file deletion after XFTP uploads * docs: revise plan wording for agent file deletion after XFTP uploads * ios: spec wording for XFTP uploads during suspension * core: pin simplexmq to the rewritten fork commit * core: pin simplexmq with ended uploads excluded from suspension wait * ios: suspend the app chat at once when the share sheet opens * docs: plan decisions for the app yielding to the share extension * core: verify agent file deletion for an item deleted during upload * ios: spec wording for awaited XFTP uploads during suspension * core: pin simplexmq with renamed upload wait functions and tests * docs: plan wording, spec text and deletion test for agent files * ios: suspend the app at once for the share sheet only while suspending * docs: plan the narrowed share extension yielding * docs: share extension wait, NSE and residual cases in plan and spec * docs: plan tests for the remaining agent file deletion paths * core: verify agent file deletion on the remaining upload paths * core: pin simplexmq to the fork commit with merged master * docs: plan line references after merging master and flow diagrams * core: agent file deletion finalizer written with flip, as in the codebase * ios: spec states the conditions of the share extension wait and the instant suspension * docs: plan names the merged master base and the spec conditions * core: pin simplexmq to the fork commit with the review fixes * docs: spec and plan state when the share extension wait ends, link the simplexmq pull request, list the device test after app suspension * core: pin simplexmq to the fork commit with the separate suspend timeout thread * docs: spec and plan state that the share extension wait ends at the first check with both states suspended * core: pin simplexmq master commit with the merged upload changes * core, ios: test instant suspension on the share extension signal * ios: deliver the share extension signal to the app in the setup wait test * ios: await the delivery result outside the assertion * ios: keep the app running until each file upload ends * tests: record each upload fixture in its own test * ios: restore the suspension of the app and the share extension of master * tests: add the upload fixture files to record into * tests: record upload responses and events for app tests * core: update query plans * tests: delete the uploaded item after its upload ends * core: no error for upload events of a deleted file |
||
|
|
14c0fa04a0 | tests: record name fixtures after the channel join settles (#8250) | ||
|
|
f406dd71a0 |
core, ui: validate short link type, show contact info for long addresses and rejected contacts (#8184)
* tests: short link type, QR code capacity and contact statuses * core: validate the type of short links * android, desktop: show contact info for addresses above QR code capacity * ui: show chats with rejected contact requests * tests: short link types with group, channel and contact data * core: validate short link type against link data * tests: fix short link data test * tests: group data in invitation link before its first use * tests: connect via address in contact profile with group link * core: connect via contact address only with address links * core: parse short link data once, by link type * core: types of short link data parser * core: test short link types and contact rejection, record app fixtures * android, desktop: test contact info, link alerts and rejected contacts * ios: test invalid link alerts and rejected contacts in the chat list * desktop: contact info tests find texts without app resources * ui: core responses of invalid link plans and a rejected contact request * desktop: contact info tests provide the app bar handler * core: normalise file and message keys in app test fixtures * core: normalise deletion times in app test fixtures * desktop: test that a QR code above capacity is not shared on tap * core: test relay link checks and known channel refresh from link data |
||
|
|
4eeddce11d |
core, ui: chatItemUpdated event has the previous item (#8219)
* core, ui: chatItemUpdated event has the previous item Apps change counters by the difference between the previous and the new item, and insert an updated item only when the update created it. * core, ui: a recreated item is sent as newChatItems An update of a locally deleted message creates it again and sends it as a new item, so chatItemUpdated always has the previous item and the apps never insert on an update. * core, ui: previous item is optional and has no chat info Events from older remote hosts decode without it; the apps then insert the item if it is not loaded and change no counters. * core: catch-up subscriber gets an edited history post as a new item * ui: updates in another profile do not notify, as on iOS * core, ui: one type for the updated item and its previous version AChatItemUpdate has the chat info, the new item and the previous item with the same chat type and direction. Its JSON is the JSON of AChatItem with an optional prevChatItem; the event keeps the key chatItem. * core: tested event key, previous item reactions, cleared mentions One function renames the event field to chatItem for JSON and docs, and the test checks the wire key and compatibility with AChatItem. The previous item of a direct edit has its reactions. An edit that removes all mentions sends the item without them. * core: test that an edit removing mentions sends the item without them * core: event JSON field mapping inline in the TH options, for the Windows build * core: file chat item update checked in one store transaction * core: test that a file reset by unknown relays sends its previous item * core, ui: chatItemUpdated event key chatItemUpdate * core, ui: chatItemUpdated always has the previous item * ci: mcp scope tests the plugin with its published dependencies * core: mention of the user follows edits of a group message * core: previous item of a prohibited file is read before the prohibition * android, desktop: missed call check inline, counter test with core pairs * ios: spec link of the chatItemUpdated event * core: mention edits in support chats update members requiring attention * core: one rule for the mention of the user in received and edited items * core: record item events of updates for app tests * android, desktop: remove the missed call notification of updates, never shown * android, desktop: test item updates on events recorded by the core * ios: test item updates on events recorded by the core * docs: plan of app tests of item updates, recording tests in the CI guide * core: record the response to an update after its item status is final * ios: notification manager replaceable in tests * ios: test notifications of updates and the update response * android, desktop: test the recorded update response * docs: plan with iOS notifications and the update response * core: recorded response to an update of a sent message |
||
|
|
dabee7dab8 |
ios: fix the crash when a new chat fails to open; ui: test lapsed and moved channel names (#8241)
* core, ui: plan name alert tests against core fixtures * core: write name lookup responses to app fixtures in name tests * android, desktop: name alerts tested against core fixtures * core, ios: plan Swift fixtures and iOS unit tests of name alerts * core: write name lookup responses in the Swift form to iOS fixtures * ios: name alerts tested against core fixtures * core: write both app fixtures of a name test in one run * ui: add name lookup responses written by the core tests as fixtures * core: keep the fixture writer of name tests to the forms it receives * desktop: run name alert tests in the US locale * ios: one switch for the title and effect of name alert actions * docs: name alert tests in the app specs, CI guide and plan * docs: known gaps of the name alert tests in the plan * ui: restore the name alert code and the iOS project of master * core: record name lookup responses and name parses for app tests * android, desktop: test name alerts of planAndConnect on recorded responses * ci: run the app tests for a change of the name fixtures * core: name lookup responses and name parses recorded by the core tests * docs: plan of app views tested on core responses * ios: test name alerts of planAndConnect on recorded responses * ci: iOS unit tests in the iOS job, the app launched on stub migrations * android, desktop: core hooks below the externals, in the specs * ios: name alert tests compile with the converter at file scope * ui: the moved name test expects the alert to open a chat with the new address * core, ui: app test fixtures under tests/fixtures/api * core: record the responses of the name lookup flows that the apps test * core: record URI parses, and normalize the random values of fixtures * android, desktop: URI parse hook and event processing for tests * ios: URI parse hook for tests * desktop: full failure messages of tests * core: domain errors view compiles with GHC 8.10.7 * core: normalize parses and profile send times in fixtures * core: record the parses of the chat list search * core: recorded responses of the name flows and the contact address * android, desktop: test name alerts, buttons, search and name view * ios: test name alerts, buttons, search and the moved event * docs: plan, specs and CI guide of the app tests * core: record lapsed names without grace, channels lapsed, moved, failed * android, desktop: test the prepare domain, cleanup, search row and reasons * ios: test the prepare domain, onOpen and the event's terminal text * core: the grace date of an expired name in tests is in seconds * core: recorded plans of lapsed, moved and unverified names; relays normalized * ios, android, desktop: test lapsed, moved and unverified channel names * docs: the follow-up tests and the gaps they leave * ios: wait for the alert of a failed prepare before the next test * ios: show the alert of a failed new chat on the main thread |
||
|
|
73761e6e0b |
core, ui: test app views on the core's recorded responses (#8234)
* core, ui: plan name alert tests against core fixtures * core: write name lookup responses to app fixtures in name tests * android, desktop: name alerts tested against core fixtures * core, ios: plan Swift fixtures and iOS unit tests of name alerts * core: write name lookup responses in the Swift form to iOS fixtures * ios: name alerts tested against core fixtures * core: write both app fixtures of a name test in one run * ui: add name lookup responses written by the core tests as fixtures * core: keep the fixture writer of name tests to the forms it receives * desktop: run name alert tests in the US locale * ios: one switch for the title and effect of name alert actions * docs: name alert tests in the app specs, CI guide and plan * docs: known gaps of the name alert tests in the plan * ui: restore the name alert code and the iOS project of master * core: record name lookup responses and name parses for app tests * android, desktop: test name alerts of planAndConnect on recorded responses * ci: run the app tests for a change of the name fixtures * core: name lookup responses and name parses recorded by the core tests * docs: plan of app views tested on core responses * ios: test name alerts of planAndConnect on recorded responses * ci: iOS unit tests in the iOS job, the app launched on stub migrations * android, desktop: core hooks below the externals, in the specs * ios: name alert tests compile with the converter at file scope * ui: the moved name test expects the alert to open a chat with the new address * core, ui: app test fixtures under tests/fixtures/api * core: record the responses of the name lookup flows that the apps test * core: record URI parses, and normalize the random values of fixtures * android, desktop: URI parse hook and event processing for tests * ios: URI parse hook for tests * desktop: full failure messages of tests * core: domain errors view compiles with GHC 8.10.7 * core: normalize parses and profile send times in fixtures * core: record the parses of the chat list search * core: recorded responses of the name flows and the contact address * android, desktop: test name alerts, buttons, search and name view * ios: test name alerts, buttons, search and the moved event * docs: plan, specs and CI guide of the app tests |