Volodymyr

just added logs for both issues in [comment](https://github.com/status-im/status-mobile/pull/21445#issuecomment-2419533023) above

[issue 1](https://github.com/status-im/status-mobile/pull/21445#issuecomment-2416569837) is fixed after [latest commit](https://github.com/status-im/status-mobile/pull/21445/commits/e03757b4d4bf68ed67a4a4e4fb3455686366baab). @dlipicar thank you!

@xAlisher, could you take a look at [this](https://github.com/status-im/status-mobile/issues/21253#issuecomment-2358836752) question? Perhaps some additional validation should be added in the Figma. Currently, we only have a Figma design for: 'Not enough native...

@clauxx Could you please provide a more detailed explanation of the validations and correct me if I'm misunderstanding anything: 1. 'Native token not found' – Does this occur if the...

> @VolodLytvynenko @xAlisher @clauxx I think it is not wrong that we show this error, the wording is not best, but it is a way clearer than "Something went wrong"...

still valid. Not related to new rpc from https://github.com/status-im/status-mobile/pull/21378

@shivekkhurana I suggest moving this issue to later milestones. We still need the toasts for debugging the router problem if something goes wrong. They aren't user-friendly, but it's better to...

This issue is resolved in the new simplification flow https://github.com/status-im/status-mobile/pull/21595

> Thank you [@VolodLytvynenko](https://github.com/VolodLytvynenko) for creating this issue. It looks like we also need to update [design files](https://www.figma.com/design/JlpPhJp0SMnEyBQy4nOZHo/Settings----Mobile?node-id=6639-417116&m=dev) - (settings variant still have this checkbox) @Parveshdhull just left message to...

> Hello [@VolodLytvynenko](https://github.com/VolodLytvynenko) It sounds like a tricky situation with that error occurring in the mobile PR build [#21453](https://github.com/status-im/status-mobile/pull/21453). Since it's rare for you to reproduce it on Desktop, it...