New transaction from notifications bug

[HoreaM]

New transaction from notifications bug

[dreautall]

fixed with 6bb14c3

[dreautall]

Thank you for the report. The stuck screen issue I fixed with bb3eca5 (not yet in the released version) and tested it during my vacation.

But a new issue popped up when you get multiple notifications and the app doesn't close in between, it will not properly handle the new notifications. So I need to have another look at it!

[dreautall]

So I'll try a new way with the new version (v0.1.9, should be released this week or weekend).

Unfortunately it is not really a "nice" way either - upon saving the transaction (launched from a notification), the app will close as it does now, but will in the background navigate to the default startup page. This might cause unnecessary network traffic, but it's really the only way I found so far.

Ideally, whatever happens when you push on a notification (no matter if it's the first or if the app is already running) should happen in a separate process which just gets nicely terminated afterwards. But I'm not sure if flutter is capable of doing this, unfortunately :(

Please test once the new version is out, and report if the user experience is improved.

[HoreaM]

It sounds like a good compromise honestly. I will for sure test it once it's out and let you know, thank you!

[HoreaM]

So I'll try a new way with the new version (v0.1.9, should be released this week or weekend).

Unfortunately it is not really a "nice" way either - upon saving the transaction (launched from a notification), the app will close as it does now, but will in the background navigate to the default startup page. This might cause unnecessary network traffic, but it's really the only way I found so far.

Ideally, whatever happens when you push on a notification (no matter if it's the first or if the app is already running) should happen in a separate process which just gets nicely terminated afterwards. But I'm not sure if flutter is capable of doing this, unfortunately :(

Please test once the new version is out, and report if the user experience is improved.

I did test it and it currently works like you described. I find it overall a better user experience.
The thing I noticed though is, if I receive multiple notifications for apps (let's say Revolut in this case) that are monitored by Waterfly, the app doesn't generate a new notification for every Revolut notification separately. It always takes the newest Revolut notification and overwrites the Waterfly notification with the data from it.
Is this intended?
If I remember correctly, the previous version generated a new Waterfly notification for every monitored apps received notification.
Thanks again for your work, it's greatly appreciated!

[dreautall]

The thing I noticed though is, if I receive multiple notifications for apps (let's say Revolut in this case) that are monitored by Waterfly, the app doesn't generate a new notification for every Revolut notification separately. It always takes the newest Revolut notification and overwrites the Waterfly notification with the data from it.

I need to check how the notifications are re-posted instead of being replaced to make that one work, thank you for the report. I didn't touch any of the notification-generating code, so I guess that was always the same.