Skip to content

Background service to check if node goes offline #994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 48 commits into from
Apr 30, 2025

Conversation

AlaaElattar
Copy link
Contributor

@AlaaElattar AlaaElattar commented Apr 9, 2025

Changes

  • Added flutter_local_notifications package for handling notifications.
  • Added background_fetch for background checking on nodes.
  • Categorized nodes into groups based on how long they've been offline:
    • Recent: 0–1 hour
    • Hour: 1–4 hours
    • Day: 4–24 hours
    • Days: 1–7 days
    • Beyond 7 days: Ignored
  • Handled tapping on notification to open dialog contains same data.

Related Issues

Tested Scenarios

  • Tested with offlline nodes.

@AlaaElattar AlaaElattar marked this pull request as draft April 9, 2025 11:54
@AlaaElattar AlaaElattar changed the title WIP: adding notifications pgk Background service to check if node goes offline Apr 13, 2025
@AlaaElattar AlaaElattar marked this pull request as ready for review April 13, 2025 09:45
Copy link
Contributor

@zaelgohary zaelgohary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you fix build workflow?

@AlaaElattar
Copy link
Contributor Author

AlaaElattar commented Apr 13, 2025

Can you fix build workflow?

The issue in the build apk not the format workflow.
I have nothing related to the apk.

@AlaaElattar AlaaElattar requested a review from zaelgohary April 13, 2025 10:06
@zaelgohary
Copy link
Contributor

zaelgohary commented Apr 13, 2025

Can you fix build workflow?

The issue in the build apk not the format workflow. I have nothing related to the apk.

The workflow fails on this branch only. It works fine on other branches. Maybe it's sth related to the new package?

@AlaaElattar AlaaElattar marked this pull request as draft April 13, 2025 11:48
@AlaaElattar AlaaElattar marked this pull request as draft April 24, 2025 07:46
@AlaaElattar AlaaElattar marked this pull request as ready for review April 24, 2025 11:19
@AlaaElattar AlaaElattar marked this pull request as draft April 28, 2025 12:46
zaelgohary and others added 8 commits April 28, 2025 15:53
* handle duplicated contacts

* undo latest solution

* fix adding duplicated wallet in fav list

* Fixed the duplicated contacts issue

* update condition when editing address
* Creating app lifecycle observer and use it in main.dart w navigator key, Replace Navigator routes w  navigator key

* Remove unused code

* Revert navigator key changes from screens

* Revert main screen changes
@AlaaElattar AlaaElattar marked this pull request as ready for review April 28, 2025 13:51
@AlaaElattar AlaaElattar marked this pull request as draft April 30, 2025 06:52
@AlaaElattar AlaaElattar marked this pull request as ready for review April 30, 2025 08:13
@AlaaElattar AlaaElattar merged commit 91299b1 into development Apr 30, 2025
2 checks passed
@AlaaElattar AlaaElattar deleted the development_check_nodes branch April 30, 2025 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants