@Bmorrow151
As @renojim indicated, this is entirely a P+ issue (their app update caused this behavior), so itll have to be solved the same way (app update) - make sure you report it to P+ CS (the more reports there are of a given issue the higher the priority the issue has on their fix list).
Until a new app update (presumably with a fix) is released we'll just have to use the workarounds...
