Release 2.38.0#20630
Open
alaibe wants to merge 64 commits into
Open
Conversation
Member
Jenkins BuildsClick to see older builds (291)
|
- fix the overall layout, respecting the modal width - fix the pre-selected color (color vs color-string mismatch) - add the modal to Storybook Fixes #19325
- Deleted constants and UI elements related to Polygon zkEVM from wallet_constants.nim, Constants.qml, and Utils.qml. - Removed SVG icons for Polygon zkEVM from the assets directory. - Updated translation files to eliminate references to Polygon zkEVM Explorer in multiple languages.
… are missing For the tokens that are not in any of the list that the app operates with "Unknown token" should be used for the name, and raw value for crypto value instead of the token key.
- add the view to Storybook Fixes #20645
- lower the `portraitBreakpoint` to 640x480, and make the portrait/landscape criteria switch depend on `width` only - let the PrimaryNavSidebar follow the same logic - update TS files Fixes #20318
- when switching to portrait mode
- similar to setting it to `visible`
* fix(browser): fix crash fixes #20591 * chore: bump status-go
* feat(connector): ephemeral dapp records refs #20676 * fix: copilot comments * chore: bump status-go
It was causing that selecting mention from suggestions list was not possible on mobile. Closes: #20798
…g mentions It's necessary to handle suggestions correctly (filtering based on the user input). Closes: #20743
Swapped word is now staying in one row
Route iOS file selection through native platform pickers to avoid Qt file dialog sizing issues on mobile. - Use `UIDocumentPickerViewController` for document-based flows such as backups and JSON imports. - Add a photo-library mode to `StatusFileDialog` for image selection flows. - Use the native iOS photo picker for profile picture, community logo/banner, and image selector uploads. - Return selected files/photos through the existing `StatusFileDialog` selected file API. - Added support for multi file selection. Closes #20704
* recreate wc client after Resume() fixes #20767
- StatusTextField: theme/style according to Status design - SearchBox: derive from StatusTextField instead of the clunky StatusInput; we only need one-line input here anyway - fix usages of the SearchBox, notably fixup the need to use a native validator if needed; greatly simplifies the code to use this component - regenerate TS files Fixes #20754
Make the sync pairing page scrollable so the instructions button stays reachable when the QR scanner content overflows. Fixes #20638
Ensure the portrait `StatusSectionLayout` visually follows `SwipeView.currentIndex` changes on Android by repositioning the internal view after programmatic panel navigation. This prevents the layout from keeping the previous `contentX` while the logical index has already changed. Fix #20771
On Android 15, taking a screenshot and invoking sharing dialog was triggering full-screen mode, not restored when sharing is finished. Closes: #20612
* perf: Async start messenger The startMessenger backend call is a lengthy process, blocking the main thread for a few seconds. Moving it to async tasks gives the main thread the chance advance on the login work until the messenger starts successfully. Perf improvement on my heavy account: Before: 17 sec warm start-up After: 14 sec warm start-up - Added `onMessengerStarted` method to `AccessInterface` to handle messenger start errors. - Implemented `onMessengerStarted` method in `Module` to emit error notifications. - Introduced `SIGNAL_MESSENGER_STARTED` constant for signaling messenger start events. - Created `asyncStartMessengerTask` to manage asynchronous messenger start operations. - Updated `startMessenger` method in `Service` to utilize the new async task and handle responses. * fix: Trim StartMessenger async task output * fix: review coment - remove dead code * perf(qml): Drop the file selectors * fix(webviewLoader): log on error * perf: seed contacts with community members Iterates: #20228 Resolving community members creates a high frequency RPC flood at start-up when the app tries to eagerly resolve every community members. On Android Status community adds around 2 sec in CPU time on warm start-up. The solution implements an enriched community member type and contact type returned from status-go. The app will receive this extra data and seed the contacts cache (instead of creating the contacts cache using 4 separate RPCs for each member/contact). * perf: enhance contact seeding with MemberSeed structure and optimize duplicate handling * feat: Migrate android binder from files to shared memory This commit aligns the client-server communication with standard Android solutions - direct binder calls and shared memory. This is done both for perf reasons (has a big impact on high frequency callse) and security concerns (no unencrypted data is touching the disk). There are two main changes in this commit: 1. Direct communication between client and service when the payload is below 64KB. This is for high frequency and ligh calls (like colorId). The file based communication overhead is just too high for such usage. 2. Shared memory - When the payload is bigger than 64KB we'll use the shared memory * perf: Avoid unnecessary community and chat copies The nim profile trace is dominated with community and chat object copies. There are 3 main types of changes: - using `lent` to borrow a community from the service. It can be used as a return type only - using openarray in favor of seq for proc args, where `lent` cannot be used. - use "communityId" instead of full community where openarray or lent migration would cascade into lots of changes * perf: Optimize community role retrieval in getChatItemFromChatDto * perf: Move `getCachedCurrencyFormats` to threadpool * fix: Fixing merge errors * perf: Granular control qml compilation and loading of main layouts This commit aims to split the qml compilation into smaller chunks and schedule the compilation at the appropriate time. Approach: Each main section lives behind a loader component that has 2 purposes - load the component at appropriate times and defer the qml compilation until the loader is created. The same approach was applied to AppMain.qml and on top of this we'll need to make sure we're loading the AppMain at an appropriate time so that we'll avoid many intermediary states if the nim layer isn't ready for it. For this, I've introduced a new component - QmlCompiler. It has a list of main components and can precompile the qml component or make sure to load it all if needed (e.g while the onboarding runs we can use that time to preload everything) This approach is fully compatible with Loader.asynchronous usage and implementing loading states for the components - the community and chat loaders already implement it partially. Can be extended to preload all the sections in the background while the user is working on the current section. - Added MarketLoader.qml to handle market-related UI loading. - Introduced NodeLoader.qml for loading node-related UI components. - Created PopupsLoader.qml to manage various popups within the application. - Developed ProfileLoader.qml for loading user profile sections. - Implemented WalletLoader.qml to manage wallet-related UI components. - Added QmlCompiler.qml to centralize URL management for QML components. - Updated qmldir to include new loaders for better modularity. - Refactored main.qml to utilize the new AppMainLoader and improve loading logic. * fix: Correct spelling, function args and bindings * chore: bump vendors * fix: home selection doesn't open the proper 1x1 chat There are 2 bugs: property binding override from within the component internals and a signal signature mismatch
- Added a custom exit procedure (https://en.cppreference.com/c/program/_Exit) to bypass libc static destructors on mobile devices, preventing potential race conditions during shutdown - Ensured proper teardown of the threadpool in the StatusFoundation delete method Fixes #20855
* fix(collectibles): add ink, katana to unsupported list fixes #20717
* chore: add dapp fields html injection to storybook * fix(dapps): use the PlainText format for dApp controlled strings fixes #20879
Use the platform popup for the chat input context menu on iOS so paste and selection actions follow native text editing behavior. Avoid toggling readOnly during iOS paste handling, since that dismisses and restores the virtual keyboard. Keep Android using the existing null context menu path. Closes #20588
Use the native iOS context menu for StatusTextField and keep Android on the default behavior.
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
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.
DO NOT MERGE