My apologies, I believe I've posted my previous post on a wrong board.
First of all, great piece of software! For me it does its job 99% of the time.
The exception is when I push two or more notes, one immediately after another (via Tasker app). Pushbullet receives both of them (with a title and body), but Push2Run can only see one correctly, while the other one is captured as empty:
2019-02-03 12:13:04.523 - Incoming push ...
2019-02-03 12:13:04.524 - <Title> Push2Run XXXXXXX-XXXXXXX
2019-02-03 12:13:04.524 - <Body> outlook on
2019-02-03 12:13:05.097 - action completed
2019-02-03 12:19:08.459 - Incoming push ...
2019-02-03 12:19:08.460 - <Title>
2019-02-03 12:19:08.461 - <Body>
2019-02-03 12:19:08.462 - Title did not match Push2Run's title filter - no further action will be taken
This can be fixed on my end by adding 1 s delay between the two pushes (500 ms seems to work intermittently).
Is there any way to avoid this bug?
bug when pushing two or more notes, one immediately after another
Re: bug when pushing two or more notes, one immediately after another
I just rechecked the code, and while there is logic to prevent reprocessing the same push if it comes in twice it's not time-based, rather based on a unique id number PushBullet assigns to each push.
Having that said, Push2Run is just processing what it picks up, and when you send two pushes within microseconds of one and another the second push, I suspect, isn't making it across to Push2Run via PushBullets API mechanism.
If I get some time to look at this I'll dive in deeper, but would likely require at least a couple hours of setup and testing only to prove that out; so for now, I'd suggest you please just add the second in your tasker routine as a workaround.
Thanks for pointing it out.
Having that said, Push2Run is just processing what it picks up, and when you send two pushes within microseconds of one and another the second push, I suspect, isn't making it across to Push2Run via PushBullets API mechanism.
If I get some time to look at this I'll dive in deeper, but would likely require at least a couple hours of setup and testing only to prove that out; so for now, I'd suggest you please just add the second in your tasker routine as a workaround.
Thanks for pointing it out.