No longer seeing pokemon caught in telegram

[javajohnHub]

Expected Behavior

A wild Weedle appeared! (CP: 254) (NCP: 0.57) (Potential 0.51) (A/D/S 12/10/1)

Great throw! Used Greatball, with chance 42.96 (118 left)

You caught a Weedle CP: 254 IV: 51

You now have 12 Weedle candy!

Actual Behavior

pokemonmon-bot, [Sep 21, 2016, 10:47 PM]:
A wild Weedle appeared! (CP: 254) (NCP: 0.57) (Potential 0.51) (A/D/S 12/10/1)

Great throw! Used Greatball, with chance 42.96 (118 left)

You now have 12 Weedle candy!

Your FULL config.json (remove your username, password, gmapkey and any other private info)

Output when issue occurred

A wild Weedle appeared! (CP: 254) (NCP: 0.57) (Potential 0.51) (A/D/S 12/10/1)

Great throw! Used Greatball, with chance 42.96 (118 left)

You now have 12 Weedle candy!

Steps to Reproduce

/sub all in telegram

Other Information

OS:
Mac

Branch:
dev

Git Commit:

Python Version:

Any other relevant files/configs (eg: path files)

[Gobberwart]

I'm getting notifications just fine, latest dev pull. What happens if you specifically subscribe to pokemon_caught instead of all?

[javajohnHub]

No output. I will try another fresh install but this one was a fresh dev install

[javajohnHub]

pokemonmon-bot, [Sep 21, 2016, 11:06 PM]:
Subscriptions updated.

Great Curveball throw! Used Pokeball, with chance 27.08 (2 left)

You now have 39 Clefairy candy!

fresh dev

[Gobberwart]

Running your branch? Or the plain dev branch? Oh and have you authenticated?

[Gobberwart]

If it's a clean install, telegram won't know who you are yet until you send the bot a message and/or login.

[Gobberwart]

Latest dev, latest telegram

[javajohnHub]

This is strange. Ill see if theres a telegram update.....and try dev again.

[Gobberwart]

Also... I know this might seem silly, but check your alert_catch config :)

[javajohnHub]

Ok so i slept on it.... another fresh install and the issue persists.

"alert_catch": {
"all": {"operator": "and", "cp": 0, "iv": 0.01}
}

Someone else on slack contacted me and said they are having the same issue.